7.5
CWE
295
Advisory Published
CVE Published
Advisory Published
Updated

CVE-2018-8034

First published: Sun 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: <a href="http://svn.apache.org/viewvc?view=revision&amp;revision=1833757">http://svn.apache.org/viewvc?view=revision&amp;revision=1833757</a> <a href="http://svn.apache.org/viewvc?view=rev&amp;rev=1833759">http://svn.apache.org/viewvc?view=rev&amp;rev=1833759</a> References: <a href="https://tomcat.apache.org/security-8.html">https://tomcat.apache.org/security-8.html</a> <a href="https://tomcat.apache.org/security-9.html">https://tomcat.apache.org/security-9.html</a>

Credit: security@apache.org security@apache.org security@apache.org

Affected SoftwareAffected VersionHow to fix
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
debian/tomcat9
9.0.43-2~deb11u10
9.0.43-2~deb11u11
9.0.70-2
9.0.95-1
Tomcat>=7.0.35<=7.0.88
Tomcat>=8.0.0<=8.0.52
Tomcat>=8.5.0<=8.5.31
Tomcat>=9.0.1<=9.0.9
Tomcat=8.0.0-rc1
Tomcat=8.0.0-rc10
Tomcat=8.0.0-rc2
Tomcat=8.0.0-rc3
Tomcat=8.0.0-rc4
Tomcat=8.0.0-rc5
Tomcat=8.0.0-rc6
Tomcat=8.0.0-rc7
Tomcat=8.0.0-rc8
Tomcat=8.0.0-rc9
Tomcat=9.0.0-milestone1
Tomcat=9.0.0-milestone10
Tomcat=9.0.0-milestone11
Tomcat=9.0.0-milestone12
Tomcat=9.0.0-milestone13
Tomcat=9.0.0-milestone14
Tomcat=9.0.0-milestone15
Tomcat=9.0.0-milestone16
Tomcat=9.0.0-milestone17
Tomcat=9.0.0-milestone18
Tomcat=9.0.0-milestone19
Tomcat=9.0.0-milestone2
Tomcat=9.0.0-milestone20
Tomcat=9.0.0-milestone21
Tomcat=9.0.0-milestone22
Tomcat=9.0.0-milestone23
Tomcat=9.0.0-milestone24
Tomcat=9.0.0-milestone25
Tomcat=9.0.0-milestone26
Tomcat=9.0.0-milestone27
Tomcat=9.0.0-milestone3
Tomcat=9.0.0-milestone4
Tomcat=9.0.0-milestone5
Tomcat=9.0.0-milestone6
Tomcat=9.0.0-milestone7
Tomcat=9.0.0-milestone8
Tomcat=9.0.0-milestone9
Ubuntu=14.04
Ubuntu=16.04
Debian=8.0
Debian=9.0
Oracle Retail Order Broker=5.1
Oracle Retail Order Broker=5.2
Oracle Retail Order Broker=15.0
Tomcat=9.0.0-m1
Tomcat=9.0.0-m10
Tomcat=9.0.0-m11
Tomcat=9.0.0-m12
Tomcat=9.0.0-m13
Tomcat=9.0.0-m14
Tomcat=9.0.0-m15
Tomcat=9.0.0-m16
Tomcat=9.0.0-m17
Tomcat=9.0.0-m18
Tomcat=9.0.0-m19
Tomcat=9.0.0-m2
Tomcat=9.0.0-m20
Tomcat=9.0.0-m21
Tomcat=9.0.0-m22
Tomcat=9.0.0-m23
Tomcat=9.0.0-m24
Tomcat=9.0.0-m25
Tomcat=9.0.0-m26
Tomcat=9.0.0-m27
Tomcat=9.0.0-m3
Tomcat=9.0.0-m4
Tomcat=9.0.0-m5
Tomcat=9.0.0-m6
Tomcat=9.0.0-m7
Tomcat=9.0.0-m8
Tomcat=9.0.0-m9

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Reference Links

Frequently Asked Questions

  • 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.

  • 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.

  • 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.

  • 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.

  • 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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203