S3 access-key disclosure via debug logging
Published Feb 1, 2024 · Updated Nov 20, 2025
Sensitive-data exposure in OpenStack Glance Store before 4.7.0 allows local users to read S3 access keys from debug logs. The S3 driver's add, get, and delete paths interpolate loc.accesskey into LOG.debug messages rather than excluding the credential. Debug logging and S3 backend use must both be enabled, and the attacker needs low-privileged local access to the resulting logs; exposed keys permit access within the key's S3 permissions.
Summary
What happened
Sensitive-data exposure in OpenStack Glance Store before 4.7.0 allows local users to read S3 access keys from debug logs. The S3 driver's add, get, and delete paths interpolate loc.accesskey into LOG.debug messages rather than excluding the credential. Debug logging and S3 backend use must both be enabled, and the attacker needs low-privileged local access to the resulting logs; exposed keys permit access within the key's S3 permissions.
The record
- CVE
- CVE-2024-1141
- Published
- Feb 1, 2024
- Updated
- Nov 20, 2025
- Vendor
- Red Hat
- Product
- Red Hat OpenStack Platform
- Classifications
- CWE-532, CWE-779, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 1, 2024CVE publishedPublication date reported by the CVE source.
- Nov 20, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo