p PatchFirst

PatchFirst · Vulnerabilidades recientes

Vulnerabilidades de pdns-recursor · Página 2

Vulnerabilidades publicadas para pdns-recursor en los últimos 30 días: 0. Incluidas en el catálogo KEV: 0.

Filtrar vulnerabilidades
Borrar filtros

Vulnerabilidades: 27

  1. CVE-2026-0398

    Media · CVSS 5.3EPSS 0,34%Sin corrección publicada

    Crafted zones can lead to increased resource usage and crafted CNAME chains can lead to cache poisoning in Recursor

    Crafted zones can lead to increased resource usage and crafted CNAME chains can lead to cache poisoning in Recursor.

    Publicación Actualización
  2. CVE-2025-59029

    Media · CVSS 5.3EPSS 0,37%Sin corrección publicada

    Internal logic flaw in cache management can lead to a denial of service in PowerDNS Recursor

    An attacker can trigger an assertion failure by requesting crafted DNS records, waiting for them to be inserted into the records cache, then send a query with qtype set to ANY.

    Publicación Actualización
  3. CVE-2025-30192

    Alta · CVSS 7.5EPSS 0,27%Sin corrección publicada

    A Recursor configured to send out ECS enabled queries can be sensitive to spoofing attempts

    An attacker spoofing answers to ECS enabled requests sent out by the Recursor has a chance of success higher than non-ECS enabled queries. The updated version include various mitigations against spoofing attempts of ECS enabled queries by chaining ECS enabled requests and enforcing stricter validation of the received answers. The most strict mitigation done when the new setting outgoing.edns_subnet_harden (old style name edns-subnet-harden) is enabled.

    Publicación Actualización
  4. CVE-2025-30195

    Alta · CVSS 7.5EPSS 0,78%Sin corrección publicada

    A crafted zone can lead to an illegal memory access in the PowerDNS Recursor

    An attacker can publish a zone containing specific Resource Record Sets. Processing and caching results for these sets can lead to an illegal memory accesses and crash of the Recursor, causing a denial of service. The remedy is: upgrade to the patched 5.2.1 version. We would like to thank Volodymyr Ilyin for bringing this issue to our attention.

    Publicación Actualización

Comprueba tu servidor

Compara tu pila y las versiones instaladas con las bases actuales de vulnerabilidades.

Comprueba tu servidor →