How severe is CVE-2014-0050?

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

Which packages are affected by CVE-2014-0050?

CVE-2014-0050 affects the following packages: commons-fileupload:commons-fileupload (Maven), org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven). Ecosystems affected: Maven.

How do I fix CVE-2014-0050?

Update commons-fileupload:commons-fileupload to 1.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-0050 is resolved across your whole dependency graph.

How do I detect CVE-2014-0050 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for commons-fileupload:commons-fileupload. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2014-0050?

O3 pinpoints whether CVE-2014-0050 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2014-0050 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2014-0050, including 1 documented proof-of-concept exploit on Exploit-DB and 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What type of vulnerability is CVE-2014-0050?

CVE-2014-0050 is classified as CWE-264 (CWE-264). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2014-0050 published, and has it been updated?

CVE-2014-0050 was published on April 1, 2014 and was last updated on April 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

CVE-2014-0050

CVE-2014-0050 is a CWE-264 vulnerability in commons-fileupload:commons-fileupload. 3 public exploit references exist, so weaponization risk is real. O3 Security confirms whether CVE-2014-0050 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Commons FileUpload Denial of service vulnerability

Also known asGHSA-xx68-jfcg-xmmf

Published

Apr 1, 2014

Updated

Apr 16, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

3 known

Blast Radius

3 pkgs affected

☕commons-fileupload:commons-fileupload☕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

MultipartStream.java in Apache Commons FileUpload before 1.3.1, as used in Apache Tomcat, JBoss Web, and other products, allows remote attackers to cause a denial of service (infinite loop and CPU consumption) via a crafted Content-Type header that bypasses a loop's intended exit conditions.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`commons-fileupload:commons-fileupload`	all versions	1.3.1
☕Maven	`org.apache.tomcat:tomcat`	≥ 8.0.0-RC1&&< 8.0.3	8.0.3
☕Maven	`org.apache.tomcat:tomcat`	≥ 7.0.0&&< 7.0.52	7.0.52

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-31615dosmultiple✓ Verified

Apache Commons FileUpload and Apache Tomcat - Denial of Service

by Trustwave's SpiderLabs · Feb 12, 2014

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for commons-fileupload:commons-fileupload. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update commons-fileupload:commons-fileupload to 1.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-0050 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2014-0050 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2014-0050. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-0050 in your dependencies?

O3 detects CVE-2014-0050 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works