CVE-2019-6292 json
An issue was discovered in singledocparser.cpp in yaml-cpp (aka LibYaml-C++) 0.6.2.
published 7y ago modified 4mo ago also EUVD-2019-15857
- cvss
- 6.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.9%
- EPSS 1.9% chance of exploitation in 30 days, percentile 79%
- public exploits
- 0
- none known
Summary
An issue was discovered in singledocparser.cpp in yaml-cpp (aka LibYaml-C++) 0.6.2. Stack Exhaustion occurs in YAML::SingleDocParser, and there is a stack consumption problem caused by recursive stack frames: HandleCompactMap, HandleMap, HandleFlowSequence, HandleSequence, HandleNode. Remote attackers could leverage this vulnerability to cause a denial-of-service via a cpp file.
Patch / fix
- yaml-cpp Debian 14, Debian 13, Debian 12 0.6.3-1
debian advisories DEBIAN-CVE-2019-6292
- yaml-cpp SLE Real Time 15 SP2, SLE Module for Desktop Applications 15 SP3, SLE Module for Basesystem 15 SP3 +8 more 0.6.1-4.5.1
- yaml-cpp SLE Workstation Extension 12 SP5 0.5.3-3.6.3
suse advisories SUSE-SU-2023:1740-3SUSE-SU-2022:1073-2SUSE-SU-2022:1073-1SUSE-SU-2022:1072-1
- yaml-cpp openSUSE Leap 15.3 0.6.1-4.5.1
opensuse advisories openSUSE-SU-2022:1073-1
Is CVE-2019-6292 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 FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2019-6292 updated cvss 5.3
yaml-cpp: DoS in singledocparser.cpp
-
Red Hat OpenStack Platform 8 (Liberty) yaml-cpp Red Hat OpenStack Platform 9 (Mitaka) yaml-cpp Red Hat OpenStack Platform 10 (Newton) yaml-cpp Red Hat OpenStack Platform 13 (Queens) yaml-cppaffected: no fix available “Fix deferred”
-
Red Hat OpenStack Platform 14 (Rocky) yaml-cppaffected: no fix available
-
Red Hat Satellite 6 yaml-cpp Red Hat Software Collections rh-mongodb32-yaml-cpp, rh-mongodb34-yaml-cpp, rh-mongodb36-yaml-cppaffected: no fix planned “Will not fix”
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
1.88% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/jbeder/yaml-cpp/issues/657 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-674 Uncontrolled Recursion
References
-
github.com
/jbeder/yaml-cpp/issues/657
exploit, third-party-advisory
Sources
- CVE List CVE-2019-6292
- NVD CVE-2019-6292
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.