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

> Local attackers can modify arbitrary files via a symlink attack on a temporary file in the Flite speech synthesis library.

- **Severity:** Low 3.3 (`AV:L/AC:M/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Jan 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-0027, GHSA-wp3x-6766-qrc3, MGASA-2014-0047

## What is CVE-2014-0027?

CVE-2014-0027 is a low-severity path traversal vulnerability in n/a, published on 26 Jan 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The play_wave_from_socket function in audio/auserver.c in Flite 1.4 allows local users to modify arbitrary files via a symlink attack on /tmp/awb.wav.  NOTE: some of these details are obtained from third party information.

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

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

It affects 1 product.


Products: Cmu Flite.

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

Apply the vendor's patch.

## Is CVE-2014-0027 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-0027 is a low-severity path traversal vulnerability in n/a, published on 26 Jan 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-0027 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-2014-0027/ (Markdown: https://insights.sbomify.com/CVE-2014-0027/index.md)
```

## Sources

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

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