Loading vulnerability…
A vulnerability in NLnet Labs Unbound (versions 1.18.0 through 1.19.1) allows a remote attacker to trigger a denial of service via an infinite loop in the code responsible for trimming EDE (Extended DNS Error) record text fields. This occurs when Unbound is configured with 'ede: yes' (non-default), and the client's advertised buffer size is smaller than the space required for EDE records. The vulnerable code attempts to trim EDE text fields to fit the response within the buffer size, but due to an unchecked condition, it can enter an infinite loop, causing the Unbound process to hang.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a proof-of-concept (PoC) exploit environment for CVE-2024-1931, a Denial of Service (DoS) vulnerability in NLnetLabs Unbound DNS server version 1.19.1. The repository includes a Dockerfile to build a containerized Unbound environment, a custom Unbound configuration (unbound.conf.exploit) to enable EDE and serve-expired features, and a bash script (exploit.sh) that sends a crafted DNS query to the local Unbound server. The exploit attempts to trigger a DoS condition by exploiting the handling of bogus DNSSEC responses and EDE code 3 (stale answer). The user is instructed to check the Unbound log file for confirmation of the exploit's effect. The main attack vector is a local DNS query within the container, but the vulnerability itself is network-reachable if Unbound is exposed. The repository is structured for easy reproduction and testing of the vulnerability, and does not contain weaponized or automated remote exploitation code.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.