Project

General

Profile

Actions
Copy link

Bug #6846

closed

alerts: wrongly using tx id 0 when there is no tx

Added by Philippe Antoine 10 months ago. Updated 6 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Philippe Antoine
Target version:
8.0.0-beta1
Affected Versions:
Effort:
Difficulty:
Label:

Description

Found by oss-fuzz:
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=64345&q=label%3AProj-suricata&can=2

cf #6770

This leads to quadratic complexity arbitrary length value being logged an arbitrary number of times because we lof tx id 0 data when there is no data

Subtasks 2 (0 open — 2 closed)

Bug #6847: alerts: wrongly using tx id 0 when there is no tx (6.0.x backport)RejectedActions
Bug #6848: alerts: wrongly using tx id 0 when there is no tx (7.0.x backport)ClosedPhilippe AntoineActions

Related issues 3 (0 open — 3 closed)

Related to Suricata - Security #6900: http2: timeout logging headersClosedPhilippe AntoineActions
Related to Suricata - Bug #6973: detect: log relevant frames app-layer metdataClosedPhilippe AntoineActions
Related to Suricata - Task #7350: firewall usecase: log app-layer metadata for for catch-all drop rulesClosedOISF DevActions
Actions
Copy link

Also available in: Atom PDF