Envoy’s TLS certificate matcher for `match_typed_subject_alt_names` may incorrectly treat certificates containing an embedded null byte
envoyproxy envoy
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/envoyproxy/envoy Go |
|
|
envoyproxy envoy
| Product | Affected | Fixed in |
|---|---|---|
| github.com/envoyproxy/envoy Go |
|
|
Envoy is a high-performance edge/middle/service proxy. In 1.33.12, 1.34.10, 1.35.6, 1.36.2, and earlier, 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.
From the CVE record · GitHub_M
Envoy’s mTLS certificate matcher may incorrectly accept a certificate as matching `match_typed_subject_alt_names` when an OTHERNAME SAN value contains an embedded null byte. This can occur when that matcher is used; the input does not specify authentication requirements or user interaction.
Teams running Envoy or the Go package `github.com/envoyproxy/envoy` should check versions before 1.33.13, or versions in the 1.34, 1.35, and 1.36 lines before 1.34.11, 1.35.7, and 1.36.3, respectively.