Actions
Bug #6303
closedconf: an empty child node is not checked for NULL
Affected Versions:
Effort:
Difficulty:
Label:
Description
Since 7.0.x, we have a change in the behavior of how children nodes in a node tree are parsed.
Earlier, if a child node was empty, it was set to an empty string and all the retriever fns like ConfGetChildValue
would check if the strlen of such a node item was 0 and take action accordingly.
However, since 7.0.x, if a child node was empty, it was set to NULL and the retriever fns would segfault on calls like strlen.
This was found while doing backports for https://redmine.openinfosecfoundation.org/issues/6228.
Updated by Shivani Bhardwaj over 1 year ago
- Related to Bug #6249: config: check and fix any empty config checks added
Updated by Shivani Bhardwaj over 1 year ago
- Related to Bug #6302: af-packet: fails to handle null bpf-filter added
Updated by Shivani Bhardwaj over 1 year ago
- Status changed from Assigned to In Review
In Review PR: https://github.com/OISF/suricata/pull/9473
Actions