CVE-2011-4644 splunk splunk: Improper Authentication
splunk splunk: no CVSS score yet. EPSS 7.2% estimated probability of exploitation activity in the next 30 days.
On this page
Splunk 4.2.5 and earlier, when a Free license is selected, enables potentially undesirable functionality within an environment that intentionally does not support authentication, which allows remote attackers to (1) read arbitrary files via a management-console session that leverages the ability to create crafted data sources, or (2) execute management commands via an HTTP request.
- EPSS
- 7.2% (unchanged from 7.5% a week ago; 7.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 94th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-287 Improper Authentication
- OWASP Top 10
- A07:2025 Authentication Failures
- Published
- Modified
- NVD analysis
- Analyzed, since modified
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2011-4644 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2011-4644?via=ask-ai-copy and https://cve.bz/cve/CVE-2011-4644?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2011-4644 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
Versions
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| splunk:splunk | through 4.2.5 |
| splunk:splunk | 2.1 |
| splunk:splunk | 2.2 |
| splunk:splunk | 2.2.1 |
| splunk:splunk | 2.2.3 |
| splunk:splunk | 2.2.6 |
| splunk:splunk | 3.0 |
| splunk:splunk | 3.0.1 |
| splunk:splunk | 3.0.2 |
| splunk:splunk | 3.1 |
| splunk:splunk | 3.1.1 |
| splunk:splunk | 3.1.2 |
| splunk:splunk | 3.1.3 |
| splunk:splunk | 3.1.4 |
| splunk:splunk | 3.2 |
| splunk:splunk | 3.2.1 |
| splunk:splunk | 3.2.2 |
| splunk:splunk | 3.2.3 |
| splunk:splunk | 3.2.4 |
| splunk:splunk | 3.2.5 |
| splunk:splunk | 3.2.6 |
| splunk:splunk | 3.3 |
| splunk:splunk | 3.3.1 |
| splunk:splunk | 3.3.2 |
| splunk:splunk | 3.3.3 |
| splunk:splunk | 3.3.4 |
| splunk:splunk | 3.4 |
| splunk:splunk | 3.4.1 |
| splunk:splunk | 3.4.2 |
| splunk:splunk | 3.4.3 |
| splunk:splunk | 3.4.5 |
| splunk:splunk | 3.4.6 |
| splunk:splunk | 3.4.8 |
| splunk:splunk | 3.4.9 |
| splunk:splunk | 3.4.10 |
| splunk:splunk | 3.4.11 |
| splunk:splunk | 3.4.12 |
| splunk:splunk | 3.4.13 |
| splunk:splunk | 3.4.14 |
| splunk:splunk | 4.0 |
| splunk:splunk | 4.0.1 |
| splunk:splunk | 4.0.2 |
| splunk:splunk | 4.0.3 |
| splunk:splunk | 4.0.4 |
| splunk:splunk | 4.0.5 |
| splunk:splunk | 4.0.6 |
| splunk:splunk | 4.0.7 |
| splunk:splunk | 4.0.8 |
| splunk:splunk | 4.0.9 |
| splunk:splunk | 4.0.10 |
| splunk:splunk | 4.0.11 |
| splunk:splunk | 4.1 |
| splunk:splunk | 4.1.1 |
| splunk:splunk | 4.1.2 |
| splunk:splunk | 4.1.3 |
| splunk:splunk | 4.1.4 |
| splunk:splunk | 4.1.5 |
| splunk:splunk | 4.1.6 |
| splunk:splunk | 4.1.7 |
| splunk:splunk | 4.1.8 |
| splunk:splunk | 4.2 |
| splunk:splunk | 4.2.1 |
| splunk:splunk | 4.2.2 |
| splunk:splunk | 4.2.3 |
| splunk:splunk | 4.2.4 |
Public exploits
- Exploit-DB Splunk - Remote Command Execution
Attack patterns (CAPEC)
- CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
- CAPEC-57 Utilizing REST's Trust in the System Resource to Obtain Sensitive Data Likelihood: Medium · Severity: Very High
- CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
- CAPEC-114 Authentication Abuse Severity: Medium
- CAPEC-115 Authentication Bypass Severity: Medium
- CAPEC-151 Identity Spoofing Likelihood: Medium · Severity: Medium
- CAPEC-194 Fake the Source of Data Severity: Medium
- CAPEC-593 Session Hijacking Likelihood: High · Severity: Very High
- CAPEC-633 Token Impersonation Severity: Medium
- CAPEC-650 Upload a Web Shell to a Web Server Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.