detect: don't run pkt sigs on ffr pkts#12264
Closed
inashivb wants to merge 1 commit intoOISF:main-7.0.xfrom
Closed
detect: don't run pkt sigs on ffr pkts#12264inashivb wants to merge 1 commit intoOISF:main-7.0.xfrom
inashivb wants to merge 1 commit intoOISF:main-7.0.xfrom
Conversation
Last packet from the TLS TCP session moves TCP state to CLOSED.
This flags the app-layer with APP_LAYER_PARSER_EOF_TS or
APP_LAYER_PARSER_EOF_TC depending on the direction of the final packet.
This flag will just have been set in a single direction.
This leads to the last packet updating the inspect id in that packets
direction.
At the end of the TLS session a pseudo packet is created, because:
- flow has ended
- inspected tx id == 0, for at least one direction
- total txs is 1
Then a packet rule matches:
```
alert tcp any any -> any 443 (flow: to_server; \
flowbits:isset,tls_error; \
sid:09901033; rev:1; \
msg:"Allow TLS error handling (outgoing packet)"; )
```
The `SIG_MASK_REQUIRE_REAL_PKT` is not preventing the match, as the
`flowbits` keyword doesn't set it.
To avoid this match. This patch skips signatures of the `SIG_TYPE_PKT`
for flow end packets.
Ticket: OISF#7318.
(cherry picked from commit 0e4faba)
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main-7.0.x #12264 +/- ##
==============================================
- Coverage 83.19% 83.18% -0.02%
==============================================
Files 922 922
Lines 260888 260890 +2
==============================================
- Hits 217048 217017 -31
- Misses 43840 43873 +33
Flags with carried forward coverage won't be shown. Click here to find out more. |
jufajardini
approved these changes
Dec 11, 2024
Contributor
jufajardini
left a comment
jufajardini
left a comment
There was a problem hiding this comment.
Consistent with work in master #12258
victorjulien
approved these changes
Dec 11, 2024
Closed
|
Information: QA ran without warnings. Pipeline 23796 |
jasonish
approved these changes
Dec 11, 2024
Closed
Closed
Member
|
part of #12268 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Link to ticket: https://redmine.openinfosecfoundation.org/issues/7368
SV_BRANCH=OISF/suricata-verify#2177