THREATIST.IORead the docs 17 records
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.
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.
In function read_yin_leaf() in libyang <= v1.0.225, it doesn't check whether the value of retval->ext[r] is NULL.
In function lys_node_free() in libyang <= v1.0.225, it asserts that the value of node->module can't be NULL.
In function ext_get_plugin() in libyang <= v1.0.225, it doesn't check whether the value of revision is NULL.
A stack overflow in libyang <= v1.0.225 can cause a denial of service through function lyxml_parse_mem().
In function read_yin_container() in libyang <= v1.0.225, it doesn't check whether the value of retval->ext[r] is NULL.
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().
A double-free is present in libyang before v1.0-r1 in the function yyparse() when an organization field is not terminated.
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.
A stack consumption issue is present in libyang before v1.0-r1 due to the self-referential union type containing leafrefs.
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.
A double-free is present in libyang before v1.0-r1 in the function yyparse() when an empty description is used.
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.
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.
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".
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".