Summary
A server-authentication failure in the erlang_quic QUIC client allowed TLS 1.3 connections to proceed without verifying the server's signature, certificate chain, or hostname. A man-in-the-middle attacker on the network path could impersonate a server and potentially read or alter QUIC and HTTP/3 traffic; PSK-authenticated session-resumption handshakes are not affected.
Affected context
The vulnerability occurs in erlang_quic client connections that use certificate-based TLS 1.3 authentication while certificate verification is not actually enforced. HTTP/3 clients using the same QUIC client authentication path are similarly exposed. PSK-authenticated handshakes are outside this affected context because the peer is authenticated through the PSK binder rather than a server certificate.
Exploit preconditions
- Attack surface: Network path between the QUIC client and its intended server
- Required access: Ability to intercept, redirect, or otherwise influence client-server traffic
- Trigger point: Certificate-based TLS 1.3 server authentication during the QUIC handshake
- Why exploitation is possible: The client did not verify the CertificateVerify signature, validate the certificate chain, or compare the requested hostname with the certificate identity
Why this happens
The client treated the presence of a server certificate as sufficient authentication without proving that the peer possessed the corresponding private key or that the certificate was trusted for the requested hostname. This behavior maps primarily to CWE-295: Improper Certificate Validation and is also related to CWE-297: Improper Validation of Certificate with Host Mismatch. Effectively disabling verification created a trust-boundary failure in which an untrusted network peer could present an arbitrary certificate.
Potential impact
- A network attacker may impersonate the intended QUIC server
- Sensitive application data could be disclosed
- Requests and responses could be modified in transit
- HTTP/3 sessions could be redirected or manipulated
- An attacker could potentially capture credentials or inject malicious content
General mitigation guidance
Mitigation focuses on ensuring that certificate-based TLS authentication is enabled and performs all required checks before application data is trusted.
Common defensive patterns include:
- Use TLS clients that verify the CertificateVerify signature
- Validate certificate chains against a controlled trust store
- Enforce hostname or service-identity matching
- Avoid disabling certificate verification outside isolated test environments
- Prefer authenticated PSK-based handshakes where that model is appropriate
- Protect trust-store configuration from unauthorized modification
- Apply least privilege to clients and services handling authenticated sessions
How teams detect issues like this
Organizations can identify this class of issue through:
- Static analysis for disabled or no-op certificate verification settings
- Code review checks confirming signature, chain, and hostname validation
- Integration tests using an untrusted certificate, an invalid chain, and a mismatched hostname
- Network testing that attempts server impersonation with a controlled interception proxy
- Policy enforcement that prohibits unauthenticated TLS clients in production
- Automated dependency and security review tools that flag known authentication flaws

