Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2015.2300
Multiple vulnerabilities have been identified in BIND
3 September 2015
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: BIND
Publisher: ISC
Operating System: UNIX variants (UNIX, Linux, OSX)
Windows
Impact/Access: Denial of Service -- Remote/Unauthenticated
Resolution: Patch/Upgrade
CVE Names: CVE-2015-5986 CVE-2015-5722
Original Bulletin:
https://kb.isc.org/article/AA-01291/74/CVE-2015-5986%3A-An-incorrect-boundary-check-can-trigger-a-REQUIRE-assertion-failure-in-openpgpkey_61.c.html
https://kb.isc.org/article/AA-01287/74/CVE-2015-5722%3A-Parsing-malformed-keys-may-cause-BIND-to-exit-due-to-a-failed-assertion-in-buffer.c.html
Comment: This bulletin contains two (2) ISC security advisories.
- --------------------------BEGIN INCLUDED TEXT--------------------
CVE-2015-5986: An incorrect boundary check can trigger a REQUIRE assertion
failure in openpgpkey_61.c
Author: Michael McNally
Reference Number: AA-01291
Created: 2015-08-19 08:22
Last Updated: 2015-09-02 20:00
CVE: CVE-2015-5986
Document Version: 2.0
Posting date: 02 September 2015
Program Impacted: BIND
Versions affected: 9.9.7 -> 9.9.7-P2, 9.10.2 -> 9.10.2-P3.
Severity: Critical
Exploitable: Remotely
Description:
An incorrect boundary check in openpgpkey_61.c can cause named to terminate
due to a REQUIRE assertion failure. This defect can be deliberately exploited
by an attacker who can provide a maliciously constructed response in answer to
a query.
Impact:
A server which encounters this error will terminate due to a REQUIRE assertion
failure, resulting in denial of service to clients.
Recursive servers are at greatest risk from this defect but some circumstances
may exist in which the attack can be successfully exploited against an
authoritative server. Servers should be upgraded to a fixed version.
CVSS Score: 7.1
CVSS Vector: (AV:N/AC:M/Au:N/C:N/I:N/A:C)
For more information on the Common Vulnerability Scoring System and to obtain
your specific environmental score please visit:
http://nvd.nist.gov/cvss.cfm?calculator&adv&version=2&vector=(AV:N/AC:M/Au:N/C:N/I:N/A:C)
Workarounds:
No workarounds are known to exist.
Active exploits:
None known.
Solution:
Upgrade to the patched release most closely related to your current version of
BIND. These can all be downloaded from http://www.isc.org/downloads.
BIND 9 version 9.9.7-P3
BIND 9 version 9.10.2-P4
BIND development releases scheduled to be published at the same time as the
public disclosure of this vulnerability will also contain the fix for this
security issue.
BIND 9 version 9.9.8rc1
BIND 9 version 9.10.3rc1
Document Revision History:
1.0 Advance Notification 19 August, 2015
2.0 Public Disclosure 2 September, 2015
Related Documents:
See our BIND9 Security Vulnerability Matrix at
https://kb.isc.org/article/AA-00913 for a complete listing of Security
Vulnerabilities and versions affected.
If you'd like more information on ISC Subscription Support and Advance
Security Notifications, please visit http://www.isc.org/support/.
Do you still have questions? Questions regarding this advisory should go to
security-officer@isc.org. To report a new issue, please encrypt your message
using security-officer@isc.org's PGP key which can be found here:
https://www.isc.org/downloads/software-support-policy/openpgp-key/. If you are
unable to use encrypted email, you may also report new issues at:
https://www.isc.org/community/report-bug/.
Note: ISC patches only currently supported versions. When possible we indicate
EOL versions affected. (For current information on which versions are actively
supported, please see http://www.isc.org/downloads/).
ISC Security Vulnerability Disclosure Policy: Details of our current security
advisory policy and practice can be found here:
https://kb.isc.org/article/AA-00861/164/ISC-Software-Defect-and-Security-Vulnerability-Disclosure-Policy.html
This Knowledge Base article https://kb.isc.org/article/AA-01291 is the
complete and official security advisory document.
Legal Disclaimer:
Internet Systems Consortium (ISC) is providing this notice on an "AS IS"
basis. No warranty or guarantee of any kind is expressed in this notice and
none should be implied. ISC expressly excludes and disclaims any warranties
regarding this notice or materials referred to in this notice, including,
without limitation, any implied warranty of merchantability, fitness for a
particular purpose, absence of hidden defects, or of non-infringement. Your
use or reliance on this notice or materials referred to in this notice is at
your own risk. ISC may change this notice at any time. A stand-alone copy or
paraphrase of the text of this document that omits the document URL is an
uncontrolled copy. Uncontrolled copies may lack important information, be out
of date, or contain factual errors.
(c) 2001-2015 Internet Systems Consortium
Please help us to improve the content of our knowledge base by letting us know
below how we can improve this article.
If you have a technical question or problem on which you'd like help, please
don't submit it here as article feedback.
For assistance with problems and questions for which you have not been able to
find an answer in our Knowledge Base, we recommend searching our community
mailing list archives and/or posting your question there (you will need to
register there first for your posts to be accepted). The bind-users and the
dhcp-users lists particularly have a long-standing and active membership.
ISC relies on the financial support of the community to fund the development
of its open source software products. If you would like to support future
product evolution and maintenance as well having peace of mind knowing that
our team of experts are poised to provide you with individual technical
assistance whenever you call upon them, then please consider our Professional
Subscription Support services - details can be found on our main website.
- ------------------------------------------------------------------------------
CVE-2015-5722: Parsing malformed keys may cause BIND to exit due to a failed
assertion in buffer.c
Author: Michael McNally
Reference Number: AA-01287
Created: 2015-08-03 21:26
Last Updated: 2015-09-02 20:00
CVE: CVE-2015-5722
Document Version: 2.0
Posting date: 2 September 2015
Program Impacted: BIND
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
Description:
Parsing a malformed DNSSEC key can cause a validating resolver to exit due to
a failed assertion in buffer.c. It is possible for a remote attacker to
deliberately trigger this condition, for example by using a query which
requires a response from a zone containing a deliberately malformed key.
Impact:
Recursive servers are at greatest risk but an authoritative server could be
affected if an attacker controls a zone the server must query against to
perform its zone service.
Servers which are affected may terminate with an assertion failure, causing
denial of service to all clients.
CVSS Score: 7.8
CVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:C)
For more information on the Common Vulnerability Scoring System and to obtain
your specific environmental score please visit:
https://nvd.nist.gov/cvss.cfm?calculator&version=2&vector=(AV:N/AC:L/Au:N/C:N/I:N/A:C)
Workarounds:
Servers which are not performing validation are not at risk from this defect
(but are at increased risk from other types of DNS attack.) ISC does not
recommend disabling validation to deal with this issue; upgrading to a fixed
version is the preferred solution.
Active exploits:
None known
Solution:
Upgrade to the patched release most closely related to your current version of
BIND. These can all be downloaded from http://www.isc.org/downloads.
BIND 9 version 9.9.7-P3
BIND 9 version 9.10.2-P4
BIND development releases scheduled to be published at the same time as the
public disclosure of this vulnerability will also contain the fix for this
security issue.
BIND 9 version 9.9.8rc1
BIND 9 version 9.10.3rc1
Acknowledgements:
ISC would like to thank Hanno Bck from the Fuzzing Project for discovering and
reporting this defect. We would also like to express our appreciation to the
developers of the American Fuzzy Lop tool, which has been instrumental in
revealing recently-disclosed vulnerabilities in BIND.
Document Revision History:
1.0 Advance Notification 19 August 2015
1.1 "Versions affected" information clarified 24 August, 2015
2.0 Public Disclosure 2 September, 2015
Related Documents:
See our BIND9 Security Vulnerability Matrix at
https://kb.isc.org/article/AA-00913 for a complete listing of Security
Vulnerabilities and versions affected.
If you'd like more information on ISC Subscription Support and Advance
Security Notifications, please visit http://www.isc.org/support/.
Do you still have questions? Questions regarding this advisory should go to
security-officer@isc.org. To report a new issue, please encrypt your message
using security-officer@isc.org's PGP key which can be found here:
https://www.isc.org/downloads/software-support-policy/openpgp-key/. If you are
unable to use encrypted email, you may also report new issues at:
https://www.isc.org/community/report-bug/.
Note: ISC patches only currently supported versions. When possible we indicate
EOL versions affected. (For current information on which versions are actively
supported, please see http://www.isc.org/downloads/).
ISC Security Vulnerability Disclosure Policy: Details of our current security
advisory policy and practice can be found here:
https://kb.isc.org/article/AA-00861/164/ISC-Software-Defect-and-Security-Vulnerability-Disclosure-Policy.html
This Knowledge Base article https://kb.isc.org/article/AA-01287 is the
complete and official security advisory document.
Legal Disclaimer:
Internet Systems Consortium (ISC) is providing this notice on an "AS IS"
basis. No warranty or guarantee of any kind is expressed in this notice and
none should be implied. ISC expressly excludes and disclaims any warranties
regarding this notice or materials referred to in this notice, including,
without limitation, any implied warranty of merchantability, fitness for a
particular purpose, absence of hidden defects, or of non-infringement. Your
use or reliance on this notice or materials referred to in this notice is at
your own risk. ISC may change this notice at any time. A stand-alone copy or
paraphrase of the text of this document that omits the document URL is an
uncontrolled copy. Uncontrolled copies may lack important information, be out
of date, or contain factual errors.
(c) 2001-2015 Internet Systems Consortium
Please help us to improve the content of our knowledge base by letting us know
below how we can improve this article.
If you have a technical question or problem on which you'd like help, please
don't submit it here as article feedback.
For assistance with problems and questions for which you have not been able to
find an answer in our Knowledge Base, we recommend searching our community
mailing list archives and/or posting your question there (you will need to
register there first for your posts to be accepted). The bind-users and the
dhcp-users lists particularly have a long-standing and active membership.
ISC relies on the financial support of the community to fund the development
of its open source software products. If you would like to support future
product evolution and maintenance as well having peace of mind knowing that
our team of experts are poised to provide you with individual technical
assistance whenever you call upon them, then please consider our Professional
Subscription Support services - details can be found on our main website.
- --------------------------END INCLUDED TEXT--------------------
You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.
NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members. As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.
NOTE: This is only the original release of the security bulletin. It may
not be updated when updates to the original are made. If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.
Contact information for the authors of the original document is included
in the Security Bulletin above. If you have any questions or need further
information, please contact them directly.
Previous advisories and external security bulletins can be retrieved from:
http://www.auscert.org.au/render.html?cid=1980
===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072
Internet Email: auscert@auscert.org.au
Facsimile: (07) 3365 7031
Telephone: (07) 3365 4417 (International: +61 7 3365 4417)
AusCERT personnel answer during Queensland business hours
which are GMT+10:00 (AEST).
On call after hours for member emergencies only.
===========================================================================
-----BEGIN PGP SIGNATURE-----
Comment: http://www.auscert.org.au/render.html?it=1967
iQIVAwUBVee4f36ZAP0PgtI9AQJD3w/+MitIh+GL/0mi3rRPzBRs3KsUwqqaaquB
ftVSSvSReRY6buSA6uHBrM8Uc0TFf9w6luIhM7hhSi4HytaFSHfwLTtJm2PkNGUd
1mInVtGTHRtzy7EWA4Y/GySWkHbriGrBdLAy3sYVxlXlH+XguorXSul5uJfVB7/Z
LmjBr+ZONEtj37uKfDHhibmxkZumbCY2xW9RjhPwXWyPPQ8CDvkta9rjTRNoMd/5
SodUqa7lgtPJJtZ7NHAuFPsUh9EBMDEs5YLHti2QVKaOKgVgWZEb898UtACVPKgK
dkCad5Xv/ler7pPtBx22eMRGWzH5Rh0R5xV6PSBiPWLHkYZWNhsavYDaDLLlU1b1
0XfQJRDUcdNMhB58JJ7Or0JFfz16MfIgLkoj3SbHNDP5F7vTG/yo3glf+vs3Mo55
kFE+NaK3XvsMGaT7tSaJbpjGCjxNSu8r4jtuS+VlJxMwD22JL2JkRFjasSop98Oq
ebPjlpCMTMuueQY9kPCNayr7SEOtSdgnyQinKrmqwrsR9ETzj+DPDm7yc31v26X1
NATsd3d26VwKPOYkTGEPzujpExCQbypoL33lDesvwrMJpUPX7Xy/YoG/5xXbes9e
MEPYaeEaqyen6b8CP7d6pk13cr2LCGfnXpMUjvtHb/v/MAay7oLJAWSEKC5oFDfo
s995oXa6V3E=
=btRq
-----END PGP SIGNATURE-----