CVE-2019-20397: A double-free is present in libyang before v1.0-r1 in the function yyparse() when an organization field is not terminated.
Noroxi assessment
Priority: Monitor (action score 36/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.5% (FIRST EPSS); higher than 85% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: libyang (AlmaLinux:8) 1.0.184-1.el8; libyang (Debian:10) 0.16.105+really1.0-0+deb10u1; libyang (Debian:13) 1.0.176-1.
Low priority for now. Upgrade to libyang (AlmaLinux:8) 1.0.184-1.el8; libyang (Debian:10) 0.16.105+really1.0-0+deb10u1; libyang (Debian:13) 1.0.176-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A double-free is present in libyang before v1.0-r1 in the function yyparse() when an organization field is not terminated. Applications that use libyang to parse untrusted input yang files may be vulnerable to this flaw, which would cause a crash or potentially code execution.
- Published
- Jan 22, 2020
- Updated
- Jun 16, 2026
- EPSS
- 2.5% · 85th percentile
- CWE
- CWE-415
Report tools
Action score
36
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.5%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| cesnet | libyang | cpe:2.3:a:cesnet:libyang |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- cesnet libyang0.11
- cesnet libyang0.12
- cesnet libyang0.13
- cesnet libyang0.14
- cesnet libyang0.15
- cesnet libyang0.16
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | libyang | before 1.0.184-1.el8 | 1.0.184-1.el8 |
| Debian:10 | libyang | before 0.16.105+really1.0-0+deb10u1 | 0.16.105+really1.0-0+deb10u1 |
| Debian:13 | libyang | before 1.0.176-1 | 1.0.176-1 |
| Red Hat:enterprise_linux:8::appstream | libyang | before 0:1.0.184-1.el8 | 0:1.0.184-1.el8 |
| Red Hat:enterprise_linux:8::appstream | libyang-cpp-debuginfo | before 0:1.0.184-1.el8 | 0:1.0.184-1.el8 |
| Red Hat:enterprise_linux:8::appstream | libyang-debuginfo | before 0:1.0.184-1.el8 | 0:1.0.184-1.el8 |
| Red Hat:enterprise_linux:8::appstream | libyang-debugsource | before 0:1.0.184-1.el8 | 0:1.0.184-1.el8 |
| Red Hat:enterprise_linux:8::appstream | python3-libyang-debuginfo | before 0:1.0.184-1.el8 | 0:1.0.184-1.el8 |
Same product
cesnet: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-19334In all versions of libyang before 1.0-r5, a stack-based buffer overflow was discovered in the way libyang parses YANG files with a leaf of…40Plan
- CVE-2019-19333In all versions of libyang before 1.0-r5, a stack-based buffer overflow was discovered in the way libyang parses YANG files with a leaf of…40Plan
- CVE-2019-20394A double-free is present in libyang before v1.0-r3 in the function yyparse() when a type statement in used in a notification statement.36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2019-20395Jan 22, 2020 · A stack consumption issue is present in libyang before v1.0-r1 due to the self-referential union type containing leafrefs.27Monitor
- ← EarlierCVE-2019-20396Jan 22, 2020 · A segmentation fault is present in yyparse in libyang before v1.0-r1 due to a malformed pattern statement value during lys_parse_path…27Monitor
- Later →CVE-2019-20398Jan 22, 2020 · A NULL pointer dereference is present in libyang before v1.0-r3 in the function lys_extension_instances_free() due to a copy of unresolved…27Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:libyang | 1.0.184-1.el8 · AlmaLinux:8 | Package registry (OSV) |
| debian:libyang | 1.0.176-1 · Debian:13 | Package registry (OSV) |
| red hat:libyang | 0:1.0.184-1.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:libyang-cpp-debuginfo | 0:1.0.184-1.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:libyang-debuginfo | 0:1.0.184-1.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:libyang-debugsource | 0:1.0.184-1.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:python3-libyang-debuginfo | 0:1.0.184-1.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-415 · Double FreeCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.