Update policies krb5-subdomain and ms-subdomain do not enforce controls promised in their documentation
Published Jan 16, 2019
6.5
MEDIUMCVSS 3.0
EPSS 3.48%
Description
To provide fine-grained controls over the ability to use Dynamic DNS (DDNS) to update records in a zone, BIND 9 provides a feature called update-policy. Various rules can be configured to limit the types of updates that can be performed by a client, depending on the key used when sending the update request. Unfortunately, some rule types were not initially documented, and when documentation for them was added to the Administrator Reference Manual (ARM) in change #3112, the language that was added to the ARM at that time incorrectly described the behavior of two rule types, krb5-subdomain and ms-subdomain. This incorrect documentation could mislead operators into believing that policies they had configured were more restrictive than they actually were. This affects BIND versions prior to BIND 9.11.5 and BIND 9.12.3.
Affected products
-
- Version BIND 9 Versions prior to BIND 9.11.5 and BIND 9.12.3StatusaffectedConstraints-
- Version
No data.
Red Hat Enterprise Linux 7
bind-32:9.11.4-9.P2.el7
Fixed · RHSA-2019:2057
Red Hat Enterprise Linux 5
bind
Not affected
Red Hat Enterprise Linux 5
bind97
Not affected
Red Hat Enterprise Linux 6
bind
Will not fix
Red Hat Enterprise Linux 8
bind
Not affected
Red Hat Virtualization 4
bind
Not affected
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 7 | bind-32:9.11.4-9.P2.el7 | Fixed | RHSA-2019:2057 |
| Red Hat Enterprise Linux 5 | bind | Not affected | n/a |
| Red Hat Enterprise Linux 5 | bind97 | Not affected | n/a |
| Red Hat Enterprise Linux 6 | bind | Will not fix | n/a |
| Red Hat Enterprise Linux 8 | bind | Not affected | n/a |
| Red Hat Virtualization 4 | bind | Not affected | n/a |
No package ranges for this CVE.
Remediation
Vendor solution
At the time of public disclosure, ISC is not providing any code changing the behavior of the update-policy feature. While we believe that there are a few operators out there who are relying on the strictest interpretation permitted by the erroneous documentation, we have to balance that against changing the behavior of features in stable branches of BIND, including the 9.11 branch which is meant to be a feature-complete Extended Support Version of BIND 9. As a compromise between these conflicting priorities, we have decided that our best course of action is to disclose the error but leave the existing behavior of the krb5-subdomain and ms-subdomain policies as they are (while correcting the erroneous documentation).
In maintenance releases issued during or after October 2018, the name field for ms-subdomain and krb5-subdomain will be corrected so that names lower than "." can be configured, and two new rule types will be added, krb5-selfsub and ms-selfsub, analogous to the existing selfsub rule type, which implement the behavior that was formerly described in the documentation for krb5-subdomain and ms-subdomain: restricting updates to names at or below the machine name encoded in the client's Windows or Kerberos principal.
Metrics
No CVSS v4.0 score for this CVE.
No CVSS v3.1 score for this CVE.
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
AV:N/AC:L/Au:S/C:N/I:P/A:N
This CVE is not in the KEV list.
No CISA SSVC assessment for this CVE yet.
Estimated probability of exploitation in the wild in the next 30 days (FIRST EPSS). As of Oct 1, 2026.
Score over time
2021–2026- EPSS v1
- EPSS v2
- EPSS v3
- EPSS v4
- EPSS v5
Percentile over time
- EPSS v1
- EPSS v2
- EPSS v3
- EPSS v4
- EPSS v5
Table of values (17 key points)
Flat stretches are collapsed; showing up to 120 newest points.
| Date | Score | Percentile | Model |
|---|---|---|---|
| Oct 1, 2026 | 3.48% (0.03479) | 88.71th | v5 (v2026.06.15) |
| Jun 23, 2026 | 3.45% (0.03451) | 87.47th | v5 (v2026.06.15) |
| Jun 15, 2026 | 5.29% (0.05285) | 91.49th | v5 (v2026.06.15) |
| Nov 21, 2025 | 0.43% (0.00431) | 61.85th | v4 (v2025.03.14) |
| Nov 18, 2025 | 1.69% (0.01685) | 80.70th | v4 (v2025.03.14) |
| Mar 17, 2025 | 0.46% (0.00464) | 62.26th | v4 (v2025.03.14) |
| Dec 12, 2024 | 0.32% (0.00319) | 71.39th | v3 (v2023.03.01) |
| Feb 10, 2024 | 0.32% (0.00319) | 69.74th | v3 (v2023.03.01) |
| Feb 8, 2024 | 0.34% (0.00343) | 70.75th | v3 (v2023.03.01) |
| Mar 7, 2023 | 0.34% (0.00340) | 66.83th | v3 (v2023.03.01) |
| Mar 6, 2023 | 2.81% (0.02812) | 83.12th | v2 (v2022.01.01) |
| Apr 1, 2022 | 2.81% (0.02812) | 81.44th | v2 (v2022.01.01) |
| Feb 4, 2022 | 2.81% (0.02812) | 63.95th | v2 (v2022.01.01) |
| Feb 3, 2022 | 2.07% (0.02069) | 50.36th | v1 |
| Jan 6, 2022 | 2.07% (0.02069) | 49.86th | v1 |
| Sep 1, 2021 | 2.07% (0.02069) | 77.27th | v1 |
| Apr 14, 2021 | 2.07% (0.02069) | 0.00th | v1 |
References (13)
- http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00041.html vendor-advisoryx_refsource_SUSE
- http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00044.html vendor-advisoryx_refsource_SUSE
- http://www.securityfocus.com/bid/105379 vdb-entryx_refsource_BIDThird Party AdvisoryVDB Entry
- http://www.securitytracker.com/id/1041674 vdb-entryx_refsource_SECTRACKThird Party AdvisoryVDB Entry
- https://access.redhat.com/errata/RHSA-2019:2057 vendor-advisoryx_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2018-5741 Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=1631131 Issue Tracking
- https://kb.isc.org/docs/cve-2018-5741 x_refsource_CONFIRMVendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2018-5741
- https://security.gentoo.org/glsa/201903-13 vendor-advisoryx_refsource_GENTOOThird Party Advisory
- https://security.netapp.com/advisory/ntap-20190830-0001/ x_refsource_CONFIRM
- https://support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpesbux03927en_us x_refsource_CONFIRM
- https://www.cve.org/CVERecord?id=CVE-2018-5741
Change history (0)
No recorded changes yet.