Skip to main content
No exploitation reportedFix available

CVE-2019-20391

No exploitation reported by the sources we read.

  • Published2020-01-22
  • WeaknessCWE-119

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2020-01-2222:15CVE publishedNVD

Versions per branch

NVD
Cesnet libyang
BranchAffectedFixed in
0.14= 0.14no fix published
0.11= 0.11no fix published
0.12= 0.12no fix published
0.13= 0.13no fix published
0.15= 0.15no fix published
0.16= 0.16no fix published
1.0= 1.0no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • libyangUbuntu:20.04:LTSall versions · no fixed version listed
  • libyangRed Hat:enterprise_linux:8::appstreamall versions · fixed in 0:1.0.184-1.el8and 4 other packages
  • libyangDebian:14all versions · fixed in 1.0.176-1
  • libyangDebian:13all versions · fixed in 1.0.176-1
  • libyangDebian:10all versions · fixed in 0.16.105+really1.0-0+deb10u1
  • libyangAlmaLinux:8all versions · fixed in 1.0.184-1.el8

Vendor advisories

  • CVE-2019-20391 Red Hat Product Security26 products fixed

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

  • RHEA-2021:1906 Red Hat Product Security26 products fixed

    Red Hat Enhancement Advisory: libyang bug fix and enhancement update

Full record on NVD

Fix

  1. Vendor fix Red Hat Product Security RHEA-2021:1906 · 26 productsBefore applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Published
2020-01-22
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-57jg-xr2w-54jg

Frequently asked questions

What is CVE-2019-20391?

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.

Is CVE-2019-20391 actively exploited?

Active exploitation of CVE-2019-20391 has not been confirmed. Its EPSS score was 1.9% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2019-20391?

CVE-2019-20391 has a CVSS v3 base score of 6.5 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H.

Running libyang? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record