CVE-2012-3426: OpenStack Keystone token expiration issues
(updated )
OpenStack Keystone before 2012.1.1, as used in OpenStack Folsom before Folsom-1 and OpenStack Essex, does not properly implement token expiration, which allows remote authenticated users to bypass intended authorization restrictions by (1) creating new tokens through token chaining, (2) leveraging possession of a token for a disabled user account, or (3) leveraging possession of a token for an account with a changed password.
References
- bugs.launchpad.net/keystone/+bug/996595
- bugs.launchpad.net/keystone/+bug/997194
- bugs.launchpad.net/keystone/+bug/998185
- github.com/advisories/GHSA-xp97-6w7r-4cjc
- github.com/openstack/keystone
- github.com/openstack/keystone/commit/375838cfceb88cacc312ff6564e64eb18ee6a355
- github.com/openstack/keystone/commit/628149b3dc6b58b91fd08e6ca8d91c728ccb8626
- github.com/openstack/keystone/commit/a67b24878a6156eab17b9098fa649f0279256f5d
- github.com/pypa/advisory-database/tree/main/vulns/keystone/PYSEC-2012-34.yaml
- launchpad.net/keystone/essex/2012.1.1/+download/keystone-2012.1.1.tar.gz
- nvd.nist.gov/vuln/detail/CVE-2012-3426
Detect and mitigate CVE-2012-3426 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →