CVE-2019-20393

CVE-2019-20393 is a high-severity vulnerability in Cesnet Libyang with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-415.

Key facts

Description

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.

Frequently asked questions

What is CVE-2019-20393?
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.
How severe is CVE-2019-20393?
CVE-2019-20393 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2019-20393 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (85th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-20393?
CVE-2019-20393 primarily affects Cesnet Libyang. In total, 11 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2019-20393?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2019-20393 published?
CVE-2019-20393 was published on 2020-01-22 and last updated on 2026-06-17.

References

Affected products (11)

More vulnerabilities in Cesnet Libyang

All CVEs affecting Cesnet Libyang →

Other CWE-415 (Double Free) vulnerabilities

Browse all CWE-415 (Double Free) vulnerabilities →