Add vpatch-CVE-2025-55748 rule and test
This rule detects path traversal attempts in XWiki Platform's ssx and jsx endpoints, specifically targeting the resource parameter. The first rule block matches requests to URIs containing /bin/ssx/ or /bin/jsx/ (case-insensitive, URL-decoded), as both endpoints are affected according to the advisory. The second rule block inspects the resource argument for the presence of '../', which is a classic indicator of path traversal. Both transformations (lowercase and urldecode) are applied to ensure normalization and case-insensitive matching. The rule avoids matching on full file paths to minimize false positives and focuses on the traversal pattern itself. The labels section includes the correct CVE, ATT&CK, and CWE references. All value: fields are lowercase, and contains is used for the traversal pattern as per best practices.
Hello @crowdsec-automation and thank you for your contribution!
:heavy_exclamation_mark: It seems that the following scenarios are not part of the 'crowdsecurity/appsec-virtual-patching' collection:
:red_circle: crowdsecurity/vpatch-CVE-2025-55748 :red_circle:
Hello @crowdsec-automation and thank you for your contribution!
I'm a bot that helps maintainers to validate scenarios and ensure they include all the required information. I've found some errors in your scenarios, please fix them and re-submit your PR, or ask for help if you need it.
The following items have errors:
crowdsecurity/crs-exclusion-plugin-cpanel:
labelsnot found
crowdsecurity/crs-exclusion-plugin-dokuwiki:
labelsnot found
crowdsecurity/crs-exclusion-plugin-drupal:
labelsnot found
crowdsecurity/crs-exclusion-plugin-nextcloud:
labelsnot found
crowdsecurity/crs-exclusion-plugin-phpbb:
labelsnot found
crowdsecurity/crs-exclusion-plugin-phpmyadmin:
labelsnot found
crowdsecurity/crs-exclusion-plugin-wordpress:
labelsnot found
crowdsecurity/crs-exclusion-plugin-xenforo:
labelsnot found
Mitre ATT&CK
Information about mitre attack can be found here. As an example, some common mitre attack techniques:
- T1110 for bruteforce attacks
- T1595 and T1190 for exploitation of public vulnerabilities
- T1595 for generic scanning of exposed applications
Expected format is (where XXXX is the technique ID):
labels:
classification:
- attack.TXXXX
CVEs
If your scenario covers a specific CVE (Common Vulnerabilities and Exposures), please add it.
Expected format is (where CVE-XXX-XXX is the CVE ID):
labels:
classification:
- cve.CVE-XXX-XXX
Behaviors
Please identify the behavior(s) your scenario is targeting. You can find the list of available behaviors here.
Expected format is (where <behavior> is the behavior you want to target):
labels:
behavior: <behavior>
See the labels documentation for more information.
Hello @buixor and thank you for your contribution!
I'm a bot that helps maintainers to validate scenarios and ensure they include all the required information. I've found some errors in your scenarios, please fix them and re-submit your PR, or ask for help if you need it.
The following items have errors:
crowdsecurity/crs-exclusion-plugin-cpanel:
labelsnot found
crowdsecurity/crs-exclusion-plugin-dokuwiki:
labelsnot found
crowdsecurity/crs-exclusion-plugin-drupal:
labelsnot found
crowdsecurity/crs-exclusion-plugin-nextcloud:
labelsnot found
crowdsecurity/crs-exclusion-plugin-phpbb:
labelsnot found
crowdsecurity/crs-exclusion-plugin-phpmyadmin:
labelsnot found
crowdsecurity/crs-exclusion-plugin-wordpress:
labelsnot found
crowdsecurity/crs-exclusion-plugin-xenforo:
labelsnot found
Mitre ATT&CK
Information about mitre attack can be found here. As an example, some common mitre attack techniques:
- T1110 for bruteforce attacks
- T1595 and T1190 for exploitation of public vulnerabilities
- T1595 for generic scanning of exposed applications
Expected format is (where XXXX is the technique ID):
labels:
classification:
- attack.TXXXX
CVEs
If your scenario covers a specific CVE (Common Vulnerabilities and Exposures), please add it.
Expected format is (where CVE-XXX-XXX is the CVE ID):
labels:
classification:
- cve.CVE-XXX-XXX
Behaviors
Please identify the behavior(s) your scenario is targeting. You can find the list of available behaviors here.
Expected format is (where <behavior> is the behavior you want to target):
labels:
behavior: <behavior>
See the labels documentation for more information.