Skip to content

Denial-of-Service when binding invalid parameters in sqlite3

High severity GitHub Reviewed Published Apr 28, 2022 in TryGhost/node-sqlite3 • Updated Jan 30, 2023

Package

npm sqlite3 (npm)

Affected versions

>= 5.0.0, < 5.0.3

Patched versions

5.0.3

Description

Affected versions of sqlite3 will experience a fatal error when supplying a specific object in the parameter array. This error causes the application to crash and could not be caught. Users of sqlite3 v5.0.0, v5.0.1 and v5.0.2 are affected by this. This issue is fixed in v5.0.3. All users are recommended to upgrade to v5.0.3 or later. Ensure there is sufficient sanitization in the parent application to protect against invalid values being supplied to binding parameters as a workaround.

References

@daniellockyer daniellockyer published to TryGhost/node-sqlite3 Apr 28, 2022
Published to the GitHub Advisory Database Apr 28, 2022
Reviewed Apr 28, 2022
Published by the National Vulnerability Database May 1, 2022
Last updated Jan 30, 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
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
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:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.150%
(52nd percentile)

Weaknesses

CVE ID

CVE-2022-21227

GHSA ID

GHSA-9qrh-qjmc-5w2p

Source code

Credits

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