Share 
## https://sploitus.com/exploit?id=48F9B274-8211-5F4A-827C-56C8C9B6173B
# CVE-2024-8418
https://vulners.com/cve/CVE-2024-8418

## Description:
A flaw was found in Aardvark-dns, which is vulnerable to a Denial of Service attack due to the serial processing of TCP DNS queries. An attacker can exploit this flaw by keeping a TCP connection open indefinitely, causing the server to become unresponsive and resulting in other DNS queries timing out. This issue prevents legitimate users from accessing DNS services, thereby disrupting normal operations and causing service downtime.

## Tested environment:
    fedora-linux-40 6.10.4-200.fc40.aarch64
    podman 5.2.0
    aardvark-dns 1.12.1

## Lab set up:

1\. Create a network named “aardvark-net”

    $ podman network create --subnet=10.89.0.0/24 --gateway=10.89.0.1 aardvark-net

2\. Create a dummy container named “web” that sits on the network (“aardvark-net”) running indefinitely, ready to be discovered by other containers as “myweb”:

    $ podman run -d —rm —network aardvark-net —name web —hostname myweb alpine tail -f /dev/null

3\. Check if container-to-container DNS lookup works correctly in the network
by trying to resolve “myweb” from a newly created short-lived container:

    $ podman run —rm —network aardvark-net alpine nslookup myweb
    Server: 10.89.0.1
    Address: 10.89.0.1:53

    Non-authoritative answer:
    Name: myweb.dns.podman
    Address: 10.89.0.2

    Non-authoritative answer:

## Attack
Assuming the attacker has access to a container connected to the victim's network (e.g. “aardvark-net”):

    $ ./poc.sh

## Denial of Service (DoS)
Trying to resolve the domain (set up step #3) fails for any user in the network from now on:

    $ podman run —rm —network aardvark-net alpine nslookup myweb
    ;; connection timed out; no servers could be reached