This page aggregates publicly disclosed CVE and security risk information related to dproxy-nexgen_project, with CVSS, EPSS, publication dates, and vulnerability intelligence data to help assess potential risk and remediation priority.
| CVE | 概要 | ソース | CVSS 最大値 | EPSS（%） | 公開 | 更新 |
|---|---|---|---|---|---|---|
| CVE-2022-33991 | dproxy-nexgen (aka dproxy nexgen) forwards and caches DNS queries with the CD (aka checking disabled) bit set to 1. This leads to disabling of DNSSEC protection provided by upstream resolvers. | [email protected] | 5.3 | 0.26% | 2022-08-15 | 2024-11-21 |
| CVE-2022-33990 | Misinterpretation of special domain name characters in dproxy-nexgen (aka dproxy nexgen) leads to cache poisoning because domain names and their associated IP addresses are cached in their misinterpreted form. | [email protected] | 7.5 | 0.29% | 2022-08-15 | 2024-11-21 |
| CVE-2022-33989 | dproxy-nexgen (aka dproxy nexgen) uses a static UDP source port (selected randomly only at boot time) in upstream queries sent to DNS resolvers. This allows DNS cache poisoning because there is not enough entropy to prevent traffic injection attacks. | [email protected] | 5.3 | 0.28% | 2022-08-15 | 2024-11-21 |
| CVE-2022-33988 | dproxy-nexgen (aka dproxy nexgen) re-uses the DNS transaction id (TXID) value from client queries, which allows attackers (able to send queries to the resolver) to conduct DNS cache-poisoning attacks because the TXID value is known to the attacker. | [email protected] | 7.5 | 0.28% | 2022-08-15 | 2024-11-21 |