Project

General

Profile

Actions

Bug #2795

closed

asan leak: processing of empty pcap

Added by Peter Manev almost 6 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Target version:
Affected Versions:
Effort:
Difficulty:
low
Label:
Beginner, C, Outreachy

Description

LSAN_OPTIONS=suppressions=/home/pevma/Work/Suricata/suricomp/suricata/qa/lsan.suppress ASAN_SYMBOLIZER_PATH=/usr/lib/llvm-6.0/bin/llvm-symbolizer  /opt/suricata-asan/bin/suricata -c /opt/suricata-asan/etc/suricata/suricata.yaml -S /dev/null  -k none -r empty.pcap -l log/ 

[20799] 28/1/2019 -- 22:19:10 - (suricata.c:1085) <Notice> (LogVersion) -- This is Suricata version 4.1.0-dev (rev 8709a20d)
[20800] 28/1/2019 -- 22:19:10 - (source-pcap-file-helper.c:174) <Error> (InitPcapFile) -- [ERRCODE: SC_ERR_FOPEN(44)] - truncated dump file; tried to read 4 file header bytes, only got 0
[20800] 28/1/2019 -- 22:19:10 - (source-pcap-file.c:276) <Warning> (ReceivePcapFileThreadInit) -- [ERRCODE: SC_ERR_PCAP_DISPATCH(20)] - Failed to init pcap file empty.pcap, skipping
[20799] 28/1/2019 -- 22:19:11 - (tm-threads.c:2127) <Error> (TmThreadWaitOnThreadInit) -- [ERRCODE: SC_ERR_THREAD_INIT(49)] - thread "RX#01" failed to initialize: flags 0145
[20799] 28/1/2019 -- 22:19:11 - (suricata.c:3007) <Error> (main) -- [ERRCODE: SC_ERR_INITIALIZATION(45)] - Engine initialization failed, aborting...

=================================================================
==20799==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 2458 byte(s) in 1 object(s) allocated from:
    #0 0x4ce333 in __interceptor_malloc (/opt/suricata-asan/bin/suricata+0x4ce333)
    #1 0x8dc862 in PacketGetFromAlloc /home/pevma/Work/Suricata/suricomp/suricata/src/decode.c:141:17
    #2 0x182904d in PacketPoolInit /home/pevma/Work/Suricata/suricomp/suricata/src/tmqh-packetpool.c:390:21
    #3 0x183f258 in TmThreadsSlotPktAcqLoop /home/pevma/Work/Suricata/suricomp/suricata/src/tm-threads.c:292:5
    #4 0x7fa15a5ccfa2 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x7fa2)

Direct leak of 72 byte(s) in 1 object(s) allocated from:
    #0 0x4ce52a in calloc (/opt/suricata-asan/bin/suricata+0x4ce52a)
    #1 0x7fa1594feef9  (/usr/lib/x86_64-linux-gnu/libnss3.so+0x7eef9)

Indirect leak of 2514534 byte(s) in 1023 object(s) allocated from:
    #0 0x4ce333 in __interceptor_malloc (/opt/suricata-asan/bin/suricata+0x4ce333)
    #1 0x8dc862 in PacketGetFromAlloc /home/pevma/Work/Suricata/suricomp/suricata/src/decode.c:141:17
    #2 0x182904d in PacketPoolInit /home/pevma/Work/Suricata/suricomp/suricata/src/tmqh-packetpool.c:390:21
    #3 0x183f258 in TmThreadsSlotPktAcqLoop /home/pevma/Work/Suricata/suricomp/suricata/src/tm-threads.c:292:5
    #4 0x7fa15a5ccfa2 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x7fa2)

SUMMARY: AddressSanitizer: 2517064 byte(s) leaked in 1025 allocation(s).


Related issues 2 (0 open2 closed)

Related to Suricata - Bug #1694: unix-socket reading 0 size pcapClosedDanny BrowningActions
Related to Suricata - Bug #2776: pcap open - invalid interface capture length 524288, bigger than maximum of 262144ClosedActions
Actions

Also available in: Atom PDF