Bug 8281

1) CVE-2015-1349: A Problem with Trust Anchor Management Can Cause named to Crash When configured to perform DNSSEC validation, named can crash when encountering a rare set of conditions in the managed trust anchors.

Versions affected: BIND 9.7.0 -> BIND 9.10.1-P1.  
Also, b1 and rc1 development versions of the upcoming BIND maintenance releases (9.9.7b1 & rc1, 9.10.2b1 & rc1) are affected.
BIND versions 9.9.6, 9.9.6-P1, 9.10.1, and 9.10.1-P1 will terminate consistently with an assertion in zone.c, but previous affected versions may exhibit unpredictable behavior, including server crashes, due to the use of an improperly initialized variable.

Severity: High, but requires specific conditions.
Exploitable: Remotely, under limited circumstances.
Reference: https://kb.isc.org/article/AA-01235/0/CVE-2015-1349%3A-A-Problem-with-Trust-Anchor-Management-Can-Cause-named-to-Crash.html 
 
Affected & fixed branches:    
            master| fido (bind_9.9.5)| dizzy(bind_9.9.5)
--------------------------------------------------------
Is affected| yes  |          yes     |  yes
Is fixed   | yes  |          yes     |  no
 
=========================================================

2) CVE-2015-4620: Specially Constructed Zone Data Can Cause a Resolver to Crash when Validating 

An attacker who can cause a validating resolver to query a zone containing specifically constructed contents can cause that resolver to fail an assertion and terminate due to a defect in validation code.

Versions affected: BIND 9.7.1 -> 9.7.7, 9.8.0 -> 9.8.8, 9.9.0 -> 9.9.7, 9.10.0 -> 9.10.2-P1.  
Severity: Critical
Exploitable: Remotely
Reference: https://kb.isc.org/article/AA-01267/0/CVE-2015-4620%3A-Specially-Constructed-Zone-Data-Can-Cause-a-Resolver-to-Crash-when-Validating.html 

Affected & fixed branches:    
            master| fido (bind_9.9.5)| dizzy(bind_9.9.5)
--------------------------------------------------------
Is affected| yes  |          yes     |  yes
Is fixed   | yes  |          yes     |  no
 
=========================================================

3) CVE-2015-5477: An error in handling TKEY queries can cause named to exit with a REQUIRE assertion failure
Versions affected: 9.1.0 -> 9.8.x, 9.9.0->9.9.7-P1, 9.10.0->9.10.2-P2
Severity: Critical
Exploitable:  Remotely
Reference: https://kb.isc.org/article/AA-01272/0/CVE-2015-5477%3A-An-error-in-handling-TKEY-queries-can-cause-named-to-exit-with-a-REQUIRE-assertion-failure.html

Affected & fixed branches:    
            master| fido (bind_9.9.5)| dizzy(bind_9.9.5)
--------------------------------------------------------
Is affected| yes  |          yes     |  yes
Is fixed   | yes  |          yes     |  yes
 
=========================================================

4) CVE-2015-5722: Parsing malformed keys may cause BIND to exit due to a failed assertion in buffer.c 
Versions affected: BIND 9.0.0 -> 9.8.8,  BIND 9.9.0 -> 9.9.7-P2, BIND 9.10.0 -> 9.10.2-P3
Severity: Critical
Exploitable: Remotely
Reference: https://www.isc.org/blogs/cve-2015-5722-parsing-malformed-keys-may-cause-bind-to-exit-due-to-a-failed-assertion-in-buffer-c/ 

Affected & fixed branches:    
            master| fido (bind_9.9.5)| dizzy(bind_9.9.5)
--------------------------------------------------------
Is affected| yes  |          yes     |  yes
Is fixed   | yes  |          yes     |  no
 
=========================================================

5) CVE-2015-5986: An incorrect boundary check can trigger a REQUIRE assertion failure in openpgpkey_61.c
Versions affected:  9.9.7 -> 9.9.7-P2 and 9.10.2 -> 9.10.2-P3.
Severity:  Critical
Exploitable: Remotely

Reference: https://www.isc.org/blogs/cve-2015-5986-an-incorrect-boundary-check-can-trigger-a-require-assertion-failure-in-openpgpkey_61-c/ 

Affected & fixed branches:    
            master| fido (bind_9.9.5)| dizzy(bind_9.9.5)
--------------------------------------------------------
Is affected| no   |          no      |  no


**Note** 
bind in master is upgraded to bind_9.10.2-P4 which addresses all these CVEs.
All these issues affected fido branch are fixed.

Remaining issues are to fix the following CVEs in dizzy branch:
CVE-2015-5722, CVE-2015-4620 and CVE-2015-1349.