K23022557: The BIG-IP system may respond with the NXDOMAIN status when it receives a DNS query of a certain type on a CNAME wide IP

Security Advisory Description The BIG-IP system may respond with the NXDOMAIN status when it receives a DNS query on a CNAME wide IP. This issue occurs when all of the following conditions are met: The BIG-IP system is configured with a CNAME wide IP. For example: test.example.com The BIG-IP syst...

K79240502: BIG-IP ASM Bot Detection DNS cache does not expire security exposure

Security Advisory Description When BIG-IP ASM Bot Detection is configured, the BIG-IP ASM system performs a reverse DNS lookup to determine if bot traffic classified as legitimate is, in fact, from those services for example, Google. These DNS responses are cached indefinitely until the Traffic...

K37661551: Unbound DNS Cache vulnerabilities CVE-2020-12662 and CVE-2020-12663

Security Advisory Description CVE-2020-12662 Unbound before 1.10.1 has Insufficient Control of Network Message Volume, aka an "NXNSAttack" issue. This is triggered by random subdomains in the NSDNAME in NS records. CVE-2020-12663 Unbound before 1.10.1 has an infinite loop via malformed DNS answer...

K41415626: Transparent DNS Cache can consume excessive resources

Security Advisory Description When transparent Domain Name System DNS cache is configured on a virtual server, undisclosed Extension Mechanisms for DNS EDNS0 queries can cause the BIG-IP system to send a large volume of User Datagram Protocol UDP traffic on the server side. Note : The DNS cache...

K48224824: BIG-IP DNS Cache vulnerability CVE-2018-5532

Security Advisory Description On F5 BIG-IP 13.0.0, 12.1.0-12.1.2, 11.6.0-11.6.3.1, or 11.2.1-11.5.6 a domain name cached within the DNS Cache of TMM may continue to be resolved by the cache even after the parent server revokes the record, if the DNS Cache is receiving a stream of requests for the...

K17450: BIND vulnerabilities CVE-1999-0024 and CVE-2006-0987

Security Advisory Description CVE-1999-0024 DNS cache poisoning via BIND, by predictable query IDs. CVE-2006-0987 The default configuration of ISC BIND before 9.4.1-P1, when configured as a caching name server, allows recursive queries and provides additional delegation information to arbitrary I...

K15748: BIND vulnerability CVE-2010-0290

Security Advisory Description Unspecified vulnerability in ISC BIND 9.0.x through 9.3.x, 9.4 before 9.4.3-P5, 9.5 before 9.5.2-P2, 9.6 before 9.6.1-P3, and 9.7.0 beta, with DNSSEC validation enabled and checking disabled CD, allows remote attackers to conduct DNS cache poisoning attacks by...

K8938: BIND DNS cache poisoning vulnerability - CVE-2008-1447 - VU#800113

Security Advisory Description Note : Versions that are not listed in this article have not been evaluated for vulnerability to this security advisory. For information about the F5 security policy regarding evaluating older and unsupported versions of F5 products, refer to K4602: Overview of the F...

SUSE CVE-2008-3217

PowerDNS Recursor before 3.1.6 does not always use the strongest random number generator for source port selection, which makes it easier for remote attack vectors to conduct DNS cache poisoning. NOTE: this is related to incomplete integration of security improvements associated with addressing...

SUSE CVE-2020-17470

An issue was discovered in FNET through 4.6.4. The code that initializes the DNS client interface structure does not set sufficiently random transaction IDs they are always set to 1 in fnetdnspoll in fnetdns.c. This significantly simplifies DNS cache poisoning attacks...

SUSE CVE-2020-25684

A flaw was found in dnsmasq before version 2.83. When getting a reply from a forwarded query, dnsmasq checks in the forward.c:replyquery if the reply destination address/port is used by the pending forwarded queries. However, it does not use the address/port to retrieve the exact forwarded query,...

SUSE CVE-2022-30295

uClibc-ng through 1.0.40 and uClibc through 0.9.33.2 use predictable DNS transaction IDs that may lead to DNS cache poisoning. This is related to a reset of a value to 0x2...

OPENSUSE-SU-2022:10209-1 Security update for tor

This update for tor fixes the following issues: tor 0.4.7.11: Improve security of DNS cache by randomly clipping the TTL value boo1205307, TROVE-2021-009 Improved defenses against network-wide DoS, multiple counters and metrics added to MetricsPorts Apply circuit creation anti-DoS defenses if the...

PT-2022-36637 · Tor · Tor

Name of the Vulnerable Software and Affected Versions: tor version 0.4.7.11 Description: The issue improves the security of the DNS cache by randomly clipping the TTL value. It also introduces improved defenses against network-wide DoS attacks, with multiple counters and metrics added to...

Security update for tor (moderate)

openSUSE Security Update: Security update for tor Announcement ID: openSUSE-SU-2022:10209-1 Rating: moderate References: 1205307 Affected Products: openSUSE Backports SLE-15-SP3 openSUSE Backports SLE-15-SP4 An update that contains security fixes can now be installed. Description: This update for...

USN-4976-2: Dnsmasq vulnerability

USN-4976-1 fixed a vulnerability in Dnsmasq. This update provides the corresponding update for Ubuntu 16.04 ESM. Dnsmasq has been updated to 2.79-1 for Ubuntu 16.04 ESM in order to fix some security issues. Original advisory details: Petr Mensik discovered that Dnsmasq incorrectly randomized sour...

Nutanix AHV : Multiple Vulnerabilities (NXSA-AHV-20201105.1045)

The version of AHV installed on the remote host is prior to 20201105.1045. It is, therefore, affected by multiple vulnerabilities as referenced in the NXSA-AHV-20201105.1045 advisory. - A heap-based buffer overflow was found in the way sudo parses command line arguments. This flaw is exploitable ...

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...

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...