Project

General

Profile

Actions
Copy link

Bug #4287

closed

Mismatch between capture and outputs in rules leads to seg fault

Added by Jeff Lucovsky about 3 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
High
Assignee:
Jeff Lucovsky
Target version:
5.0.6
Affected Versions:
Effort:
Difficulty:
low
Label:

Description

Parsing bug: Given 2 or more outputs for one capture in the regex, there will be a segmentation fault.

For example,

alert tcp any any -> any any (msg:"get username in nntp"; \

content:"USER"; \
pcre: "/AUTHINFO USER\r\n/i, pkt:nntp_username, pkt:nntp_password";\
sid:2000020;\
gid:100;)

Files

Download all files
bug2.png (34.5 KB) bug2.png Shawn Yao, 01/12/2021 05:18 AM
bug1.png (41.2 KB) bug1.png Shawn Yao, 01/12/2021 05:18 AM

Related issues 1 (0 open — 1 closed)

Copied from Suricata - Bug #4261: Mismatch between capture and outputs in rules leads to seg faultClosedJeff LucovskyActions
Actions
Copy link
 #1

Updated by Jeff Lucovsky about 3 years ago

  • Copied from Bug #4261: Mismatch between capture and outputs in rules leads to seg fault added
Actions
Copy link
 #2

Updated by Jeff Lucovsky about 3 years ago

  • Status changed from New to In Review
Actions
Copy link
 #3

Updated by Jeff Lucovsky about 3 years ago

  • Status changed from In Review to Closed
Actions
Copy link

Also available in: Atom PDF