dbcve.org
OpenstackApplication · Redhat

CVE-2017-2627

HIGH · 8.2 CVSS v3.0 Published 2018-08-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
A flaw was found in openstack-tripleo-common as shipped with Red Hat Openstack Enterprise 10 and 11. The sudoers file as installed with OSP's openstack-tripleo-common package is much too permissive. It contains several lines for the mistral user that have wildcards that allow directory traversal with '..' and it grants full passwordless root access to the validations user.

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 confidence

The openstack-tripleo-common package installs a sudoers file with severely misconfigured permissions. The mistral user has sudo entries containing wildcard characters that allow directory traversal via '..', potentially enabling access to unintended files and directories. Additionally, the validations user is granted passwordless root access without restrictions. This constitutes a local privilege escalation vulnerability enabling an authenticated attacker to gain root privileges.

MitigationReplace the permissive sudoers entries with specific, narrowly-scoped command restrictions. Remove wildcards and '..' patterns from mistral user rules. Restrict or remove the validations user root access, granting only the minimum permissions required for validations to function.

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:= 10= 11
Tripleo CommonApplication
Affected:all versions

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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/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 if openstack-tripleo-common package is installed
    On RHEL-based systems, run: rpm -qa | grep tripleo-common or dnf list installed | grep tripleo-common
    Affected if The package is installed and matches version 10 or 11 (RHEL OSP), or is any version of Openstack Tripleo Common
  2. Locate the sudoers file installed by tripleo-common
    Examine files in /etc/sudoers.d/ directory for any files containing 'mistral' or 'validations' user rules, or check the main /etc/sudoers file for these users
    Affected if A sudoers file containing mistral or validations user entries exists on the system
  3. Inspect mistral user sudo entries for wildcard traversal
    Review the mistral user configuration in the sudoers file, looking for patterns containing wildcard characters (*) and '..' path traversal sequences
    Affected if The mistral user has sudo rules containing wildcards or '..' that allow directory traversal beyond intended directories
  4. Inspect validations user sudo entries for unrestricted root access
    Review the validations user configuration in the sudoers file, checking for entries that grant passwordless ALL privilege or unrestricted root access
    Affected if The validations user has passwordless sudo access to ALL commands without restrictions

A system is affected if openstack-tripleo-common is installed AND its sudoers configuration contains either unrestricted mistral user wildcard entries with '..' patterns or passwordless unrestricted root access for the validations user.

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

Replace the permissive sudoers entries with specific, narrowly-scoped command restrictions. Remove wildcards and '..' patterns from mistral user rules. Restrict or remove the validations user root access, granting only the minimum permissions required for validations to function.

Fix this in Openstack Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-2627 — 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-2017-2627 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