Описание
Using a specially-crafted message, an attacker may potentially cause a BIND server to reach an inconsistent state if the attacker knows (or successfully guesses) the name of a TSIG key used by the server. Since BIND, by default, configures a local session key even on servers whose configuration does not otherwise make use of it, almost all current BIND servers are vulnerable. In releases of BIND dating from March 2018 and after, an assertion check in tsig.c detects this inconsistent state and deliberately exits. Prior to the introduction of the check the server would continue operating in an inconsistent state, with potentially harmful results.
| Релиз | Статус | Примечание |
|---|---|---|
| bionic | released | 1:9.11.3+dfsg-1ubuntu1.12 |
| devel | released | 1:9.16.1-0ubuntu3 |
| eoan | released | 1:9.11.5.P4+dfsg-5.1ubuntu2.2 |
| esm-infra-legacy/trusty | released | 1:9.9.5.dfsg-3ubuntu0.19+esm2 |
| esm-infra-legacy/xenial | released | 1:9.10.3.dfsg.P4-8ubuntu1.16 |
| esm-infra/bionic | released | 1:9.11.3+dfsg-1ubuntu1.12 |
| esm-infra/focal | released | 1:9.16.1-0ubuntu2.1 |
| esm-infra/xenial | released | 1:9.10.3.dfsg.P4-8ubuntu1.16 |
| focal | released | 1:9.16.1-0ubuntu2.1 |
| precise/esm | not-affected | 1:9.8.1.dfsg.P1-4ubuntu0.30 |
Показывать по
EPSS
4.3 Medium
CVSS2
7.5 High
CVSS3
Связанные уязвимости
Using a specially-crafted message, an attacker may potentially cause a BIND server to reach an inconsistent state if the attacker knows (or successfully guesses) the name of a TSIG key used by the server. Since BIND, by default, configures a local session key even on servers whose configuration does not otherwise make use of it, almost all current BIND servers are vulnerable. In releases of BIND dating from March 2018 and after, an assertion check in tsig.c detects this inconsistent state and deliberately exits. Prior to the introduction of the check the server would continue operating in an inconsistent state, with potentially harmful results.
Using a specially-crafted message, an attacker may potentially cause a BIND server to reach an inconsistent state if the attacker knows (or successfully guesses) the name of a TSIG key used by the server. Since BIND, by default, configures a local session key even on servers whose configuration does not otherwise make use of it, almost all current BIND servers are vulnerable. In releases of BIND dating from March 2018 and after, an assertion check in tsig.c detects this inconsistent state and deliberately exits. Prior to the introduction of the check the server would continue operating in an inconsistent state, with potentially harmful results.
Using a specially-crafted message, an attacker may potentially cause a ...
Using a specially-crafted message, an attacker may potentially cause a BIND server to reach an inconsistent state if the attacker knows (or successfully guesses) the name of a TSIG key used by the server. Since BIND, by default, configures a local session key even on servers whose configuration does not otherwise make use of it, almost all current BIND servers are vulnerable. In releases of BIND dating from March 2018 and after, an assertion check in tsig.c detects this inconsistent state and deliberately exits. Prior to the introduction of the check the server would continue operating in an inconsistent state, with potentially harmful results.
Уязвимость компонента tsig.c DNS-сервера BIND, позволяющая нарушителю вызвать отказ в обслуживании
EPSS
4.3 Medium
CVSS2
7.5 High
CVSS3