BlackTreeIndependent security intelligence
← Back to the CVE catalogue
Full vulnerability report · 2019
CVE-2018-5745High confidence

An assertion failure can occur if a trust anchor rolls over to an unsupported key algorithm when using managed-keys

ISC · BIND 9

4.9MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2018-5745 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitybind: An assertion failure if a trust anchor rolls over to an unsupported key algorithm when using managed-keys
7 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • bind as a component of Red Hat Enterprise Linux 6
  • bind-chroot as a component of Red Hat Enterprise Linux 6
  • bind-devel as a component of Red Hat Enterprise Linux 6
  • bind-libs as a component of Red Hat Enterprise Linux 6
  • bind-sdb as a component of Red Hat Enterprise Linux 6
  • bind-utils as a component of Red Hat Enterprise Linux 6
  • bind.src as a component of Red Hat Enterprise Linux 6
Summary
An assertion failure was found in the way bind implemented the "managed keys" feature. An attacker could use this flaw to cause the named daemon to crash. This flaw is very difficult for an attacker to trigger because it requires an operator to have BIND configured to use a trust anchor managed by the attacker.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2018-17514

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

"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.

What

"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.

Why

The product uses a broken or risky cryptographic algorithm or protocol.

How

An attacker operating through a network path may attempt exploitation with elevated privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

"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.

Why

The product uses a broken or risky cryptographic algorithm or protocol.

How

An attacker operating through a network path may attempt exploitation with elevated privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Use of a Broken or Risky Cryptographic Algorithm → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
High: elevated access is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-327 ↗

CWE-327: Use of a Broken or Risky Cryptographic Algorithm. The product uses a broken or risky cryptographic algorithm or protocol.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRHighPrivileges required: The attacker needs elevated or administrative privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkCWE-327
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-W-2025-1194Internet Systems Consortium BIND: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Internet Systems Consortium BIND ausnutzen, um einen Denial of Service Angriff durchzuführen oder Informationen offenzulegen.

Official advisory
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
bind as a component of Red Hat Enterprise Linux 6; bind-chroot as a component of Red Hat Enterprise Linux 6; bind-devel as a component of Red Hat Enterprise Linux 6; bind-libs as a component of Red Hat Enterprise Linux 6; bind-sdb as a component of Red Hat Enterprise Linux 6; bind-utils as a component of Red Hat Enterprise Linux 6; bind.src as a component of Red Hat Enterprise Linux 6
Fixed
bind-32:9.11.4-16.P2.el7.src as a component of Red Hat Enterprise Linux Client (v. 7); bind-debuginfo-32:9.11.4-16.P2.el7.i686 as a component of Red Hat Enterprise Linux Client (v. 7); bind-debuginfo-32:9.11.4-16.P2.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7); bind-export-libs-32:9.11.4-16.P2.el7.i686 as a component of Red Hat Enterprise Linux Client (v. 7); bind-export-libs-32:9.11.4-16.P2.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7); bind-libs-32:9.11.4-16.P2.el7.i686 as a component of Red Hat Enterprise Linux Client (v. 7); bind-libs-32:9.11.4-16.P2.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7); bind-libs-lite-32:9.11.4-16.P2.el7.i686 as a component of Red Hat Enterprise Linux Client (v. 7); bind-libs-lite-32:9.11.4-16.P2.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7); bind-license-32:9.11.4-16.P2.el7.noarch as a component of Red Hat Enterprise Linux Client (v. 7); bind-utils-32:9.11.4-16.P2.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7); bind-32:9.11.4-16.P2.el7.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7); bind-chroot-32:9.11.4-16.P2.el7.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7); bind-debuginfo-32:9.11.4-16.P2.el7.i686 as a component of Red Hat Enterprise Linux Client Optional (v. 7); bind-debuginfo-32:9.11.4-16.P2.el7.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7); bind-devel-32:9.11.4-16.P2.el7.i686 as a component of Red Hat Enterprise Linux Client Optional (v. 7); bind-devel-32:9.11.4-16.P2.el7.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7); bind-export-devel-32:9.11.4-16.P2.el7.i686 as a component of Red Hat Enterprise Linux Client Optional (v. 7); bind-export-devel-32:9.11.4-16.P2.el7.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7); bind-lite-devel-32:9.11.4-16.P2.el7.i686 as a component of Red Hat Enterprise Linux Client Optional (v. 7); bind-lite-devel-32:9.11.4-16.P2.el7.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7); bind-pkcs11-32:9.11.4-16.P2.el7.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7); bind-pkcs11-devel-32:9.11.4-16.P2.el7.i686 as a component of Red Hat Enterprise Linux Client Optional (v. 7); bind-pkcs11-devel-32:9.11.4-16.P2.el7.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7); bind-pkcs11-libs-32:9.11.4-16.P2.el7.i686 as a component of Red Hat Enterprise Linux Client Optional (v. 7); bind-pkcs11-libs-32:9.11.4-16.P2.el7.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7); bind-pkcs11-utils-32:9.11.4-16.P2.el7.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7); bind-sdb-32:9.11.4-16.P2.el7.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7); bind-sdb-chroot-32:9.11.4-16.P2.el7.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7); bind-32:9.11.4-16.P2.el7.src as a component of Red Hat Enterprise Linux ComputeNode (v. 7); and 328 more
Action
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, the BIND daemon (named) will be restarted automatically.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 9 Oct 2019 · Last source change 16 Sept 2024, 23:51 UTC · CWE-327 · Use of a Broken or Risky Cryptographic Algorithm

CVE recordCVE.org · 5.1
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-09-01
European sourceENISA EUVD · EUVD-2018-17514
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates →
  1. ENISA EUVD mappingEUVD-2018-17514 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2018-17514"}
    ENISA EUVD ↗
  2. Vendor guidanceAuthoritative vendor guidance changed from vendor advisory to no authoritative guidance recorded.
    Before
    vendor advisory
    After
    no authoritative guidance recorded
    CNA ↗
  3. CVSS scoreCVSS version changed from 3.0 to 3.1; the displayed base score remains 4.9.
    Before
    4.9 (CVSS 3.0 · CNA · CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H)
    After
    4.9 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H)
    NIST NVD ↗
  4. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
ENISA EUVD · EUVD-2018-17514↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2018-5745 · cve.blacktree.nl