Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.7

Missing connection timeout in Aardvark-dns

CVE-2024-8418GHSA-g5jh-57wm-p79m

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (aardvark-dns 1.12.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • crates.io aardvark-dns

    Affected
    >= 1.12.0, < 1.12.2
    Fixed in
    1.12.2

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2024-8418: 0.81% estimated exploitation activity in the next 30 days; percentile 56.88 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

A flaw was found in Aardvark-dns versions 1.12.0 and 1.12.1. They contain a denial of service vulnerability due to serial processing of TCP DNS queries. This flaw allows a malicious client to keep a TCP connection open indefinitely, causing other DNS queries to time out and resulting in a denial of service for all other containers using aardvark-dns.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-g5jh-57wm-p79m

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-8418

Advisory: Missing connection timeout in Aardvark-dns
IDs: CVE-2024-8418, GHSA-g5jh-57wm-p79m
Record: https://patchnext.com/advisories/cve-2024-8418 (revision 1, source checked 26 Oct 2026, 15:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: aardvark-dns 1.12.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io aardvark-dns: affected >= 1.12.0, < 1.12.2; fixed in 1.12.2

## Suggested inspection (read-only)
- crates.io aardvark-dns: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on aardvark-dns.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-g5jh-57wm-p79m (GitHub-reviewed advisory GHSA-g5jh-57wm-p79m lists affected ranges: crates.io aardvark-dns >=1.12.0 <1.12.2)

Commands are suggestions: review each one before running it.

Loading voting…