# CVE-2015-8612: The EnableNetwork method in the Network class in plugins/mechanism/Network.py in Blueman before 2.0.3 allows local users to gain privileges


- **Severity:** High 8.4 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 8 Jan 2016
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-8612, DSA-3427-1, MGASA-2015-0491

## What is CVE-2015-8612?

CVE-2015-8612 is a high-severity vulnerability in n/a, published on 8 Jan 2016. 

### Official description

The EnableNetwork method in the Network class in plugins/mechanism/Network.py in Blueman before 2.0.3 allows local users to gain privileges via the dhcp_handler argument.

Weakness: CWE-264

## Which versions are affected by CVE-2015-8612?

It affects 1 product.


Products: Blueman Project Blueman.

## How do I fix CVE-2015-8612?

Upgrade to a fixed version.

## Is CVE-2015-8612 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-8612 exists.

Public exploit code:

- blueman set_dhcp_handler D-Bus Privilege Escalation (metasploit)
- blueman - set_dhcp_handler D-Bus Privilege Escalation (Metasploit) (exploitdb)
- blueman - set_dhcp_handler D-Bus Privilege Escalation (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2020-15238](https://insights.sbomify.com/CVE-2020-15238/): Local privilege escalation Blueman (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-8612 and fix it if it is affected.

What it is: CVE-2015-8612 is a high-severity vulnerability in n/a, published on 8 Jan 2016. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-8612 exists.

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-2015-8612/ (Markdown: https://insights.sbomify.com/CVE-2015-8612/index.md)
```

## Sources

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

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