Описание
Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the "KeyTrap" issue. One of the concerns is that, when there is a zone with many DNSKEY and RRSIG records, the protocol specification implies that an algorithm must evaluate all combinations of DNSKEY and RRSIG records.
Релиз | Статус | Примечание |
---|---|---|
bionic | ignored | end of standard support |
devel | released | 1:9.18.24-0ubuntu1 |
esm-infra-legacy/trusty | not-affected | 1:9.9.5.dfsg-3ubuntu0.19+esm12 |
esm-infra/bionic | released | 1:9.11.3+dfsg-1ubuntu1.19+esm3 |
esm-infra/focal | not-affected | 1:9.16.48-0ubuntu0.20.04.1 |
esm-infra/xenial | released | 1:9.10.3.dfsg.P4-8ubuntu1.19+esm8 |
focal | released | 1:9.16.48-0ubuntu0.20.04.1 |
jammy | released | 1:9.18.18-0ubuntu0.22.04.2 |
mantic | released | 1:9.18.18-0ubuntu2.1 |
noble | released | 1:9.18.24-0ubuntu1 |
Показывать по
Релиз | Статус | Примечание |
---|---|---|
bionic | DNE | |
devel | DNE | |
esm-infra/focal | needs-triage | |
focal | ignored | end of standard support, was needs-triage |
jammy | needs-triage | |
mantic | DNE | |
noble | DNE | |
oracular | DNE | |
plucky | DNE | |
trusty | DNE |
Показывать по
Релиз | Статус | Примечание |
---|---|---|
bionic | ignored | end of standard support |
devel | released | 2.90-1 |
esm-infra-legacy/trusty | needs-triage | |
esm-infra/bionic | released | 2.90-0ubuntu0.18.04.1+esm1 |
esm-infra/focal | not-affected | 2.90-0ubuntu0.20.04.1 |
esm-infra/xenial | released | 2.90-0ubuntu0.16.04.1+esm1 |
focal | released | 2.90-0ubuntu0.20.04.1 |
jammy | released | 2.90-0ubuntu0.22.04.1 |
mantic | released | 2.90-0ubuntu0.23.10.1 |
noble | released | 2.90-1 |
Показывать по
Релиз | Статус | Примечание |
---|---|---|
bionic | not-affected | code not present |
devel | needs-triage | |
esm-apps/noble | needs-triage | |
esm-infra-legacy/trusty | not-affected | code not present |
esm-infra/bionic | needs-triage | |
esm-infra/focal | not-affected | code not present |
esm-infra/xenial | not-affected | code not present |
focal | not-affected | code not present |
jammy | not-affected | code not present |
mantic | ignored | end of life, was needs-triage |
Показывать по
Релиз | Статус | Примечание |
---|---|---|
bionic | ignored | end of standard support |
devel | not-affected | 5.7.1-1 |
esm-apps/bionic | needs-triage | |
esm-apps/focal | needs-triage | |
esm-apps/jammy | needs-triage | |
esm-apps/noble | not-affected | 5.7.1-1 |
esm-apps/xenial | needs-triage | |
focal | ignored | end of standard support, was needs-triage |
jammy | needs-triage | |
mantic | ignored | end of life, was needs-triage |
Показывать по
Релиз | Статус | Примечание |
---|---|---|
bionic | ignored | end of standard support |
devel | not-affected | 4.9.3-1 |
esm-apps/bionic | needs-triage | |
esm-apps/focal | needs-triage | |
esm-apps/jammy | needs-triage | |
esm-apps/noble | not-affected | 4.9.3-1 |
esm-apps/xenial | needs-triage | |
focal | ignored | end of standard support, was needs-triage |
jammy | needs-triage | |
mantic | ignored | end of life, was needs-triage |
Показывать по
Релиз | Статус | Примечание |
---|---|---|
bionic | ignored | end of standard support |
devel | released | 1.19.1-1ubuntu1 |
esm-infra-legacy/trusty | needs-triage | |
esm-infra/bionic | needs-triage | |
esm-infra/focal | not-affected | 1.9.4-2ubuntu1.5 |
esm-infra/xenial | needs-triage | |
focal | released | 1.9.4-2ubuntu1.5 |
jammy | released | 1.13.1-1ubuntu5.4 |
mantic | released | 1.17.1-2ubuntu0.1 |
noble | released | 1.19.1-1ubuntu1 |
Показывать по
Ссылки на источники
EPSS
7.5 High
CVSS3
Связанные уязвимости
Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the "KeyTrap" issue. One of the concerns is that, when there is a zone with many DNSKEY and RRSIG records, the protocol specification implies that an algorithm must evaluate all combinations of DNSKEY and RRSIG records.
Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the "KeyTrap" issue. One of the concerns is that, when there is a zone with many DNSKEY and RRSIG records, the protocol specification implies that an algorithm must evaluate all combinations of DNSKEY and RRSIG records.
MITRE: CVE-2023-50387 DNSSEC verification complexity can be exploited to exhaust CPU resources and stall DNS resolvers
Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6 ...
Certain DNSSEC aspects of the DNS protocol (in RFC 4035 and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses when there is a zone with many DNSKEY and RRSIG records, aka the "KeyTrap" issue. The protocol specification implies that an algorithm must evaluate all combinations of DNSKEY and RRSIG records.
EPSS
7.5 High
CVSS3