← Sigma detections
Sigma · CVE exploitation
CVE-2021-22017 exploitation attempt
- severity
- high
- confidence
- 90/100
- generated
- 14 Nov 2026
- Linked CVE
- CVE-2021-22017
Web request carrying the exploit observable of CVE-2021-22017 (CISA KEV), taken from the public nuclei template.
False-positive notes
Generated because: CISA KEV. 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.
References
title: Skopnix - CVE-2021-22017 exploitation attemptid: 7eef14c1-3de3-572a-85e0-2aef9ca74b16status: experimentaldescription: Web request carrying the exploit observable of CVE-2021-22017 (CISA KEV), taken from the public nuclei template.references: - https://skopnix.com/cve/CVE-2021-22017 - https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2021/CVE-2021-22017.yaml - https://nvd.nist.gov/vuln/detail/CVE-2021-22017author: skopnixdate: '2026-11-14'tags: - attack.initial-access - attack.t1190 - cve.2021-22017logsource: category: webserverdetection: selection_1: cs-uri-stem|contains: /analytics/ceip/sdk/..;/ condition: selection_1falsepositives: - Vulnerability scanners and authorised penetration tests (attempts, not compromise)level: highskopnix-sigma-cve-cve-2021-22017-e7b41ffa.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.