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

> Physically proximate attackers can tamper with Samsung's remote tracking feature to defeat product recovery efforts by manipulating location data.

- **Severity:** Low 3.3 (`AV:A/AC:L/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:** No
- **Published:** 31 Dec 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-9q5c-26vg-42hp

## What is CVE-2012-6337?

CVE-2012-6337 is a low-severity vulnerability in n/a, published on 31 Dec 2012. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Track My Mobile feature in the SamsungDive subsystem for Android on Samsung Galaxy devices shows the activation of remote tracking, which might allow physically proximate attackers to defeat a product-recovery effort by tampering with this feature or its location data.

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

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

It affects 1 product.


Products: Samsung Samsungdive.

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

No fix has been published for CVE-2012-6337 yet. Limit exposure of the affected software until one is available.

## Is CVE-2012-6337 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-6334](https://insights.sbomify.com/CVE-2012-6334/): Security feature bypass in n/a (low 2.9)

## Fix prompt for AI coding agents

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

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

## Sources

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

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