CVE-2014-0187
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 openvswitch-agent process in OpenStack Neutron 2013.1 before 2013.2.4 and 2014.1 before 2014.1.1 allows remote authenticated users to bypass security group restrictions via an invalid CIDR in a security group rule, which prevents further rules from being applied.
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 confidenceIn OpenStack Neutron's openvswitch-agent, security group rules are processed sequentially. When an invalid CIDR (e.g., malformed or out-of-range) is submitted in a security group rule, the agent fails to parse it and halts processing of subsequent rules entirely. This allows an authenticated attacker to bypass security group enforcement by inserting an invalid CIDR rule, causing all rules after it to be ignored by the firewall.
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= 13.04= 14.04= 2013.1= 2013.1.1= 2013.1.2= 2013.1.3= 2013.1.4= 2013.1.5= 2013.2= 2013.2.1= 2013.2.2= 2013.2.3= 2014.1= 13.1CVSS 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
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:S/C:C/I:C/A:C
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.
-
Identify Neutron installation and versionRun 'neutron --version' or check the installed package version via package manager (dpkg -l | grep neutron or rpm -qa | grep neutron)Affected if The installed version matches any of: 2013.1, 2013.1.1, 2013.1.2, 2013.1.3, 2013.1.4, 2013.1.5, 2013.2, 2013.2.1, 2013.2.2, 2013.2.3, 2014.1 (or Ubuntu 13.04/14.04 or openSUSE 13.1 with neutron packages from these releases)
-
Verify openvswitch-agent is deployedCheck running processes for 'neutron-openvswitch-agent' or check /etc/neutron/plugins/openvswitch/ for configuration filesAffected if The openvswitch-agent service is running and handling security groups
-
Confirm security groups are in useList security groups with 'neutron security-group-list' or check neutron configuration files for 'enable_security_group = True' in /etc/neutron/Affected if Security groups are enabled and instances are using them
-
Identify the firewall driverCheck neutron configuration (usually /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini) for 'firewall_driver' setting under the securitygroup sectionAffected if The firewall driver is set to use openvswitch-agent (e.g., neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver or similar openvswitch-based firewall driver)
You are affected if Neutron version is 2013.1 through 2014.1 (or Ubuntu 13.04/14.04/openSUSE 13.1 packages from these releases) AND the openvswitch-agent is handling security groups with a vulnerable firewall driver.
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 · scopedUpgrade Neutron to version 2013.2.4 or 2014.1.1 or later, which includes proper validation of CIDR inputs before processing security group rules. Alternatively, implement input validation at the API layer to reject invalid CIDR formats before they reach the openvswitch-agent.
Neutron 2013.2.4 or later (for 2013.x branch) or Neutron 2014.1.1 or later (for 2014.x branch)
- 1. Identify the current Neutron version by running: neutron --version or dpkg -l | grep neutron
- 2. For Ubuntu systems: Run 'apt-get update' and 'apt-get install neutron' to upgrade to the latest available fixed version
- 3. For openSUSE systems: Run 'zypper update neutron' to apply the security patch
- 4. After upgrading, restart the openvswitch-agent service: 'service neutron-plugin-openvswitch-agent restart'
- 5. Verify the upgrade was successful by checking the Neutron version again
- 6. Test that security group rules with invalid CIDRs are now properly handled and don't cause rule bypass
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0187 — 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-2014-0187 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