OpenstackApplication · Redhat
CVE-2017-2622
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 · uneditedAn accessibility flaw was found in the OpenStack Workflow (mistral) service where a service log directory was improperly made world readable. A malicious system user could exploit this flaw to access sensitive information.
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 Workflow service (mistral) stored its log directory with world-readable permissions (likely 755), allowing any local system user to read log files. These logs could contain sensitive information such as API credentials, token data, or debugging output that reveals internal system details.
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
= 10CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify mistral is installedRun 'rpm -qa | grep mistral' or check for the mistral service via 'systemctl list-units | grep mistral'Affected if mistral package or service is found on the system
-
Locate the mistral log directoryCheck /var/log/mistral/ or inspect the mistral configuration file (typically /etc/mistral/mistral.conf) for the 'log_dir' setting under the [DEFAULT] sectionAffected if A log directory path is configured and exists on the filesystem
-
Check directory permissionsRun 'ls -ld /var/log/mistral/' or the identified log directory pathAffected if The permissions output shows 'drwxr-xr-x' (755) or similar world-readable permissions (e.g., o+r)
-
Verify world-read accessRun 'stat -c %a /var/log/mistral/' to get the octal permission bitsAffected if The third digit (others permission) is 5 or 7, granting read access to any local user
-
Check directory ownershipRun 'stat -c '%U:%G' /var/log/mistral/' to see owner and groupAffected if The directory is not owned exclusively by the mistral service user (typically 'mistral' or 'root') or allows access via group/other permissions
If the mistral log directory exists with permissions allowing world-read access (octal 755 or higher for others), the system is vulnerable to information disclosure via local user access.
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 dataChange the mistral log directory permissions to remove world-read access (e.g., chmod 750 or 700) and ensure the directory is owned by the mistral service user. Verify no other log files retain overly permissive access.
Fix this in Openstack
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2622 — 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-2017-2622 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