Skip to content

detect/http: fix progress for headers keywords (backport7)#12097

Closed
catenacyber wants to merge 1 commit intoOISF:main-7.0.xfrom
catenacyber:detect-http-header-progress-7326-backport7
Closed

detect/http: fix progress for headers keywords (backport7)#12097
catenacyber wants to merge 1 commit intoOISF:main-7.0.xfrom
catenacyber:detect-http-header-progress-7326-backport7

Conversation

@catenacyber
Copy link
Contributor

Link to ticket: https://redmine.openinfosecfoundation.org/issues/
https://redmine.openinfosecfoundation.org/issues/7327

Describe changes:

SV_BRANCH=OISF/suricata-verify#2122

Ticket: 7326

Having a lower progress than one where we actually can get
occurences of the multibuffer made prefilter
bail out too early, not having found a buffer in the multi-buffer
that matiched the prefilter.

For example, we registered http_request_header with progress 0
instad of progress HTP_REQUEST_HEADERS==2, and if the first
packet had only the request line, we would consider
that signatures with http_request_header as prefilter/fast_pattern
could not match for this transaction, even if they in fact
could have a later packet with matching headers.

Hence, we got false negatives, if http.request_header or
http.response_header was used as fast pattern, and if the request
or response came in multiple packets, and the first of these packets
did not have enough data (like only http request line),
and the next packets did have the matching data.

(cherry picked from commit cca59cd)
@catenacyber
Copy link
Contributor Author

do we need to backport some CI netmap caching commit ?

@suricata-qa
Copy link

Information: QA ran without warnings.

Pipeline 23292

@victorjulien
Copy link
Member

Merged in #12106, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants