# CVE-2014-8114: UberFire Framework Improperly Restricts Paths

> Remote attackers can execute arbitrary code or read arbitrary files in the UberFire Framework due to improper path restrictions in upload and download servlets.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Feb 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-6h58-c7r7-g2hw

## What is CVE-2014-8114?

CVE-2014-8114 is a medium-severity path traversal vulnerability in n/a, published on 20 Feb 2015. It can be exploited over the network, with no action from the victim.

### Official description

The UberFire Framework 0.3.x does not properly restrict paths, which allows remote attackers to (1) execute arbitrary code by uploading crafted content to FileUploadServlet or (2) read arbitrary files via vectors involving FileDownloadServlet.

Weakness: CWE-264

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

2 open source packages ship an affected version, including org.uberfire:uberfire-parent. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.uberfire:uberfire-parent` | Maven | From 0.3.0.Beta5 to 0.3.1.Final | None |
| `org.uberfire:uberfire-parent` | Maven | From 0.3.0.Beta5 to 0.3.1.Final | None |

Products: Redhat Uberfire.

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

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

## Is CVE-2014-8114 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-8114 is a medium-severity path traversal vulnerability in n/a, published on 20 Feb 2015. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-8114 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.uberfire:uberfire-parent (Maven): affected from 0.3.0.Beta5 up to 0.3.1.Final; no fix listed
- org.uberfire:uberfire-parent (Maven): affected from 0.3.0.Beta5 up to 0.3.1.Final; no fix listed

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

## Sources

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

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