github.com/envoyproxy/envoy
Affected
- introduced
1.36.0, fixed1.36.3(semver)
Fixed versions
1.36.3
Fix
- Fixed version
1.36.3go get github.com/envoyproxy/[email protected]
Advisory
Also known as: BIT-envoy-2025-66220, CVE-2025-66220
Envoy's TLS certificate matcher for match_typed_subject_alt_names may incorrectly treat certificates containing an embedded null byte
Summary
Envoy’s mTLS certificate matcher for match_typed_subject_alt_names may incorrectly treat certificates containing an embedded null byte (\0) inside an OTHERNAME SAN value as valid matches.
Details
This occurs when the SAN is encoded as a BMPSTRING or UNIVERSALSTRING, and its UTF-8 conversion result is truncated at the first null byte during string assignment. As a result, "victim\0evil" may match an exact: "victim" rule and be accepted by Envoy.
PoC
Create a CA and a server certificate signed by that CA.
Create two client certificates signed by the same CA:
client_evil with OTHERNAME BMPSTRING = "evil"
client_null with OTHERNAME BMPSTRING = "victim\0evil"
Configure Envoy with require_client_certificate: true and a match_typed_subject_alt_names entry for the OTHERNAME OID with matcher.exact: "victim".
Connect without a client cert → connection rejected.
Connect with client_evil → connection rejected.
Connect with client_null → connection accepted (but shouldn't!).
Impact
An attacker who can obtain a trusted client certificate with a null byte embedded in an OTHERNAME SAN can exploit this vulnerability. The practical impact is unauthorized impersonation of the matched identity, enabling access to services or APIs protected by that exact OTHERNAME check.
Credit
[[email protected]](mailto:[email protected])
Medium Basis: The source's own band: MODERATE
1.36.0, fixed 1.36.3 (semver)1.36.3
1.36.3go get github.com/envoyproxy/[email protected]1.35.0, fixed 1.35.7 (semver)1.35.7
1.35.7go get github.com/envoyproxy/[email protected]1.34.0, fixed 1.34.11 (semver)1.34.11
1.34.11go get github.com/envoyproxy/[email protected]0, fixed 1.33.13 (semver)1.33.13
1.33.13go get github.com/envoyproxy/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0