Project

General

Profile

Actions

Optimization #3591

open

fuzz: target with pcap, rules and yaml

Added by Victor Julien about 4 years ago. Updated 3 months ago.

Status:
In Progress
Priority:
High
Target version:
Effort:
Difficulty:
Label:

Description

Like fuzz_sigpcap, but with yaml also added as input. We see missing coverage due to code paths disabled in yaml.


Related issues 2 (1 open1 closed)

Related to Suricata - Optimization #4125: Ideal integration into oss-fuzzIn ProgressPhilippe AntoineActions
Related to Suricata - Security #6279: Crash in SMTP parser during parsing of emailClosedPhilippe AntoineActions
Actions #1

Updated by Victor Julien almost 4 years ago

  • Priority changed from Normal to Low
Actions #2

Updated by Victor Julien almost 4 years ago

  • Assignee set to Philippe Antoine
Actions #3

Updated by Philippe Antoine almost 4 years ago

That was the original intent of the fuzz_sigpcap target.
But I think you told me that configuration could be only loaded once at startup...
Should I dig it ?

Actions #4

Updated by Philippe Antoine about 3 years ago

Actions #5

Updated by Philippe Antoine 11 months ago

  • Target version set to QA
Actions #6

Updated by Philippe Antoine 8 months ago

  • Related to Security #6279: Crash in SMTP parser during parsing of email added
Actions #7

Updated by Philippe Antoine 8 months ago

  • Priority changed from Low to High
Actions #8

Updated by Philippe Antoine 8 months ago

This requires the possibility to modify and apply some config values. (which we may want to reuse or not with the socket command for instance)

For example SMTPConfigure is only called at startup and we cannot change smtp_config.mime_config.body_md5 after it

Actions #9

Updated by Philippe Antoine 7 months ago

  • Status changed from New to In Progress
Actions #10

Updated by Philippe Antoine 3 months ago

Actions

Also available in: Atom PDF