Security readout for executives and security teams
Plain-English summary
This is a denial-of-service issue in Eclipse Jetty. Certain malformed HTTP request headers can make affected Jetty versions spend minutes of CPU time parsing header quality values, reducing service availability. The sources do not show data theft, code execution, or active exploitation.
Executive priority
Treat as a moderate availability risk. It is not described as data compromise, but affected public services could be degraded by CPU exhaustion. Patch during the next normal security maintenance window, faster for exposed production systems.
Technical view
Affected Jetty versions process multiple Accept headers with many q parameters inefficiently, causing high CPU usage and availability impact. The CVE maps to CWE-407 and CVSS 3.1 score 5.2, with no confidentiality or integrity impact stated in the source bundle.
Likely exposure
Exposure is most likely in Java services or embedded products running Jetty 9.4.6.v20170531 through 9.4.36.v20210114, 10.0.0, or 11.0.0. Transitive Jetty use matters because Apache project threads show dependency upgrades for this CVE.
Exploitation context
The bundle does not indicate CISA KEV listing or confirmed active exploitation. The attack condition described is request handling with multiple Accept headers and many q parameters, leading to CPU exhaustion rather than compromise.
Researcher notes
Evidence is strongest for affected Jetty ranges and DoS behavior. Fix details are not fully present in the bundle, so remediation should follow Eclipse Jetty GHSA guidance and downstream vendor advisories rather than assuming a single safe version.
Mitigation direction
- Inventory direct and transitive Eclipse Jetty dependencies.
- Upgrade Jetty to a release outside the affected ranges using Eclipse guidance.
- Prioritize internet-facing or latency-sensitive Jetty services first.
- Review downstream platform advisories where Jetty is bundled.
- Monitor CPU saturation and unusual Accept header patterns.
Validation and detection
- Check dependency manifests and runtime classpaths for Jetty versions.
- Confirm deployed artifacts no longer contain affected Jetty releases.
- Review SBOM and dependency scanner results for CVE-2020-27223.
- Validate affected services have CPU and request-rate monitoring.
- Document any exception with compensating controls and owner.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-407: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2020-27223 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H1.53.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.2MediumVector: CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=571128CVE reference · x_refsource_CONFIRM
- https://github.com/eclipse/jetty.project/security/advisories/GHSA-m394-8rww-3jr7CVE reference · x_refsource_CONFIRM
- [karaf-user] 20210301 Re: Jetty security defectCVE reference · mailing-list, x_refsource_MLIST
- [kafka-jira] 20210302 [GitHub] [kafka] dongjinleekr commented on pull request #10245: KAFKA-12400: Upgrade jetty to fix CVE-2020-27223CVE reference · mailing-list, x_refsource_MLIST
- [kafka-dev] 20210302 [jira] [Created] (KAFKA-12400) Upgrade jetty to fix CVE-2020-27223CVE reference · mailing-list, x_refsource_MLIST
- [kafka-jira] 20210302 [GitHub] [kafka] dongjinleekr opened a new pull request #10245: KAFKA-12400: Upgrade jetty to fix CVE-2020-27223CVE reference · mailing-list, x_refsource_MLIST
- [kafka-jira] 20210302 [jira] [Created] (KAFKA-12400) Upgrade jetty to fix CVE-2020-27223CVE reference · mailing-list, x_refsource_MLIST
- [druid-commits] 20210302 [GitHub] [druid] a2l007 opened a new pull request #10937: Upgrade jetty to latest versionCVE reference · mailing-list, x_refsource_MLIST
- [kafka-jira] 20210302 [GitHub] [kafka] ableegoldman commented on pull request #10245: KAFKA-12400: Upgrade jetty to fix CVE-2020-27223CVE reference · mailing-list, x_refsource_MLIST
- [kafka-dev] 20210302 [jira] [Resolved] (KAFKA-12400) Upgrade jetty to fix CVE-2020-27223CVE reference · mailing-list, x_refsource_MLIST
- [kafka-jira] 20210302 [jira] [Resolved] (KAFKA-12400) Upgrade jetty to fix CVE-2020-27223CVE reference · mailing-list, x_refsource_MLIST
- [kafka-commits] 20210302 [kafka] branch 2.7 updated: KAFKA-12400: Upgrade jetty to fix CVE-2020-27223CVE reference · mailing-list, x_refsource_MLIST
- [kafka-commits] 20210302 [kafka] branch 2.8 updated: KAFKA-12400: Upgrade jetty to fix CVE-2020-27223CVE reference · mailing-list, x_refsource_MLIST
- [kafka-jira] 20210302 [GitHub] [kafka] omkreddy closed pull request #10245: KAFKA-12400: Upgrade jetty to fix CVE-2020-27223CVE reference · mailing-list, x_refsource_MLIST
- [kafka-commits] 20210302 [kafka] branch 2.6 updated: KAFKA-12400: Upgrade jetty to fix CVE-2020-27223CVE reference · mailing-list, x_refsource_MLIST
- [activemq-gitbox] 20210303 [GitHub] [activemq] ehossack-aws opened a new pull request #616: Upgrade to Jetty 9.4.38.v20210224CVE reference · mailing-list, x_refsource_MLIST
- [zookeeper-notifications] 20210307 [GitHub] [zookeeper] ztzg opened a new pull request #1623: ZOOKEEPER-4233: dependency-check:check failing - Jetty 9.4.35.v20201120 - CVE-2020-27223CVE reference · mailing-list, x_refsource_MLIST
- [zookeeper-notifications] 20210307 [GitHub] [zookeeper] ztzg commented on pull request #1623: ZOOKEEPER-4233: dependency-check:check failing - Jetty 9.4.35.v20201120 - CVE-2020-27223CVE reference · mailing-list, x_refsource_MLIST
- [zookeeper-issues] 20210307 [jira] [Updated] (ZOOKEEPER-4233) dependency-check:check failing - Jetty 9.4.35.v20201120 - CVE-2020-27223CVE reference · mailing-list, x_refsource_MLIST
- [zookeeper-issues] 20210307 [jira] [Created] (ZOOKEEPER-4233) dependency-check:check failing - Jetty 9.4.35.v20201120 - CVE-2020-27223CVE reference · mailing-list, x_refsource_MLIST
- [zookeeper-notifications] 20210307 [GitHub] [zookeeper] ztzg opened a new pull request #1624: ZOOKEEPER-4233: dependency-check:check failing - Jetty 9.4.35.v20201120 - CVE-2020-27223CVE reference · mailing-list, x_refsource_MLIST
- [zookeeper-notifications] 20210307 [GitHub] [zookeeper] ztzg opened a new pull request #1625: ZOOKEEPER-4233: dependency-check:check failing - Jetty 9.4.35.v20201120 - CVE-2020-27223CVE reference · mailing-list, x_refsource_MLIST
- [zookeeper-dev] 20210307 [jira] [Created] (ZOOKEEPER-4233) dependency-check:check failing - Jetty 9.4.35.v20201120 - CVE-2020-27223CVE reference · mailing-list, x_refsource_MLIST
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Inefficient Algorithmic Complexity
Inefficient Algorithmic Complexity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
