new: silent-call rules - #6230
Open
mromanode wants to merge 2 commits into
Open
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
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.
Summary of the Pull Request
Adds new detection rules covering the Silent;Call exploit chain against Cisco CUCM 15.x, where an attacker bypasses Tomcat Manager's source-address restriction via a forged
X-Forwarded-For: 127.0.0.1header, deploys a malicious WAR file to achieve RCE as thetomcatuser, and escalates to root by abusing a sudoers entry permitting passwordless gdb execution against PID 1.The rules cover the full attack chain:
/manager/deploy,/manager/text/deploy,/manager/html/upload)sudo gdbattach to PID 1 with command files (--command=,-x) in temporary directoriesChangelog
Example Log Event
Fixed Issues
SigmaHQ Rule Creation Conventions
If your PR adds new rules, please consider following and applying these conventions