CVE-2016-5362
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 · uneditedThe IPTables firewall in OpenStack Neutron before 7.0.4 and 8.0.0 through 8.1.0 allows remote attackers to bypass an intended DHCP-spoofing protection mechanism and consequently cause a denial of service or intercept network traffic via a crafted DHCP discovery message.
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 confidenceThe IPTables firewall in OpenStack Neutron contains a flaw in its DHCP-spoofing protection mechanism. Attackers can send crafted DHCP discovery messages that bypass the intended IPTables filtering rules, enabling DHCP spoofing attacks that result in denial of service or allow interception of network traffic.
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>= 7.0.0, < 7.0.4>= 8.0.0, <= 8.1.0CVSS 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
- Low
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 installed Neutron versionRun 'neutron --version' or 'pip show neutron' to determine the installed Neutron versionAffected if The version falls within 7.0.0 to 7.0.3, or 8.0.0 to 8.1.0
-
Verify DHCP spoofing protection is in useCheck if security groups with DHCP spoofing protection are applied to instances: list security groups and inspect their rules for DHCP filter propertiesAffected if DHCP spoofing protection rules are configured and the Neutron version is vulnerable
-
Inspect IPTables rules for DHCP filteringRun 'iptables -L -n -v | grep -E "67|68|dhcp"' on compute nodes to verify DHCP packets are being filtered by IPTablesAffected if DHCP-related IPTables rules exist but can be bypassed by crafted packets in vulnerable versions
-
Check for crafted DHCP packet handlingReview Neutron's dhcp_agent.log or security group logs for any indicators of DHCP packet processing that might show the filtering mechanism in useAffected if DHCP filtering is active and the Neutron version is within the affected range
You are affected if OpenStack Neutron is installed at a version between 7.0.0 and 7.0.3, or between 8.0.0 and 8.1.0, and DHCP spoofing protection via IPTables security groups is enabled in your environment.
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 data7.0.4
Upgrade OpenStack Neutron to version 7.0.4 or 8.1.1 and later to patch the IPTables DHCP-spoofing bypass vulnerability.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-5362 — 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-2016-5362 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