Add vpatch-CVE-2023-29357 rule and test#1758
Add vpatch-CVE-2023-29357 rule and test#1758crowdsec-automation wants to merge 4 commits intomasterfrom
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-2023-29357 🔴 |
|
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. The following items have errors: crowdsecurity/crs-exclusion-plugin-cpanel:
crowdsecurity/crs-exclusion-plugin-dokuwiki:
crowdsecurity/crs-exclusion-plugin-drupal:
crowdsecurity/crs-exclusion-plugin-nextcloud:
crowdsecurity/crs-exclusion-plugin-phpbb:
crowdsecurity/crs-exclusion-plugin-phpmyadmin:
crowdsecurity/crs-exclusion-plugin-wordpress:
crowdsecurity/crs-exclusion-plugin-xenforo:
Mitre ATT&CKInformation about mitre attack can be found here.
Expected format is (where labels:
classification:
- attack.TXXXXCVEsIf your scenario covers a specific CVE (Common Vulnerabilities and Exposures), please add it. Expected format is (where labels:
classification:
- cve.CVE-XXX-XXXBehaviorsPlease identify the behavior(s) your scenario is targeting. You can find the list of available behaviors here. Expected format is (where labels:
behavior: <behavior>See the labels documentation for more information. |
This rule detects attempts to exploit CVE-2023-29357, an authentication bypass in Microsoft SharePoint where attackers forge JWT tokens using the "none" algorithm. The detection logic is as follows:
/api/web/siteusers, which is the focus of the exploit.Authorizationheader containing the stringbearer(case-insensitive), indicating a bearer token is being used.Authorizationheader for the substringnone, which is characteristic of JWT tokens using the "none" algorithm (i.e., unsigned tokens), a key part of this exploit.All
value:fields are lowercase, and thelowercasetransform is applied to ensure case-insensitive matching. The rule avoids false positives by focusing on the specific endpoint and the unique use of the "none" algorithm in the Authorization header. No regex or unnecessary complexity is used, and the rule is optimized for minimal false positives and negatives. The test nuclei template is adapted to expect a 403 response, as required.