VDB

CVE-2016-5018

CVE-2016-5018 PUBLISHED CVSS 9.100000381469727 CRITICAL

Authentication Bypass Using an Alternate Path or Channel in Apache Tomcat

Reported by apache · Published August 10, 2017

tomcat-embed-jasper is fixed in 9.0.0.M10, 8.5.5, 8.0.37 and 2 more (Maven Central)

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 a malicious web application was able to bypass a configured SecurityManager via a Tomcat utility method that was accessible to web applications.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
org.apache.tomcat.embed:tomcat-embed-jasperMaven Central9.0.0.M10, 8.5.5, 8.0.37, 7.0.72, 6.0.47
org.apache.tomcat:tomcat-jasperMaven Central9.0.0.M10, 8.5.5, 8.0.37, 7.0.72
tomcat7Ubuntu:14.04:LTS7.0.52-1ubuntu0.8
tomcatapache8.5.4, 8.0.36, 7.0.70, 6.0.45
tomcat8Ubuntu:16.04:LTS8.0.32-1ubuntu1.3
tekelec_platform_distributionoracle7.7.1

Risk scores

CVSS 3.1
9.100000381469727
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

VendorProductVersions
Apache Software FoundationApache Tomcat9.0.0.M1 to 9.0.0.M9, 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36
Apache Software FoundationApache Tomcat9.0.0.M1, 6.0.0, 7.0.0
Mavenorg.apache.tomcat:tomcat-catalina6.0.0, 9.0.0.M1, 8.5.0
Maventomcat:jasper-runtime0
Mavenorg.apache.tomcat:jasper6.0.0
Mavenorg.apache.tomcat:tomcat-jasper9.0.0.M1, 7.0.0, 8.0.0RC1
Mavenorg.apache.tomcat.embed:tomcat-embed-jasper9.0.0.M1, 6.0.0, 7.0.0

Timeline

  • Oct 28, 2016 CVE Published
  • Jan 8, 2020 PoC Published (2 in total, the first dated here)
  • Feb 4, 2022 EPSS Score (30 in total, the first dated here)
  • Sep 8, 2025 CVE Updated
  • Mar 5, 2026 Distribution Patch (10 in total, the first dated here)
  • Mar 5, 2026 Security Advisory (11 in total, the first dated here)
  • Oct 8, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2016-5018
vulnetix vdb fixes CVE-2016-5018

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2016-5018/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

…and 35 more

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›