Skip to content

Add vpatch-CVE-2023-29357 rule and test#1758

Open
crowdsec-automation wants to merge 4 commits intomasterfrom
1775654378-vpatch-CVE-2023-29357
Open

Add vpatch-CVE-2023-29357 rule and test#1758
crowdsec-automation wants to merge 4 commits intomasterfrom
1775654378-vpatch-CVE-2023-29357

Conversation

@crowdsec-automation
Copy link
Copy Markdown
Contributor

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:

  • The first rule ensures the request targets the SharePoint API endpoint /api/web/siteusers, which is the focus of the exploit.
  • The second rule checks for the presence of an Authorization header containing the string bearer (case-insensitive), indicating a bearer token is being used.
  • The third rule further inspects the Authorization header for the substring none, 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 the lowercase transform 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.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 8, 2026

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 🔴

@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 8, 2026

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:

  • labels not found

crowdsecurity/crs-exclusion-plugin-dokuwiki:

  • labels not found

crowdsecurity/crs-exclusion-plugin-drupal:

  • labels not found

crowdsecurity/crs-exclusion-plugin-nextcloud:

  • labels not found

crowdsecurity/crs-exclusion-plugin-phpbb:

  • labels not found

crowdsecurity/crs-exclusion-plugin-phpmyadmin:

  • labels not found

crowdsecurity/crs-exclusion-plugin-wordpress:

  • labels not found

crowdsecurity/crs-exclusion-plugin-xenforo:

  • labels not 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants