# CVE-2008-5827: Security feature bypass in n/a

> Remote attackers can execute arbitrary code on Nokia 6131 NFC phones by exploiting automatic JAR installation via crafted NDEF tags.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Jan 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2hvh-29rf-rgx7

## What is CVE-2008-5827?

CVE-2008-5827 is a high-severity vulnerability in n/a, published on 2 Jan 2009. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The Nokia 6131 Near Field Communication (NFC) phone with 05.12 firmware automatically installs software upon completing the download of a JAR file, which makes it easier for remote attackers to execute arbitrary code via a crafted URI record in an NDEF tag.

Weakness: CWE-16

## Which versions are affected by CVE-2008-5827?

It affects 1 product.


Products: Nokia 6131 Nfc.

## How do I fix CVE-2008-5827?

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

## Is CVE-2008-5827 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-5826](https://insights.sbomify.com/CVE-2008-5826/): Denial of service in n/a (high 7.8)
- [CVE-2008-5825](https://insights.sbomify.com/CVE-2008-5825/): Open redirect in n/a (low 2.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-5827 and fix it if it is affected.

What it is: CVE-2008-5827 is a high-severity vulnerability in n/a, published on 2 Jan 2009. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2008-5827 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-2008-5827/ (Markdown: https://insights.sbomify.com/CVE-2008-5827/index.md)
```

## Sources

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

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