Use of a Risky Cryptographic Algorithm Affecting bind package, versions [9.9.0,9.10.8)[9.11.0,9.11.5)[9.12.0,9.12.3)[9.13.0,9.13.7)


Severity

Recommended
0.0
medium
0
10

CVSS assessment made by Snyk's Security Team. Learn more

Threat Intelligence

EPSS
0.08% (36th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Use of a Risky Cryptographic Algorithm vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-UNMANAGED-BIND-2382069
  • published26 Jan 2022
  • disclosed9 Oct 2019
  • creditUnknown

Introduced: 9 Oct 2019

CVE-2018-5745  (opens in a new tab)
CWE-327  (opens in a new tab)

How to fix?

Upgrade bind to version 9.10.8, 9.11.5, 9.12.3, 9.13.7 or higher.

Overview

Affected versions of this package are vulnerable to Use of a Risky Cryptographic Algorithm. "managed-keys" is a feature which allows a BIND resolver to automatically maintain the keys used by trust anchors which operators configure for use in DNSSEC validation. Due to an error in the managed-keys feature it is possible for a BIND server which uses managed-keys to exit due to an assertion failure if, during key rollover, a trust anchor's keys are replaced with keys which use an unsupported algorithm. Versions affected: BIND 9.9.0 -> 9.10.8-P1, 9.11.0 -> 9.11.5-P1, 9.12.0 -> 9.12.3-P1, and versions 9.9.3-S1 -> 9.11.5-S3 of BIND 9 Supported Preview Edition. Versions 9.13.0 -> 9.13.6 of the 9.13 development branch are also affected. Versions prior to BIND 9.9.0 have not been evaluated for vulnerability to CVE-2018-5745.

References

CVSS Scores

version 3.1