keystone 16.0.0 vulnerabilities

Known vulnerabilities in the keystone package. This does not include vulnerabilities belonging to this package’s dependencies.

Vulnerability	Vulnerable Version
M Information Exposure keystone is a package that provides authentication, authorization and service discovery mechanisms via HTTP primarily for use by projects in the OpenStack family. Affected versions of this package are vulnerable to Information Exposure during account locking. By guessing the name of an account and failing to authenticate multiple times, any unauthenticated actor could both confirm the account exists and obtain that account's corresponding `UUID`, which might be leveraged for other unrelated attacks. How to fix Information Exposure? Upgrade `keystone` to version 16.0.2, 17.0.1, 18.1.0, 20.0.0 or higher.	[,16.0.2)[17.0.0,17.0.1)[18.0.0,18.1.0)[19.0.0,20.0.0)
H Privilege Escalation keystone is a package that provides authentication, authorization and service discovery mechanisms via HTTP primarily for use by projects in the OpenStack family. Affected versions of this package are vulnerable to Privilege Escalation. Any authenticated user can create an EC2 credential for themselves for a project that they have a specified role on, and then perform an update to the credential user and project, allowing them to masquerade as another user. This potentially allows a malicious user to act as the admin on a project another user has the admin role on, which can effectively grant that user global admin privileges. How to fix Privilege Escalation? Upgrade `keystone` to version 15.0.1, 16.0.1 or higher.	[,15.0.1)[16.0.0,16.0.1)
M Improper Access Control keystone is a package that provides authentication, authorization and service discovery mechanisms via HTTP primarily for use by projects in the OpenStack family. Affected versions of this package are vulnerable to Improper Access Control. The list of roles provided for an OAuth1 access token is silently ignored. Thus, when an access token is used to request a keystone token, the keystone token contains every role assignment the creator had for the project. This results in the provided keystone token having more role assignments than the creator intended, possibly giving unintended escalated access. How to fix Improper Access Control? Upgrade `keystone` to version 17.0.0 or higher.	[0,17.0.0)
M Improper Authentication keystone is a package that provides authentication, authorization and service discovery mechanisms via HTTP primarily for use by projects in the OpenStack family. Affected versions of this package are vulnerable to Improper Authentication. The EC2 API doesn't have a signature TTL check for AWS Signature V4. An attacker can sniff the Authorization header, and then use it to reissue an OpenStack token an unlimited number of times. How to fix Improper Authentication? Upgrade `keystone` to version 17.0.0 or higher.	[0,17.0.0)
H Improper Access Control keystone is a package that provides authentication, authorization and service discovery mechanisms via HTTP primarily for use by projects in the OpenStack family. Affected versions of this package are vulnerable to Improper Access Control. Any user authenticated within a limited scope (trust/oauth/application credential) can create an EC2 credential with an escalated permission, such as obtaining admin while the user is on a limited viewer role. This potentially allows a malicious user to act as the admin on a project another user has the admin role on, which can effectively grant that user global admin privileges. How to fix Improper Access Control? Upgrade `keystone` to version 17.0.0 or higher.	[0,17.0.0)
M Privilege Escalation keystone is a package that provides authentication, authorization and service discovery mechanisms via HTTP primarily for use by projects in the OpenStack family. Affected versions of this package are vulnerable to Privilege Escalation via the list credentials API. Any user with a role on a project is able to list any credentials with the `/v3/credentials` API when `enforce_scope` is false. How to fix Privilege Escalation? Upgrade `keystone` to version 17.0.0 or higher.	[15.0.0,17.0.0)

Vulnerability

Vulnerable Version

Information Exposure

keystone is a package that provides authentication, authorization and service discovery mechanisms via HTTP primarily for use by projects in the OpenStack family.

Affected versions of this package are vulnerable to Information Exposure during account locking. By guessing the name of an account and failing to authenticate multiple times, any unauthenticated actor could both confirm the account exists and obtain that account's corresponding UUID, which might be leveraged for other unrelated attacks.

How to fix Information Exposure?

Upgrade keystone to version 16.0.2, 17.0.1, 18.1.0, 20.0.0 or higher.

[,16.0.2)[17.0.0,17.0.1)[18.0.0,18.1.0)[19.0.0,20.0.0)

Privilege Escalation

keystone is a package that provides authentication, authorization and service discovery mechanisms via HTTP primarily for use by projects in the OpenStack family.

Affected versions of this package are vulnerable to Privilege Escalation. Any authenticated user can create an EC2 credential for themselves for a project that they have a specified role on, and then perform an update to the credential user and project, allowing them to masquerade as another user. This potentially allows a malicious user to act as the admin on a project another user has the admin role on, which can effectively grant that user global admin privileges.

How to fix Privilege Escalation?

Upgrade keystone to version 15.0.1, 16.0.1 or higher.

[,15.0.1)[16.0.0,16.0.1)

Improper Access Control

keystone is a package that provides authentication, authorization and service discovery mechanisms via HTTP primarily for use by projects in the OpenStack family.

Affected versions of this package are vulnerable to Improper Access Control. The list of roles provided for an OAuth1 access token is silently ignored. Thus, when an access token is used to request a keystone token, the keystone token contains every role assignment the creator had for the project. This results in the provided keystone token having more role assignments than the creator intended, possibly giving unintended escalated access.

How to fix Improper Access Control?

Upgrade keystone to version 17.0.0 or higher.

[0,17.0.0)

Improper Authentication

keystone is a package that provides authentication, authorization and service discovery mechanisms via HTTP primarily for use by projects in the OpenStack family.

Affected versions of this package are vulnerable to Improper Authentication. The EC2 API doesn't have a signature TTL check for AWS Signature V4. An attacker can sniff the Authorization header, and then use it to reissue an OpenStack token an unlimited number of times.

How to fix Improper Authentication?

Upgrade keystone to version 17.0.0 or higher.

[0,17.0.0)

Improper Access Control

keystone is a package that provides authentication, authorization and service discovery mechanisms via HTTP primarily for use by projects in the OpenStack family.

Affected versions of this package are vulnerable to Improper Access Control. Any user authenticated within a limited scope (trust/oauth/application credential) can create an EC2 credential with an escalated permission, such as obtaining admin while the user is on a limited viewer role.

This potentially allows a malicious user to act as the admin on a project another user has the admin role on, which can effectively grant that user global admin privileges.

How to fix Improper Access Control?

Upgrade keystone to version 17.0.0 or higher.

[0,17.0.0)

Privilege Escalation

keystone is a package that provides authentication, authorization and service discovery mechanisms via HTTP primarily for use by projects in the OpenStack family.

Affected versions of this package are vulnerable to Privilege Escalation via the list credentials API. Any user with a role on a project is able to list any credentials with the /v3/credentials API when enforce_scope is false.

How to fix Privilege Escalation?

Upgrade keystone to version 17.0.0 or higher.

[15.0.0,17.0.0)

keystone@16.0.0 vulnerabilities

OpenStack Identity

latest version

latest non vulnerable version

first published

latest version published

licenses detected

Direct Vulnerabilities

How to fix?