This page lists publicly disclosed CVE vulnerabilities affecting cesnet libyang (linked via NVD CPE). Each row includes severity scores, summaries, and publication dates to help identify and analyze security issues.
| CVE | Summary | Source | Max CVSS | EPSS % | Published | Updated |
|---|---|---|---|---|---|---|
| CVE-2023-26917 | libyang from v2.0.164 to v2.1.30 was discovered to contain a NULL pointer dereference via the function lysp_stmt_validate_value at lys_parse_mem.c. | [email protected] | 7.5 | 0.89% | 2023-04-11 | 2025-02-11 |
| CVE-2023-26916 | libyang from v2.0.164 to v2.1.30 was discovered to contain a NULL pointer dereference via the function lys_parse_mem at lys_parse_mem.c. | [email protected] | 5.3 | 0.99% | 2023-04-03 | 2025-02-18 |
| CVE-2021-28906 | In function read_yin_leaf() in libyang <= v1.0.225, it doesn't check whether the value of retval->ext[r] is NULL. In some cases, it can be NULL, which leads to the operation of retval->ext[r]->flags that results in a crash. | [email protected] | 7.5 | 1.57% | 2021-05-20 | 2024-11-21 |
| CVE-2021-28905 | In function lys_node_free() in libyang <= v1.0.225, it asserts that the value of node->module can't be NULL. But in some cases, node->module can be null, which triggers a reachable assertion (CWE-617). | [email protected] | 7.5 | 1.42% | 2021-05-20 | 2024-11-21 |
| CVE-2021-28904 | In function ext_get_plugin() in libyang <= v1.0.225, it doesn't check whether the value of revision is NULL. If revision is NULL, the operation of strcmp(revision, ext_plugins[u].revision) will lead to a crash. | [email protected] | 7.5 | 1.41% | 2021-05-20 | 2024-11-21 |
| CVE-2021-28903 | A stack overflow in libyang <= v1.0.225 can cause a denial of service through function lyxml_parse_mem(). lyxml_parse_elem() function will be called recursively, which will consume stack space and lead to crash. | [email protected] | 7.5 | 2.43% | 2021-05-20 | 2024-11-21 |
| CVE-2021-28902 | In function read_yin_container() in libyang <= v1.0.225, it doesn't check whether the value of retval->ext[r] is NULL. In some cases, it can be NULL, which leads to the operation of retval->ext[r]->flags that results in a crash. | [email protected] | 7.5 | 1.55% | 2021-05-20 | 2024-11-21 |
| CVE-2019-20398 | A NULL pointer dereference is present in libyang before v1.0-r3 in the function lys_extension_instances_free() due to a copy of unresolved extensions in lys_restr_dup(). Applications that use libyang to parse untrusted input yang files may crash. | [email protected] | 6.5 | 1.82% | 2020-01-22 | 2024-11-21 |
| 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. 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. | [email protected] | 8.8 | 2.49% | 2020-01-22 | 2024-11-21 |
| CVE-2019-20396 | A segmentation fault is present in yyparse in libyang before v1.0-r1 due to a malformed pattern statement value during lys_parse_path parsing. | [email protected] | 6.5 | 1.91% | 2020-01-22 | 2024-11-21 |
| CVE-2019-20395 | A stack consumption issue is present in libyang before v1.0-r1 due to the self-referential union type containing leafrefs. Applications that use libyang to parse untrusted input yang files may crash. | [email protected] | 6.5 | 1.84% | 2020-01-22 | 2024-11-21 |
| 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. 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. | [email protected] | 8.8 | 2.79% | 2020-01-22 | 2024-11-21 |
| 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. | [email protected] | 8.8 | 2.79% | 2020-01-22 | 2024-11-21 |
| CVE-2019-20392 | An invalid memory access flaw is present in libyang before v1.0-r1 in the function resolve_feature_value() when an if-feature statement is used inside a list key node, and the feature used is not defined. Applications that use libyang to parse untrusted input yang files may crash. | [email protected] | 6.5 | 1.86% | 2020-01-22 | 2024-11-21 |
| CVE-2019-20391 | An invalid memory access flaw is present in libyang before v1.0-r3 in the function resolve_feature_value() when an if-feature statement is used inside a bit. Applications that use libyang to parse untrusted input yang files may crash. | [email protected] | 6.5 | 1.86% | 2020-01-22 | 2024-11-21 |
| 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". 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. | [email protected] | 9.8 | 3.98% | 2019-12-06 | 2024-11-21 |
| 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". 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. | [email protected] | 9.8 | 3.75% | 2019-12-06 | 2024-11-21 |