# CVE-2023-29465: Path traversal in n/a

> A local attacker can overwrite files with another user's privileges by exploiting insecure temporary file handling in the FlintQS library.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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:** No
- **Published:** 6 Apr 2023
- **Updated:** 12 Feb 2025
- **Also known as:** DEBIAN-CVE-2023-29465, GHSA-p749-q5wf-mcpv, UBUNTU-CVE-2023-29465

## What is CVE-2023-29465?

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

### Official description

SageMath FlintQS 1.0 relies on pathnames under TMPDIR (typically world-writable), which (for example) allows a local user to overwrite files with the privileges of a different user (who is running FlintQS).

## Which versions are affected by CVE-2023-29465?

It affects 1 product.


Products: Sagemath Flintqs.

## How do I fix CVE-2023-29465?

No fix has been published for CVE-2023-29465 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-29465 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-29465 and fix it if it is affected.

What it is: CVE-2023-29465 is a medium-severity path traversal vulnerability in n/a, published on 6 Apr 2023. 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-2023-29465 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-2023-29465/ (Markdown: https://insights.sbomify.com/CVE-2023-29465/index.md)
```

## Sources

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

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