cve/2018/CVE-2018-5745.md

24 lines
3.3 KiB
Markdown
Raw Normal View History

2024-05-26 14:27:05 +02:00
### [CVE-2018-5745](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5745)
![](https://img.shields.io/static/v1?label=Product&message=BIND%209&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=BIND%209BIND%209.9.0%20-%3E%209.10.8-P1%2C%209.11.0%20-%3E%209.11.5-P1%2C%209.12.0%20-%3E%209.12.3-P1%2C%20and%20versions%209.9.3-S1%20-%3E%209.11.5-S3%20of%20BIND%209%20Supported%20Preview%20Edition.%20Versions%209.13.0%20-%3E%209.13.6%20of%20the%209.13%20development%20branch%20are%20also%20affected.%20Versions%20prior%20to%20BIND%209.9.0%20have%20not%20been%20evaluated%20for%20vulnerability%20to%20CVE-2018-5745.%20&color=brighgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=This%20particular%20vulnerability%20would%20be%20very%20difficult%20for%20an%20arbitrary%20attacker%20to%20use%20because%20it%20requires%20an%20operator%20to%20have%20BIND%20configured%20to%20use%20a%20trust%20anchor%20managed%20by%20the%20attacker.%20However%2C%20if%20successfully%20exercised%2C%20the%20defect%20will%20cause%20named%20to%20deliberately%20exit%20after%20encountering%20an%20assertion%20failure.%0A%0AIt%20is%20more%20likely%2C%20perhaps%2C%20that%20this%20bug%20could%20be%20encountered%20accidentally%2C%20as%20not%20all%20versions%20of%20BIND%20support%20the%20same%20set%20of%20cryptographic%20algorithms.%20Specifically%2C%20recent%20branches%20of%20BIND%20have%20begun%20deliberately%20removing%20support%20for%20cryptographic%20algorithms%20that%20are%20now%20deprecated%20(for%20example%20because%20they%20are%20no%20longer%20considered%20sufficiently%20secure.)%20This%20vulnerability%20could%20be%20encountered%20if%20a%20resolver%20running%20a%20version%20of%20BIND%20which%20has%20removed%20support%20for%20deprecated%20algorithms%20is%20configured%20to%20use%20a%20trust%20anchor%20which%20elects%20to%20change%20algorithm%20types%20to%20one%20of%20those%20deprecated%20algorithms.%0A%0A%20%20%20%20Support%20for%20GOST%20was%20removed%20from%20BIND%20in%209.13.1.%0A%20%20%20%20Support%20for%20DSA%20was%20removed%20from%20BIND%20in%209.13.4%0A%20%20%20%20Support%20for%20RSAMD5%20will%20be%20removed%20from%20future%20BIND%20releases%20in%20the%209.13%20branch%20and%20higher.%0A&color=brighgreen)
### Description
"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.
### POC
#### Reference
No PoCs from references.
#### Github
- https://github.com/ARPSyndicate/cvemon
- https://github.com/HJXSaber/bind9-my
- https://github.com/balabit-deps/balabit-os-8-bind9-libs
- https://github.com/balabit-deps/balabit-os-9-bind9-libs
- https://github.com/fokypoky/places-list
- https://github.com/pexip/os-bind9
- https://github.com/pexip/os-bind9-libs