-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
smb: New keyword smb.cmd v7 #7372
Closed
Closed
Conversation
This file contains 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
zer1t0
requested review from
victorjulien,
jasonish,
norg and
a team
as code owners
May 4, 2022 08:26
cppcheck: src/util-memcmp.h:281:18: warning: Identical condition 'len-offset<16', second condition is always false [identicalConditionAfterEarlyExit] if (diff < 16) { ^ src/util-memcmp.h:280:24: note: 'diff' is assigned value 'len-offset' here. int diff = len - offset; ^ src/util-memcmp.h:269:33: note: If condition 'len-offset<16' is true, the function will return/exit if (likely(len - offset < 16)) { ^ src/util-memcmp.h:281:18: note: Testing identical condition 'len-offset<16' if (diff < 16) { ^ src/util-memcmp.h:344:18: warning: Identical condition 'len-offset<16', second condition is always false [identicalConditionAfterEarlyExit] if (diff < 16) { ^ src/util-memcmp.h:343:24: note: 'diff' is assigned value 'len-offset' here. int diff = len - offset; ^ src/util-memcmp.h:318:33: note: If condition 'len-offset<16' is true, the function will return/exit if (likely(len - offset < 16)) { ^ src/util-memcmp.h:344:18: note: Testing identical condition 'len-offset<16' if (diff < 16) { ^ src/util-memcmp.h:171:18: warning: Identical condition 'len-offset<16', second condition is always false [identicalConditionAfterEarlyExit] if (diff < 16) { ^ src/util-memcmp.h:170:24: note: 'diff' is assigned value 'len-offset' here. int diff = len - offset; ^ src/util-memcmp.h:159:33: note: If condition 'len-offset<16' is true, the function will return/exit if (likely(len - offset < 16)) { ^ src/util-memcmp.h:171:18: note: Testing identical condition 'len-offset<16' if (diff < 16) { ^ src/util-memcmp.h:233:18: warning: Identical condition 'len-offset<16', second condition is always false [identicalConditionAfterEarlyExit] if (diff < 16) { ^ src/util-memcmp.h:232:24: note: 'diff' is assigned value 'len-offset' here. int diff = len - offset; ^ src/util-memcmp.h:208:33: note: If condition 'len-offset<16' is true, the function will return/exit if (likely(len - offset < 16)) { ^ src/util-memcmp.h:233:18: note: Testing identical condition 'len-offset<16' if (diff < 16) { ^
Since GCC 12 the memcmp code using `_mm_blendv_epi8` failed to work. Inspection of the disassembled objects suggests that it simply omits the instruction on systems that are not AVX512 capable. On AVX512 it does replace it with VPCMPB logic that appears to work. Luckily our use of blend is actually uncessary. A simple AND is sufficient. Bug: OISF#5312.
Reduce scope where possible. Suggested by cppcheck.
src/detect-engine-state.c:127:91: style: Suspicious calculation. Please use parentheses to clarify the code. The code ''a&b?c:d'' should be written as either ''(a&b)?c:d'' or ''a&(b?c:d)''. [clarifyCalculation] DetectEngineStateDirection *dir_state = &state->dir_state[direction & STREAM_TOSERVER ? 0 : 1]; ^ src/detect-engine-state.c:194:53: style: Suspicious calculation. Please use parentheses to clarify the code. The code ''a&b?c:d'' should be written as either ''(a&b)?c:d'' or ''a&(b?c:d)''. [clarifyCalculation] de_state->dir_state[direction & STREAM_TOSERVER ? 0 : 1].filestore_cnt += file_no_match; ^ src/detect-engine-state.c:201:57: style: Suspicious calculation. Please use parentheses to clarify the code. The code ''a&b?c:d'' should be written as either ''(a&b)?c:d'' or ''a&(b?c:d)''. [clarifyCalculation] if (de_state->dir_state[direction & STREAM_TOSERVER ? 0 : 1].filestore_cnt == sgh->filestore_cnt) ^
src/app-layer-ftp.c:945:49: style: Parameter 'ftp_state' can be declared with const [constParameter] static FTPTransaction *FTPGetOldestTx(FtpState *ftp_state, FTPTransaction *starttx) ^
regit
added a commit
to regit/suricata
that referenced
this pull request
Dec 15, 2024
This patch introduces a new keyword datajson that is similar to dataset with a twist. Where dataset allows match from sets, datajson allows the same but also adds JSON data to the alert event. This data is comint from the set definition it self. For example, an ipv4 set will look like: 10.16.1.11,{"test": "success","context":3} The syntax is value and json data separated by a comma. The syntax of the keyword is the following: datajson:isset,src_ip,type ip,load src.lst,key src_ip; Compare to dataset, it just have a supplementary option key that is used to indicate in which subobject the JSON value should be added. The information is added in the even under the alert.extra subobject: "alert": { "extra": { "src_ip": { "test": "success", "context": 3 }, The main interest of the feature is to be able to contextualize a match. For example, if you have an IOC source, you can do value1,{"actor":"APT28","Country":"FR"} value2,{"actor":"APT32","Country":"NL"} This way, a single dataset is able to produce context to the event where it was not possible before and multiple signatures had to be used. Ticket: OISF#7372
regit
added a commit
to regit/suricata
that referenced
this pull request
Dec 15, 2024
regit
added a commit
to regit/suricata
that referenced
this pull request
Dec 15, 2024
Previous code was using an array and introducing a limit in the number of datajson keywords that can be used in a signature. This patch uses a linked list instead to overcome the limit. By using a first element of the list that is part of the structure we limit the cost of the feature to a structure member added to PacketAlert structure. Only the PacketAlertFree function is impacted as we need to iterate to find potential allocation. Ticket: OISF#7372
regit
added a commit
to regit/suricata
that referenced
this pull request
Dec 15, 2024
regit
added a commit
to regit/suricata
that referenced
this pull request
Dec 15, 2024
regit
added a commit
to regit/suricata
that referenced
this pull request
Dec 15, 2024
It was not handling correctly the json values with space as they were seen as multiple arguments. Ticket: OISF#7372
regit
added a commit
to regit/suricata
that referenced
this pull request
Dec 22, 2024
This patch introduces a new keyword datajson that is similar to dataset with a twist. Where dataset allows match from sets, datajson allows the same but also adds JSON data to the alert event. This data is comint from the set definition it self. For example, an ipv4 set will look like: 10.16.1.11,{"test": "success","context":3} The syntax is value and json data separated by a comma. The syntax of the keyword is the following: datajson:isset,src_ip,type ip,load src.lst,key src_ip; Compare to dataset, it just have a supplementary option key that is used to indicate in which subobject the JSON value should be added. The information is added in the even under the alert.extra subobject: "alert": { "extra": { "src_ip": { "test": "success", "context": 3 }, The main interest of the feature is to be able to contextualize a match. For example, if you have an IOC source, you can do value1,{"actor":"APT28","Country":"FR"} value2,{"actor":"APT32","Country":"NL"} This way, a single dataset is able to produce context to the event where it was not possible before and multiple signatures had to be used. Ticket: OISF#7372
regit
added a commit
to regit/suricata
that referenced
this pull request
Dec 22, 2024
regit
added a commit
to regit/suricata
that referenced
this pull request
Dec 22, 2024
Previous code was using an array and introducing a limit in the number of datajson keywords that can be used in a signature. This patch uses a linked list instead to overcome the limit. By using a first element of the list that is part of the structure we limit the cost of the feature to a structure member added to PacketAlert structure. Only the PacketAlertFree function is impacted as we need to iterate to find potential allocation. Ticket: OISF#7372
regit
added a commit
to regit/suricata
that referenced
this pull request
Dec 22, 2024
regit
added a commit
to regit/suricata
that referenced
this pull request
Dec 22, 2024
regit
added a commit
to regit/suricata
that referenced
this pull request
Dec 22, 2024
It was not handling correctly the json values with space as they were seen as multiple arguments. Ticket: OISF#7372
regit
added a commit
to regit/suricata
that referenced
this pull request
Dec 22, 2024
This patch introduces a new keyword datajson that is similar to dataset with a twist. Where dataset allows match from sets, datajson allows the same but also adds JSON data to the alert event. This data is comint from the set definition it self. For example, an ipv4 set will look like: 10.16.1.11,{"test": "success","context":3} The syntax is value and json data separated by a comma. The syntax of the keyword is the following: datajson:isset,src_ip,type ip,load src.lst,key src_ip; Compare to dataset, it just have a supplementary option key that is used to indicate in which subobject the JSON value should be added. The information is added in the even under the alert.extra subobject: "alert": { "extra": { "src_ip": { "test": "success", "context": 3 }, The main interest of the feature is to be able to contextualize a match. For example, if you have an IOC source, you can do value1,{"actor":"APT28","Country":"FR"} value2,{"actor":"APT32","Country":"NL"} This way, a single dataset is able to produce context to the event where it was not possible before and multiple signatures had to be used. Ticket: OISF#7372
regit
added a commit
to regit/suricata
that referenced
this pull request
Dec 22, 2024
regit
added a commit
to regit/suricata
that referenced
this pull request
Dec 22, 2024
Previous code was using an array and introducing a limit in the number of datajson keywords that can be used in a signature. This patch uses a linked list instead to overcome the limit. By using a first element of the list that is part of the structure we limit the cost of the feature to a structure member added to PacketAlert structure. Only the PacketAlertFree function is impacted as we need to iterate to find potential allocation. Ticket: OISF#7372
regit
added a commit
to regit/suricata
that referenced
this pull request
Dec 22, 2024
regit
added a commit
to regit/suricata
that referenced
this pull request
Dec 22, 2024
regit
added a commit
to regit/suricata
that referenced
this pull request
Dec 22, 2024
It was not handling correctly the json values with space as they were seen as multiple arguments. Ticket: OISF#7372
regit
added a commit
to regit/suricata
that referenced
this pull request
Dec 23, 2024
This patch introduces a new keyword datajson that is similar to dataset with a twist. Where dataset allows match from sets, datajson allows the same but also adds JSON data to the alert event. This data is comint from the set definition it self. For example, an ipv4 set will look like: 10.16.1.11,{"test": "success","context":3} The syntax is value and json data separated by a comma. The syntax of the keyword is the following: datajson:isset,src_ip,type ip,load src.lst,key src_ip; Compare to dataset, it just have a supplementary option key that is used to indicate in which subobject the JSON value should be added. The information is added in the even under the alert.extra subobject: "alert": { "extra": { "src_ip": { "test": "success", "context": 3 }, The main interest of the feature is to be able to contextualize a match. For example, if you have an IOC source, you can do value1,{"actor":"APT28","Country":"FR"} value2,{"actor":"APT32","Country":"NL"} This way, a single dataset is able to produce context to the event where it was not possible before and multiple signatures had to be used. Ticket: OISF#7372
regit
added a commit
to regit/suricata
that referenced
this pull request
Dec 23, 2024
regit
added a commit
to regit/suricata
that referenced
this pull request
Dec 23, 2024
Previous code was using an array and introducing a limit in the number of datajson keywords that can be used in a signature. This patch uses a linked list instead to overcome the limit. By using a first element of the list that is part of the structure we limit the cost of the feature to a structure member added to PacketAlert structure. Only the PacketAlertFree function is impacted as we need to iterate to find potential allocation. Ticket: OISF#7372
regit
added a commit
to regit/suricata
that referenced
this pull request
Dec 23, 2024
regit
added a commit
to regit/suricata
that referenced
this pull request
Dec 23, 2024
regit
added a commit
to regit/suricata
that referenced
this pull request
Dec 23, 2024
It was not handling correctly the json values with space as they were seen as multiple arguments. Ticket: OISF#7372
regit
added a commit
to regit/suricata
that referenced
this pull request
Dec 24, 2024
This patch introduces a new keyword datajson that is similar to dataset with a twist. Where dataset allows match from sets, datajson allows the same but also adds JSON data to the alert event. This data is comint from the set definition it self. For example, an ipv4 set will look like: 10.16.1.11,{"test": "success","context":3} The syntax is value and json data separated by a comma. The syntax of the keyword is the following: datajson:isset,src_ip,type ip,load src.lst,key src_ip; Compare to dataset, it just have a supplementary option key that is used to indicate in which subobject the JSON value should be added. The information is added in the even under the alert.extra subobject: "alert": { "extra": { "src_ip": { "test": "success", "context": 3 }, The main interest of the feature is to be able to contextualize a match. For example, if you have an IOC source, you can do value1,{"actor":"APT28","Country":"FR"} value2,{"actor":"APT32","Country":"NL"} This way, a single dataset is able to produce context to the event where it was not possible before and multiple signatures had to be used. Ticket: OISF#7372
regit
added a commit
to regit/suricata
that referenced
this pull request
Dec 24, 2024
regit
added a commit
to regit/suricata
that referenced
this pull request
Dec 24, 2024
Previous code was using an array and introducing a limit in the number of datajson keywords that can be used in a signature. This patch uses a linked list instead to overcome the limit. By using a first element of the list that is part of the structure we limit the cost of the feature to a structure member added to PacketAlert structure. Only the PacketAlertFree function is impacted as we need to iterate to find potential allocation. Ticket: OISF#7372
regit
added a commit
to regit/suricata
that referenced
this pull request
Dec 24, 2024
regit
added a commit
to regit/suricata
that referenced
this pull request
Dec 24, 2024
regit
added a commit
to regit/suricata
that referenced
this pull request
Dec 24, 2024
It was not handling correctly the json values with space as they were seen as multiple arguments. Ticket: OISF#7372
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Make sure these boxes are signed before submitting your Pull Request -- thank you.
Link to redmine ticket:
https://redmine.openinfosecfoundation.org/issues/5069
Describe changes:
Example of rule
alert smb any any -> any any (msg: "Smb command rule"; smb.cmd: 10; sid: 1;)
. More examples in documentation.suricata-verify-pr: 733