Actions
Bug #3726
closedSegmentation fault on rule reload when using libmagic
Affected Versions:
Effort:
medium
Difficulty:
medium
Label:
Needs backport to 4.1, Needs backport to 5.0
Description
If libmagic is enabled and there are signature using libmagic, rule reloading causes a segmentation fault on the next file matching the rule.
This is due to an improper reinitialization of the thread contexts.
In attachment there are a sample stack trace and a sample rule file.
Files
Actions
#1
Updated by Angelo Mirabella over 4 years ago
- File suricata_testcase.zip suricata_testcase.zip added
- File build-info.txt build-info.txt added
Uploading the build-info and a zip with a pcap and rules to reproduce the bug.
The password for the zip is: password
Steps to reproduce the bug:
- Start suricata in PCAP mode
- Send signal SIGUSR2 to reload the signatures
- Replay the pcap on the sniffing interface
This should lead to the segmentation fault
Updated by Victor Julien about 4 years ago
- Target version changed from 5.0.4 to 6.0.1
- Label Needs backport to 4.1, Needs backport to 5.0 added
Updated by Jeff Lucovsky about 4 years ago
- Copied to Bug #4133: Segmentation fault on rule reload when using libmagic added
Updated by Jeff Lucovsky about 4 years ago
- Copied to Bug #4134: Segmentation fault on rule reload when using libmagic added
Updated by Victor Julien about 4 years ago
- Status changed from New to Closed
Actions