CVE-2022-2929
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 · uneditedIn ISC DHCP 1.0 -> 4.4.3, ISC DHCP 4.1-ESV-R1 -> 4.1-ESV-R16-P1 a system with access to a DHCP server, sending DHCP packets crafted to include fqdn labels longer than 63 bytes, could eventually cause the server to run out of memory.
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 · moderate confidenceMemory exhaustion vulnerability in ISC DHCP server where specially crafted DHCP packets with FQDN labels exceeding 63 bytes can cause unbounded memory allocation, eventually leading to server exhaustion and denial of service.
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= 10.0= 35= 36= 37>= 1.0.0, < 4.1-esv>= 4.2.0, <= 4.4.3= 4.1-esvCVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/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 checksWork through these to decide whether this CVE applies to you.
-
Check if ISC DHCP server is installedRun 'dhcpd -v' or 'rpm -q dhcp' (RHEL/Fedora) or 'dpkg -l isc-dhcp-server' (Debian) to find the installed packageAffected if No ISC DHCP server package is found, then this CVE does not apply
-
Determine the installed ISC DHCP versionRun 'dhcpd -v' and note the version number, then compare to affected ranges: < 4.1-esv, >= 4.1-esv to <= 4.4.3, or >= 4.2.0Affected if The installed version falls within any of the affected ranges: >= 1.0.0 and < 4.1-esv; = 4.1-esv; or >= 4.2.0 through <= 4.4.3
-
Verify the DHCP server is network-accessibleCheck if dhcpd is running and listening on network interfaces with 'netstat -tulpn | grep dhcp' or 'ss -tulpn | grep dhcp'Affected if The server is exposed to network traffic (not firewalled or isolated), making it reachable to attackers sending malicious DHCP packets
-
Confirm FQDN or dynamic DNS update configuration is in useInspect /etc/dhcp/dhcpd.conf (or equivalent config path) for 'fqdn', 'ddns-update-style', or client FQDN options that enable FQDN label processingAffected if FQDN-related DHCP options are enabled in the configuration, as the vulnerability triggers via oversized FQDN labels
You are affected if ISC DHCP server is running with a version in the affected ranges and the server is network-accessible with FQDN processing enabled.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.1-esv
Update ISC DHCP to patched version; implement network segmentation and access controls to restrict DHCP packet sources; consider DHCP request rate limiting.
ISC DHCP 4.4.4 or later, or 4.1-ESV-R17 or later; Debian 10 (Buster) and Fedora 35-37 updates via package manager
- Update the package repository by running: apt-get update (Debian) or dnf check-update (Fedora)
- Install the updated DHCP package: apt-get install isc-dhcp-server (Debian) or dnf update dhcp (Federa)
- Alternatively, obtain ISC DHCP 4.4.4 or later from kb.isc.org and compile/install from source
- Restart the DHCP server service to apply the update: systemctl restart isc-dhcp-server or systemctl restart dhcpd
- Verify the server is running and not experiencing memory leaks with process monitoring tools
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2929 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-2929 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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