NeutronApplication · Openstack

CVE-2016-5363

HIGH · 8.2 CVSS v3.0 Published 2016-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
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
The IPTables firewall in OpenStack Neutron before 7.0.4 and 8.0.0 through 8.1.0 allows remote attackers to bypass an intended MAC-spoofing protection mechanism and consequently cause a denial of service or intercept network traffic via (1) a crafted DHCP discovery message or (2) crafted non-IP traffic.

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 confidence

OpenStack Neutron's IPTables firewall contains a flaw that allows attackers to bypass MAC-spoofing protection mechanisms. By sending specially crafted DHCP discovery messages or non-IP traffic, remote attackers can circumvent security controls and potentially cause denial of service or intercept network traffic.

MitigationUpgrade OpenStack Neutron to version 7.0.4 or later, or 8.1.1 or later to obtain the patched code that properly enforces MAC-spoofing protection on all traffic types.

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
NeutronApplication
Affected:= 7.0.0= 7.0.1= 7.0.2= 7.0.3= 7.0.4= 8.0.0= 8.1.0

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
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 checks

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

  1. Check installed Neutron version
    Run `neutron --version` or query the package manager (e.g., `rpm -q neutron` or `dpkg -l neutron`) to obtain the installed version number
    Affected if The version matches 7.0.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 8.0.0, or 8.1.0
  2. Identify the active firewall driver
    Check the Neutron configuration file (typically /etc/neutron/neutron.conf or /etc/neutron/fwaas_driver.ini) for the `firewall_driver` setting under the firewall or security group configuration section
    Affected if The firewall_driver is set to `neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver` or another iptables-based driver (not the Open vSwitch native driver)
  3. Verify MAC-spoofing rules exist for DHCP
    On the compute node, list iptables rules for the security group chains (e.g., `sudo iptables -L -n -v | grep -i spoof` or inspect the neutron security group chain) and check if rules explicitly handle DHCP traffic (port 67/68) for anti-spoofing
    Affected if No specific anti-spoofing rule exists for DHCP traffic (UDP ports 67-68) in the iptables rules, or rules only cover IP traffic and not ARP/DHCP
  4. Confirm non-IP traffic handling
    Review the iptables rules for the security group provider chain to see if there are rules that block or filter non-IP/non-ARP traffic, or check if all traffic types are subject to MAC-spoofing enforcement
    Affected if The iptables rules do not filter or block non-IP traffic (such as ARP, custom layer 2 frames) or there is no rule dropping traffic that fails MAC validation for non-IP protocols

A system is affected if it runs Neutron version 7.0.0-7.0.4 or 8.0.0-8.1.0 with an iptables-based firewall driver and lacks proper anti-MAC-spoofing rules for DHCP and non-IP traffic.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade OpenStack Neutron to version 7.0.4 or later, or 8.1.1 or later to obtain the patched code that properly enforces MAC-spoofing protection on all traffic types.

Fix this in Neutron Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-5363 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-5363 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