# CVE-2011-4644: Auth bypass in n/a

> Remote attackers can read arbitrary files and execute commands on Splunk servers using a Free license due to missing authentication in the management console.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jan 2012
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-84gg-j7wj-x5hv

## What is CVE-2011-4644?

CVE-2011-4644 is a critical authentication bypass vulnerability in Splunk Splunk, published on 3 Jan 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2011-4644?

It affects 1 product.


Products: Splunk Splunk.

## How do I fix CVE-2011-4644?

No fix has been published for CVE-2011-4644 yet. Limit exposure of the affected software until one is available.

## Is CVE-2011-4644 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-4644 exists.

Public exploit code:

- Splunk - Remote Command Execution (exploitdb)

## Other vulnerabilities in Splunk Splunk

- [CVE-2026-20253](https://insights.sbomify.com/CVE-2026-20253/): Splunk Enterprise Missing Authentication for Critical Function (critical 9.8, exploited in the wild)
- [CVE-2026-76268](https://insights.sbomify.com/CVE-2026-76268/): Missing Authentication for Critical Function in the Patroni REST API in Splunk Enterprise (critical 9.8)
- [CVE-2026-76284](https://insights.sbomify.com/CVE-2026-76284/): Improper Neutralization in Splunk Enterprise (critical 9.8)
- [CVE-2026-76285](https://insights.sbomify.com/CVE-2026-76285/): Improper Adherence to Coding Standards in Splunk Enterprise (critical 9.8)
- [CVE-2017-17067](https://insights.sbomify.com/CVE-2017-17067/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-4644 and fix it if it is affected.

What it is: CVE-2011-4644 is a critical authentication bypass vulnerability in Splunk Splunk, published on 3 Jan 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-4644 exists.

Affected product: Splunk Splunk. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2011-4644/ (Markdown: https://insights.sbomify.com/CVE-2011-4644/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2011-4644
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2011-4644
- OSV: https://osv.dev/vulnerability/CVE-2011-4644

---
From sbomify Insights: https://insights.sbomify.com/CVE-2011-4644/
Summaries are generated and may contain mistakes; the official description above is the record.