You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bdns: error when CAA query response is truncated (#8839)
This change ensures Boulder never trusts a CAA DNS query response when
the TC (truncated) bit is set. Because the truncated portion may contain
a valid CAA record that forbids issuance, it is not safe to trust a
partial response. A truncated record like `CAA 0 issue ";"` could be
safely ignored given a non-truncated `CAA 0 issue "letsencrypt.org"`;
but if a record with an unknown/unsupported Property tag and the
critical bit set, e.g. `CAA 128 unknown "foo"`, is ever truncated,
that's a definitive misissuance per RFC 8659, [Section
4.1](https://datatracker.ietf.org/doc/html/rfc8659#section-4.1-6.2.2.2).
> __Bit 0, Issuer Critical Flag:__ If the value is set to "1", the
Property is critical. A CA __MUST NOT__ issue certificates for any FQDN
if the Relevant RRset for that FQDN contains a CAA critical Property for
an unknown or unsupported Property Tag.
In practice, it would require a freak accident DNS misconfiguration or a
malicious construction of records (an exercise left to the reader) to
trigger this bug. And in any case, doing so doesn't grant an attacker
any issuance capabilities they don't already have. If you have access to
a domain's DNS zone to exploit this bug, you can already edit CAA
records and validate DNS-01 challenges sufficient to issue a legitimate
certificate.
Nevertheless, this bug represents an attacker-controlled compliance risk
and we should patch it.
0 commit comments