First published: Wed Jan 22 2020(Updated: )
A double-free is present in libyang before v1.0-r3 in the function yyparse() when a type statement in used in a notification statement. 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.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/libyang | <1.0 | 1.0 |
CESNET libyang | =0.11-r1 | |
CESNET libyang | =0.11-r2 | |
CESNET libyang | =0.12-r1 | |
CESNET libyang | =0.12-r2 | |
CESNET libyang | =0.13-r1 | |
CESNET libyang | =0.13-r2 | |
CESNET libyang | =0.14-r1 | |
CESNET libyang | =0.15-r1 | |
CESNET libyang | =0.16-r1 | |
CESNET libyang | =0.16-r2 | |
CESNET libyang | =0.16-r3 | |
CESNET libyang | =1.0-r1 | |
CESNET libyang | =1.0-r2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-20394 has a high severity due to the potential for crashes or code execution from a double-free vulnerability.
To fix CVE-2019-20394, update libyang to version 1.0-r3 or higher.
CVE-2019-20394 affects libyang versions before 1.0-r3, including specific versions 0.11-r1, 0.11-r2, 0.12-r1, 0.12-r2, 0.13-r1, 0.13-r2, 0.14-r1, 0.15-r1, 0.16-r1, 0.16-r2, and 0.16-r3.
CVE-2019-20394 is caused by a double-free vulnerability in the yyparse() function when processing type statements in notification statements.
Yes, applications that use libyang to parse untrusted input yang files may be vulnerable to exploitation due to CVE-2019-20394.