# CVE-2008-0595: Auth bypass in n/a

> Local users can bypass D-Bus access restrictions by sending method calls with a NULL interface, circumventing intended security policies.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 29 Feb 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-0595, DSA-1599-1, GHSA-r2x7-p32r-g3vj, RHSA-2008:0159

## What is CVE-2008-0595?

CVE-2008-0595 is a medium-severity authentication bypass vulnerability in Fedoraproject Fedora, published on 29 Feb 2008. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

dbus-daemon in D-Bus before 1.0.3, and 1.1.x before 1.1.20, recognizes send_interface attributes in allow directives in the security policy only for fully qualified method calls, which allows local users to bypass intended access restrictions via a method call with a NULL interface.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2008-0595?

It affects 4 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dbus` | Red Hat:enterprise_linux:5::client | All versions | 0:1.0.0-6.3.el5_1 |
| `dbus-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:1.0.0-6.3.el5_1 |
| `dbus-x11` | Red Hat:enterprise_linux:5::client | All versions | 0:1.0.0-6.3.el5_1 |
| `dbus` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.0.0-6.3.el5_1 |
| `dbus-debuginfo` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.0.0-6.3.el5_1 |
| `dbus-devel` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.0.0-6.3.el5_1 |
| `dbus` | Red Hat:enterprise_linux:5::server | All versions | 0:1.0.0-6.3.el5_1 |
| `dbus-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:1.0.0-6.3.el5_1 |
| `dbus-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:1.0.0-6.3.el5_1 |
| `dbus-x11` | Red Hat:enterprise_linux:5::server | All versions | 0:1.0.0-6.3.el5_1 |

Products: Fedoraproject Fedora, Freedesktop Dbus, Mandrakesoft Mandrake Linux, Redhat Enterprise Linux.

## How do I fix CVE-2008-0595?

Upgrade to a fixed version.

## Is CVE-2008-0595 being exploited?

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

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-0595 and fix it if it is affected.

What it is: CVE-2008-0595 is a medium-severity authentication bypass vulnerability in Fedoraproject Fedora, published on 29 Feb 2008. 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-2008-0595 in the wild and no public exploit code.

Affected product: Fedoraproject Fedora. 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-2008-0595/ (Markdown: https://insights.sbomify.com/CVE-2008-0595/index.md)
```

## Sources

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

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