Wednesday, March 19, 2025
HomeSecurity UpdateApache Security Update that Covers Multiple Vulnerabilities With Tomcat Native

Apache Security Update that Covers Multiple Vulnerabilities With Tomcat Native

Published on

SIEM as a Service

Follow Us on Google News

Multiple vulnerabilities with TLS implementation and OCSP check’s fixed with the Apache security update. By exploiting the vulnerabilities a remote attacker can gain access to the server.

Apache Security Update

OCSP Invalid Response

OCSP responder Apache Tomcat Native failed in handling the invalid OCSP responses. The vulnerability allows the users with the revoked client certificates can authenticate when using mutual TLS.

The vulnerability affects 1.2.0 to 1.2.16 and 1.1.23 to 1.1.34 version and it has been fixed with revision 1832832. The vulnerability can be tracked as CVE-2018-8019.

Authentication with Revoked Certificates

Apache Tomcat Native failed in check OCSP pre-produced responses, which may impact in revoked certificate detection and the vulnerability allows the users with the revoked client certificates can authenticate when using mutual TLS.

The vulnerability affects 1.2.0 to 1.2.16 and 1.1.23 to 1.1.34 version and it has been fixed with revision 1832863. The vulnerability can be tracked as CVE-2018-8020.

OCSP Check Omitted

Apache Tomcat Native Connector 1.2.0 to 1.2.14 and 1.1.23 to 1.1.34 did not correctly handle fields longer than 127 bytes. The result of the parsing error was to skip the OCSP check. It allows a client that has been rejected to be accepted.

The vulnerability affects 1.2.0 to 1.2.14 and 1.1.23 to 1.1.34 version and it has been fixed with revision 1815200 and 1815218. The vulnerability can be tracked as CVE-2017-15698.

TLS SSL Man In The Middle

Not an Apache Tomcat Native vulnerability, if the APR/native connector uses OpenSSL version that is
vulnerable then APR/native connector is vulnerable also vulnerable and it allows attackers to inject arbitrary requests into a TLS stream during renegotiation.

Starting from version 1.1.18 client-initiated renegotiations are rejected to provide partial protection against this vulnerability with any OpenSSL version. The vulnerability can be tracked as CVE-2009-3555.

Heartbleed

The vulnerability affects all OpenSSL version before 1.0.1 to 1.0.1f, it also a remote attacker to read certain contents of the server’s memory.

Tcnative version 1.1.24 – 1.1.29 includes the vulnerable version of the OpenSSL, starting from tcnative 1.1.30 it comes with the OpenSSL version that patched for this vulnerability. The vulnerability can be tracked as CVE-2014-0160.

Also Read

Apache Software Foundation Releases Important Security Patches for Multiple Apache Tomcat Versions

Ubuntu Security Updates for Vulnerabilities that Affects Multiple Versions

VMware Released Critical Security Updates for Multiple Vulnerabilities Including L1 Terminal Fault

Gurubaran
Gurubaran
Gurubaran is a co-founder of Cyber Security News and GBHackers On Security. He has 10+ years of experience as a Security Consultant, Editor, and Analyst in cybersecurity, technology, and communications.

Latest articles

Severe AMI BMC Vulnerability Enables Remote Authentication Bypass by Attackers

A critical vulnerability has been discovered in AMI's MegaRAC software, which is used in...

CISA Warns of Supply-Chain Attack Exploiting GitHub Action Vulnerability

The Cybersecurity and Infrastructure Security Agency (CISA) has sounded the alarm over a critical...

MirrorFace Hackers Modify AsyncRAT Execution for Stealthy Deployment in Windows Sandbox

In a significant development, the China-aligned advanced persistent threat (APT) group known as MirrorFace...

11 State-Sponsored Threat Actors Exploit 8-Year-Old Windows Shortcut Flaw

Cybersecurity researchers have discovered that multiple state-sponsored threat actors have been exploiting an eight-year-old...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Severe AMI BMC Vulnerability Enables Remote Authentication Bypass by Attackers

A critical vulnerability has been discovered in AMI's MegaRAC software, which is used in...

CISA Warns of Supply-Chain Attack Exploiting GitHub Action Vulnerability

The Cybersecurity and Infrastructure Security Agency (CISA) has sounded the alarm over a critical...

11 State-Sponsored Threat Actors Exploit 8-Year-Old Windows Shortcut Flaw

Cybersecurity researchers have discovered that multiple state-sponsored threat actors have been exploiting an eight-year-old...