dbcve.org
FedoraOperating system · Fedoraproject

CVE-2024-1931

HIGH · 7.5 CVSS v3.1 Published 2024-03-07
Fix available
A fix is available. Upgrade to 1.19.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
NLnet Labs Unbound version 1.18.0 up to and including version 1.19.1 contain a vulnerability that can cause denial of service by a certain code path that can lead to an infinite loop. Unbound 1.18.0 introduced a feature that removes EDE records from responses with size higher than the client's advertised buffer size. Before removing all the EDE records however, it would try to see if trimming the extra text fields on those records would result in an acceptable size while still retaining the EDE codes. Due to an unchecked condition, the code that trims the text of the EDE records could loop indefinitely. This happens when Unbound would reply with attached EDE information on a positive reply and the client's buffer size is smaller than the needed space to include EDE records. The vulnerability can only be triggered when the 'ede: yes' option is used; non default configuration. From version 1.19.2 on, the code is fixed to avoid looping indefinitely.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Unbound DNS resolver versions 1.18.0 through 1.19.1 contain an infinite loop vulnerability in the EDE (Extended DNS Errors) record trimming logic. When the non-default 'ede: yes' option is enabled and a client advertises a buffer size too small to accommodate EDE records, the code that attempts to trim extra text fields from EDE records enters an unchecked loop, causing a denial of service.

MitigationUpgrade Unbound to version 1.19.2 or later, or temporarily disable the 'ede: yes' configuration option if upgrading is not immediately feasible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FedoraOperating system
Affected:= 38= 39= 40
UnboundApplication
Affected:>= 1.18.0, < 1.19.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Unbound version
    Run 'unbound -V' or check the package version via your system package manager (e.g., 'rpm -q unbound' on Fedora/RHEL, 'dpkg -l unbound' on Debian)
    Affected if Version is 1.18.0, 1.18.1, 1.19.0, or 1.19.1 (versions 1.19.2 and later are fixed)
  2. Locate Unbound configuration file
    Common locations are /etc/unbound/unbound.conf, /etc/unbound/unbound.conf.d/*.conf, or check for 'include:' directives that reference additional config files
    Affected if The configuration file exists and is readable
  3. Check if EDE is enabled
    Search the configuration file(s) for the directive 'ede: yes' (case-insensitive search). This is a non-default option that must be explicitly set
    Affected if The directive 'ede: yes' is found in the active configuration (if absent or set to 'no', the vulnerability is not triggered)
  4. Verify the combination
    Confirm that both conditions are true: (1) installed Unbound version is 1.18.0-1.19.1 inclusive, AND (2) 'ede: yes' is enabled in the active configuration
    Affected if Both version is vulnerable AND 'ede: yes' is enabled - only then is the environment affected by CVE-2024-1931

Your environment is affected only if running Unbound version 1.18.0 through 1.19.1 with the non-default 'ede: yes' option enabled in the configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.19.2 or later
Fixed in 1.19.2
Interim mitigation

Upgrade Unbound to version 1.19.2 or later, or temporarily disable the 'ede: yes' configuration option if upgrading is not immediately feasible.

Recommended fix High confidence

Unbound 1.19.2

  1. Check the current Unbound version installed (e.g., 'unbound -V' or 'unbound-control status')
  2. Upgrade Unbound to version 1.19.2 or later (e.g., 'dnf update unbound' on Fedora, or use your system's package manager)
  3. If using a package that requires manual version selection, ensure the repository provides 1.19.2 or newer
  4. After upgrade, restart the Unbound service (e.g., 'systemctl restart unbound')
  5. Verify the new version is running (e.g., 'unbound -V' or 'unbound-control status')

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fedora Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1931 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-1931 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data