Skip to content

Add vpatch-CVE-2024-21650 rule and test#1484

Open
crowdsec-automation wants to merge 6 commits intomasterfrom
1758723485-vpatch-CVE-2024-21650
Open

Add vpatch-CVE-2024-21650 rule and test#1484
crowdsec-automation wants to merge 6 commits intomasterfrom
1758723485-vpatch-CVE-2024-21650

Conversation

@crowdsec-automation
Copy link
Copy Markdown
Contributor

This rule targets the XWiki user registration endpoint vulnerable to RCE via the "first name" or "last name" fields. The detection logic is as follows:

  • The first rule block matches requests to the registration endpoint (/bin/register/xwiki/xwikiregister), using both lowercase and urldecode transforms to ensure case-insensitive and encoded/decoded matching.
  • The second rule block inspects the POST body arguments, specifically the register_first_name and register_last_name fields, for the presence of the string {{groovy}} (case-insensitive, URL-decoded). This string is a strong indicator of an attempt to inject Groovy code, which is the vector for RCE in this vulnerability.
  • The rule avoids matching on the full payload or specific code, instead focusing on the Groovy macro marker, which is the minimal and most reliable indicator of exploitation attempts, reducing false positives.
  • The test nuclei template is adapted to send a POST request with a malicious register_first_name containing the Groovy macro, and expects a 403 response to confirm the rule blocks the attack.

Validation checklist:

  • All value: fields are lowercase.
  • All relevant transforms include lowercase and urldecode.
  • No match.value contains capital letters.
  • The rule uses contains for matching, not regex, as per guidelines.

@github-actions
Copy link
Copy Markdown

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-2024-21650 🔴

@github-actions
Copy link
Copy Markdown

Hello @crowdsec-automation,

Scenarios/AppSec Rule are compliant with the taxonomy, thank you for your contribution!

@github-actions
Copy link
Copy Markdown

Hello @blotus 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-0600 🔴
🔴 crowdsecurity/vpatch-CVE-2023-2009 🔴
🔴 crowdsecurity/vpatch-CVE-2023-0900 🔴
🔴 crowdsecurity/vpatch-CVE-2023-6623 🔴
🔴 crowdsecurity/vpatch-CVE-2023-23489 🔴
🔴 crowdsecurity/vpatch-CVE-2023-4634 🔴
🔴 crowdsecurity/vpatch-CVE-2023-23488 🔴
🔴 crowdsecurity/vpatch-CVE-2024-1071 🔴
🔴 crowdsecurity/vpatch-CVE-2023-6567 🔴
🔴 crowdsecurity/vpatch-CVE-2023-6360 🔴
🔴 crowdsecurity/vpatch-CVE-2024-1061 🔴

@github-actions
Copy link
Copy Markdown

Hello @blotus,

Scenarios/AppSec Rule are compliant with the taxonomy, thank you for your contribution!

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.

3 participants