CVE-2018-5737

published 16 Jan 2019 · updated 16 Sep 2024

BIND 9.12's serve-stale implementation can cause an assertion failure in rbtdb.c or other undesirable behavior, even if serve-stale is not enabled.

6.4MediumCVSS 5.9EPSS 11%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 11%. No fixed version is recorded.

A problem with the implementation of the new serve-stale feature in BIND 9.12 can lead to an assertion failure in rbtdb.c, even when stale-answer-enable is off. Additionally, problematic interaction between the serve-stale feature and NSEC aggressive negative caching can in some cases cause undesirable behavior from named, such as a recursion loop or excessive logging. Deliberate exploitation of this condition could cause operational problems depending on the particular manifestation -- either degradation or denial of service. Affects BIND 9.12.0 and 9.12.1.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
ISCBIND=9.12.0 and 9.12.1

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in BIND, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2018-5737 severity on Zeptric[![CVE-2018-5737](https://zeptric.io/badge/cve/CVE-2018-5737.svg)](https://zeptric.io/cve/CVE-2018-5737)