# CVE-2017-5648: Exposure of Resource to Wrong Sphere in Apache Tomcat > Untrusted applications can access or modify other web applications' data when running under a SecurityManager due to missing facade objects. - **Severity:** Critical 9.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 17 Apr 2017 - **Updated:** 15 Oct 2026 - **Also known as:** GHSA-3vx3-xf6q-r5xp, UBUNTU-CVE-2017-5648 ## What is CVE-2017-5648? CVE-2017-5648 is a critical vulnerability in Apache Tomcat, published on 17 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-668 (Exposure of Resource to Wrong Sphere) ## Which versions are affected by CVE-2017-5648? 16 open source packages ship an affected version, including org.apache.tomcat.embed:tomcat-embed-core and org.apache.tomcat:tomcat-catalina. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 7.0.0 | 7.0.76 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 7.0.0 | 7.0.76 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 8.0.0 | 8.0.42 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 8.0.0 | 8.0.42 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 8.5.0 | 8.5.13 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 8.5.0 | 8.5.13 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 9.0.0.M1 | 9.0.0.M18 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 9.0.0.M1 | 9.0.0.M18 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 7.0.0 | 7.0.76 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 7.0.0 | 7.0.76 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 8.0.0 | 8.0.42 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 8.0.0 | 8.0.42 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 8.5.0 | 8.5.13 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 8.5.0 | 8.5.13 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 9.0.0.M1 | 9.0.0.M18 | | `org.apache.tomcat:tomcat-catalina` | Maven | From 9.0.0.M1 | 9.0.0.M18 | Products: Apache Tomcat. ## How do I fix CVE-2017-5648? Upgrade org.apache.tomcat.embed:tomcat-embed-core to a fixed version for your release line: 7.0.76, 8.0.42, 8.5.13 or 9.0.0.M18. ## Is CVE-2017-5648 being exploited? There is no known exploitation of CVE-2017-5648 in the wild and no public exploit code. ## Other vulnerabilities in Apache Tomcat - [CVE-2025-24813](https://insights.sbomify.com/CVE-2025-24813/): Apache Tomcat Path Equivalence (critical 10.0, exploited in the wild) - [CVE-2016-8735](https://insights.sbomify.com/CVE-2016-8735/): Apache Tomcat Remote Code Execution (critical 9.8, exploited in the wild) - [CVE-2017-12617](https://insights.sbomify.com/CVE-2017-12617/): Apache Tomcat Remote Code Execution (high 8.1, exploited in the wild) - [CVE-2017-12615](https://insights.sbomify.com/CVE-2017-12615/): Apache Tomcat on Windows Remote Code Execution (high 8.1, exploited in the wild) - [CVE-2026-34486](https://insights.sbomify.com/CVE-2026-34486/): Apache Tomcat Missing Encryption of Sensitive Data (high 7.5, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2017-5648 and fix it if it is affected. What it is: CVE-2017-5648 is a critical vulnerability in Apache Tomcat, published on 17 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2017-5648 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 7.0.0; fixed in 7.0.76 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 7.0.0; fixed in 7.0.76 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 8.0.0; fixed in 8.0.42 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 8.0.0; fixed in 8.0.42 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 8.5.0; fixed in 8.5.13 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 8.5.0; fixed in 8.5.13 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 9.0.0.M1; fixed in 9.0.0.M18 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 9.0.0.M1; fixed in 9.0.0.M18 - org.apache.tomcat:tomcat-catalina (Maven): affected from 7.0.0; fixed in 7.0.76 - org.apache.tomcat:tomcat-catalina (Maven): affected from 7.0.0; fixed in 7.0.76 - org.apache.tomcat:tomcat-catalina (Maven): affected from 8.0.0; fixed in 8.0.42 - org.apache.tomcat:tomcat-catalina (Maven): affected from 8.0.0; fixed in 8.0.42 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2017-5648/ (Markdown: https://insights.sbomify.com/CVE-2017-5648/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2017-5648 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-5648 - OSV: https://osv.dev/vulnerability/CVE-2017-5648 --- From sbomify Insights: https://insights.sbomify.com/CVE-2017-5648/ Summaries are generated and may contain mistakes; the official description above is the record.