CVE-2022-0324
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 · uneditedThere is a vulnerability in DHCPv6 packet parsing code that could be explored by remote attacker to craft a packet that could cause buffer overflow in a memcpy call, leading to out-of-bounds memory write that would cause dhcp6relay to crash. Dhcp6relay is a critical process and could cause dhcp relay docker to shutdown. Discovered by Eugene Lim of GovTech Singapore.
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 confidenceA buffer overflow vulnerability exists in the DHCPv6 packet parsing code of dhcp6relay. A remote attacker can craft a malicious DHCPv6 packet that causes an out-of-bounds memory write during a memcpy operation, leading to process crash and Docker container shutdown.
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= 202111CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if dhcp6relay is installedRun 'dpkg -l | grep dhcp6relay' or 'rpm -qa | grep dhcp6relay' or check for the binary at /usr/sbin/dhcp6relayAffected if The package or binary is present on the system
-
Identify the installed package versionRun 'dpkg -l dhcp6relay' or 'rpm -qi dhcp6relay' to retrieve the version numberAffected if The version matches '202111' or is a variant of the Linux Foundation Software for Open Networking in the Cloud release 202111
-
Verify the dhcp6relay service is enabledCheck service status with 'systemctl status dhcp6relay' or check for running processes with 'ps aux | grep dhcp6relay'Affected if The service is running and processing DHCPv6 packets
-
Confirm DHCPv6 relay functionality is activeInspect the dhcp6relay configuration file (typically in /etc/default/ or /etc/dhcp6relay.conf) and check for active relay interfacesAffected if DHCPv6 relay is configured and actively processing DHCPv6 traffic on any interface
-
Monitor for unexpected process crashesReview system logs with 'journalctl -u dhcp6relay' or check /var/log/syslog for dhcp6relay crash entriesAffected if The process has crashed or terminated unexpectedly, which may indicate exploitation
A system is affected if dhcp6relay version 202111 (Linux Foundation Software for Open Networking in the Cloud) is installed, the service is running, and DHCPv6 relay functionality is enabled, allowing remote attackers to send malicious DHCPv6 packets to trigger the buffer overflow.
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.
From vendor dataApply available security patches for the dhcp6relay component. If no patch is available, implement network-level filtering to restrict DHCPv6 traffic to trusted sources and monitor for anomalous packet patterns.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0324 — 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-0324 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