-
Notifications
You must be signed in to change notification settings - Fork 183
Add vpatch-CVE-2025-34028 rule and test #1361
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
base: master
Are you sure you want to change the base?
Conversation
Hello @crowdsec-automation and thank you for your contribution! ❗ It seems that the following scenarios are not part of the 'crowdsecurity/appsec-virtual-patching' collection: 🔴 crowdsecurity/vpatch-CVE-2025-34028 🔴 |
Hello @crowdsec-automation, Scenarios/AppSec Rule are compliant with the taxonomy, thank you for your contribution! |
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! |
Hello @buixor and thank you for your contribution! ❗ It seems that the following scenarios are not part of the 'crowdsecurity/appsec-virtual-patching' collection: 🔴 crowdsecurity/vpatch-CVE-2024-1061 🔴 |
Hello @buixor, Scenarios/AppSec Rule are compliant with the taxonomy, thank you for your contribution! |
Hello @buixor, Scenarios/AppSec Rule are compliant with the taxonomy, thank you for your contribution! |
Hello @buixor, Scenarios/AppSec Rule are compliant with the taxonomy, thank you for your contribution! |
Hello @buixor, Scenarios/AppSec Rule are compliant with the taxonomy, thank you for your contribution! |
Hello @buixor, Scenarios/AppSec Rule are compliant with the taxonomy, thank you for your contribution! |
Hello @buixor, Scenarios/AppSec Rule are compliant with the taxonomy, thank you for your contribution! |
This rule detects exploitation attempts for CVE-2025-34028, a vulnerability in Commvault Command Center's
/commandcenter/deployWebpackage.do
endpoint that allows SSRF and path traversal. The detection logic is as follows:/commandcenter/deploywebpackage.do
, using a lowercase transform for case insensitivity.commcellName
parameter in the POST body. If it contains the substringhttp
(case-insensitive, with urldecode), it is likely an attempt to trigger SSRF, as the exploit uses a URL in this parameter.Validation checklist:
value:
fields are lowercase.lowercase
.match.value
contains capital letters.contains
instead ofregex
where applicable.Exploit URL: https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2025/CVE-2025-34028.yaml