CVE-2022-44877 exploitation attempt
SIGmediumconfidence 70/100generated 2026-10-18
Web request carrying the exploit observable of CVE-2022-44877 (public PoC), taken from the public nuclei template.
- Linked CVE
- CVE-2022-44877
- Linked actors
- CRYSTALRAY
- 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.
Sigma rule
skopnix-sigma-cve-cve-2022-44877-f83398f6.ymldownload .yml ↓title: Skopnix - CVE-2022-44877 exploitation attempt
id: 0c1ffb96-1de9-50f2-a9c5-6388b562b982
status: experimental
description: Web request carrying the exploit observable of CVE-2022-44877 (public PoC), taken from the public nuclei template.
references:
- https://skopnix.com/cve/CVE-2022-44877
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2022/CVE-2022-44877.yaml
- https://nvd.nist.gov/vuln/detail/CVE-2022-44877
author: skopnix
date: '2026-10-18'
tags:
- attack.initial-access
- attack.t1190
- cve.2022-44877
logsource:
category: webserver
detection:
selection_1:
cs-uri-stem|contains: /login/index.php
cs-uri-query|contains: ${
condition: selection_1
falsepositives:
- Vulnerability scanners and authorised penetration tests (attempts, not compromise)
level: high
How to deploy on Sigma
- 1.Convert for your SIEM with sigma-cli / pySigma, e.g. sigma convert -t splunk -p sysmon rule.yml.
- 2.Run it as a hunt first: every rule ships as status experimental.
- 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.