Skip to content

sqlite vulnerable to code execution due to Object coercion

High severity GitHub Reviewed Published Mar 13, 2023 in TryGhost/node-sqlite3 • Updated Mar 22, 2023

Package

npm sqlite3 (npm)

Affected versions

>= 5.0.0, < 5.1.5

Patched versions

5.1.5

Description

Impact

Due to the underlying implementation of .ToString(), it's possible to execute arbitrary JavaScript, or to achieve a denial-of-service, if a binding parameter is a crafted Object.

Users of sqlite3 v5.0.0 - v5.1.4 are affected by this.

Patches

Fixed in v5.1.5. All users are recommended to upgrade to v5.1.5 or later.

Workarounds

  • Ensure there is sufficient sanitization in the parent application to protect against invalid values being supplied to binding parameters.

References

For more information

If you have any questions or comments about this advisory:

Credits: Dave McDaniel of Cisco Talos

References

@daniellockyer daniellockyer published to TryGhost/node-sqlite3 Mar 13, 2023
Published to the GitHub Advisory Database Mar 13, 2023
Reviewed Mar 13, 2023
Published by the National Vulnerability Database Mar 16, 2023
Last updated Mar 22, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.307%
(71st percentile)

Weaknesses

CVE ID

CVE-2022-43441

GHSA ID

GHSA-jqv5-7xpx-qj74

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.