1-minute read
What a defender needs to know
CERT/CC’s October 14 note divides five Google BoringSSL Name Constraints findings by validator and outcome. The legacy crypto/x509 path covers wildcard DNS exclusion (VU#410595.8), URI host parsing with a colon before @ (.9), disputed multi-@ mail-name matching (.10), and trailing-dot DNS normalization (.12). The newer pki path covers a trailing-dot mail-name finding (.11) that BoringSSL declined. CERT/CC says upstream commit 5774eca fixed .8 and .12 on March 4; .9 remains accepted and under coordination.
A constrained subordinate CA can issue a trusted signature, but the validator must still enforce its permitted and excluded names before the application authorizes access. Identify the product build and the validator actually used for that decision. Obtain the vendor’s update carrying the two fixed legacy-path findings and follow .9 separately. Record which SAN forms the authorization path accepts before labeling the product affected.
Use the product’s supported validation test with the same constrained test CA and authorization path. An in-scope name should pass; an excluded name should fail. Keep the installed build, presented certificate chain, and certificate-validation log entry or supported test output showing the decision. CERT/CC says a second validator helps when it receives the same inputs and fails closed.