CVE-2014-3632
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 default configuration in a sudoers file in the Red Hat openstack-neutron package before 2014.1.2-4, as used in Red Hat Enterprise Linux Open Stack Platform 5.0 for Red Hat Enterprise Linux 6, allows remote attackers to gain privileges via a crafted configuration file. NOTE: this vulnerability exists because of a CVE-2013-6433 regression.
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 openstack-neutron package for Red Hat Enterprise Linux Open Stack Platform 5.0 ships with an insecure default sudoers configuration that allows privilege escalation. Remote attackers can exploit this by providing a crafted configuration file to gain elevated (root) privileges on the system. This issue is a regression of CVE-2013-6433.
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>= 2014.1, <= 2014.1.2CVSS 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
- High
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:H/Au:N/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.
-
Verify openstack-neutron package is installedRun 'rpm -q openstack-neutron' or 'dpkg -l | grep neutron' to check if the neutron package is present on the systemAffected if The package is installed and the version falls within 2014.1 through 2014.1.2
-
Determine installed neutron versionRun 'rpm -q --qf "%{VERSION}-%{RELEASE}" openstack-neutron' or check the package details to obtain the exact version numberAffected if The version returned is >= 2014.1 and <= 2014.1.2 (versions 2014.1.2-4 and later are fixed)
-
Locate neutron sudoers configurationExamine /etc/sudoers and any files in /etc/sudoers.d/ directory for neutron-related sudo rules. Look for files containing 'neutron' in the filename or contentAffected if A sudoers file or snippet containing neutron sudo rules exists on the system
-
Inspect neutron sudo rules for overly permissive settingsRead the neutron-related sudoers entries found in the previous step. Check for rules that grant neutron user or neutron group excessive sudo privileges without proper restrictionsAffected if The sudoers configuration contains neutron rules that allow broad or unrestricted sudo access, enabling potential privilege escalation
A system is affected if openstack-neutron version 2014.1 through 2014.1.2 is installed and the sudoers configuration contains insecure neutron-related sudo rules that permit privilege escalation.
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 dataUpdate the openstack-neutron package to version 2014.1.2-4 or later, which contains the corrected sudoers configuration. If immediate patching is not possible, manually review and restrict the sudoers file to remove overly permissive neutron-related sudo rules.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.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,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3632 — 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-3632 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