← IBM QRadar detections
IBM QRadar · 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
SELECT sourceip, destinationip, destinationport, QIDNAME(qid) AS event, LOGSOURCENAME(logsourceid) AS log_source, "URL"FROM eventsWHERE (("URL" ILIKE '%/analytics/ceip/sdk/..;/%'))AND LOGSOURCETYPENAME(devicetype) IN ('Apache HTTP Server', 'Microsoft IIS', 'F5 Networks BIG-IP ASM', 'Squid Web Proxy', 'Blue Coat SG', 'Zscaler Nanolog Streaming Service', 'Palo Alto PA Series', 'Fortinet FortiGate Security Gateway', 'Imperva SecureSphere', 'Citrix NetScaler', 'Akamai KONA')LAST 7 DAYSskopnix-qradar-cve-cve-2021-22017-cc22ad7c.aql
How to deploy on IBM QRadar
- Step 1
- Create the reference set from its spec (Reference Data API, or Admin > Reference Set Management) and schedule the skopnix feed load.
- Step 2
- Paste the AQL into Log Activity > Advanced Search to hunt the last seven days.
- Step 3
- For alerting, build the CRE rule from the test stack shown and exclude your known-good building block.
- Check
- Custom properties ("URL Host", "URL", "File Hash", "Process CommandLine") come from your DSMs and content extensions; rename them if yours differ.