Project

General

Profile

Bug #3117

multiple valgrind reported warnings - 5.0.0-dev (9e126b210 2019-08-07)

Added by Peter Manev about 2 months ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assignee:
Target version:
Affected Versions:
Effort:
Difficulty:
Label:

Description

When running against a qa pcap I see he following valgrind reports.

==13958==  Uninitialised value was created by a heap allocation
==13958==    at 0x4C2FB0F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==13958==    by 0x19607D: PacketCopyDataOffset (decode.c:236)
==13958==    by 0x19607D: PacketCopyData (decode.c:262)
==13958==    by 0x2C7E33: PcapFileCallbackLoop (source-pcap-file-helper.c:82)
==13958==    by 0x62E6D18: ??? (in /usr/lib/x86_64-linux-gnu/libpcap.so.1.8.1)
==13958==    by 0x2C8397: PcapFileDispatch (source-pcap-file-helper.c:138)
==13958==    by 0x2C4FBD: ReceivePcapFileLoop (source-pcap-file.c:177)
==13958==    by 0x2E26B0: TmThreadsSlotPktAcqLoop (tm-threads.c:335)
==13958==    by 0x69386DA: start_thread (pthread_create.c:463)
==13958==    by 0x840188E: clone (clone.S:95)

==13958== Invalid read of size 1
==13958==    at 0x8325A57: ____strtoul_l_internal (strtol_l.c:432)
==13958==    by 0x2ED2DA: ByteExtractString (util-byte.c:212)
==13958==    by 0x1AC730: DetectBytetestDoMatch (detect-bytetest.c:152)
==13958==    by 0x1DBEA5: DetectEngineContentInspection (detect-engine-content-inspection.c:470)
==13958==    by 0x1BF0D5: DetectEngineInspectBufferGeneric (detect-engine.c:1603)
==13958==    by 0x1AEC38: DetectRunTxInspectRule (detect.c:1137)
==13958==    by 0x1AEC38: DetectRunTx (detect.c:1456)
==13958==    by 0x1AF388: DetectRun.part.15 (detect.c:136)
==13958==    by 0x1B0337: DetectRun (detect.c:1583)
==13958==    by 0x1B0337: DetectNoFlow (detect.c:1590)
==13958==    by 0x1B0337: Detect (detect.c:1650)
==13958==    by 0x253C20: FlowWorker (flow-worker.c:275)
==13958==    by 0x2E1431: TmThreadsSlotVarRun (tm-threads.c:130)
==13958==    by 0x2E2DD3: TmThreadsSlotVar (tm-threads.c:585)
==13958==    by 0x69386DA: start_thread (pthread_create.c:463)
==13958==  Address 0x2bf2d51b is 0 bytes after a block of size 27 alloc'd
==13958==    at 0x4C2FB0F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==13958==    by 0x4E443DC: bstr_alloc (bstr.c:44)
==13958==    by 0x4E447E1: bstr_dup_mem (bstr.c:259)
==13958==    by 0x4E4BDFE: htp_parse_request_header_generic (htp_request_generic.c:264)
==13958==    by 0x4E4BF0E: htp_process_request_header_generic (htp_request_generic.c:58)
==13958==    by 0x4E4B11C: htp_connp_REQ_HEADERS (htp_request.c:685)
==13958==    by 0x4E4B91B: htp_connp_req_data (htp_request.c:1007)
==13958==    by 0x171A9C: HTPHandleRequestData (app-layer-htp.c:787)
==13958==    by 0x17D0CD: AppLayerParserParse (app-layer-parser.c:1210)
==13958==    by 0x138AFC: TCPProtoDetect (app-layer.c:447)
==13958==    by 0x13934F: AppLayerHandleTCPData (app-layer.c:615)
==13958==    by 0x2D7232: ReassembleUpdateAppLayer (stream-tcp-reassemble.c:1066)
==13958==    by 0x2D7232: StreamTcpReassembleAppLayer (stream-tcp-reassemble.c:1123)

Details of the run attached.


Files

bug-additional-info.tar.xz (8.43 KB) bug-additional-info.tar.xz Peter Manev, 08/18/2019 02:43 PM

Related issues

Related to Bug #2960: valgrind gives 'Conditional jump or move depends on uninitialised value(s)'FeedbackActions

History

#1

Updated by Victor Julien about 2 months ago

  • Subject changed from multiple valgrind reported leaks - 5.0.0-dev (9e126b210 2019-08-07) to multiple valgrind reported warnings - 5.0.0-dev (9e126b210 2019-08-07)
#2

Updated by Victor Julien about 2 months ago

  • Description updated (diff)

Removed the duplicate warnings that are already tracked in #2960.

#3

Updated by Victor Julien about 2 months ago

  • Related to Bug #2960: valgrind gives 'Conditional jump or move depends on uninitialised value(s)' added
#4

Updated by Andreas Herz about 2 months ago

  • Assignee set to OISF Dev
  • Target version set to TBD

Also available in: Atom PDF