# CVE-2012-6459: Information disclosure in n/a

> Remote attackers can obtain sensitive information via Bluetooth packets because ConnMan lists services after offline mode is enabled.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Jan 2013
- **Updated:** 17 Sep 2024
- **Also known as:** DEBIAN-CVE-2012-6459, GHSA-cv6g-gqg8-xr2p

## What is CVE-2012-6459?

CVE-2012-6459 is a medium-severity vulnerability in n/a, published on 1 Jan 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ConnMan 1.3 on Tizen continues to list the bluetooth service after offline mode has been enabled, which might allow remote attackers to obtain sensitive information via Bluetooth packets.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2012-6459?

It affects 1 product.


Products: Intel Connman.

## How do I fix CVE-2012-6459?

Apply the vendor's patch.

## Is CVE-2012-6459 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-28488](https://insights.sbomify.com/CVE-2023-28488/): Memory corruption in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-6459 and fix it if it is affected.

What it is: CVE-2012-6459 is a medium-severity vulnerability in n/a, published on 1 Jan 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-2012-6459 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-2012-6459/ (Markdown: https://insights.sbomify.com/CVE-2012-6459/index.md)
```

## Sources

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

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