Concurrent GSS-TSIG messages corrupt memory
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. No fixed version is recorded.
Replaying GSS-TSIG signed UDP messages can result in memory corruption in "`named`". An attacker who can capture a previously signed UDP message can replay it while the negotiated TSIG key is still valid. By also sending crafted queries to a zone the attacker controls, the attacker may potentially achieve remote code execution. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.29, 9.21.0 through 9.21.26, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.29-S1.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| ISC | BIND | >=9.11.0 <=9.18.50, >=9.11.3-S1 <=9.18.50-S1, >=9.20.0 <=9.20.29, >=9.20.9-S1 <=9.20.29-S1, >=9.21.0 <=9.21.26 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in BIND, strongest first
Embed
A live severity badge for an advisory, README or ticket