CVE-2017-3137
Description
Mistaken assumptions about the ordering of records in the answer section of a response containing CNAME or DNAME resource records could lead to a situation in which named would exit with an assertion failure when processing a response in which records occurred in an unusual order. Affects BIND 9.9.9-P6, 9.9.10b1->9.9.10rc1, 9.10.4-P6, 9.10.5b1->9.10.5rc1, 9.11.0-P3, 9.11.1b1->9.11.1rc1, and 9.9.9-S8.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
| OS | Version | Status | Fixed in |
|---|---|---|---|
| debian | bookworm | fixed | 1:9.10.3.dfsg.P4-12.3 |
| debian | bullseye | fixed | 1:9.10.3.dfsg.P4-12.3 |
| debian | forky | fixed | 1:9.10.3.dfsg.P4-12.3 |
| debian | sid | fixed | 1:9.10.3.dfsg.P4-12.3 |
| debian | trixie | fixed | 1:9.10.3.dfsg.P4-12.3 |
| arch | fixed | 9.11.1-1 | |
| sles | affected | |
References
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.