# CVE-2013-1813: Misconfiguration in n/a

> Local attackers can exploit insecure directory permissions in BusyBox mdev to potentially escalate privileges or modify system files.

- **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:** 23 Nov 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-1813, GHSA-gv44-p9m5-qjmr, MGASA-2013-0358, RHSA-2013:1732

## What is CVE-2013-1813?

CVE-2013-1813 is a high-severity vulnerability in Redhat Enterprise Linux, published on 23 Nov 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

util-linux/mdev.c in BusyBox before 1.21.0 uses 0777 permissions for parent directories when creating nested directories under /dev/, which allows local users to have unknown impact and attack vectors.

Weakness: CWE-264

## Which versions are affected by CVE-2013-1813?

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `busybox` | Red Hat:enterprise_linux:6::client | All versions | 1:1.15.1-20.el6 |
| `busybox-petitboot` | Red Hat:enterprise_linux:6::client | All versions | 1:1.15.1-20.el6 |
| `busybox` | Red Hat:enterprise_linux:6::computenode | All versions | 1:1.15.1-20.el6 |
| `busybox-petitboot` | Red Hat:enterprise_linux:6::computenode | All versions | 1:1.15.1-20.el6 |
| `busybox` | Red Hat:enterprise_linux:6::server | All versions | 1:1.15.1-20.el6 |
| `busybox-petitboot` | Red Hat:enterprise_linux:6::server | All versions | 1:1.15.1-20.el6 |
| `busybox` | Red Hat:enterprise_linux:6::workstation | All versions | 1:1.15.1-20.el6 |
| `busybox-petitboot` | Red Hat:enterprise_linux:6::workstation | All versions | 1:1.15.1-20.el6 |

Products: Busybox Busybox, Redhat Enterprise Linux, T-Mobile Tm-Ac1900.

## How do I fix CVE-2013-1813?

Upgrade to a fixed version.

## Is CVE-2013-1813 being exploited?

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

## Other vulnerabilities in Redhat Enterprise Linux

- [CVE-2022-48174](https://insights.sbomify.com/CVE-2022-48174/): Memory corruption in n/a (critical 9.8)
- [CVE-2021-42377](https://insights.sbomify.com/CVE-2021-42377/): Memory corruption in busybox (critical 9.8)
- [CVE-2016-2148](https://insights.sbomify.com/CVE-2016-2148/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-28391](https://insights.sbomify.com/CVE-2022-28391/): Command injection in n/a (high 8.8)
- [CVE-2017-16544](https://insights.sbomify.com/CVE-2017-16544/): Code injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-1813 and fix it if it is affected.

What it is: CVE-2013-1813 is a high-severity vulnerability in Redhat Enterprise Linux, published on 23 Nov 2013. 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-2013-1813 in the wild and no public exploit code.

Affected product: Redhat Enterprise Linux. 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-2013-1813/ (Markdown: https://insights.sbomify.com/CVE-2013-1813/index.md)
```

## Sources

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

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