# CVE-2014-3499: Privilege Escalation in Docker

> Local attackers can escalate privileges by accessing the Docker management socket due to insecure world-readable and world-writable permissions.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Jul 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wxj3-qwv4-cvfm, GO-2022-0752, RHSA-2014:0820

## What is CVE-2014-3499?

CVE-2014-3499 is a high-severity vulnerability in Fedoraproject Fedora, published on 11 Jul 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Docker 1.0.0 uses world-readable and world-writable permissions on the management socket, which allows local users to gain privileges via unspecified vectors.

Weakness: CWE-264

## Which versions are affected by CVE-2014-3499?

3 open source packages ship an affected version, including github.com/docker/docker. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/docker/docker` | Go | All versions | 1.0.1 |
| `github.com/docker/docker` | Go | All versions | 1.0.1 |
| `github.com/docker/docker` | Go | All versions | 1.0.1 |
| `docker` | Red Hat:rhel_extras_other:7 | All versions | 0:0.11.1-22.el7 |

Products: Docker Docker, Fedoraproject Fedora.

## How do I fix CVE-2014-3499?

Upgrade github.com/docker/docker to 1.0.1 or later.

## Is CVE-2014-3499 being exploited?

There is no known exploitation of CVE-2014-3499 in the wild and no public exploit code.

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2014-9357](https://insights.sbomify.com/CVE-2014-9357/): Arbitrary Code Execution (critical 10.0)
- [CVE-2020-14298](https://insights.sbomify.com/CVE-2020-14298/): Privilege escalation in Docker (high 8.8)
- [CVE-2020-14300](https://insights.sbomify.com/CVE-2020-14300/): Privilege escalation in Docker (high 8.8)
- [CVE-2018-15514](https://insights.sbomify.com/CVE-2018-15514/): Deserialization in n/a (high 8.8)
- [CVE-2014-9356](https://insights.sbomify.com/CVE-2014-9356/): Path Traversal in Docker (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-3499 and fix it if it is affected.

What it is: CVE-2014-3499 is a high-severity vulnerability in Fedoraproject Fedora, published on 11 Jul 2014. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-3499 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/docker/docker (Go): affected all versions; fixed in 1.0.1
- github.com/docker/docker (Go): affected all versions; fixed in 1.0.1
- github.com/docker/docker (Go): affected all versions; fixed in 1.0.1

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-2014-3499/ (Markdown: https://insights.sbomify.com/CVE-2014-3499/index.md)
```

## Sources

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

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