How severe is GHSA-m394-8rww-3jr7?

GHSA-m394-8rww-3jr7 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-m394-8rww-3jr7?

GHSA-m394-8rww-3jr7 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-m394-8rww-3jr7?

Update org.eclipse.jetty:jetty-server to 9.4.37 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m394-8rww-3jr7 is resolved across your whole dependency graph.

How do I detect GHSA-m394-8rww-3jr7 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-m394-8rww-3jr7 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.

How does O3 Security protect against GHSA-m394-8rww-3jr7?

O3 pinpoints whether GHSA-m394-8rww-3jr7 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-m394-8rww-3jr7 actively exploited in the wild?

Yes. There are 2 known exploit references for GHSA-m394-8rww-3jr7, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What type of vulnerability is GHSA-m394-8rww-3jr7?

GHSA-m394-8rww-3jr7 is classified as CWE-407 (CWE-407), Uncontrolled Resource Consumption (CWE-400). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-m394-8rww-3jr7 published, and has it been updated?

GHSA-m394-8rww-3jr7 was published on March 10, 2021 and was last updated on July 8, 2026. 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

MEDIUM severity

GHSA-m394-8rww-3jr7

MEDIUM

GHSA-m394-8rww-3jr7 is a medium-severity (CVSS 5.3) CWE-407 vulnerability in org.eclipse.jetty:jetty-server. 2 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-m394-8rww-3jr7 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

DOS vulnerability for Quoted Quality CSV headers

Also known asBIT-nifi-2020-27223BIT-solr-2020-27223BIT-spark-2020-27223CVE-2020-27223

Published

Mar 10, 2021

Updated

Jul 8, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

2 known

Exploitation data as of Jul 8, 2026 · OSV.dev, NVD, 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

Impact

When Jetty handles a request containing request headers with a large number of “quality” (i.e. q) parameters (such as what are seen on the Accept, Accept-Encoding, and Accept-Language request headers), the server may enter a denial of service (DoS) state due to high CPU usage while sorting the list of values based on their quality values. A single request can easily consume minutes of CPU time before it is even dispatched to the application.

The only features within Jetty that can trigger this behavior are:

Default Error Handling - the Accept request header with the QuotedQualityCSV is used to determine what kind of content to send back to the client (html, text, json, xml, etc)
StatisticsServlet - uses the Accept request header with the QuotedQualityCSV to determine what kind of content to send back to the client (xml, json, text, html, etc)
HttpServletRequest.getLocale() - uses the Accept-Language request header with the QuotedQualityCSV to determine which “preferred” language is returned on this call.
HttpservletRequest.getLocales() - is similar to the above, but returns an ordered list of locales based on the quality values on the Accept-Language request header.
DefaultServlet - uses the Accept-Encoding request header with the QuotedQualityCSV to determine which kind of pre-compressed content should be sent back for static content (content that is not matched against a url-pattern in your web app)

Versions

QuotedQualityCSV was introduced to Jetty 9.3.9.v20160517 and the bug that introduced the vulnerability was in 9.4.6.v20170531.

Currently, known vulnerable versions include:

9.4.6.v20170531 thru to 9.4.36.v20210114
10.0.0
11.0.0

Workarounds

Quality ordered values are used infrequently by jetty so they can be avoided by:

Do not use the default error page/handler.
Do not deploy the StatisticsServlet exposed to the network
Do not call getLocale API
Do not enable precompressed static content in the DefaultServlet

Patches

All patches are available for download from the Eclipse Jetty website at https://www.eclipse.org/jetty/download.php

9.4.37.v20210219 and greater
10.0.1 and greater
11.0.1 and greater

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.eclipse.jetty:jetty-server`	≥ 9.4.6&&< 9.4.37	9.4.37
☕Maven	`org.eclipse.jetty:jetty-server`	≥ 10.0.0&&< 10.0.1	10.0.1
☕Maven	`org.eclipse.jetty:jetty-server`	≥ 11.0.0&&< 11.0.1	11.0.1

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

In Eclipse Jetty 9.4.6.v20170531 to 9.4.36.v20210114 (inclusive), 10.0.0…

github.comGithubMar 2021

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.eclipse.jetty:jetty-server to 9.4.37 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m394-8rww-3jr7 is resolved across your whole dependency graph.
Workarounds
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.
How O3 protects you
O3 pinpoints whether GHSA-m394-8rww-3jr7 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-m394-8rww-3jr7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 HatModerate

In OpenShift Container Platform (OCP), the Hive/Presto/Hadoop components that comprise the OCP Metering stack, ship the vulnerable version of jetty. Since the release of OCP 4.6, the Metering product has been deprecated [1], hence the affected components are marked as wontfix. This may be fixed in the future. [1]…

RHSA-2021:2689Red Hat AMQ 7.8.2 RHSA-2021:3700Red Hat AMQ 7.9.0 RHSA-2021:5134Red Hat Fuse 7.10 RHSA-2021:4767Red Hat Integration Camel Quarkus 2 RHBA-2021:2854Red Hat Migration Toolkit for Containers 1.4 RHSA-2021:2517Red Hat OpenShift Container Platform 3.11 RHSA-2021:2431Red Hat OpenShift Container Platform 4.5 RHSA-2021:2499Red Hat OpenShift Container Platform 4.6

Frequently Asked Questions

### Impact When Jetty handles a request containing request headers with a large number of “quality” (i.e. q) parameters (such as what are seen on the `Accept`, `Accept-Encoding`, and `Accept-Language` request headers), the server may enter a denial of service (DoS) state due to high CPU usage while sorting the list of values based on their quality values. A single request can easily consume minutes of CPU time before it is even dispatched to the application. The only features within Jetty that can trigger this behavior are: - Default Error Handling - the `Accept` request header with the `Qu

O3 Security · Impact-Aware SCA

Is GHSA-m394-8rww-3jr7 in your dependencies?

O3 detects GHSA-m394-8rww-3jr7 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-m394-8rww-3jr7

Real-World Exposure

Description

Impact

Versions

Workarounds

Patches

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Fixing This On Your OS

Frequently Asked Questions

Is GHSA-m394-8rww-3jr7 in your dependencies?