CVE-2017-5648 — Exposure of Resource to Wrong Sphere in Apache Tomcat
While investigating bug 60718, it was noticed that some calls to application listeners in Apache Tomcat 9.0.0.M1 to 9.0.0.M17, 8.5.0 to 8.5.11, 8.0.0.RC1 to 8.0.41, and 7.0.0 to 7.0.75 did not use the appropriate facade object. When running an untrusted application under a SecurityManager, it was therefore possible for that untrusted application to retain a reference to the request or response object and thereby access and/or modify information associated with another web application.
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 13.2% (30-day exploitation probability)+14
- Technical severity (critical)+10
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.
- Maven Org.apache.tomcat:tomcat-catalina: fixed in version 9.0.0.M18 — github.com (GitHub Security Advisories)
- Maven Org.apache.tomcat:tomcat-catalina: fixed in version 8.5.13 — github.com (GitHub Security Advisories)
- Maven Org.apache.tomcat:tomcat-catalina: fixed in version 8.0.42 — github.com (GitHub Security Advisories)
- Maven Org.apache.tomcat:tomcat-catalina: fixed in version 7.0.76 — github.com (GitHub Security Advisories)
- Maven Org.apache.tomcat.embed:tomcat-embed-core: fixed in version 9.0.0.M18 — github.com (GitHub Security Advisories)
- Maven Org.apache.tomcat.embed:tomcat-embed-core: fixed in version 8.5.13 — github.com (GitHub Security Advisories)
- Maven Org.apache.tomcat.embed:tomcat-embed-core: fixed in version 8.0.42 — github.com (GitHub Security Advisories)
- Maven Org.apache.tomcat.embed:tomcat-embed-core: fixed in version 7.0.76 — github.com (GitHub Security Advisories)
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, Maven Org.apache.tomcat:tomcat-catalina, Maven Org.apache.tomcat.embed:tomcat-embed-core).
- 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 96% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes matching the vulnerability class (access control), 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 9.0.0-milestone5version 9.0.0-milestone13version 9.0.0-milestone14version 9.0.0-milestone15version 9.0.0-milestone16version 9.0.0-milestone17version 9.0.0-milestone2version 9.0.0-milestone3 and 140 moreversion 9.0.0-milestone4version 8.0.40version 9.0.0-milestone6version 9.0.0-milestone7version 9.0.0-milestone8version 9.0.0-milestone9version 9.0.0-milestone11version 8.0.39version 8.0.41version 8.5.0version 8.5.1version 8.5.2version 8.5.3version 8.5.4version 8.5.5version 8.5.7version 9.0.0-milestone12version 9.0.0-milestone10version 9.0.0-milestone1version 8.5.11version 8.5.10version 8.5.9version 8.5.8version 8.5.6version 7.0.0version 7.0.1version 7.0.2version 7.0.3version 7.0.4version 7.0.5version 7.0.6version 7.0.7version 7.0.8version 7.0.9version 7.0.10version 7.0.11version 7.0.12version 7.0.13version 7.0.14version 7.0.15version 7.0.16version 7.0.17version 7.0.18version 7.0.19version 7.0.20version 7.0.21version 7.0.22version 7.0.23version 7.0.24version 7.0.25version 7.0.26version 7.0.27version 7.0.28version 7.0.29version 7.0.30version 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.39version 7.0.40version 7.0.41version 7.0.42version 7.0.43version 7.0.44version 7.0.45version 7.0.46version 7.0.47version 7.0.48version 7.0.49version 7.0.50version 7.0.51version 7.0.52version 7.0.53version 7.0.54version 7.0.55version 7.0.56version 7.0.57version 7.0.58version 7.0.59version 7.0.60version 7.0.61version 7.0.62version 7.0.63version 7.0.64version 7.0.65version 7.0.66version 7.0.67version 7.0.68version 7.0.69version 7.0.70version 7.0.71version 7.0.72version 7.0.73version 7.0.74version 7.0.75version 8.0.0version 8.0.0-rc1version 8.0.1version 8.0.2version 8.0.3version 8.0.4version 8.0.5version 8.0.6version 8.0.7version 8.0.8version 8.0.9version 8.0.10version 8.0.11version 8.0.12version 8.0.13version 8.0.14version 8.0.15version 8.0.16version 8.0.17version 8.0.18version 8.0.19version 8.0.20version 8.0.21version 8.0.22version 8.0.23version 8.0.24version 8.0.25version 8.0.26version 8.0.27version 8.0.28version 8.0.29version 8.0.30version 8.0.31version 8.0.32version 8.0.33version 8.0.34version 8.0.35version 8.0.36version 8.0.37version 8.0.38 |
Vulnerable | NIST National Vulnerability Database |
| Apache Software Foundation | Tomcat | version 9.0.0.M1 to 9.0.0.M17version 8.5.0 to 8.5.11version 8.0.0.RC1 to 8.0.41version 7.0.0 to 7.0.75 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Maven | Org.apache.tomcat:tomcat-catalina | ≥ 9.0.0.M1 and ≤ 9.0.0.M17≥ 8.5.0 and ≤ 8.5.12≥ 8.0.0 and ≤ 8.0.41≥ 7.0.0 and ≤ 7.0.75 | Vulnerable | GitHub Security Advisories |
| Maven | Org.apache.tomcat.embed:tomcat-embed-core | ≥ 9.0.0.M1 and ≤ 9.0.0.M17≥ 8.5.0 and ≤ 8.5.12≥ 8.0.0 and ≤ 8.0.41≥ 7.0.0 and ≤ 7.0.75 | Vulnerable | GitHub Security Advisories |
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 |
|---|---|---|---|---|---|
| 9.1 | CVSS 3.0 | Critical | 3.9 | 5.2 | nvd@nist.gov via NIST National Vulnerability Database |
| 9.1 | CVSS 3.0 | Critical | — | — | GitHub, Inc. via GitHub Security Advisories |
| 6.4 | CVSS 2.0 | Medium | 10.0 | 4.9 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
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).
- Audit administrative actions and access to resources outside each user’s normal pattern.
Timeline
What happened to this CVE, newest first.
- 2026
- Fix documented
- Affected products added · maven/org.apache.tomcat:tomcat-catalina, maven/org.apache.tomcat.embed:tomcat-embed-core
- Affected products added · apache software foundation/apache tomcat
- SSVC assessment updated
- Record published
- Affected products added · apache/tomcat
- CVSS changed · 9.1
- Source status changed · → Modified
- Record created in this database
- 2017
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 15, 2026 – Oct 15, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
41 on the record
- www.openwall.com/lists/oss-security/2020/07/20/8
- lists.apache.org/thread.html/b5e3f51d28cd5d9b1809f56594f2cf63dcd6a90429e16ea9f83bbedc@
- access.redhat.com/errata/RHSA-2017:1801
- github.com/apache/tomcat80/commit/6d73b079c55ee25dea1bbd0556bb568a4247dacd
- lists.apache.org/thread.html/845312a10aabbe2c499fca94003881d2c79fc993d85f34c1f5c77424%
- web.archive.org/web/20170420115120/http://www.securitytracker.com/id/1038220
- lists.apache.org/thread.html/r3bbb800a816d0a51eccc5a228c58736960a9fffafa581a225834d97d
- lists.apache.org/thread.html/343558d982879bf88ec20dbf707f8c11255f8e219e81d45c4f8d0551%
- lists.apache.org/thread.html/d0e00f2e147a9e9b13a6829133092f349b2882bf6860397368a52600%
- lists.apache.org/thread.html/d0e00f2e147a9e9b13a6829133092f349b2882bf6860397368a52600@
- github.com/apache/tomcat/commit/0f7b9465d594b9814e1853d1e3a6e3aa51a21610
- www.debian.org/security/2017/dsa-3842
- www.debian.org/security/2017/dsa-3843
- lists.apache.org/thread.html/388a323769f1dff84c9ec905455aa73fbcb20338e3c7eb131457f708@
- lists.apache.org/thread.html/r48c1444845fe15a823e1374674bfc297d5008a5453788099ea14caf0
- lists.apache.org/thread.html/88855876c33f2f9c532ffb75bfee570ccf0b17ffa77493745af9a17a@
- nvd.nist.gov/vuln/detail/CVE-2017-5648
- security.netapp.com/advisory/ntap-20180614-0001
- lists.apache.org/thread.html/b5e3f51d28cd5d9b1809f56594f2cf63dcd6a90429e16ea9f83bbedc%
- lists.apache.org/thread.html/r48c1444845fe15a823e1374674bfc297d5008a5453788099ea14caf0
- lists.apache.org/thread.html/r9136ff5b13e4f1941360b5a309efee2c114a14855578c3a2cbe5d19c
- access.redhat.com/errata/RHSA-2017:1802
- lists.apache.org/thread.html/343558d982879bf88ec20dbf707f8c11255f8e219e81d45c4f8d0551@
- access.redhat.com/errata/RHSA-2017:1809
- lists.apache.org/thread.html/845312a10aabbe2c499fca94003881d2c79fc993d85f34c1f5c77424@
- lists.apache.org/thread.html/3d19773b4cf0377db62d1e9328bf9160bf1819f04f988315086931d7@
- lists.apache.org/thread.html/6af47120905aa7d8fe12f42e8ff2284fb338ba141d3b77b8c7cb61b3%
- github.com/advisories/GHSA-3vx3-xf6q-r5xp
- lists.apache.org/thread.html/r9136ff5b13e4f1941360b5a309efee2c114a14855578c3a2cbe5d19c
- lists.apache.org/thread.html/88855876c33f2f9c532ffb75bfee570ccf0b17ffa77493745af9a17a%
- www.securityfocus.com/bid/97530
- security.gentoo.org/glsa/201705-09
- github.com/apache/tomcat/commit/6bb36dfdf6444efda074893dff493b9eb3648808
- lists.apache.org/thread.html/6af47120905aa7d8fe12f42e8ff2284fb338ba141d3b77b8c7cb61b3@
- security.netapp.com/advisory/ntap-20180614-0001/
- github.com/apache/tomcat/commit/dfa40863421d7681fed893b4256666491887e38c
- lists.apache.org/thread.html/r3bbb800a816d0a51eccc5a228c58736960a9fffafa581a225834d97d
- lists.apache.org/thread.html/388a323769f1dff84c9ec905455aa73fbcb20338e3c7eb131457f708%
- lists.apache.org/thread.html/3d19773b4cf0377db62d1e9328bf9160bf1819f04f988315086931d7%
- web.archive.org/web/20170417124117/http://www.securityfocus.com/bid/97530
- www.securitytracker.com/id/1038220
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-87022 Apache Tomcat: WebSocket message smuggling with per-message-deflate 22d
- Critical CVE-2026-86350 Apache Tomcat: Regression in fix for CVE-2026-41293 can trigger request header mix-up 22d
- Critical CVE-2026-86248 Apache Tomcat: Fix for CVE-2026-34500 was incomplete. OCSP checks sometimes soft-fail with FFM even when soft-fail is disabled 22d
- High CVE-2026-78437 Apache Tomcat: HTTP/2 DoS via malformed request 22d
- High CVE-2026-78383 Apache Tomcat: AJP DoS via missing request body 22d
- High CVE-2026-79677 Apache Tomcat: WebSocket DoS due to lost asynchronous write timeout 22d
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-2017-5648 is "Exposure of Resource to Wrong Sphere in Apache Tomcat", rated Critical. 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 9.1 describes technical severity. EPSS 13.23% 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.