CVE-2018-0296
Linked CVE
- CVE-2018-0296 exploitation attemptSIGAQLXQLT1190conf 90CVE exploitation, high
Generated because: CISA KEV, EPSS 1.00. 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.
How to deploy
SIGSigma
- 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.
AQLIBM 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.
XQLCortex XDR
- Step 1
- Paste the XQL into Incident Response > Investigation > Query Builder > XQL Search.
- Step 2
- To alert, save it as a Correlation Rule and set the MITRE tactic and technique printed with the rule.
- Step 3
- Schedule it on the interval you hunt at; keep the fields stage for the alert's columns.
- Check
- CVE rules read PAN-OS URL logs (panw_ngfw_url_raw), which need the NGFW integration and, for HTTPS, decryption.