Critical severity · published Dec 6, 2019
CVE-2019-19333
In all versions of libyang before 1.0-r5, a stack-based buffer overflow was discovered in the way libyang parses YANG files with a leaf of type "bits"
9.8
CVSS
3.6%
EPSS
No
On KEV
Description
In all versions of libyang before 1.0-r5, a stack-based buffer overflow was discovered in the way libyang parses YANG files with a leaf of type "bits". An application that uses libyang to parse untrusted YANG files may be vulnerable to this flaw, which would allow an attacker to cause a denial of service or possibly gain code execution.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
High
Integrity
High
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)3.6% · higher than 90% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
EL
Enterprise Linux · Redhat
8.0 · source: NVD
LI
Libyang · Cesnet
0.11; 0.11; 0.12; 0.12; 0.13; 0.13; +9 more · source: NVD
Affected product
LI
Libyang
Cesnet
More from Libyang
9.8
CVE-2019-19334
In all versions of libyang before 1.0-r5, a stack-based buffer overflow was discovered in the way libyang parses YANG files with a leaf of type "identityref"
8.8
CVE-2019-20397
A double-free is present in libyang before v1.0-r1 in the function yyparse() when an organization field is not terminated
8.8
CVE-2019-20394
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
8.8
CVE-2019-20393
A double-free is present in libyang before v1.0-r1 in the function yyparse() when an empty description is used
7.5
CVE-2026-44673
libyang: lyb_read_string() integer overflow → heap buffer overflow