Add vpatch-CVE-2025-53693 rule and test#49
Open
crowdsec-automation wants to merge 4 commits into
Open
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-53693 🔴 |
|
Hello @crowdsec-automation, Scenarios/AppSec Rule are compliant with the taxonomy, thank you for your contribution! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This rule detects exploitation attempts for CVE-2025-53693, a Sitecore XAML AjaxScriptManager cache poisoning vulnerability. The exploit involves sending a POST request to a XAML control endpoint (e.g., /-/xaml/Sitecore.Shell.Applications.Dialogs.ItemLister.ItemLister) with a specially crafted __PARAMETERS argument containing a JSON object with the method "AddToCache". The rule matches:
This approach ensures detection of the core exploit vector while minimizing false positives by focusing on the unique combination of endpoint and method name. The rule uses "contains" for flexibility and applies both "lowercase" and "urldecode" transforms to handle encoding and case variations.
Validation Checklist:
value:fields are lowercase.lowercase(andurldecodefor body args).containsinstead ofregexwhere applicable.