Add CVE-2024-13161 rule and test #1275
Closed
Conversation
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
|
Hello @buixor, ✅ The new VPATCH Rule is compliant, thank you for your contribution! |
|
Hello @buixor, Scenarios/AppSec Rule are compliant with the taxonomy, thank you for your contribution! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
The detection rule for CVE-2024-13161 targets the Ivanti EPM vulnerability where an attacker can coerce NTLM credentials. The rule checks for:
/WSVulnerabilityCore/VulCore.asmxin the URI.wildcardXML tag within the SOAP body, which is indicative of the attack.Soapactionheader must exactly match the expected action for the vulnerable function.The rule uses case-insensitive matching (
lowercasetransformation) to ensure robust detection against variations in case. The regex used for thewildcardtag is designed to detect typical UNC path exploitation patterns. This rule is designed to have high confidence with minimal false positives by specifically targeting the elements involved in the exploit.