dbcve.org
OpenstackApplication · Redhat

CVE-2014-0071

MEDIUM · 6.4 CVSS v2.0 Published 2014-04-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
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
PackStack in Red Hat OpenStack 4.0 does not enforce the default security groups when deployed to Neutron, which allows remote attackers to bypass intended access restrictions and make unauthorized connections.

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

PackStack installation tool for Red Hat OpenStack 4.0 fails to properly configure and enforce Neutron security groups during deployment. Security groups act as virtual stateful firewalls controlling instance traffic; when not enforced, instances are exposed to unauthorized network access from remote attackers.

MitigationApply the PackStack patch to enforce default security groups in Neutron deployments, or manually configure Neutron security groups to deny unauthorized inbound connections by default.

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
OpenstackApplication
Affected:= 4.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
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
None

AV:N/AC:L/Au:N/C:P/I:P/A:N

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. Identify the networking backend in use
    Run 'neutron agent-list' or check /etc/neutron/neutron.conf for the 'core_plugin' setting. If core_plugin is not 'neutron.plugins.ml2.plugin.Ml2Plugin', Neutron may not be active.
    Affected if Neutron is not the active networking backend (e.g., nova-network is used instead)
  2. Verify security groups are enabled in Neutron
    Check /etc/neutron/neutron.conf for 'enable_security_group = True' under the [securitygroup] section, or run 'neutron security-group-list' to list existing groups.
    Affected if enable_security_group is set to False or is missing entirely
  3. Check the default security group rules
    Run 'neutron security-group-show default' and inspect the rules. Look for ingress (inbound) rules. If any ingress rule has '0.0.0.0/0' as source IP and allows TCP/UDP/ICMP, security groups are not properly restricting access.
    Affected if The default security group allows unrestricted inbound traffic (0.0.0.0/0 source)
  4. Confirm security group enforcement at the hypervisor
    Run 'neutron agent-list' and check for the security group agent ( neutron.agent.l3.agentscheduler.SecurityGroupAgentMapping ). Also verify iptables rules on compute nodes: 'iptables -L -n | grep -i neutron' should show security group rules.
    Affected if No security group agent is mapped to compute hosts, or iptables does not contain neutron security group chains
  5. Inspect PackStack answer file for security group configuration
    Check the answer file used during deployment (typically /root/packstack-answers.txt) for 'CONFIG_NEUTRON_...=y' parameters, specifically CONFIG_NEUTRON_SECGROUP=y and whether a default deny rule was set.
    Affected if CONFIG_NEUTRON_SECGROUP is not set to 'y' or PackStack did not apply default security group rules during installation

A user is affected if Neutron is deployed via PackStack 4.0 and the default security group allows inbound traffic from any source (0.0.0.0/0), indicating security groups were not enforced during installation.

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

Apply the PackStack patch to enforce default security groups in Neutron deployments, or manually configure Neutron security groups to deny unauthorized inbound connections by default.

Fix this in Openstack Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-0071 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2014-0071 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