LiveActive security incident?Get immediate response
CVE Record

CVE-2013-4286: 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 con...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

Older Apache Tomcat versions mishandle conflicting HTTP length headers. A remote attacker could exploit this parsing mismatch to smuggle requests through affected HTTP or AJP connectors. The main business concern is hidden request handling that bypasses expected front-end controls in exposed or proxied Tomcat services. Exposure is most likely where legacy Tomcat is internet-facing, behind reverse proxies, or embedded in vendor products that bundle Tomcat. The source bundle lists downstream advisories from Red Hat, Debian, VMware, Oracle, IBM, HP, Mandriva, and Mageia, so inventory should include packaged and appliance-based Tomcat deployments. Address during near-term patching, with faster action for exposed or proxied legacy Tomcat. The lack of KEV evidence lowers emergency urgency, but request smuggling can undermine trust boundaries and may affect bundled enterprise products that are easy to overlook. Mitigation focus: Upgrade Tomcat to 6.0.39, 7.0.47, 8.0.0-RC3, or later supported releases.; Apply relevant vendor security updates for bundled or distribution-managed Tomcat packages.; Check Apache and product-vendor guidance before changing connector behavior..

Prepared

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.

cve · low confidence lookup

CVE-2013-4286 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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