Code execution via parser-state double free
Published Jan 22, 2020 · Updated Aug 5, 2024
Double-free in libyang before 1.0-r3 allows attackers to crash a consuming application or execute code via a crafted YANG file. In yyparse, entering a notification after parsing a nested type statement leaves parser pointer s live, so later cleanup frees the same allocation twice. The condition is reachable only when a consuming application parses untrusted YANG input, producing heap corruption that crashes the process and can enable code execution.
Summary
What happened
Double-free in libyang before 1.0-r3 allows attackers to crash a consuming application or execute code via a crafted YANG file. In yyparse, entering a notification after parsing a nested type statement leaves parser pointer s live, so later cleanup frees the same allocation twice. The condition is reachable only when a consuming application parses untrusted YANG input, producing heap corruption that crashes the process and can enable code execution.
The record
- CVE
- CVE-2019-20394
- Published
- Jan 22, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-415, CWE-416, T1204.002, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 22, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Crafted YANG crash reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo