How severe is GHSA-xc67-hjx6-cgg6?

GHSA-xc67-hjx6-cgg6 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-xc67-hjx6-cgg6?

GHSA-xc67-hjx6-cgg6 affects the following packages: org.eclipse.jetty:jetty-server (Maven), org.eclipse.jetty:jetty-server (Maven), org.eclipse.jetty:jetty-server (Maven). Ecosystems affected: Maven.

How do I fix GHSA-xc67-hjx6-cgg6?

Update org.eclipse.jetty:jetty-server to 9.2.28.v20190418 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xc67-hjx6-cgg6 is resolved across your whole dependency graph.

How do I detect GHSA-xc67-hjx6-cgg6 in my Maven dependencies?

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

How do I mitigate GHSA-xc67-hjx6-cgg6 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-xc67-hjx6-cgg6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-xc67-hjx6-cgg6 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 GHSA-xc67-hjx6-cgg6?

GHSA-xc67-hjx6-cgg6 has an EPSS (Exploit Prediction Scoring System) score of 5.9%, placing it in the 93th 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 GHSA-xc67-hjx6-cgg6?

GHSA-xc67-hjx6-cgg6 is classified as CWE-213 (CWE-213), Information Exposure (CWE-200). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-xc67-hjx6-cgg6 published, and has it been updated?

GHSA-xc67-hjx6-cgg6 was published on April 23, 2019 and was last updated on March 14, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Installation information leak in Eclipse Jetty (Medium 5.3)

EPSS Exploitation Probability

via FIRST.org ↗

5.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs93th percentile — riskier than 93% of all scored CVEsHighest risk

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

Real-World Exposure

3 pkgs affected

☕org.eclipse.jetty:jetty-server☕org.eclipse.jetty:jetty-server☕org.eclipse.jetty:jetty-server

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

In Eclipse Jetty version 7.x, 8.x, 9.2.27 and older, 9.3.26 and older, and 9.4.16 and older, the server running on any OS and Jetty version combination will reveal the configured fully qualified directory base resource location on the output of the 404 error for not finding a Context that matches the requested path. The default server behavior on jetty-distribution and jetty-home will include at the end of the Handler tree a DefaultHandler, which is responsible for reporting this 404 error, it presents the various configured contexts as HTML for users to click through to. This produced HTML includes output that contains the configured fully qualified directory base resource location for each context.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.eclipse.jetty:jetty-server`	≥ 7.0.0&&< 9.2.28.v20190418	9.2.28.v20190418`org.eclipse.jetty:jetty-server:9.2.28.v20190418`
☕Maven	`org.eclipse.jetty:jetty-server`	≥ 9.3.0&&< 9.3.27.v20190418	9.3.27.v20190418`org.eclipse.jetty:jetty-server:9.3.27.v20190418`
☕Maven	`org.eclipse.jetty:jetty-server`	≥ 9.4.0&&< 9.4.17.v20190418	9.4.17.v20190418`org.eclipse.jetty:jetty-server:9.4.17.v20190418`

Affected Products

26 products · 335 configurations

OS

debian linuxdebian

2 versions

9.010.0

Application

jettyeclipse

163 versions

7.0.07.0.17.0.27.1.07.1.17.1.27.1.37.1.47.1.57.1.67.2.07.2.1

OS

elementnetapp

all

Application

oncommand system managernetapp

≥ 3.0 && ≤ 3.1.3

range

Application

snap creator frameworknetapp

all

Application

snapcenternetapp

all

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.jetty:jetty-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.eclipse.jetty:jetty-server to 9.2.28.v20190418 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xc67-hjx6-cgg6 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

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 HatLow

This issue affects the versions of jetty which is embedded in the nutch package as shipped with Red Hat Satellite 5. The jetty server is not exposed, as such exploitation is difficult, Red Hat Product Security has rated this issue as having security impact of Low in the context of Red Hat Satellite 5. A future update…

Product	Fixed in	Advisory
Red Hat AMQ	`jetty`	RHSA-2020:0922
Red Hat AMQ 7.4.3	`jetty`	RHSA-2020:1445
Red Hat Fuse 7.6.0	see advisory	RHSA-2020:0983

Frequently Asked Questions

In Eclipse Jetty version 7.x, 8.x, 9.2.27 and older, 9.3.26 and older, and 9.4.16 and older, the server running on any OS and Jetty version combination will reveal the configured fully qualified directory base resource location on the output of the 404 error for not finding a Context that matches the requested path. The default server behavior on jetty-distribution and jetty-home will include at the end of the Handler tree a DefaultHandler, which is responsible for reporting this 404 error, it presents the various configured contexts as HTML for users to click through to. This produced HTML in

O3 Security · Impact-Aware SCA

Is GHSA-xc67-hjx6-cgg6 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

Installation information leak in Eclipse JettyGHSA-xc67-hjx6-cgg6

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is GHSA-xc67-hjx6-cgg6 in your dependencies?