Security #7450
closed
tracking: signature can allocate arbitrary amount of memory
Added by Philippe Antoine 8 months ago.
Updated 5 days ago.
Disclosure Date:
12/09/2024
Description
cf usage of FUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION in util-thash.c and detect-base64-decode.c
- Label deleted (
Needs backport to 7.0)
- Blocked by Task #7461: suricata-verify: pass all tests added
- Blocked by deleted (Task #7461: suricata-verify: pass all tests)
- Related to Task #7461: suricata-verify: pass all tests added
- Related to Bug #7462: suricata-verify: pass when compiled with FUZZING_UNSAFE added
- Status changed from New to In Review
Some POC in Gitlab to discuss on
Need to keep this private until all known vectors are fixed and part of a public release.
- Subject changed from signature can allocate arbitrary amount of memory to tracking: signature can allocate arbitrary amount of memory
- Status changed from In Review to In Progress
- Assignee changed from Philippe Antoine to Victor Julien
- Severity changed from MODERATE to HIGH
- Status changed from In Progress to Closed
- Private changed from Yes to No
Also available in: Atom
PDF