CVE-2014-5253: OpenStack Keystone Domain-scoped tokens don't get revoked
(updated )
OpenStack Identity (Keystone) 2014.1.x before 2014.1.2.1 and Juno before Juno-3 does not properly revoke tokens when a domain is invalidated, which allows remote authenticated users to retain access via a domain-scoped token for that domain.
References
- bugs.launchpad.net/keystone/+bug/1349597
- github.com/advisories/GHSA-77w8-qv8m-386h
- github.com/openstack/keystone
- github.com/openstack/keystone/commit/317f9d34b4da20c21edd5b851889298b67c843e1
- github.com/openstack/keystone/commit/3e035ebb726167aef43c4a865c7e7f7d3b0978fb
- github.com/openstack/keystone/commit/c4447f16da036fe878382ce4e1b05b84bdcc4d4e
- github.com/openstack/keystone/commit/cccc3f3239c68479de0f6a41bd64badf2a9ec9e7
- github.com/pypa/advisory-database/tree/main/vulns/keystone/PYSEC-2014-109.yaml
- nvd.nist.gov/vuln/detail/CVE-2014-5253
Code Behaviors & Features
Detect and mitigate CVE-2014-5253 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →