# CVE-2013-0292: Privilege escalation in n/a

> Local attackers can escalate privileges by spoofing NameOwnerChanged signals in the D-Bus GLib library due to improper sender verification.

- **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:** 4 Mar 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-0292, GHSA-rw79-5p9f-842m, RHSA-2013:0568

## What is CVE-2013-0292?

CVE-2013-0292 is a high-severity vulnerability in n/a, published on 4 Mar 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The dbus_g_proxy_manager_filter function in dbus-gproxy in Dbus-glib before 0.100.1 does not properly verify the sender of NameOwnerChanged signals, which allows local users to gain privileges via a spoofed signal.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dbus-glib` | Red Hat:enterprise_linux:5::server | All versions | 0:0.73-11.el5_9 |
| `dbus-glib-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:0.73-11.el5_9 |
| `dbus-glib-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:0.73-11.el5_9 |
| `dbus-glib` | Red Hat:enterprise_linux:6::client | All versions | 0:0.86-6.el6_4 |
| `dbus-glib-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:0.86-6.el6_4 |
| `dbus-glib-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:0.86-6.el6_4 |
| `dbus-glib` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.86-6.el6_4 |
| `dbus-glib-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.86-6.el6_4 |
| `dbus-glib-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.86-6.el6_4 |
| `dbus-glib` | Red Hat:enterprise_linux:6::server | All versions | 0:0.86-6.el6_4 |
| `dbus-glib-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:0.86-6.el6_4 |
| `dbus-glib-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:0.86-6.el6_4 |
| `dbus-glib` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.86-6.el6_4 |
| `dbus-glib-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.86-6.el6_4 |
| `dbus-glib-devel` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.86-6.el6_4 |

Products: Freedesktop Dbus-Glib.

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

Upgrade to a fixed version.

## Is CVE-2013-0292 being exploited?

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

Public exploit code:

- dbus-glib pam_fprintd - Local Privilege Escalation (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2010-1172](https://insights.sbomify.com/CVE-2010-1172/): Security feature bypass in n/a (low 3.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-0292 is a high-severity vulnerability in n/a, published on 4 Mar 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-0292 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-2013-0292/ (Markdown: https://insights.sbomify.com/CVE-2013-0292/index.md)
```

## Sources

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

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