# CVE-2009-0115: Misconfiguration in n/a

> Local attackers can exploit world-writable socket permissions to send arbitrary commands to the multipath daemon, potentially escalating privileges or executing code.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 30 Mar 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-0115, DSA-1767-1, GHSA-m58q-qh36-cwx8, RHSA-2009:0411

## What is CVE-2009-0115?

CVE-2009-0115 is a high-severity vulnerability in Debian Debian Linux, published on 30 Mar 2009. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Device Mapper multipathing driver (aka multipath-tools or device-mapper-multipath) 0.4.8, as used in SUSE openSUSE, SUSE Linux Enterprise Server (SLES), Fedora, and possibly other operating systems, uses world-writable permissions for the socket file (aka /var/run/multipathd.sock), which allows local users to send arbitrary commands to the multipath daemon.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2009-0115?

It affects 11 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `device-mapper-multipath` | Red Hat:enterprise_linux:4::as | All versions | 0:0.4.5-31.el4_7.1 |
| `device-mapper-multipath-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:0.4.5-31.el4_7.1 |
| `device-mapper-multipath` | Red Hat:enterprise_linux:4::desktop | All versions | 0:0.4.5-31.el4_7.1 |
| `device-mapper-multipath-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:0.4.5-31.el4_7.1 |
| `device-mapper-multipath` | Red Hat:enterprise_linux:4::es | All versions | 0:0.4.5-31.el4_7.1 |
| `device-mapper-multipath-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:0.4.5-31.el4_7.1 |
| `device-mapper-multipath` | Red Hat:enterprise_linux:4::ws | All versions | 0:0.4.5-31.el4_7.1 |
| `device-mapper-multipath-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:0.4.5-31.el4_7.1 |
| `device-mapper-multipath` | Red Hat:enterprise_linux:5::client | All versions | 0:0.4.7-23.el5_3.2 |
| `device-mapper-multipath-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:0.4.7-23.el5_3.2 |
| `kpartx` | Red Hat:enterprise_linux:5::client | All versions | 0:0.4.7-23.el5_3.2 |
| `device-mapper-multipath` | Red Hat:enterprise_linux:5::server | All versions | 0:0.4.7-23.el5_3.2 |
| `device-mapper-multipath-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:0.4.7-23.el5_3.2 |
| `kpartx` | Red Hat:enterprise_linux:5::server | All versions | 0:0.4.7-23.el5_3.2 |

Products: Avaya Intuity Audix Lx, Avaya Message Networking, Avaya Messaging Storage Server, Christophe.varoqui Multipath-Tools, Debian Debian Linux, Fedoraproject Fedora, Juniper Ctpview, Novell Open Enterprise Server, Opensuse Opensuse, Suse Linux Enterprise Desktop, Suse Linux Enterprise Server.

## How do I fix CVE-2009-0115?

Apply the vendor's patch.

## Is CVE-2009-0115 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-0115 and fix it if it is affected.

What it is: CVE-2009-0115 is a high-severity vulnerability in Debian Debian Linux, published on 30 Mar 2009. 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-2009-0115 in the wild and no public exploit code.

Affected product: Debian Debian 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-2009-0115/ (Markdown: https://insights.sbomify.com/CVE-2009-0115/index.md)
```

## Sources

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

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