# CVE-2016-5018: Authentication Bypass Using an Alternate Path or Channel in Apache Tomcat

Source: https://junglewise.ai/threats/cve-2016-5018-authentication-bypass-using-an-alternate-path-or-channel-in-apache  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2022-05-13  
License: CC BY 4.0 with a link back

CVE-2016-5018 · Severity: low · CVSS 3.1 · Published 2022-05-13

Authentication Bypass Using an Alternate Path or Channel in Apache Tomcat

Technologies: [org.apache.tomcat:tomcat-jasper (Maven)](https://junglewise.ai/threats/technologies/org-apache-tomcat-tomcat-jasper). Vendors: [Maven](https://junglewise.ai/threats/vendors/maven).

## Quick answers

**Is CVE-2016-5018 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2016-5018 being exploited in the wild.

**How severe is CVE-2016-5018?** Low severity, with a CVSS score of 3.1, published 13 May 2022.

**Which products and versions are affected?** org.apache.tomcat:jasper (Maven) ECOSYSTEM:introduced=6.0.0,fixed=6.0.47; org.apache.tomcat:tomcat-jasper (Maven) ECOSYSTEM:introduced=9.0.0.M1,fixed=9.0.0.M10; org.apache.tomcat.embed:tomcat-embed-jasper (Maven) ECOSYSTEM:introduced=9.0.0.M1,fixed=9.0.0.M10.

**Is there a fix for CVE-2016-5018?** Yes. org.apache.tomcat:jasper (Maven): upgrade to 6.0.47 or later; org.apache.tomcat:tomcat-jasper (Maven): upgrade to 9.0.0.M10 or later; org.apache.tomcat.embed:tomcat-embed-jasper (Maven): upgrade to 9.0.0.M10 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2016-5018?** Check whether you run org.apache.tomcat:jasper (Maven), org.apache.tomcat:tomcat-jasper (Maven) or org.apache.tomcat.embed:tomcat-embed-jasper (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- org.apache.tomcat:jasper (Maven): upgrade to 6.0.47 or later

  ```sh
  # set org.apache.tomcat:jasper to 6.0.47 in your pom.xml or build.gradle
  ```

- org.apache.tomcat:tomcat-jasper (Maven): upgrade to 9.0.0.M10 or later

  ```sh
  # set org.apache.tomcat:tomcat-jasper to 9.0.0.M10 in your pom.xml or build.gradle
  ```

- org.apache.tomcat.embed:tomcat-embed-jasper (Maven): upgrade to 9.0.0.M10 or later

  ```sh
  # set org.apache.tomcat.embed:tomcat-embed-jasper to 9.0.0.M10 in your pom.xml or build.gradle
  ```


## Affected products

- org.apache.tomcat:jasper (Maven) ECOSYSTEM:introduced=6.0.0,fixed=6.0.47
- org.apache.tomcat:tomcat-jasper (Maven) ECOSYSTEM:introduced=9.0.0.M1,fixed=9.0.0.M10
- org.apache.tomcat.embed:tomcat-embed-jasper (Maven) ECOSYSTEM:introduced=9.0.0.M1,fixed=9.0.0.M10

## Identifiers

- CVE-2016-5018
- GHSA-4v3g-g84w-hv7r

## Related threats

- [Apache Tomcat XSS in generated JSPs](https://junglewise.ai/threats/cve-2024-52318-apache-tomcat-xss-in-generated-jsps)
- [Missing XML Validation in Apache Tomcat](https://junglewise.ai/threats/cve-2014-0119-missing-xml-validation-in-apache-tomcat)