Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1578591 - (CVE-2018-5736) CVE-2018-5736 bind: Multiple transfers of a zone in quick succession can cause an assertion failure in rbtdb.c
CVE-2018-5736 bind: Multiple transfers of a zone in quick succession can caus...
Status: CLOSED NOTABUG
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20180518,repor...
: Security
Depends On: 1578903
Blocks: 1578592
  Show dependency treegraph
 
Reported: 2018-05-15 19:52 EDT by Sam Fowler
Modified: 2018-05-23 20:06 EDT (History)
16 users (show)

See Also:
Fixed In Version: bind 9.12.1-P2
Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in the way zone databases were handled by bind. An attacker with permissions to initiate a zone transfer could cause bind to crash.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-05-17 00:01:31 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Sam Fowler 2018-05-15 19:52:04 EDT
BIND versions 9.12.0 and 9.12.1 have an error in zone database reference counting that can lead to an assertion failure if a server attempts several transfers of a slave zone in quick succession.

This defect could be deliberately exercised by an attacker who is permitted to cause a vulnerable server to initiate zone transfers (for example: by sending valid NOTIFY messages), causing the named process to exit after failing the assertion test.
Comment 2 Huzaifa S. Sidhpurwala 2018-05-16 23:59:20 EDT
Statement:

This security flaw only affects bind versions 9.12.0 and 9.12.1. Since Red Hat Enterprise Linux does not ship any of these bind versions, it is not affected.

Note You need to log in before you can comment on or make changes to this bug.