CVE-2016-6797

The ResourceLinkFactory implementation in Apache Tomcat 9.0.0.M1 to 9.0.0.M9, 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36, 7.0.0 to 7.0.70 and 6.0.0 to 6.0.45 did not limit web application access to global JNDI resources to those resources explicitly linked to the web application. Therefore, it was possible for a web application to access any global JNDI resource whether an explicit ResourceLink had been configured or not.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2016-6797 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (9.0.0.M10, 8.5.5, 8.0.37, 7.0.72); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2016-6797? CVE-2016-6797 is a high-severity incorrect authorization vulnerability in org.apache.tomcat:tomcat (maven), affecting versions >= 9.0.0.M1, <= 9.0.0.M9. It is fixed in 9.0.0.M10, 8.5.5, 8.0.37, 7.0.72. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is CVE-2016-6797? CVE-2016-6797 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.apache.tomcat:tomcat are affected by CVE-2016-6797? org.apache.tomcat:tomcat (maven) versions >= 9.0.0.M1, <= 9.0.0.M9 is affected.
4. Is there a fix for CVE-2016-6797? Yes. CVE-2016-6797 is fixed in 9.0.0.M10, 8.5.5, 8.0.37, 7.0.72. Upgrade to this version or later.
5. Is CVE-2016-6797 exploitable, and should I be worried? Whether CVE-2016-6797 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2016-6797 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2016-6797?
   • Upgrade org.apache.tomcat:tomcat to 9.0.0.M10 or later
   • Upgrade org.apache.tomcat:tomcat to 8.5.5 or later
   • Upgrade org.apache.tomcat:tomcat to 8.0.37 or later
   • Upgrade org.apache.tomcat:tomcat to 7.0.72 or later

Other vulnerabilities in org.apache.tomcat:tomcat