Add vpatch-CVE-2026-42208 rule and test#59
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-2026-42208 🔴 |
|
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 targets the SQL injection vulnerability in LiteLLM (CVE-2026-42208) that is exploited via a crafted Authorization header on the
/v1/chat/completionsendpoint. The detection logic is as follows:/v1/chat/completionsby matching the URI with a lowercase transformation for normalization.authorizationheader for the presence of the SQL injection pattern"' or ", which is characteristic of the attack payload (e.g.,Bearer <token>' OR ...). The lowercase transformation ensures case-insensitive matching.labelssection includes the correct CVE, ATT&CK, and CWE references, and the product/vuln class label is formatted as required.Validation Checklist:
value:fields are lowercase.transformincludeslowercasewherever applicable.match.valuecontains capital letters.containsinstead ofregexfor the Authorization header pattern, as only a substring match is needed.Exploit URL: https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2026/CVE-2026-42208.yaml