| Package | Affected versions | Patched versions |
|---|---|---|
| bind | = 9.10.5= 9.10.7= 9.11.12= 9.11.21= 9.11.27= 9.11.29= 9.11.3= 9.11.35= 9.11.37= 9.11.4= 9.11.5= 9.11.6= 9.11.7= 9.11.8= 9.16.11= 9.16.12= 9.16.13= 9.16.14= 9.16.21= 9.16.32= 9.16.36= 9.16.43= 9.16.8= 9.18.0= 9.18.18= 9.9.12= 9.9.13= 9.9.3≥ 9.18.0, < 9.18.19≥ 9.19.0, < 9.19.17≥ 9.2.0, < 9.16.44 | 9.18.199.19.179.16.44 |
The code that processes control channel messages sent to `named` calls certain functions recursively during packet parsing. Recursion depth is only limited by the maximum accepted packet size; depending on the environment, this may cause the packet-parsing code to run out of available stack memory, causing `named` to terminate unexpectedly. Since each incoming control channel message is fully parsed before its contents are authenticated, exploiting this flaw does not require the attacker to hold a valid RNDC key; only network access to the control channel's configured TCP port is necessary. This issue affects BIND 9 versions 9.2.0 through 9.16.43, 9.18.0 through 9.18.18, 9.19.0 through 9.19.16, 9.9.3-S1 through 9.16.43-S1, and 9.18.0-S1 through 9.18.18-S1.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free