# CVE-2007-5936: Race condition in n/a

> Local attackers can exploit a race condition in dvips to read or modify sensitive temporary files during document processing.

- **Severity:** Low 3.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Nov 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-5936, GHSA-h8g9-jwcj-22mf

## What is CVE-2007-5936?

CVE-2007-5936 is a low-severity vulnerability in n/a, published on 13 Nov 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

dvips in teTeX and TeXlive 2007 and earlier allows local users to obtain sensitive information and modify certain data by creating certain temporary files before they are processed by dviljk, which can then be read or modified in place.

Weakness: CWE-264

## Which versions are affected by CVE-2007-5936?

It affects 2 products.


Products: Tetex Tetex, Tug Texlive 2007.

## How do I fix CVE-2007-5936?

Upgrade to a fixed version.

## Is CVE-2007-5936 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-5935](https://insights.sbomify.com/CVE-2007-5935/): Memory corruption in n/a (medium 6.8)
- [CVE-2007-5937](https://insights.sbomify.com/CVE-2007-5937/): Memory corruption in n/a (medium 6.8)
- [CVE-2001-0906](https://insights.sbomify.com/CVE-2001-0906/): Path traversal in n/a (medium 6.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-5936 and fix it if it is affected.

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

## Sources

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

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