# CVE-2013-0437: Other in n/a

> Remote attackers can compromise confidentiality, integrity, and availability in Oracle Java SE via unspecified 2D vectors, requiring user interaction.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 2 Feb 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-q94x-7w93-7vv3

## What is CVE-2013-0437?

CVE-2013-0437 is a critical vulnerability in Oracle Javafx, published on 2 Feb 2013. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 through Update 11 and JavaFX 2.2.4 and earlier allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to 2D.

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

It affects 3 products.


Products: Oracle Javafx, Oracle Jdk, Oracle Jre.

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

Upgrade to a fixed version.

## Is CVE-2013-0437 being exploited?

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

## Other vulnerabilities in Oracle Javafx

- [CVE-2015-2638](https://insights.sbomify.com/CVE-2015-2638/): Other in n/a (critical 10.0)
- [CVE-2013-5843](https://insights.sbomify.com/CVE-2013-5843/): Memory corruption in n/a (critical 10.0)
- [CVE-2013-2414](https://insights.sbomify.com/CVE-2013-2414/): Other in n/a (critical 10.0)
- [CVE-2013-2427](https://insights.sbomify.com/CVE-2013-2427/): Other in n/a (critical 10.0)
- [CVE-2013-2428](https://insights.sbomify.com/CVE-2013-2428/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-0437 is a critical vulnerability in Oracle Javafx, published on 2 Feb 2013. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2013-0437 in the wild and no public exploit code.

Affected product: Oracle Javafx. 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-0437/ (Markdown: https://insights.sbomify.com/CVE-2013-0437/index.md)
```

## Sources

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

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