-
Notifications
You must be signed in to change notification settings - Fork 29
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
meta_content and json_meta_content modifier #49
Comments
Not sure about this. First off, "distance" and "within" won't apply to json_content. json_content is in the order it is placed in the signature. So your first example would be an and. If the first json_content doesn't match, it will never get to the second json_content. |
Let's say I want to detect an exe in the \AppData\Local directory. With the current usage I would need to do something like: Current Usage: My proposal would be to put it all in one statement, prepended with the Proposed Usage:
In the proposed statement instead of |
The
meta_content
andjson_meta_content
both accept multiple multiple value can are compared based on OR logic, meaning only one needs to match to make the statement true. What about a&
modifier to change them to use AND logic and have to match all value? This of course can be done with multiple json_content statements but may look cleaner for certain usages.This can also be accomplished with
json_pcre
but may be faster than using pcre?Current Usage:
json_content:".SourceImage", "|5c|AppData|5c|Local|5c|"; json_content:".SourceImage","|2e|exe"; distance:0; within:100;
Proposed Usage:
json_meta_content:&".SourceImage",|5c|AppData|5c|Local|5c|, |2e|exe;
The proposed usage can even be processed in order. So in this example it would have to match
|5c|AppData|5c|Local|5c|
first then|2e|exe
would be next and have to be found after the first match. This may need an additional modifier likejson_meta_ordered;
json_meta_content:&".SourceImage",|5c|AppData|5c|Local|5c|, |2e|exe; json_meta_ordered;
The text was updated successfully, but these errors were encountered: