Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2013-4286

tomcat: multiple content-length header poisoning flaws

Overview

Published
26 Feb 2014
Modified
9 Oct 2026
Medium CVE
1 Registry packages
10 OS packages
2 Linux distributions
Yes Fix available

Description

Apache Tomcat before 6.0.39, 7.x before 7.0.47, and 8.x before 8.0.0-RC3, when an HTTP connector or AJP connector is used, does not properly handle certain inconsistent HTTP request headers, which allows remote attackers to trigger incorrect identification of a request's length and conduct request-smuggling attacks via (1) multiple Content-Length headers or (2) a Content-Length header and a "Transfer-Encoding: chunked" header. NOTE: this vulnerability exists because of an incomplete fix for CVE-2005-2090.

Source: OX vulnerability database

Severity

5.8 · MEDIUM

CVSS 2.0 base score, scored by NVD.

Access vector
Network
Access complexity
Medium
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
None

AV:N/AC:M/Au:N/C:P/I:P/A:N

Weakness: CWE-20

Affected packages · 1

Packages affected by CVE-2013-4286
EcosystemPackageVulnerableFixed in
Maven org.apache.tomcat:tomcat <6.0.39>=7.0.0, <7.0.47>=8.0.0-RC1, <8.0.0-RC3 6.0.397.0.478.0.0-RC3

Open a package to see all its vulnerabilities.

Operating systems · 2 fixes

Oracle Linux 1 release · 1 package

fixed 1
tomcat
Oracle Linux fixes for CVE-2013-4286
ReleasePackageFixed in
7 tomcat +9 7.0.42-5.el7_0

Red Hat 1 release · 1 package

fixed 1
tomcat
Red Hat fixes for CVE-2013-4286
ReleasePackageFixed inAdvisory
7 tomcat +9 0:7.0.42-5.el7_0 RHSA-2014:0686

References

Show all 77 references

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.