<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Apache HTTP Server (2.4.35-2.4.62) - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/apache-http-server-2.4.35-2.4.62/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Sun, 01 Nov 2026 09:58:38 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/apache-http-server-2.4.35-2.4.62/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>Apache HTTP Server: TLS 1.3 Session Resumption Authentication Bypass (CVE-2025-23048)</title><link>https://feed.craftedsignal.io/briefs/2026-11-cve-2025-23048/</link><pubDate>Sun, 01 Nov 2026 09:58:38 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-cve-2025-23048/</guid><description>CVE-2025-23048 allows an attacker to bypass client certificate authentication in Apache HTTP Server versions 2.4.35 through 2.4.62 by resuming a TLS 1.3 session across virtual hosts with different CA configurations.</description><content:encoded><![CDATA[<p>Apache HTTP Server versions 2.4.35 through 2.4.62 are vulnerable to a client certificate authentication bypass (CVE-2025-23048) when TLS 1.3 session resumption is enabled. The vulnerability occurs because the server may incorrectly reuse a session established on one virtual host (vhost1) for a different virtual host (vhost2) that requires a distinct client CA certificate. This allows an attacker possessing a valid certificate for vhost1 to access protected resources on vhost2 without providing a certificate trusted by vhost2.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker identifies two virtual hosts on a target Apache server configured with differing <code>SSLCACertificateFile</code> directives.</li>
<li>Attacker performs a full TLS 1.3 handshake with the first virtual host using a valid client certificate trusted by that specific host.</li>
<li>The Apache server accepts the handshake and issues a session ticket.</li>
<li>Attacker captures the session ticket or maintains the session state.</li>
<li>Attacker initiates a connection to the second virtual host (vhost2) requesting a restricted path.</li>
<li>Attacker uses the session ticket from vhost1 to resume the TLS session on vhost2.</li>
<li>Apache incorrectly validates the resumed session, bypassing the client certificate check required for vhost2.</li>
<li>Attacker gains unauthorized access to protected resources on vhost2.</li>
</ol>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade Apache HTTP Server to version 2.4.64 or later to address the vulnerability.</li>
<li>If upgrading is not immediately possible, set <code>SSLStrictSNIVHostCheck on</code> within the virtual host configuration for all TLS 1.3 enabled hosts that rely on distinct client certificate authorities. This setting prevents cross-SNI session resumption and mitigates the bypass.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item></channel></rss>