Skip to content

Directory exposure in jetty

Low severity GitHub Reviewed Published Apr 1, 2021 in jetty/jetty.project • Updated Feb 1, 2023

Package

maven org.eclipse.jetty:jetty-deploy (Maven)

Affected versions

>= 9.4.32, < 9.4.39
>= 10.0.0, < 10.0.2
>= 11.0.0, < 11.0.2

Patched versions

9.4.39
10.0.2
11.0.2

Description

Impact

If the ${jetty.base} directory or the ${jetty.base}/webapps directory is a symlink (soft link in Linux), the contents of the ${jetty.base}/webapps directory may be deployed as a static web application, exposing the content of the directory for download.

For example, the problem manifests in the following ${jetty.base}:

demo-base/
├── etc
├── lib
├── resources
├── start.d
├── deploy
│   └── async-rest.war
└── webapps -> deploy

Workarounds

Do not use a symlink

References

@waynebeaton waynebeaton published to jetty/jetty.project Apr 1, 2021
Published by the National Vulnerability Database Apr 1, 2021
Reviewed Apr 2, 2021
Published to the GitHub Advisory Database Apr 6, 2021
Last updated Feb 1, 2023

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N

EPSS score

0.059%
(26th percentile)

Weaknesses

CVE ID

CVE-2021-28163

GHSA ID

GHSA-j6qj-j888-vvgq

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.