CVE-2019-20392 json
An invalid memory access flaw is present in libyang before v1.0-r1 in the function resolve_feature_value() when an if-feature statement is…
published 6y ago modified 4mo ago also EUVD-2019-10942
- cvss
- 6.5
- version 3.1, 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 invalid memory access flaw is present in libyang before v1.0-r1 in the function resolve_feature_value() when an if-feature statement is used inside a list key node, and the feature used is not defined. Applications that use libyang to parse untrusted input yang files may crash.
Patch / fix
- libyang Debian 14, Debian 13 1.0.176-1
debian advisories DEBIAN-CVE-2019-20392
- libyang RHEL 8 1.0.184-1.el8
red hat advisories RHEA-2021:1906
- libyang AlmaLinux 8 1.0.184-1.el8
almalinux advisories ALEA-2021:1906
Is CVE-2019-20392 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-20392 updated cvss 5.5
libyang: invalid memory access when if-feature statement is used inside a list key node
-
Red Hat Enterprise Linux AppStream (v. 8) libyang 1.0.184-1.el8fixed: vendor fix RHEA-2021:1906
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/CESNET/libyang/issues/723 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/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-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
github.com
/CESNET/libyang/commit/32fb4993bc8bb49e93e84016af3c10ea53964be5
patch, third-party-advisory
-
bugzilla.redhat.com
/show_bug.cgi?id=1793922
issue-tracking, patch, third-party-advisory
-
github.com
/CESNET/libyang/issues/723
exploit, third-party-advisory
-
github.com
/CESNET/libyang/compare/v0.16-r3...v1.0-r1
third-party-advisory
-
lists.debian.org
/debian-lts-announce/2023/09/msg00019.html
mailing-list
Sources
- CVE List CVE-2019-20392
- NVD CVE-2019-20392
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.