Описание
In NLnet Labs Unbound up to and including 1.26.0, a 255 length query name with a large TCP response can lead to a heap buffer overflow during the RRSet canonicalisation routine. This is caused by missing to add the first owner name into the buffer length check. A malicious actor operating a malicious name server or tampering with an incoming response to Unbound (canonicalisation happens before DNSSEC validation), can trigger the vulnerability.
| Релиз | Статус | Примечание |
|---|---|---|
| devel | needed | |
| esm-infra-legacy/trusty | released | 1.4.22-1ubuntu4.14.04.3+esm5 |
| esm-infra-legacy/xenial | released | 1.5.8-1ubuntu1.1+esm5 |
| esm-infra/bionic | released | 1.6.7-1ubuntu2.6+esm6 |
| esm-infra/focal | released | 1.9.4-2ubuntu1.11+esm3 |
| jammy | released | 1.13.1-1ubuntu5.17 |
| noble | released | 1.19.2-1ubuntu3.12 |
| resolute | released | 1.24.2-1ubuntu2.4 |
| stonking | released | 1.25.1-1ubuntu3.1 |
| upstream | released | 1.26.1-1 |
Показывать по
EPSS
7.5 High
CVSS3
Связанные уязвимости
In NLnet Labs Unbound up to and including 1.26.0, a 255 length query name with a large TCP response can lead to a heap buffer overflow during the RRSet canonicalisation routine. This is caused by missing to add the first owner name into the buffer length check. A malicious actor operating a malicious name server or tampering with an incoming response to Unbound (canonicalisation happens before DNSSEC validation), can trigger the vulnerability.
In NLnet Labs Unbound up to and including 1.26.0, a 255 length query name with a large TCP response can lead to a heap buffer overflow during the RRSet canonicalisation routine. This is caused by missing to add the first owner name into the buffer length check. A malicious actor operating a malicious name server or tampering with an incoming response to Unbound (canonicalisation happens before DNSSEC validation), can trigger the vulnerability.
In NLnet Labs Unbound up to and including 1.26.0, a 255 length query n ...
In NLnet Labs Unbound up to and including 1.26.0, a 255 length query name with a large TCP response can lead to a heap buffer overflow during the RRSet canonicalisation routine. This is caused by missing to add the first owner name into the buffer length check. A malicious actor operating a malicious name server or tampering with an incoming response to Unbound (canonicalisation happens before DNSSEC validation), can trigger the vulnerability.
EPSS
7.5 High
CVSS3