Skip to content
Fencer Vulns
high 7.5

CVE-2022-21227 json

Denial of Service (DoS)

published 2022-04-28 4 y ago modified 2026-06-17 4 mo ago also GHSA-9qrh-qjmc-5w2p , EUVD-2022-1694

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
2.2%
EPSS 2.2% chance of exploitation in 30 days, percentile 82%
public exploits
0
none known

Summary

The package sqlite3 before 5.0.3 are vulnerable to Denial of Service (DoS) which will invoke the toString function of the passed parameter. If passed an invalid Function object it will throw and crash the V8 engine.

Patch / fix

  • npm sqlite3 5.0.3
  • n/a sqlite3 5.0.3
  • node-sqlite3 Debian 14, Debian 13, Debian 12 5.0.6+ds1-1

debian advisories DEBIAN-CVE-2022-21227

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-21227 updated cvss 7.5

sqlite3: Denial of Service (DoS) in sqlite3

  • Red Hat Enterprise Linux 6 lemon, sqlite, sqlite-tcl Red Hat Enterprise Linux 7 lemon, sqlite, sqlite-tcl Red Hat Enterprise Linux 8 lemon, sqlite, sqlite-libs Red Hat Enterprise Linux 9 sqlite, sqlite-libs
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.21% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
npm sqlite3
>=5.0.0, <5.0.3
5.0.3

Affected products

  • n/a sqlite3

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.