[CVE-2022-0635] DNAME lookups can trigger INSIST when synth-from-dnssec is enabled
Lookups involving a DNAME
could trigger an INSIST
when synth-from-dnssec
is enabled.
CVE-specific actions
-
Assign a CVE identifier -
Determine CVSS score -
Determine the range of BIND versions affected (including the Subscription Edition) - 9.18.0
-
Determine whether workarounds for the problem exists - Issue can be mitigated by setting
synth-from-dnssec no;
.
- Issue can be mitigated by setting
-
Create a draft of the security advisory and put the information above in there -
Prepare a detailed description of the problem which should include the following by default: - instructions for reproducing the problem (a system test is good enough)
-
synthfromdnssec
system test in isc-private/bind9!370
-
- explanation of code flow which triggers the problem (a system test is not good enough)
- instructions for reproducing the problem (a system test is good enough)
-
Prepare a private merge request containing the following items in separate commits: - a test for the issue (may be moved to a separate merge request for deferred merging)
- isc-private/bind9!370
- a fix for the issue
- isc-private/bind9!390
- documentation updates (
CHANGES
, release notes, anything else applicable)- isc-private/bind9!390
- a test for the issue (may be moved to a separate merge request for deferred merging)
-
Ensure the merge request from the previous step is reviewed by SWENG staff and has no outstanding discussions -
Ensure the documentation changes introduced by the merge request addressing the problem are reviewed by Support and Marketing staff -
Prepare backports of the merge request addressing the problem for all affected (and still maintained) BIND branches (backporting might affect the issue's scope and/or description) - v9.18 isc-private/bind9!391 & isc-private/bind9!372
-
Prepare a standalone patch for the last stable release of each affected (and still maintained) BIND branch - patch for BIND 9.18.0 release derived from isc-private/bind9!391 diff and stripped of documentation changes: 391.diff
Release-specific actions
-
Create/update the private issue containing links to fixes & reproducers for all CVEs fixed in a given release cycle -
Reserve a block of CHANGES
placeholders once the complete set of vulnerabilities fixed in a given release cycle is determined -
Ensure the merge requests containing CVE fixes are merged into security-*
branches in CVE identifier order
Post-disclosure actions
-
Merge a regression test reproducing the bug into all affected (and still maintained) BIND branches
Edited by Michal Nowak