# CVE-2014-2893: Path traversal in n/a

> Local attackers can exploit predictable temporary directory names in Clang's scan-build to read sensitive information or overwrite arbitrary files via symlink attacks.

- **Severity:** Low 1.9 (`AV:L/AC:M/Au:N/C:P/I:N/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:** 23 Apr 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-rg9j-qf6h-jpwg

## What is CVE-2014-2893?

CVE-2014-2893 is a low-severity path traversal vulnerability in Opensuse Opensuse, published on 23 Apr 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The GetHTMLRunDir function in the scan-build utility in Clang 3.5 and earlier allows local users to obtain sensitive information or overwrite arbitrary files via a symlink attack on temporary directories with predictable names.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2014-2893?

It affects 2 products.


Products: Llvm Clang, Opensuse Opensuse.

## How do I fix CVE-2014-2893?

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

## Is CVE-2014-2893 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-2893 and fix it if it is affected.

What it is: CVE-2014-2893 is a low-severity path traversal vulnerability in Opensuse Opensuse, published on 23 Apr 2014. 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-2014-2893 in the wild and no public exploit code.

Affected product: Opensuse Opensuse. 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-2014-2893/ (Markdown: https://insights.sbomify.com/CVE-2014-2893/index.md)
```

## Sources

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

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