TomcatWeb server / proxy · Apache

CVE-2014-0075

MEDIUM · 5.0 CVSS v2.0 Published 2014-05-31

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

59/100

Remediation priority · Elevated

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Integer overflow in the parseChunkHeader function in java/org/apache/coyote/http11/filters/ChunkedInputFilter.java in Apache Tomcat before 6.0.40, 7.x before 7.0.53, and 8.x before 8.0.4 allows remote attackers to cause a denial of service (resource consumption) via a malformed chunk size in chunked transfer coding of a request during the streaming of data.

Technical summary

dbcve analysis · high confidence

Integer overflow vulnerability in Apache Tomcat's ChunkedInputFilter.java parseChunkHeader function allows remote attackers to cause denial of service by sending malformed chunk sizes in chunked transfer coding, leading to excessive resource consumption.

MitigationUpgrade Apache Tomcat to version 6.0.40 or higher, 7.0.53 or higher, or 8.0.4 or higher to patch the integer overflow vulnerability in chunked input processing.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

TomcatWeb server / proxy

Affected:= 7.0.0= 7.0.1= 7.0.2= 7.0.3= 7.0.4= 7.0.5= 7.0.6= 7.0.7= 7.0.8= 7.0.9= 7.0.10= 7.0.11

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Authentication: None
Confidentiality: None
Integrity: None
Availability: Partial

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

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Determine Apache Tomcat version

Locate the Tomcat installation and check the version. Common methods: inspect the server.xml banner, check catalina.jar version via 'java -jar catalina.jar version', or look for a RELEASE-NOTES file in the Tomcat home directory.

Affected if The installed version is Apache Tomcat 7.0.0 through 7.0.11 inclusive
Identify if chunked transfer encoding is in use

Review the web application configuration and server.xml for HTTP responses using 'Transfer-Encoding: chunked'. This can also be observed in HTTP traffic logs or by checking application code that explicitly sets chunked encoding.

Affected if Chunked transfer encoding is enabled or used by any deployed application
Verify the HTTP connector is exposed

Examine server.xml in the conf directory and locate the Connector definitions. Confirm the HTTP connector is active and listening on a network port.

Affected if An HTTP connector is configured and reachable over the network, enabling external attackers to send malformed chunked requests

If Apache Tomcat 7.0.0-7.0.11 is running with an exposed HTTP connector and chunked transfer encoding is in use, the environment is vulnerable to the integer overflow DoS via malformed chunk sizes.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Upgrade Apache Tomcat to version 6.0.40 or higher, 7.0.53 or higher, or 8.0.4 or higher to patch the integer overflow vulnerability in chunked input processing.

Fix this in Tomcat Scoped from the published advisory

Consultation2.0 h
Implementation3.0 h
Testing4.0 h
Review / QA1.0 h

10.0 hours of engineering $1,720

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2014-0075 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-0075 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2014-0075?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsA vendor remedy is published

Severity 5.0 Medium

Exploit likelihood EPSS, next 30 days 20.1%

Affects: Tomcat

Remediation

Need this fixed?

Fix this in Tomcat 10 hrs · Low

Typical engagement from $1,720

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2014-0075 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References