OpenstackApplication · Redhat
CVE-2017-2621
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 access-control flaw was found in the OpenStack Orchestration (heat) service before 8.0.0, 6.1.0 and 7.0.2 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 confidenceOpenStack Heat orchestration service had improperly permissive file permissions making its log directory world-readable before versions 8.0.0, 6.1.0, and 7.0.2. Any local system user could read sensitive information from these logs.
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
= 9= 10< 8.0.0CVSS 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.1/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.
-
Identify Heat service versionRun 'heat-manage --version' or check the package manager (e.g., 'rpm -q heat-common' or 'dpkg -l heat-common') to determine the installed version of the Heat service.Affected if The version is less than 8.0.0, or for older branches, less than 6.1.0 or 7.0.2, or on Red Hat OpenStack versions 9 or 10.
-
Locate the Heat log directoryCheck the Heat configuration file (typically /etc/heat/heat.conf) for the 'log_dir' setting under the [DEFAULT] section to identify the log directory path.Affected if A log directory is configured and exists on the system.
-
Inspect log directory permissionsRun 'ls -ld <log_dir_path>' (e.g., 'ls -ld /var/log/heat') to view the directory permissions in the first column (e.g., drwxr-xr-x).Affected if The permissions allow world-read access (the fourth character is 'r' or the permission octal starts with a digit higher than 7 for the 'other' field, such as 755 or 775).
-
Check for sensitive content in logsAs a secondary check, examine files in the log directory (e.g., 'ls -la <log_dir_path>/') and verify if any contain sensitive information such as credentials, tokens, or configuration details.Affected if Log files are readable by any local user (world-readable permissions).
The environment is affected if Heat version is below 8.0.0 (or 6.1.0/7.0.2 for older branches) AND the log directory has world-readable permissions (e.g., 755 or 777), allowing any local user to access potentially sensitive log contents.
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 data8.0.0
Restrict read permissions on the Heat service log directory to the heat service user and administrators only (e.g., chmod 750 or 700), then upgrade to a patched version.
Fix this in Openstack
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2621 — 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-2621 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