Skip to content

GHSA-qh2x-hpf9-cf2g CVE-2013-2255 PYSEC-2026-2413 PYSEC-2026-2677 PYSEC-2026-3034 PYSEC-2026-656

OpenStack Keystone and other components vulnerable to Improper Certificate Validation

Medium PyPI
Severity
5.9 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.97%
Chance of exploitation in the next 30 days. Higher than 61.89% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-295 Improper Certificate Validation
Fix
Available
4 packages have a fixed version

Description

HTTPSConnections in OpenStack Keystone 2013, OpenStack Compute 2013.1, and possibly other OpenStack components, fail to validate server-side SSL certificates.

Affected versions

PyPI

PackageVulnerableFixed in
cinder
< 7.0.0a0
7.0.0a0
keystone
< 8.0.0a0
8.0.0a0
neutron
< 7.0.0a0
7.0.0a0
python-keystoneclient
< 0.4.0
0.4.0

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.

cinder PyPI → 7.0.0a0

pip
pip install --upgrade "cinder>=7.0.0a0"
poetry
poetry add "cinder>=7.0.0a0"
uv
uv add "cinder>=7.0.0a0"

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"

neutron PyPI → 7.0.0a0

pip
pip install --upgrade "neutron>=7.0.0a0"
poetry
poetry add "neutron>=7.0.0a0"
uv
uv add "neutron>=7.0.0a0"

python-keystoneclient PyPI → 0.4.0

pip
pip install --upgrade "python-keystoneclient>=0.4.0"
poetry
poetry add "python-keystoneclient>=0.4.0"
uv
uv add "python-keystoneclient>=0.4.0"

Severity breakdown

CVSS 3.1 5.9

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

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

Weakness

CWE-295: Improper Certificate Validation

The product does not validate, or incorrectly validates, a certificate.

How to prevent it
  • Architecture and Design, Implementation: Certificates should be carefully managed and checked to assure that data are encrypted with the intended owner's public key.
  • Implementation: If certificate pinning is being used, ensure that all relevant properties of the certificate are fully validated before the certificate is pinned, including the hostname.

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