CVE-2019-20394: Double Free
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.
Other sources
A double-free is present in libyang up to version v1.0-r3 in 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.
Upstream issue: https://github.com/CESNET/libyang/issues/769
Upstream fix: https://github.com/CESNET/libyang/commit/6cc51b1757dfbb7cff92de074ada65e8523289a6
— Red Hat
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2019-20394?
CVE-2019-20394 has a high severity due to the potential for crashes or code execution from a double-free vulnerability.
How do I fix CVE-2019-20394?
To fix CVE-2019-20394, update libyang to version 1.0-r3 or higher.
What versions of libyang are affected by CVE-2019-20394?
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.
What is the cause of CVE-2019-20394?
CVE-2019-20394 is caused by a double-free vulnerability in the yyparse() function when processing type statements in notification statements.
Can applications using libyang be exploited due to CVE-2019-20394?
Yes, applications that use libyang to parse untrusted input yang files may be vulnerable to exploitation due to CVE-2019-20394.