Actions
Bug #8763
closed
PA
PA
frame: incorrect debug assertion triggered
Bug #8763:
frame: incorrect debug assertion triggered
Added by Philippe Antoine 3 months ago. Updated about 1 month ago.
Affected Versions:
Effort:
Difficulty:
Label:
Files
| frame.pcap (389 Bytes) frame.pcap | Philippe Antoine, 07/23/2026 03:35 PM |
PA Updated by Philippe Antoine 3 months ago Actions #1
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 3 months ago Actions #2
- File frame.pcap frame.pcap added
With to+sha1 instead of to+md5 I have 14 instead of 10
PA Updated by Philippe Antoine 3 months ago Actions #3
- Status changed from New to In Review
Gitlab MR, I think this can be made public
JI Updated by Jason Ish about 2 months ago Actions #4
- Label Needs backport to 8.0 added
OT Updated by OISF Ticketbot about 2 months ago Actions #5
- Subtask #8912 added
OT Updated by OISF Ticketbot about 2 months ago Actions #6
- Label deleted (
Needs backport to 8.0)
PA Updated by Philippe Antoine about 2 months ago Actions #7
- Tracker changed from Security to Bug
This was not a security problem, just a debug assertion that was wrong
PA Updated by Philippe Antoine about 2 months ago Actions #8
JI Updated by Jason Ish about 2 months ago Actions #9
- Private changed from Yes to No
PA Updated by Philippe Antoine about 2 months ago Actions #10
- Status changed from In Review to Resolved
PA Updated by Philippe Antoine about 2 months ago Actions #11
- Status changed from Resolved to Closed
SB Updated by Shivani Bhardwaj about 1 month ago Actions #12
- 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