CVE-2013-4444 — Code Injection in Apache Software Foundation Tomcat
Unrestricted file upload vulnerability in Apache Tomcat 7.x before 7.0.40, in certain situations involving outdated java.io.File code and a custom JMX configuration, allows remote attackers to execute arbitrary code by uploading and accessing a JSP file.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 14% (30-day exploitation probability)+14
- Technical severity (medium)+3
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — tomcat.apache.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Apache Software Foundation Tomcat).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- Apply the fixed version or the patch documented under Remediation.
- EPSS ahead of 97% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Apache Software Foundation | Tomcat |
version 7.0.30version 7.0.21version 7.0.22version 7.0.23version 7.0.24version 7.0.25version 7.0.26version 7.0.27 and 30 moreversion 7.0.28version 7.0.29version 7.0.20version 7.0.31version 7.0.32version 7.0.33version 7.0.34version 7.0.35version 7.0.36version 7.0.37version 7.0.38version 7.0.11version 7.0.0version 7.0.0-betaversion 7.0.1version 7.0.2version 7.0.2-betaversion 7.0.3version 7.0.4version 7.0.4-betaversion 7.0.10≤ 7.0.39version 7.0.12version 7.0.13version 7.0.14version 7.0.15version 7.0.16version 7.0.17version 7.0.18version 7.0.19 |
Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 6.8 | CVSS 2.0 | Medium | 8.6 | 6.4 | nvd@nist.gov via NIST National Vulnerability Database |
AV:N/AC:M/Au:N/C:P/I:P/A:P (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 13.99%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Look for parameters with command/query metacharacters and unexpected child processes of the service.
Timeline
What happened to this CVE, newest first.
- 2026
- SSVC assessment updated
- Record published
- Fix documented
- CVSS changed · 6.8
- Source status changed · → Modified
- Record created in this database
- 2014
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
10 on the record
- tomcat.apache.org/security-7.html
- openwall.com/lists/oss-security/2014/10/24/12
- h20564.www2.hpe.com/portal/site/hpsc/public/kb/docDisplay
- www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html
- www.securitytracker.com/id/1030834
- www.securityfocus.com/bid/69728
- www.debian.org/security/2016/dsa-3447
- seclists.org/fulldisclosure/2021/Jan/23
- marc.info/
- archives.neohapsis.com/archives/bugtraq/2014-09/0075.html
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-55956 Apache Tomcat: Security constraints for default servlet ignored method Jun 29, 2026
- Critical CVE-2026-55276 Apache Tomcat: Logged effective web.xml is incomplete Jun 29, 2026
- Medium CVE-2026-55955 Apache Tomcat: EncryptInterceptor not protected against replay attacks Jun 29, 2026
- High CVE-2026-55957 Apache Tomcat: Authentication bypass with JNDIRealm and GSSAPI authenticated bind Jun 29, 2026
- Medium CVE-2026-50229 Apache Tomcat: XSS in number guess example Jun 29, 2026
- High CVE-2026-53404 Apache Tomcat: Bad ornext processing in RewriteValve Jun 29, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2013-4444 is "Code Injection in Apache Software Foundation Tomcat", rated Medium. It affects Tomcat (Apache Software Foundation); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.8 describes technical severity. EPSS 13.99% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.