37 matches found
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...
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...
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...
EUVD-2022-37024
Malicious code in bioql PyPI...
EUVD-2022-37021
Malicious code in bioql PyPI...
EUVD-2022-37022
Malicious code in bioql PyPI...
EUVD-2022-37023
Malicious code in bioql PyPI...
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...
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...
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...
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...
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...
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...
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...
Design/Logic Flaw
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...
Design/Logic Flaw
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...
Code injection
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...
Information disclosure
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...
CVE-2022-33989
CVE-2022-33989 concerns dproxy-nexgen (dproxy nexgen), which uses a static UDP source port that is chosen randomly only at boot for upstream DNS queries. The limited entropy enables DNS cache poisoning since traffic injection becomes easier without a fresh, per-query port randomization. Connected...
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...