# CVE-2006-6107: Missing authorization in n/a

> Local applications can remove match rules for other applications in D-Bus, causing a denial of service by losing process messages.

- **Severity:** Low 1.7 (`AV:L/AC:L/Au:S/C:N/I:N/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:** 14 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-6107, GHSA-r8m2-5wq2-xvh3, RHSA-2007:0008

## What is CVE-2006-6107?

CVE-2006-6107 is a low-severity missing authorization vulnerability in n/a, published on 14 Dec 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unspecified vulnerability in the match_rule_equal function in bus/signals.c in D-Bus before 1.0.2 allows local applications to remove match rules for other applications and cause a denial of service (lost process messages).

## Which versions are affected by CVE-2006-6107?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dbus` | Red Hat:enterprise_linux:4::as | All versions | 0:0.22-12.EL.8 |
| `dbus-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:0.22-12.EL.8 |
| `dbus-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:0.22-12.EL.8 |
| `dbus-glib` | Red Hat:enterprise_linux:4::as | All versions | 0:0.22-12.EL.8 |
| `dbus-python` | Red Hat:enterprise_linux:4::as | All versions | 0:0.22-12.EL.8 |
| `dbus-x11` | Red Hat:enterprise_linux:4::as | All versions | 0:0.22-12.EL.8 |
| `dbus` | Red Hat:enterprise_linux:4::desktop | All versions | 0:0.22-12.EL.8 |
| `dbus-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:0.22-12.EL.8 |
| `dbus-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:0.22-12.EL.8 |
| `dbus-glib` | Red Hat:enterprise_linux:4::desktop | All versions | 0:0.22-12.EL.8 |
| `dbus-python` | Red Hat:enterprise_linux:4::desktop | All versions | 0:0.22-12.EL.8 |
| `dbus-x11` | Red Hat:enterprise_linux:4::desktop | All versions | 0:0.22-12.EL.8 |
| `dbus` | Red Hat:enterprise_linux:4::es | All versions | 0:0.22-12.EL.8 |
| `dbus-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:0.22-12.EL.8 |
| `dbus-devel` | Red Hat:enterprise_linux:4::es | All versions | 0:0.22-12.EL.8 |
| `dbus-glib` | Red Hat:enterprise_linux:4::es | All versions | 0:0.22-12.EL.8 |
| `dbus-python` | Red Hat:enterprise_linux:4::es | All versions | 0:0.22-12.EL.8 |
| `dbus-x11` | Red Hat:enterprise_linux:4::es | All versions | 0:0.22-12.EL.8 |
| `dbus` | Red Hat:enterprise_linux:4::ws | All versions | 0:0.22-12.EL.8 |
| `dbus-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:0.22-12.EL.8 |
| `dbus-devel` | Red Hat:enterprise_linux:4::ws | All versions | 0:0.22-12.EL.8 |
| `dbus-glib` | Red Hat:enterprise_linux:4::ws | All versions | 0:0.22-12.EL.8 |
| `dbus-python` | Red Hat:enterprise_linux:4::ws | All versions | 0:0.22-12.EL.8 |
| `dbus-x11` | Red Hat:enterprise_linux:4::ws | All versions | 0:0.22-12.EL.8 |

Products: D-Bus D-Bus.

## How do I fix CVE-2006-6107?

Upgrade to a fixed version.

## Is CVE-2006-6107 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-0201](https://insights.sbomify.com/CVE-2005-0201/): Missing authorization in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-6107 and fix it if it is affected.

What it is: CVE-2006-6107 is a low-severity missing authorization vulnerability in n/a, published on 14 Dec 2006. 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-2006-6107 in the wild and no public exploit code.

Affected product: n/a. 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-2006-6107/ (Markdown: https://insights.sbomify.com/CVE-2006-6107/index.md)
```

## Sources

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

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