Actions
Bug #5106
closeddetect/iponly: rule parsing does not always apply netmask correctly
Affected Versions:
Effort:
Difficulty:
Label:
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 Jeff Lucovsky almost 3 years ago
- Copied from Bug #5081: detect/iponly: rule parsing does not always apply netmask correctly added
Updated by Shivani Bhardwaj over 2 years ago
- Status changed from Assigned to In Review
- Assignee changed from Shivani Bhardwaj to Victor Julien
Updated by Shivani Bhardwaj over 2 years ago
- Status changed from In Review to Closed
Actions