Skip to content
Fencer Intel
critical 9.8

CVE-2019-11834 json

cJSON before 1.7.11 allows out-of-bounds access, related to \x00 in a string literal.

published 7y ago modified 4mo ago also EUVD-2019-3497

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.5%
EPSS 2.5% chance of exploitation in 30 days, percentile 84%
public exploits
0
none known

Summary

cJSON before 1.7.11 allows out-of-bounds access, related to \x00 in a string literal.

Patch / fix

  • davegamble cjson 1.7.11
  • oracle timesten_in-memory_database 18.1.3.1.0
  • cjson Debian 14, Debian 13, Debian 12 1.7.10-1.1

debian advisories DEBIAN-CVE-2019-11834

  • libglvnd Azure Linux 3.0 1.7.0-2

azure linux advisories AZL-41111

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Is CVE-2019-11834 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

2.52% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/DaveGamble/cJSON/issues/337 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness

References

Sources

Fencer Intel 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.