# CVE-2009-1189: Other in n/a

> Remote attackers can spoof signatures in D-Bus due to incorrect validation logic, bypassing security checks.

- **Severity:** Low 3.6 (`AV:L/AC:L/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Apr 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-1189, DSA-1837-1, GHSA-2332-hcww-wjmr, RHSA-2010:0018

## What is CVE-2009-1189?

CVE-2009-1189 is a low-severity vulnerability in n/a, published on 27 Apr 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The _dbus_validate_signature_with_reason function (dbus-marshal-validate.c) in D-Bus (aka DBus) before 1.2.14 uses incorrect logic to validate a basic type, which allows remote attackers to spoof a signature via a crafted key.  NOTE: this is due to an incorrect fix for CVE-2008-3834.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dbus` | Red Hat:enterprise_linux:5::client | All versions | 0:1.1.2-12.el5_4.1 |
| `dbus-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:1.1.2-12.el5_4.1 |
| `dbus-libs` | Red Hat:enterprise_linux:5::client | All versions | 0:1.1.2-12.el5_4.1 |
| `dbus-x11` | Red Hat:enterprise_linux:5::client | All versions | 0:1.1.2-12.el5_4.1 |
| `dbus` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.1.2-12.el5_4.1 |
| `dbus-debuginfo` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.1.2-12.el5_4.1 |
| `dbus-devel` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:1.1.2-12.el5_4.1 |
| `dbus` | Red Hat:enterprise_linux:5::server | All versions | 0:1.1.2-12.el5_4.1 |
| `dbus-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:1.1.2-12.el5_4.1 |
| `dbus-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:1.1.2-12.el5_4.1 |
| `dbus-libs` | Red Hat:enterprise_linux:5::server | All versions | 0:1.1.2-12.el5_4.1 |
| `dbus-x11` | Red Hat:enterprise_linux:5::server | All versions | 0:1.1.2-12.el5_4.1 |

Products: Freedesktop Dbus.

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

Upgrade to a fixed version.

## Is CVE-2009-1189 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-35512](https://insights.sbomify.com/CVE-2020-35512/): Use after free in D-Bus Development branch (high 7.8)
- [CVE-2008-4311](https://insights.sbomify.com/CVE-2008-4311/): Security feature bypass in n/a (medium 4.6)
- [CVE-2011-2533](https://insights.sbomify.com/CVE-2011-2533/): Path traversal in n/a (low 3.3)
- [CVE-2014-3637](https://insights.sbomify.com/CVE-2014-3637/): Denial of service in n/a (low 2.1)
- [CVE-2008-3834](https://insights.sbomify.com/CVE-2008-3834/): Denial of service in n/a (low 2.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-1189 is a low-severity vulnerability in n/a, published on 27 Apr 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2009-1189 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-2009-1189/ (Markdown: https://insights.sbomify.com/CVE-2009-1189/index.md)
```

## Sources

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

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