p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in c-ares

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für c-ares: 0. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 2

  1. CVE-2026-69184

    Hoch · CVSS 7.5EPSS 0,48%Korrektur verfügbar

    c-ares: CPU-exhaustion denial of service via unbounded DNS name compression pointer chains

    c-ares is an asynchronous resolver library. Prior to 1.34.7, ares_dns_name_parse() enforces backward DNS compression pointers but does not bound the total pointer hops or assembled name length. A malicious DNS server can send a response containing a long descending pointer chain and many resource records whose NAME or RDATA fields refer to the chain, causing repeated decompression work that grows quadratically with message size. A single crafted response can stall the single-threaded c-ares event loop and deny DNS resolution, without causing memory corruption or information disclosure. This issue is fixed in version 1.34.7.

    • Auf 1.27.0-1.0ubuntu1.1 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2026-69186

    Mittel · CVSS 5.3EPSS 0,47%Korrektur verfügbar

    c-ares: Memory-amplification denial of service via unvalidated DNS header record counts

    c-ares is an asynchronous resolver library. Prior to 1.34.7, ares_dns_parse() trusts the attacker-controlled ANCOUNT, NSCOUNT, and ARCOUNT fields before confirming that the DNS response contains enough bytes for the claimed records. Because process_answer() invokes parsing before transaction ID and question validation, a malicious DNS response can cause ares_dns_record_rr_prealloc() and ares_array_set_size() to reserve disproportionate heap memory for a tiny message. Repeated responses create large allocation and release cycles that can degrade or deny name resolution, without causing memory corruption or information disclosure. This issue is

    • Auf 1.27.0-1.0ubuntu1.1 aktualisieren
    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →