CVE-2017-3137

Publication date 12 April 2017

Last updated 24 July 2024

Ubuntu priority

Cvss 3 Severity Score

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.

Read the notes from the security team

Status

Show unmaintained releases

Package	Ubuntu Release	Status
bind9	17.04 zesty	Fixed 1:9.10.3.dfsg.P4-10.1ubuntu5
	16.10 yakkety	Fixed 1:9.10.3.dfsg.P4-10.1ubuntu1.6
	16.04 LTS xenial	Fixed 1:9.10.3.dfsg.P4-8ubuntu1.6
	14.04 LTS trusty	Fixed 1:9.9.5.dfsg-3ubuntu0.14
	12.04 LTS precise	Fixed 1:9.8.1.dfsg.P1-4ubuntu0.22

Notes

sbeattie

in bind9 9.9 and earlier, with the bind9 patch for this issue applied, named will hit another assertion; to fix that requires the lib/dns/named.c change from https://source.isc.org/cgi-bin/gitweb.cgi?p=bind9.git;a=commitdiff;h=dc3912f3caac1104fef441fd18571b7a975708ea

Severity score breakdown

Parameter	Value
Base score	7.5 · High
Attack vector	Network
Attack complexity	Low
Privileges required	None
User interaction	None
Scope	Unchanged
Confidentiality	None
Integrity impact	None
Availability impact	High
Vector	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

Related Ubuntu Security Notices (USN)

USN-3259-1
Bind vulnerabilities
17 April 2017