# CVE-2024-34490: Path traversal in n/a

> Local attackers can exploit predictable temporary file names in Maxima's plotting features to execute arbitrary code or escalate privileges.

- **Severity:** Medium 5.1 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** DEBIAN-CVE-2024-34490, GHSA-gpc9-w434-fvwx, UBUNTU-CVE-2024-34490

## What is CVE-2024-34490?

CVE-2024-34490 is a medium-severity path traversal vulnerability in n/a, published on 5 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Maxima through 5.47.0 before 51704c, the plotting facilities make use of predictable names under /tmp. Thus, the contents may be controlled by a local attacker who can create files in advance with these names. This affects, for example, plot2d.

Weakness: CWE-377 (DEPRECATED: Insecure Temporary File)

## Which versions are affected by CVE-2024-34490?


## How do I fix CVE-2024-34490?

Upgrade to a fixed version.

## Is CVE-2024-34490 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-34490 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-34490 and fix it if it is affected.

What it is: CVE-2024-34490 is a medium-severity path traversal vulnerability in n/a, published on 5 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-34490 exists.

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

## Sources

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

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