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

> Remote authenticated users can compromise integrity in Oracle Java SE and JRockit via unspecified Javadoc vectors.

- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 16 Oct 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-cxh8-c38w-rhhm

## What is CVE-2013-5797?

CVE-2013-5797 is a low-severity vulnerability in Oracle Javafx, published on 16 Oct 2013. Any signed-in user can exploit it over the network.

### Official description

Unspecified vulnerability in Oracle Java SE 7u40 and earlier, Java SE 6u60 and earlier, Java SE 5.0u51 and earlier, JRockit R28.2.8 and earlier, JRockit R27.7.6 and earlier, and JavaFX 2.2.40 and earlier allows remote authenticated users to affect integrity via unknown vectors related to Javadoc.

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

It affects 6 products.


Products: Oracle Javafx, Oracle Jdk, Oracle Jre, Oracle Jrockit, Sun Jdk, Sun Jre.

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

Upgrade to a fixed version.

## Is CVE-2013-5797 being exploited?

There is no known exploitation of CVE-2013-5797 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-5797 and fix it if it is affected.

What it is: CVE-2013-5797 is a low-severity vulnerability in Oracle Javafx, published on 16 Oct 2013. Any signed-in user can exploit it over the network.
Exploitation: There is no known exploitation of CVE-2013-5797 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-5797/ (Markdown: https://insights.sbomify.com/CVE-2013-5797/index.md)
```

## Sources

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

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