GHSA-rxrm-xvp4-jqvh CVE-2013-2006 PYSEC-2013-40
OpenStack Keystone Sensitive information disclosure via log files
- Severity
- Low
- The publisher's own rating, not a CVSS score
- Exploit chance (EPSS)
- 0.61%
- Chance of exploitation in the next 30 days. Higher than 49.04% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Fix
8.0.0a0- Upgrade keystone to this version or later
Description
OpenStack Identity (Keystone) Grizzly 2013.1.1, when DEBUG mode logging is enabled, logs the (1) admin_token and (2) LDAP password in plaintext, which allows local users to obtain sensitive by reading the log file.
Affected versions
PyPI
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
keystone PyPI → 8.0.0a0
- pip
pip install --upgrade "keystone>=8.0.0a0"- poetry
poetry add "keystone>=8.0.0a0"- uv
uv add "keystone>=8.0.0a0"
Weakness
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
How to prevent it
- Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
References
Advisories
Packages
Other links
- github.com/openstack/keystone/commit/c5037dd6b82909efaaa8720e8cfa8bdb8b4a0edd
- github.com/openstack/keystone/commit/d43e2a51a1ed7adbed3c5ddf001d46bc4a824ae8
- bugs.launchpad.net/keystone/+bug/1172195
- bugs.launchpad.net/ossn/+bug/1168252
- github.com/pypa/advisory-database/tree/main/vulns/keystone/PYSEC-2013-40.yaml
- lists.fedoraproject.org/pipermail/package-announce/2013-May/105916.html
- lists.fedoraproject.org/pipermail/package-announce/2013-May/106220.html
- rhn.redhat.com/errata/RHSA-2013-0806.html
- openwall.com/lists/oss-security/2013/04/24/1
- openwall.com/lists/oss-security/2013/04/24/2
- securityfocus.com/bid/59411
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-whqr-fgm5-x77q OpenStack Keystone's federated token rescoping mechanism doesn't propagate the original token's expiry to the newly issued token | High | Also affects keystone |
| GHSA-q623-f4j4-p4xj OpenStack Keystone has an Incorrect Authorization issue | High | Also affects keystone |
| GHSA-2r23-2g6v-2m5f OpenStack Keystone has an Authorization Bypass | High | Also affects keystone |
| GHSA-8f8m-wrvr-wcvf OpenStack Keystone doesn't verify that the user supplied in the authentication request matches the owner of the application credential | High | Also affects keystone |
| GHSA-hhq2-3832-xxcv OpenStack Keystone has an Incorrect Authorization Issue | High | Also affects keystone |
| GHSA-pfx2-9x9m-7ghx OpenStack Keystone: LDAP identity backend does not convert enabled attribute to boolean | High | Also affects keystone |
| GHSA-4phw-6824-6cfp OpenStack Keystone: Restricted application credentials can create EC2 credentials | Medium | Also affects keystone |
| GHSA-hcqg-5g63-7j9h OpenStack Keystone allows /v3/ec2tokens or /v3/s3tokens request with valid AWS Signature to provide Keystone authorization. | High | Also affects keystone |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor