Skip to content
skopnix
Section E · Detections · Rule
← IBM QRadar detectionsIBM QRadar · CVE exploitation

CVE-2002-1131 exploitation attempt

AQLmediumconfidence 70/100generated 2026-10-18

Web request carrying the exploit observable of CVE-2002-1131 (public PoC), taken from the public nuclei template.

ATT&CK
T1190 mitre ↗
Linked CVE
CVE-2002-1131
False positives
Keys on the distinctive part of the exploit request only (path traversal, exploit syntax in the query, an unusual parameter) — never on an endpoint the product serves in normal use. 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.

AQL search

skopnix-qradar-cve-cve-2002-1131-6310b324.aqldownload .aql ↓
SELECT sourceip, destinationip, destinationport, QIDNAME(qid) AS event, LOGSOURCENAME(logsourceid) AS log_source, "URL"
FROM events
WHERE ("URL" ILIKE '%/src/addressbook.php%' AND "URL" ILIKE '%%3C%2Fscript%3E%3Cscript%3Ealert%28document.domain%29%3C%2Fscript%3E%')
LAST 7 DAYS

CRE rule (build in Offenses > Rules)

download .txt ↓
Rule name: "Skopnix: CVE-2002-1131 exploitation attempt"
Rule type: Event
Test stack:
  - and when the event(s) were detected by one or more of [your web server / WAF / proxy log sources]
  - and when the event matches this AQL filter query: ("URL" ILIKE '%/src/addressbook.php%' AND "URL" ILIKE '%%3C%2Fscript%3E%3Cscript%3Ealert%28document.domain%29%3C%2Fscript%3E%')
Response: dispatch new event / create offense indexed by Destination IP (the targeted server); annotate "Skopnix CVE-2002-1131 attempt".
FP-safety: correlate with the HTTP status / response size; scanner noise is an attempt, not a breach.

How to deploy on IBM QRadar

  1. 1.Create the reference set from its spec (Reference Data API, or Admin > Reference Set Management) and schedule the skopnix feed load.
  2. 2.Paste the AQL into Log Activity > Advanced Search to hunt the last seven days.
  3. 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.

References