Actions
Bug #5081
closeddetect/iponly: rule parsing does not always apply netmask correctly
Affected Versions:
Effort:
Difficulty:
Label:
Needs backport to 5.0, Needs backport to 6.0
Description
If the ipaddress is not the address range start, it's not masked to turn it into that. So 1.2.3.4/24 is not stored as address 1.2.3.0 with netmask 24, but as 1.2.3.4 with netmask 24. This is then propagated into the radix tree, where it is used as an exact key in exact lookups, giving unexpected results.
Updated by Victor Julien almost 3 years ago
- Related to Bug #5066: detect/iponly: mixing netblocks can lead to FN/FP added
Updated by Victor Julien almost 3 years ago
- Related to Bug #5086: htp: server personality radix handling issue added
Updated by Victor Julien almost 3 years ago
- Related to Bug #5084: iprep: cidr support can set up radix incorrectly added
Updated by Victor Julien almost 3 years ago
- Related to Bug #5085: defrag: policy config can setup radix incorrectly added
Updated by Victor Julien almost 3 years ago
- Status changed from Assigned to Closed
Updated by Jeff Lucovsky almost 3 years ago
- Copied to Bug #5106: detect/iponly: rule parsing does not always apply netmask correctly added
Updated by Jeff Lucovsky almost 3 years ago
- Copied to Bug #5107: detect/iponly: rule parsing does not always apply netmask correctly added
Updated by Victor Julien over 2 years ago
- Related to Bug #5168: detect/iponly: non-cidr netmask settings can lead incorrect detection added
Actions