First published: Wed Jan 22 2020(Updated: )
A double-free is present in libyang before v1.0-r1 in the function yyparse() when an empty description is used. 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 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-20393 has a high severity due to the potential for crashes or remote code execution.
To fix CVE-2019-20393, upgrade libyang to version 1.0-r1 or later.
CVE-2019-20393 affects multiple versions of libyang, specifically prior to version 1.0-r1.
Yes, untrusted input yang files can exploit CVE-2019-20393 and lead to a double-free vulnerability.
CVE-2019-20393 is a double-free vulnerability occurring in the libyang library.