Add vpatch-CVE-2025-48703 rule and test#39
Open
crowdsec-automation wants to merge 4 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
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.
This rule detects exploitation attempts against CentOS Web Panel (CWP) filemanager's changePerm functionality, which is vulnerable to RCE via the
t_totalparameter (CVE-2022-44877). The rule matches requests to URIs containing/filemanager&acc=changeperm(case-insensitive, URL-decoded) and checks if thet_totalargument contains a backtick (`) character, which is commonly used for command injection in shell contexts. This approach minimizes false positives by focusing on the specific vulnerable endpoint and the shell metacharacter in the relevant parameter. All value fields are lowercase, and the required transforms are applied for normalization. The test nuclei template simulates a POST request with a command injection payload and expects a 403 response to confirm the rule's effectiveness.