LiveActive security incident?Get immediate response
CVE Record

CVE-2022-42252: Apache Tomcat request smuggling via malformed content-length

If Apache Tomcat 8.5.0 to 8.5.82, 9.0.0-M1 to 9.0.67, 10.0.0-M1 to 10.0.26 or 10.1.0-M1 to 10.1.0 was configured to ignore invalid HTTP headers via setting rejectIllegalHeader to false (the default for 8.5.x only), Tomcat did not reject a request containing an invalid Content-Length header making a request smuggling attack possible if Tomcat was located behind a reverse proxy that also failed to reject the request with the invalid header.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Apache Tomcat could allow HTTP request smuggling when it accepts malformed Content-Length headers behind a reverse proxy that also fails to reject them. The risk is conditional, but serious because an attacker can potentially interfere with how requests are interpreted.

Executive priority

Treat as high priority for exposed Tomcat services behind proxies. The issue is configuration-dependent, so teams should quickly identify affected deployments before broader remediation work.

Technical view

CVE-2022-42252 is CWE-444 request smuggling in Apache Tomcat. It affects specified Tomcat 8.5, 9.0, 10.0, and 10.1 ranges when rejectIllegalHeader is false, with 8.5.x noted as defaulting that way, and when a reverse proxy also permits the malformed request.

Likely exposure

Internet-facing Tomcat applications behind reverse proxies are the primary concern, especially Tomcat 8.5.x deployments or any deployment with rejectIllegalHeader set to false.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. Exploitation requires a vulnerable Tomcat configuration and a reverse proxy that also fails to reject invalid Content-Length headers.

Researcher notes

Do not assume all Tomcat deployments are exposed. The key conditions are affected version range, rejectIllegalHeader=false, and a permissive reverse proxy. The provided sources do not include weaponization details or confirmed exploitation.

Mitigation direction

  • Upgrade Tomcat to a release outside the affected ranges using Apache guidance.
  • Ensure rejectIllegalHeader is not set to false.
  • Configure reverse proxies to reject malformed Content-Length headers.
  • Review Gentoo or distribution advisories if Tomcat came from an OS package.
  • Prioritize internet-facing reverse-proxy deployments first.

Validation and detection

  • Inventory Tomcat versions across production and staging.
  • Check Tomcat configuration for rejectIllegalHeader settings.
  • Confirm whether Tomcat is behind any reverse proxy or load balancer.
  • Validate proxy behavior for malformed Content-Length rejection without offensive testing.
  • Review access logs for unusual request parsing or routing anomalies.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-444: 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 lookup
cve · low confidence lookup

CVE-2022-42252 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2022-42252Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Apache Software FoundationApache Tomcat10.1.0-M1, 10.0.0-M1, 9.0.0-M1, 8.5.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-444 · source CWE mapping

Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')

Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.