Bug #1426: Files prematurely truncated by detection engine even though force-md5 is enabled - Suricata - Open Information Security Foundation

Actions

Copy link

Bug #1426

closed

Files prematurely truncated by detection engine even though force-md5 is enabled

Added by Ray Ruvinskiy almost 10 years ago. Updated almost 10 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Victor Julien

Target version:

2.1beta4

Affected Versions:

Effort:

Difficulty:

Label:

Description

I'm using suricata 2.0, running with force-md5 and the Emerging Threats ruleset. I've noticed behaviour that I can't understand. Under some circumstances, files end up being prematurely truncated, and therefore the MD5 hash does not encompass as much of the file as I would like.

The truncation happens because FileDisableStoringForTransaction is called, specifically with the following stack trace:

#0  FileCloseFilePtr (ff=0x7f02ecec05b0, data=0x0, data_len=0, flags=33 '!') at util-file.c:560
#1  0x0000000000567535 in FileDisableStoringForTransaction (f=&lt;optimized out&gt;, direction=&lt;optimized out&gt;, tx_id=0) at util-file.c:822
#2  0x00000000004af7ea in DeStateDetectStartDetection (tv=0xae87890, de_ctx=0x3c4ac30, det_ctx=0x7f02ec001c50, s=&lt;optimized out&gt;, p=0x378c6e0, f=0x39665b0, flags=8 '\b', alstate=0x7f02ecec2030,
    alproto=1, alversion=2) at detect-engine-state.c:441
#3  0x000000000047dfb7 in SigMatchSignatures (th_v=0xae87890, de_ctx=0x3c4ac30, det_ctx=0x7f02ec001c50, p=0x378c6e0) at detect.c:1513
#4  0x000000000047e1f5 in Detect (data=&lt;optimized out&gt;, p=&lt;optimized out&gt;, tv=&lt;optimized out&gt;, pq=&lt;optimized out&gt;, postpq=&lt;optimized out&gt;) at detect.c:1711
#5  Detect (tv=&lt;optimized out&gt;, p=&lt;optimized out&gt;, data=&lt;optimized out&gt;, pq=&lt;optimized out&gt;, postpq=&lt;optimized out&gt;) at detect.c:1683
#6  0x000000000054b328 in TmThreadsSlotVarRun (tv=0xae87890, p=0x378c6e0, slot=<

This happens after FileOpenFile but before FileAppendData, so anything written out with FileAppendData is excluded.

I'm struggling wrapping my head around the detection engine code sufficiently to understand what's going on. I'd appreciate assistance in debugging this. Thanks!