Bug #1101: Segmentation in AppLayerParserGetTxCnt - Suricata - Open Information Security Foundation

Actions

Copy link

Bug #1101

closed

Segmentation in AppLayerParserGetTxCnt

Added by Duarte Silva almost 11 years ago. Updated over 10 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Victor Julien

Target version:

2.0.1rc1

Affected Versions:

Effort:

Difficulty:

Label:

Description

Detected a segmentation fault in AppLayerParserGetTxCnt. One interesting fact, is the CPU usage on the flow manager thread, don't know if it could have impact or not. I can reproduce it consistently by replaying a packet dump (replaying at ~400Mbps).

Suricata has been compiled without optimizations.

Files

Download all files

thread-dump.txt (18.3 KB) thread-dump.txt	Back trace for the various threads	Duarte Silva, 02/07/2014 10:43 AM
buildinfo.txt (2.11 KB) buildinfo.txt	Suricata build information	Duarte Silva, 02/07/2014 10:44 AM
top.txt (702 Bytes) top.txt	CPU usage while processing replayed packed capture	Duarte Silva, 02/07/2014 10:44 AM
flow-dump-thread-2.txt (7.63 KB) flow-dump-thread-2.txt	Thread were the segmentation fault happened	Duarte Silva, 02/07/2014 12:10 PM
flow-dump-thread-4.txt (7.29 KB) flow-dump-thread-4.txt	Thread that is processing the same flow	Duarte Silva, 02/07/2014 12:10 PM
thread-dump-2.txt (18.2 KB) thread-dump-2.txt	Second back trace for all threads	Duarte Silva, 02/07/2014 12:10 PM
suricata.yaml (49 KB) suricata.yaml	Current Suricata configuration	Duarte Silva, 02/07/2014 12:10 PM