|
keystone (2:21.0.1-0ubuntu2.6) jammy-security; urgency=medium
* SECURITY UPDATE: privilege escalation via application credential token
- debian/patches/notifications-test-config.patch: Ensure
oslo_messaging_notifications group exists in
keystone/tests/unit/common/test_notifications.py.
- debian/patches/Block-app-credential-token-rescoping.patch: Block app
credential token rescoping Application credential tokens could be rescoped
to system scope via token-from-token auth, bypassing the intended scope
binding. The check only blocked project and domain scope but not system,
allowing escalation to full system-admin privileges. . Check for any
requested scope rather than enumerating individual scope types. in
keystone/auth/plugins/token.py, keystone/tests/unit/test_v3_auth.py.
- debian/patches/Ban-ec2credential-tokens-from-Keystone-API.patch: Ban
ec2credential tokens from Keystone API in
keystone/server/flask/request_processing/middleware/auth_context.py,
keystone/tests/unit/test_contrib_ec2_core.py.
- d/p/auth-encode-ec2credential-and-oauth2-credential-in-the-method-
bitmask.patch: auth: encode ec2credential and oauth2_credential in the
method bitmask in keystone/auth/plugins/core.py,
keystone/tests/unit/auth/plugins/test_core.py, releasenotes/notes/reserve-
pseudo-method-bits-404f8c553e033246.yaml.
* debian/patches/fix-test-state-cleanup.patch: Fix test state cleanup. Dirty
test state was causing tests to fail if they were run in a specific order
in keystone/tests/unit/ksfixtures/backendloader.py.
* SECURITY UPDATE: privilege escalation via delegated tokens on trust
- debian/patches/CVE-2026-80182.patch: trusts, oauth1, app-creds: reject
delegated tokens across all endpoints in
keystone/api/_shared/delegation.py, keystone/api/os_oauth1.py,
keystone/api/trusts.py, keystone/api/users.py, keystone/conf/auth.py,
keystone/tests/unit/test_v3_application_credential.py,
keystone/tests/unit/test_v3_oauth1.py,
keystone/tests/unit/test_v3_trust.py,
releasenotes/notes/bug-2153453-6f2a1d9e0c7b4a83.yaml.
- CVE-2026-80182
* SECURITY UPDATE: privilege escalation via delegated token reauthentication
- debian/patches/CVE-2026-80184.patch: auth: reject delegated tokens from
token-method reauthentication in keystone/auth/plugins/token.py,
keystone/tests/unit/test_v3_auth.py,
releasenotes/notes/bug-2158538-delegated-token-rescope-a1b2c3d4e5f6.yaml,
keystone/tests/unit/test_contrib_ec2_core.py,
keystone/api/_shared/authentication.py.
- CVE-2026-80184
* SECURITY UPDATE: unauthorized domain role assignment information exposure
- debian/patches/CVE-2026-80183.patch: Prevent unauthorized project-scoped
assignment list in keystone/common/policies/role_assignment.py,
releasenotes/notes/bug-2154645-role-assignment-tree-domain-
bypass-f126c413bd62c375.yaml.
- debian/patches/CVE-2026-80183-2.patch: Fix project policy allowing
unauthorized access to root domains in
keystone/common/policies/project.py.
- CVE-2026-80183
-- Isabel Garcia Contreras Mon, 28 Sep 2026 13:13:58 -0400
|
| CVE-2026-80182 |
In OpenStack Keystone before 29.0.3, tokens obtained via OAuth1 access token, application credential, or trust-scoped authentication could create new |
| CVE-2026-80184 |
In OpenStack Keystone before 29.0.3, tokens obtained via delegated authentication mechanisms (OAuth1 access tokens, application credentials, trusts) |
| CVE-2026-80183 |
In OpenStack Keystone before 29.0.3, any authenticated user holding role:reader on any project can list every project-scoped role assignment under an |
|