CVE-2018-8034: High severity Apache Tomcat vulnerability

Published Jul 22, 2018
·
Updated

Flaw affecting tomcat 8.0.0.RC1 to 8.0.52 and 9.0.0.M1 to 9.0.9 . The host name verification when using TLS with the WebSocket client was not enabled by default.

Upstream patch:

http://svn.apache.org/viewvc?view=revision&revision=1833757 http://svn.apache.org/viewvc?view=rev&rev=1833759

References:

https://tomcat.apache.org/security-8.html https://tomcat.apache.org/security-9.html

Other sources

The host name verification when using TLS with the WebSocket client was missing. It is now enabled by default. Versions Affected: Apache Tomcat 9.0.0.M1 to 9.0.9, 8.5.0 to 8.5.31, 8.0.0.RC1 to 8.0.52, and 7.0.35 to 7.0.88.

Launchpad

Affected Software

84 affected componentsFixes available
redhat/tomcat<8.0.53
8.0.53
redhat/tomcat<8.5.32
8.5.32
redhat/tomcat<9.0.10
9.0.10
redhat/tomcat<7.0.90
7.0.90
maven/org.apache.tomcat.embed:tomcat-embed-core>=7.0.35<=7.0.88
7.0.90
maven/org.apache.tomcat.embed:tomcat-embed-core>=8.0.0<8.0.53
8.0.53
maven/org.apache.tomcat.embed:tomcat-embed-core>=8.5.0<8.5.32
8.5.32
maven/org.apache.tomcat.embed:tomcat-embed-core>=9.0.0<=9.0.9
9.0.10
Apache Tomcat>=7.0.35<=7.0.88
Apache Tomcat>=8.0.0<=8.0.52
Apache Tomcat>=8.5.0<=8.5.31
Apache Tomcat>=9.0.1<=9.0.9
Apache Tomcat=8.0.0-rc1
Apache Tomcat=8.0.0-rc10
Apache Tomcat=8.0.0-rc2
Apache Tomcat=8.0.0-rc3
Apache Tomcat=8.0.0-rc4
Apache Tomcat=8.0.0-rc5
Apache Tomcat=8.0.0-rc6
Apache Tomcat=8.0.0-rc7
Apache Tomcat=8.0.0-rc8
Apache Tomcat=8.0.0-rc9
Apache Tomcat=9.0.0-milestone1
Apache Tomcat=9.0.0-milestone10
Apache Tomcat=9.0.0-milestone11
Apache Tomcat=9.0.0-milestone12
Apache Tomcat=9.0.0-milestone13
Apache Tomcat=9.0.0-milestone14
Apache Tomcat=9.0.0-milestone15
Apache Tomcat=9.0.0-milestone16
Apache Tomcat=9.0.0-milestone17
Apache Tomcat=9.0.0-milestone18
Apache Tomcat=9.0.0-milestone19
Apache Tomcat=9.0.0-milestone2
Apache Tomcat=9.0.0-milestone20
Apache Tomcat=9.0.0-milestone21
Apache Tomcat=9.0.0-milestone22
Apache Tomcat=9.0.0-milestone23
Apache Tomcat=9.0.0-milestone24
Apache Tomcat=9.0.0-milestone25
Apache Tomcat=9.0.0-milestone26
Apache Tomcat=9.0.0-milestone27
Apache Tomcat=9.0.0-milestone3
Apache Tomcat=9.0.0-milestone4
Apache Tomcat=9.0.0-milestone5
Apache Tomcat=9.0.0-milestone6
Apache Tomcat=9.0.0-milestone7
Apache Tomcat=9.0.0-milestone8
Apache Tomcat=9.0.0-milestone9
Canonical Ubuntu Linux=14.04
Canonical Ubuntu Linux=16.04
Debian Debian Linux=8.0
Debian Debian Linux=9.0
Oracle Retail Order Broker=5.1
Oracle Retail Order Broker=5.2
Oracle Retail Order Broker=15.0
Apache Tomcat=9.0.0-m1
Apache Tomcat=9.0.0-m10
Apache Tomcat=9.0.0-m11
Apache Tomcat=9.0.0-m12
Apache Tomcat=9.0.0-m13
Apache Tomcat=9.0.0-m14
Apache Tomcat=9.0.0-m15
Apache Tomcat=9.0.0-m16
Apache Tomcat=9.0.0-m17
Apache Tomcat=9.0.0-m18
Apache Tomcat=9.0.0-m19
Apache Tomcat=9.0.0-m2
Apache Tomcat=9.0.0-m20
Apache Tomcat=9.0.0-m21
Apache Tomcat=9.0.0-m22
Apache Tomcat=9.0.0-m23
Apache Tomcat=9.0.0-m24
Apache Tomcat=9.0.0-m25
Apache Tomcat=9.0.0-m26
Apache Tomcat=9.0.0-m27
Apache Tomcat=9.0.0-m3
Apache Tomcat=9.0.0-m4
Apache Tomcat=9.0.0-m5
Apache Tomcat=9.0.0-m6
Apache Tomcat=9.0.0-m7
Apache Tomcat=9.0.0-m8
Apache Tomcat=9.0.0-m9
debian/tomcat9
9.0.43-2~deb11u109.0.107-0+deb11u29.0.70-29.0.95-19.0.115-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-core to a version that resolves this vulnerability.

    Fixed in 7.0.90
  2. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-core to a version that resolves this vulnerability.

    Fixed in 8.0.53
  3. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-core to a version that resolves this vulnerability.

    Fixed in 8.5.32
  4. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-core to a version that resolves this vulnerability.

    Fixed in 9.0.10
  5. Upgrade

    Upgrade debian/tomcat9 to a version that resolves this vulnerability.

    Fixed in 9.0.43-2~deb11u10Fixed in 9.0.107-0+deb11u2Fixed in 9.0.70-2Fixed in 9.0.95-1Fixed in 9.0.115-1
  6. Upgrade

    Upgrade redhat/tomcat to a version that resolves this vulnerability.

    Fixed in 8.0.53
  7. Upgrade

    Upgrade redhat/tomcat to a version that resolves this vulnerability.

    Fixed in 8.5.32
  8. Upgrade

    Upgrade redhat/tomcat to a version that resolves this vulnerability.

    Fixed in 9.0.10
  9. Upgrade

    Upgrade redhat/tomcat to a version that resolves this vulnerability.

    Fixed in 7.0.90
  10. Compensating control

    For Apache Tomcat WebSocket over TLS, enable host name verification for TLS connections made by the WebSocket client (the issue was that host name verification was missing / not enabled by default).

