medium
5.4
CWE
399
Advisory Published
CVE Published
Updated

CVE-2015-1349

First published: Wed Feb 18 2015(Updated: )

It was reported that a problem with trust anchor management can cause named to crash, affecting BIND versions 9.7.0+. ISC developers believe that it will be very difficult for this to be triggered in most cases, requiring DNSSEC validation amongst other factors. ISC will not be producing patches specifically for BIND 9.8 or BIND 9.6-ESV, both of which are beyond their End of Life (EOL) and are no longer supported by ISC. Patches that correct this issue for ISC BIND 9.10.1 and ISC BIND 9.9.6 are attached to this Bugzilla.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
redhat/BIND<9.9.7
9.9.7
redhat/BIND<9.10.2
9.10.2
BIND 9=9.7.0
BIND 9=9.7.0-b1
BIND 9=9.7.0-p1
BIND 9=9.7.0-p2
BIND 9=9.7.0-rc1
BIND 9=9.7.0-rc2
BIND 9=9.7.1
BIND 9=9.7.1-p1
BIND 9=9.7.1-p2
BIND 9=9.7.1-rc1
BIND 9=9.7.2
BIND 9=9.7.2-p1
BIND 9=9.7.2-p2
BIND 9=9.7.2-p3
BIND 9=9.7.2-rc1
BIND 9=9.7.3
BIND 9=9.7.3-b1
BIND 9=9.7.3-p1
BIND 9=9.7.3-rc1
BIND 9=9.7.4
BIND 9=9.7.4-b1
BIND 9=9.7.4-p1
BIND 9=9.7.4-rc1
BIND 9=9.7.5
BIND 9=9.7.5-b1
BIND 9=9.7.5-rc1
BIND 9=9.7.5-rc2
BIND 9=9.7.6
BIND 9=9.7.6-p1
BIND 9=9.7.6-p2
BIND 9=9.7.7
BIND 9=9.8.0
BIND 9=9.8.0-a1
BIND 9=9.8.0-b1
BIND 9=9.8.0-p1
BIND 9=9.8.0-p2
BIND 9=9.8.0-p4
BIND 9=9.8.0-rc1
BIND 9=9.8.1
BIND 9=9.8.1-b1
BIND 9=9.8.1-b2
BIND 9=9.8.1-b3
BIND 9=9.8.1-p1
BIND 9=9.8.1-rc1
BIND 9=9.8.2-b1
BIND 9=9.8.2-rc1
BIND 9=9.8.2-rc2
BIND 9=9.8.3
BIND 9=9.8.3-p1
BIND 9=9.8.3-p2
BIND 9=9.8.4
BIND 9=9.8.5
BIND 9=9.8.5-b1
BIND 9=9.8.5-b2
BIND 9=9.8.5-p1
BIND 9=9.8.5-p2
BIND 9=9.8.5-rc1
BIND 9=9.8.5-rc2
BIND 9=9.8.6-b1
BIND 9=9.8.6-rc1
BIND 9=9.8.6-rc2
BIND 9=9.9.0
BIND 9=9.9.0-a1
BIND 9=9.9.0-a2
BIND 9=9.9.0-a3
BIND 9=9.9.0-b1
BIND 9=9.9.0-b2
BIND 9=9.9.0-rc1
BIND 9=9.9.0-rc2
BIND 9=9.9.0-rc3
BIND 9=9.9.0-rc4
BIND 9=9.9.1
BIND 9=9.9.1-p1
BIND 9=9.9.1-p2
BIND 9=9.9.2
BIND 9=9.9.3
BIND 9=9.9.3-b1
BIND 9=9.9.3-b2
BIND 9=9.9.3-p1
BIND 9=9.9.3-p2
BIND 9=9.9.3-rc1
BIND 9=9.9.3-rc2
BIND 9=9.9.4-b1
BIND 9=9.9.5
BIND 9=9.9.6
BIND 9=9.9.6-p1
BIND 9=9.9.7-b1
BIND 9=9.10.0
BIND 9=9.10.1
BIND 9=9.10.1-p1
BIND 9=9.10.2-b1
BIND 9=9.10.2-rc1

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2015-1349?

    CVE-2015-1349 has a moderate severity level, primarily affecting the stability of BIND when DNSSEC validation is used.

  • How do I fix CVE-2015-1349?

    To fix CVE-2015-1349, update BIND to version 9.9.7 or 9.10.2.

  • Which versions of BIND are affected by CVE-2015-1349?

    CVE-2015-1349 affects BIND versions 9.7.0 and above.

  • Is there a workaround for CVE-2015-1349?

    There is no official workaround aside from upgrading to a patched version of BIND.

  • What type of vulnerability is CVE-2015-1349?

    CVE-2015-1349 is a trust anchor management vulnerability that can lead to a crash in BIND.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203