dbcve.org
Glance StoreApplication · Openstack

CVE-2024-1141

MEDIUM · 5.5 CVSS v3.1 Published 2024-02-01
Fix available
A fix is available. Upgrade to 4.7.0 or later.
See remediation →
57/100
Remediation priority · Elevated
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 vulnerability was found in python-glance-store. The issue occurs when the package logs the access_key for the glance-store when the DEBUG log level is enabled.

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 python-glance-store package contains a logging vulnerability where the access_key credential is written to log files when DEBUG log level is enabled. This exposes sensitive authentication credentials to anyone with access to the logs, potentially leading to unauthorized access to the glance-store backend.

MitigationDisable DEBUG logging in production environments or upgrade to a patched version of python-glance-store that masks or redacts the access_key in log output.

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
Glance StoreApplication
Affected:< 4.7.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed python-glance-store version
    Run 'pip show python-glance-store' or 'rpm -q python-glance-store' to check the installed package version
    Affected if Version is lower than 4.7.0 (e.g., 4.6.x, 4.5.x, etc.)
  2. Determine current logging configuration
    Inspect the glance-api configuration file (typically /etc/glance/glance-api.conf or /etc/glance.conf) and look for the 'log_level' or 'debug' setting under the [DEFAULT] section
    Affected if The 'debug' option is set to 'True' or 'log_level' is set to 'DEBUG'
  3. Locate glance-store log files
    Check the log directory configured in glance (typically /var/log/glance/ or as specified in the log_file configuration option)
    Affected if Log files exist and are accessible to users who should not see credentials
  4. Search logs for access_key exposure
    Grep log files for the string 'access_key' or 'secret_key' patterns: 'grep -i access_key /var/log/glance/*.log' (adjust path to actual log location)
    Affected if Log files contain plaintext access_key values or credential strings in DEBUG output

Environment is affected if python-glance-store version is below 4.7.0 AND DEBUG logging is enabled, resulting in potential credential exposure in log files.

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.

dbcve · scoped
Upgrade available Upgrade to 4.7.0 or later
Fixed in 4.7.0
Interim mitigation

Disable DEBUG logging in production environments or upgrade to a patched version of python-glance-store that masks or redacts the access_key in log output.

Recommended fix High confidence

4.7.0

  1. Check the current installed version of python-glance-store using: pip show python-glance-store or pip freeze | grep glance-store
  2. Upgrade to version 4.7.0 or later using: pip install --upgrade python-glance-store>=4.7.0
  3. Verify the upgrade was successful by running: pip show python-glance-store and confirming the version number
  4. If using a Red Hat OpenStack environment, also run the appropriate platform package manager update (e.g., yum update python-glance-store or dnf update python-glance-store)
  5. Restart the glance services (glance-api) to ensure the new version is loaded: systemctl restart openstack-glance-api or systemctl restart glance-api

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Glance Store Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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