How severe is CVE-2014-8114?

No CVSS score has been assigned to CVE-2014-8114 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2014-8114?

CVE-2014-8114 affects the following packages: org.uberfire:uberfire-parent (Maven). Ecosystems affected: Maven.

How do I fix CVE-2014-8114?

The records we use list no patched version of org.uberfire:uberfire-parent for CVE-2014-8114. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2014-8114 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.uberfire:uberfire-parent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2014-8114 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2014-8114 actively exploited in the wild?

No public exploit code has been indexed for CVE-2014-8114 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2014-8114?

CVE-2014-8114 has an EPSS (Exploit Prediction Scoring System) score of 3.1%, placing it in the 88th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2014-8114?

CVE-2014-8114 is classified as CWE-264 (CWE-264). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2014-8114 published, and has it been updated?

CVE-2014-8114 was published on May 14, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2014-8114 — uberfire-parent

Fix: uberfire/uberfire@21ec50e

CVE-2014-8114 is a CWE-264 vulnerability in org.uberfire:uberfire-parent. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

UberFire Framework Improperly Restricts Paths

Published

May 14, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

3.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs88th percentile — riskier than 88% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕org.uberfire:uberfire-parent

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.uberfire:uberfire-parent`	≥ 0.3.0.Beta5	No fix

Affected Products

1 product · 4 configurations

Application

uberfireredhat

4 versions

0.3.00.3.10.3.20.3.3

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.uberfire:uberfire-parent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of org.uberfire:uberfire-parent for CVE-2014-8114. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Product	Fixed in	Advisory
Red Hat JBoss BPMS 6.0	`uberfire`	RHSA-2015:0234
Red Hat JBoss BRMS 6.0	`uberfire`	RHSA-2015:0235

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-8114 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works