Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

Поиск уязвимостей

Количество 15

Количество 15

github логотип

GHSA-cj23-2crp-2xvv

4 месяца назад

In NLnet Labs Unbound 1.6.0 up to and including 1.25.1, a replay of a wildcard rrset as another piece of data, could be briefly considered DNSSEC secure based only on the RRSIG validation and stored into cache, before later validation treats it as bogus based on NSEC validation. When the resolving thread puts secure on the rrset, and another thread that is on the serve expired path then picks up the updated rrset contents with the secure status for a reply, it can be used to change a specific record, next to a wildcard that could be covered by the wildcard, into the wildcard. A malicious actor can exploit the possible poisonous effect by having any DNSSEC-singed domain (irrelevant to the victim domain) and a CNAME wrapper record that points to a record next to a wildcard (that could be covered by the wildcard). Then quering Unbound for the wildcard sibling record would seed the secure message. A later (after expiry) query for the CNAME wrapper would need to resolve the target siblin...

CVSS3: 3.7
EPSS: Низкий
ubuntu логотип

CVE-2026-46582

4 месяца назад

In NLnet Labs Unbound 1.6.0 up to and including 1.25.1, a replay of a wildcard rrset as another piece of data, could be briefly considered DNSSEC secure based only on the RRSIG validation and stored into cache, before later validation treats it as bogus based on NSEC validation. When the resolving thread puts secure on the rrset, and another thread that is on the serve expired path then picks up the updated rrset contents with the secure status for a reply, it can be used to change a specific record, next to a wildcard that could be covered by the wildcard, into the wildcard. A malicious actor can exploit the possible poisonous effect by having any DNSSEC-singed domain (irrelevant to the victim domain) and a CNAME wrapper record that points to a record next to a wildcard (that could be covered by the wildcard). Then quering Unbound for the wildcard sibling record would seed the secure message. A later (after expiry) query for the CNAME wrapper would need to resolve the target siblin...

CVSS3: 3.7
EPSS: Низкий
redhat логотип

CVE-2026-46582

4 месяца назад

In NLnet Labs Unbound 1.6.0 up to and including 1.25.1, a replay of a wildcard rrset as another piece of data, could be briefly considered DNSSEC secure based only on the RRSIG validation and stored into cache, before later validation treats it as bogus based on NSEC validation. When the resolving thread puts secure on the rrset, and another thread that is on the serve expired path then picks up the updated rrset contents with the secure status for a reply, it can be used to change a specific record, next to a wildcard that could be covered by the wildcard, into the wildcard. A malicious actor can exploit the possible poisonous effect by having any DNSSEC-singed domain (irrelevant to the victim domain) and a CNAME wrapper record that points to a record next to a wildcard (that could be covered by the wildcard). Then quering Unbound for the wildcard sibling record would seed the secure message. A later (after expiry) query for the CNAME wrapper would need to resolve the target siblin...

CVSS3: 3.7
EPSS: Низкий
nvd логотип

CVE-2026-46582

4 месяца назад

In NLnet Labs Unbound 1.6.0 up to and including 1.25.1, a replay of a wildcard rrset as another piece of data, could be briefly considered DNSSEC secure based only on the RRSIG validation and stored into cache, before later validation treats it as bogus based on NSEC validation. When the resolving thread puts secure on the rrset, and another thread that is on the serve expired path then picks up the updated rrset contents with the secure status for a reply, it can be used to change a specific record, next to a wildcard that could be covered by the wildcard, into the wildcard. A malicious actor can exploit the possible poisonous effect by having any DNSSEC-singed domain (irrelevant to the victim domain) and a CNAME wrapper record that points to a record next to a wildcard (that could be covered by the wildcard). Then quering Unbound for the wildcard sibling record would seed the secure message. A later (after expiry) query for the CNAME wrapper would need to resolve the target sibling r

CVSS3: 3.7
EPSS: Низкий
msrc логотип

CVE-2026-46582

4 месяца назад

A wildcard replay, as another piece of data, triggers poisoning in the serve expired reply path

CVSS3: 3.7
EPSS: Низкий
debian логотип

CVE-2026-46582

4 месяца назад

In NLnet Labs Unbound 1.6.0 up to and including 1.25.1, a replay of a ...

CVSS3: 3.7
EPSS: Низкий
redos логотип

ROS-20260921-80-0115

около 2 месяцев назад

Уязвимость unbound

CVSS3: 3.7
EPSS: Низкий
redos логотип

ROS-20260921-73-0092

около 2 месяцев назад

Уязвимость unbound

CVSS3: 3.7
EPSS: Низкий
suse-cvrf логотип

SUSE-SU-2026:3884-1

3 месяца назад

Security update for unbound

EPSS: Низкий
suse-cvrf логотип

SUSE-SU-2026:3885-1

3 месяца назад

Security update for unbound

EPSS: Низкий
rocky логотип

RLSA-2026:97497

5 дней назад

Moderate: unbound security, bug fix, and enhancement update

EPSS: Низкий
rocky логотип

RLSA-2026:97121

5 дней назад

Moderate: unbound security, bug fix, and enhancement update

EPSS: Низкий
suse-cvrf логотип

openSUSE-SU-2026:21550-1

3 месяца назад

Security update for unbound

EPSS: Низкий
altlinux логотип

ALT-PU-2026-11574

4 месяца назад

ALT-PU-2026-11574: package `unbound` update to version 1.25.2-alt1

CVSS3: 9.3
EPSS: Низкий
altlinux логотип

ALT-PU-2026-11359

4 месяца назад

ALT-PU-2026-11359: package `unbound` update to version 1.25.2-alt1

