Skip to content
Fencer Vulns
medium 6.5

CVE-2019-20391 json

An invalid memory access flaw is present in libyang before v1.0-r3 in the function resolve_feature_value() when an if-feature statement is…

published 2020-01-22 6 y ago modified 2026-06-17 4 mo ago also EUVD-2019-10941

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-r3 in the function resolve_feature_value() when an if-feature statement is used inside a bit. 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-20391

  • 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

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-2019-20391 updated cvss 5.5

libyang: invalid memory access in resolve_feature_value() when a if-feature is used inside a bit

  • Red Hat Enterprise Linux AppStream (v. 8) libyang 1.0.184-1.el8
    fixed: 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-08).

Exploits and checks

  • github.com https://github.com/CESNET/libyang/issues/772 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

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.