Skip to content

GHSA-f82m-w3p3-cgp3 CVE-2016-4911 PYSEC-2016-38

OpenStack Identity Keystone Improper Access Control

Medium PyPI
Severity
0.0 / 10
Medium · CVSS 4.0
Exploit chance (EPSS)
1.40%
Chance of exploitation in the next 30 days. Higher than 72.53% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-284 Improper Access Control
Fix
9.0.1
Upgrade keystone to this version or later

Description

The Fernet Token Provider in OpenStack Identity (Keystone) 9.0.x before 9.0.1 (mitaka) allows remote authenticated users to prevent revocation of a chain of tokens and bypass intended access restrictions by rescoping a token.

Affected versions

PyPI

PackageVulnerableFixed in
keystone
>= 9.0.0, < 9.0.1
9.0.1

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 → 9.0.1

pip
pip install --upgrade "keystone>=9.0.1"
poetry
poetry add "keystone>=9.0.1"
uv
uv add "keystone>=9.0.1"

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Attack vector
Network
Attack complexity
Low
Attack requirements
None
Privileges required
Low
User interaction
None
Confidentiality (vulnerable system)
None
Integrity (vulnerable system)
Low
Availability (vulnerable system)
None
Confidentiality (subsequent systems)
None
Integrity (subsequent systems)
None
Availability (subsequent systems)
None

CVSS 3.0 4.3

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

Weakness

CWE-284: Improper Access Control

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

How to prevent it
  • Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
  • 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

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy 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
Is this in your code?

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