Sigma · CVE exploitation
CVE-2024-22320 exploitation attempt
- severity
- medium
- confidence
- 80/100
- generated
- 14 Nov 2026
- Linked CVE
- CVE-2024-22320
Web request carrying the exploit observable of CVE-2024-22320 (EPSS 0.73), taken from the public nuclei template.
False-positive notes
Generated because: EPSS 0.73. Keys on the distinctive part of the exploit request only (path traversal behind a product-specific path, exploit syntax in the query, an unusual parameter); a match on a common path plus a generic token such as ../ or a quote is rejected, never emitted. Needs raw request-URI logging (some web servers normalise ../ away). Scanners hitting the internet produce true-positive ATTEMPTS: correlate with sc-status / response size before declaring compromise. The product's own pages can send this parameter: the rule keys on a parameter NAME, not on exploit syntax in its value. Check the value before treating a match as an attack; level capped at medium.
References
title: Skopnix - CVE-2024-22320 exploitation attemptid: 4537d968-78e0-5c20-9475-4ea686cee54estatus: experimentaldescription: Web request carrying the exploit observable of CVE-2024-22320 (EPSS 0.73), taken from the public nuclei template.references: - https://skopnix.com/cve/CVE-2024-22320 - https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2024/CVE-2024-22320.yaml - https://nvd.nist.gov/vuln/detail/CVE-2024-22320author: skopnixdate: '2026-11-14'tags: - attack.initial-access - attack.t1190 - cve.2024-22320logsource: category: webserverdetection: selection_1: cs-uri-stem|contains: /res/login.jsf cs-uri-query|contains: javax.faces.ViewState condition: selection_1falsepositives: - Vulnerability scanners and authorised penetration tests (attempts, not compromise) - 'The product''s own pages can send this parameter: the rule keys on a parameter NAME, not on exploit syntax in its value. Check the value before treating a match as an attack'level: mediumskopnix-sigma-cve-cve-2024-22320-ee2149c0.yml
How to deploy on Sigma
- Step 1
- Convert for your SIEM with sigma-cli / pySigma, e.g. sigma convert -t splunk -p sysmon rule.yml.
- Step 2
- Run it as a hunt first: every rule ships as status experimental.
- Step 3
- Promote to an alert once a week of results is clean on your data.
- Check
- The processing pipeline must map the logsource (firewall, dns, proxy, webserver, process_creation) to your field names.