# CVE-2022-40299: Path traversal in n/a

> Local attackers can escalate privileges by exploiting predictable temporary file paths in Singular's sdb.cc interface.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 9 Sep 2022
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2022-40299, GHSA-92qh-jj8j-74cv, JLSEC-2026-289, UBUNTU-CVE-2022-40299

## What is CVE-2022-40299?

CVE-2022-40299 is a high-severity path traversal vulnerability in n/a, published on 9 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Singular before 4.3.1, a predictable /tmp pathname is used (e.g., by sdb.cc), which allows local users to gain the privileges of other users via a procedure in a file under /tmp. NOTE: this CVE Record is about sdb.cc and similar files in the Singular interface that have predictable /tmp pathnames; this CVE Record is not about the lack of a safe temporary-file creation capability in the Singular language.

Weakness: CWE-330 (Use of Insufficiently Random Values)

## Which versions are affected by CVE-2022-40299?

It affects 1 product.


Products: Singular Singular.

## How do I fix CVE-2022-40299?

Upgrade to a fixed version.

## Is CVE-2022-40299 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-40299 and fix it if it is affected.

What it is: CVE-2022-40299 is a high-severity path traversal vulnerability in n/a, published on 9 Sep 2022. 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-2022-40299 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-2022-40299/ (Markdown: https://insights.sbomify.com/CVE-2022-40299/index.md)
```

## Sources

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

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