Add vpatch-CVE-2025-59528 rule and test#48
Merged
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-59528 🔴 |
|
Hello @crowdsec-automation, Scenarios/AppSec Rule are compliant with the taxonomy, thank you for your contribution! |
|
Hello @buixor, ✅ The new VPATCH Rule is compliant, thank you for your contribution! |
|
Hello @buixor, 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
2 participants
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 targets the Flowise RCE vulnerability (CVE-2025-59528) by detecting POST requests to the vulnerable endpoint
/api/v1/node-load-method/custommcp(case-insensitive). It specifically inspects the JSON body argumentinputs.mcpServerConfigfor the presence of the stringfunction(), which is indicative of a JavaScript function injection used in the exploit. Thelowercaseandurldecodetransforms ensure case-insensitive and encoded payloads are detected. This approach minimizes false positives by focusing on the exact vulnerable parameter and the exploit pattern. The test nuclei template is adapted to only check for a 403 response, as required. Allvalue:fields are lowercase, and the rule usescontainsfor robust detection.