# CVE-2013-2035: Improper Control of Generation of Code in HawtJNI

> Local attackers can execute arbitrary Java code by exploiting a race condition in HawtJNI's temporary file handling.

- **Severity:** Medium 4.4 (`AV:L/AC:M/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:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-2035, GHSA-49j7-qghp-5wj8, MGASA-2014-0461, UBUNTU-CVE-2013-2035

## What is CVE-2013-2035?

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

### Official description

Race condition in hawtjni-runtime/src/main/java/org/fusesource/hawtjni/runtime/Library.java in HawtJNI before 1.8, when a custom library path is not specified, allows local users to execute arbitrary Java code by overwriting a temporary JAR file with a predictable name in /tmp.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

2 open source packages ship an affected version, including org.fusesource.hawtjni:hawtjni-runtime. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.fusesource.hawtjni:hawtjni-runtime` | Maven | All versions | 1.8 |
| `org.fusesource.hawtjni:hawtjni-runtime` | Maven | All versions | 1.8 |

Products: Redhat Hawtjni.

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

Upgrade org.fusesource.hawtjni:hawtjni-runtime to 1.8 or later.

## Is CVE-2013-2035 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-2035 is a medium-severity vulnerability in n/a, published on 28 Aug 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-2013-2035 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.fusesource.hawtjni:hawtjni-runtime (Maven): affected all versions; fixed in 1.8
- org.fusesource.hawtjni:hawtjni-runtime (Maven): affected all versions; fixed in 1.8

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-2035/ (Markdown: https://insights.sbomify.com/CVE-2013-2035/index.md)
```

## Sources

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

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