How severe is CVE-2012-3544?

No CVSS score has been assigned to CVE-2012-3544 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2012-3544?

CVE-2012-3544 affects the following packages: org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven). Ecosystems affected: Maven.

How do I fix CVE-2012-3544?

Update org.apache.tomcat:tomcat to 6.0.37 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-3544 is resolved across your whole dependency graph.

How do I detect CVE-2012-3544 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2012-3544 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2012-3544 actively exploited in the wild?

No public exploit code has been indexed for CVE-2012-3544 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2012-3544?

CVE-2012-3544 has an EPSS (Exploit Prediction Scoring System) score of 11.0%, placing it in the 96th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2012-3544?

CVE-2012-3544 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2012-3544 published, and has it been updated?

CVE-2012-3544 was published on May 14, 2022 and was last updated on April 12, 2025. 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

CVE-2012-3544 — tomcat

CVE-2012-3544 is a Improper Input Validation vulnerability in org.apache.tomcat:tomcat. EPSS puts its 30-day exploitation probability at 11.0% (96th percentile). A fix is available for org.apache.tomcat:tomcat — see the affected versions and patch details below.

Apache Tomcat Vulnerable to Denial of Service (DoS) via Improper Handling of chunk extensions

Published

May 14, 2022

Updated

Apr 12, 2025

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 30, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2012-3544.

EPSS Exploitation Probability

via FIRST.org ↗

11.0%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs96th percentile — riskier than 96% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat

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

Apache Tomcat 6.x before 6.0.37 and 7.x before 7.0.30 does not properly handle chunk extensions in chunked transfer coding, which allows remote attackers to cause a denial of service by streaming data.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 6.0.0&&< 6.0.37	6.0.37`org.apache.tomcat:tomcat:6.0.37`
☕Maven	`org.apache.tomcat:tomcat`	≥ 7.0.0&&< 7.0.30	7.0.30`org.apache.tomcat:tomcat:7.0.30`

Affected Products

1 product · 72 configurations

Application

tomcatapache

59 versions

6.06.0.06.0.16.0.26.0.36.0.46.0.56.0.66.0.76.0.86.0.96.0.10

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.tomcat:tomcat to 6.0.37 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-3544 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

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

This flaw affects Apache Tomcat 6.0.30 - 6.0.36 and 7.0.0 - 7.0.29. It does not affect JBoss Web.

Product	Fixed in	Advisory
Red Hat JBoss Enterprise Web Server 2 for RHEL 5	`apache-commons-daemon-eap6-1:1.0.15-4.redhat_1.ep6.el5`	RHSA-2013:1011
Red Hat JBoss Enterprise Web Server 2 for RHEL 6	`apache-commons-daemon-eap6-1:1.0.15-4.redhat_1.ep6.el6`	RHSA-2013:1012
Red Hat JBoss Web Server 2.0	see advisory	RHSA-2013:1013

Ubuntu

USN-1841-1Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2012-3544 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works