Actions
Bug #8763
closed
PA
PA
frame: incorrect debug assertion triggered
Bug #8763:
frame: incorrect debug assertion triggered
Affected Versions:
Effort:
Difficulty:
Label:
Files
PA Updated by Philippe Antoine about 2 months ago
Not sure it is a security issue, but investigating first here
Reproducer is with rules
alert ip any any -> any any (frame:http1.response; to_md5;pcre://;sid:3;)
suricata -c fuzz.yaml -S fuzz.rules -r frame.pcap
finds
fsd->frame->len=5 data_len=10
PA Updated by Philippe Antoine about 2 months ago
- File frame.pcap frame.pcap added
With to+sha1 instead of to+md5 I have 14 instead of 10
PA Updated by Philippe Antoine about 2 months ago
- Status changed from New to In Review
Gitlab MR, I think this can be made public
JI Updated by Jason Ish about 1 month ago
- Label Needs backport to 8.0 added
OT Updated by OISF Ticketbot about 1 month ago
- Subtask #8912 added
OT Updated by OISF Ticketbot about 1 month ago
- Label deleted (
Needs backport to 8.0)
PA Updated by Philippe Antoine 26 days ago
- Tracker changed from Security to Bug
This was not a security problem, just a debug assertion that was wrong
PA Updated by Philippe Antoine 26 days ago
PA Updated by Philippe Antoine 25 days ago
- Status changed from In Review to Resolved
PA Updated by Philippe Antoine 24 days ago
- Status changed from Resolved to Closed
SB Updated by Shivani Bhardwaj 11 days ago
- Subject changed from frame: assertion triggered DEBUG_VALIDATE_BUG_ON(fsd->frame->len > 0 && (int64_t)data_len > fsd->frame->len); to frame: incorrect debug assertion triggered
Actions