CVSS3: 9.3
EPSS: Низкий

Уязвимостей на страницу

Уязвимость
CVSS
EPSS
Опубликовано
github логотип
GHSA-cj23-2crp-2xvv

In NLnet Labs Unbound 1.6.0 up to and including 1.25.1, a replay of a wildcard rrset as another piece of data, could be briefly considered DNSSEC secure based only on the RRSIG validation and stored into cache, before later validation treats it as bogus based on NSEC validation. When the resolving thread puts secure on the rrset, and another thread that is on the serve expired path then picks up the updated rrset contents with the secure status for a reply, it can be used to change a specific record, next to a wildcard that could be covered by the wildcard, into the wildcard. A malicious actor can exploit the possible poisonous effect by having any DNSSEC-singed domain (irrelevant to the victim domain) and a CNAME wrapper record that points to a record next to a wildcard (that could be covered by the wildcard). Then quering Unbound for the wildcard sibling record would seed the secure message. A later (after expiry) query for the CNAME wrapper would need to resolve the target siblin...

CVSS3: 3.7
0%
Низкий
4 месяца назад
ubuntu логотип
CVE-2026-46582

In NLnet Labs Unbound 1.6.0 up to and including 1.25.1, a replay of a wildcard rrset as another piece of data, could be briefly considered DNSSEC secure based only on the RRSIG validation and stored into cache, before later validation treats it as bogus based on NSEC validation. When the resolving thread puts secure on the rrset, and another thread that is on the serve expired path then picks up the updated rrset contents with the secure status for a reply, it can be used to change a specific record, next to a wildcard that could be covered by the wildcard, into the wildcard. A malicious actor can exploit the possible poisonous effect by having any DNSSEC-singed domain (irrelevant to the victim domain) and a CNAME wrapper record that points to a record next to a wildcard (that could be covered by the wildcard). Then quering Unbound for the wildcard sibling record would seed the secure message. A later (after expiry) query for the CNAME wrapper would need to resolve the target siblin...

CVSS3: 3.7
0%
Низкий
4 месяца назад
redhat логотип
CVE-2026-46582

In NLnet Labs Unbound 1.6.0 up to and including 1.25.1, a replay of a wildcard rrset as another piece of data, could be briefly considered DNSSEC secure based only on the RRSIG validation and stored into cache, before later validation treats it as bogus based on NSEC validation. When the resolving thread puts secure on the rrset, and another thread that is on the serve expired path then picks up the updated rrset contents with the secure status for a reply, it can be used to change a specific record, next to a wildcard that could be covered by the wildcard, into the wildcard. A malicious actor can exploit the possible poisonous effect by having any DNSSEC-singed domain (irrelevant to the victim domain) and a CNAME wrapper record that points to a record next to a wildcard (that could be covered by the wildcard). Then quering Unbound for the wildcard sibling record would seed the secure message. A later (after expiry) query for the CNAME wrapper would need to resolve the target siblin...

CVSS3: 3.7
0%
Низкий
4 месяца назад
nvd логотип
CVE-2026-46582

In NLnet Labs Unbound 1.6.0 up to and including 1.25.1, a replay of a wildcard rrset as another piece of data, could be briefly considered DNSSEC secure based only on the RRSIG validation and stored into cache, before later validation treats it as bogus based on NSEC validation. When the resolving thread puts secure on the rrset, and another thread that is on the serve expired path then picks up the updated rrset contents with the secure status for a reply, it can be used to change a specific record, next to a wildcard that could be covered by the wildcard, into the wildcard. A malicious actor can exploit the possible poisonous effect by having any DNSSEC-singed domain (irrelevant to the victim domain) and a CNAME wrapper record that points to a record next to a wildcard (that could be covered by the wildcard). Then quering Unbound for the wildcard sibling record would seed the secure message. A later (after expiry) query for the CNAME wrapper would need to resolve the target sibling r

CVSS3: 3.7
0%
Низкий
4 месяца назад
msrc логотип
CVE-2026-46582

A wildcard replay, as another piece of data, triggers poisoning in the serve expired reply path

CVSS3: 3.7
0%
Низкий
4 месяца назад
debian логотип
CVE-2026-46582

In NLnet Labs Unbound 1.6.0 up to and including 1.25.1, a replay of a ...

CVSS3: 3.7
0%
Низкий
4 месяца назад
redos логотип
ROS-20260921-80-0115

Уязвимость unbound

CVSS3: 3.7
0%
Низкий
около 2 месяцев назад
redos логотип
ROS-20260921-73-0092

Уязвимость unbound

CVSS3: 3.7
0%
Низкий
около 2 месяцев назад
suse-cvrf логотип
SUSE-SU-2026:3884-1

Security update for unbound

3 месяца назад
suse-cvrf логотип
SUSE-SU-2026:3885-1

Security update for unbound

3 месяца назад
rocky логотип
RLSA-2026:97497

Moderate: unbound security, bug fix, and enhancement update

5 дней назад
rocky логотип
RLSA-2026:97121

Moderate: unbound security, bug fix, and enhancement update

5 дней назад
suse-cvrf логотип
openSUSE-SU-2026:21550-1

Security update for unbound

3 месяца назад
altlinux логотип
ALT-PU-2026-11574

ALT-PU-2026-11574: package `unbound` update to version 1.25.2-alt1

CVSS3: 9.3
4 месяца назад
altlinux логотип
ALT-PU-2026-11359

ALT-PU-2026-11359: package `unbound` update to version 1.25.2-alt1

CVSS3: 9.3
4 месяца назад

Уязвимостей на страницу