Event History

Jul 23, 2018
Data Sourced
via Red Hat·07:15 PM
DescriptionSeverityAffected Software
Aug 1, 2018
CVE Published
via MITRE·06:00 PM
Data Sourced
via MITRE·06:00 PM
DescriptionWeakness
Oct 17, 2018
Advisory Published
via GitHub·04:32 PM
Feb 20, 2026
Data Sourced
via Ubuntu·06:45 PM
RemedyDescriptionSeverityAffected Software
Data Sourced
via Launchpad·06:46 PM
Description
Data Sourced
via Debian·06:47 PM
DescriptionAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2018-8034?

CVE-2018-8034 is considered a moderate severity vulnerability due to insufficient hostname verification in TLS connections.

2

How do I fix CVE-2018-8034?

To fix CVE-2018-8034, upgrade your Tomcat installation to version 8.0.53, 8.5.32, or 9.0.10 or later.

3

Which versions of Tomcat are affected by CVE-2018-8034?

CVE-2018-8034 affects Tomcat versions 8.0.0.RC1 to 8.0.52 and 9.0.0.M1 to 9.0.9.

4

What kind of attack can CVE-2018-8034 enable?

CVE-2018-8034 could allow an attacker to perform man-in-the-middle attacks if hostname verification is bypassed.

5

Is CVE-2018-8034 present in embedded versions of Tomcat?

Yes, CVE-2018-8034 is present in embedded versions of Tomcat that fall within the affected version ranges.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203