Skip to content

UberFire Framework Improperly Restricts Paths

Moderate severity GitHub Reviewed Published May 14, 2022 to the GitHub Advisory Database • Updated Aug 16, 2023

Package

maven org.uberfire:uberfire-parent (Maven)

Affected versions

>= 0.3.0.Beta5, <= 0.3.1.Final

Patched versions

None

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.

References

Published by the National Vulnerability Database Feb 20, 2015
Published to the GitHub Advisory Database May 14, 2022
Reviewed Aug 16, 2023
Last updated Aug 16, 2023

Severity

Moderate

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(82nd percentile)

Weaknesses

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Learn more on MITRE.

CVE ID

CVE-2014-8114

GHSA ID

GHSA-6h58-c7r7-g2hw

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.