Tim Shephard

**Name of the Vulnerable Software and Affected Versions** OpenStack Keystone versions prior to 29.0.3 **Description** Tokens obtained through delegated authentication mechanisms, such as OAuth1 access tokens, application credentials, or trusts, can be submitted to the token-method authentication path for reauthentication. This allows an attacker to escape the intended project scope. Specifically, when an application credential token is presented without an explicit scope, the system issues a new token scoped to the default project of the credential owner instead of the project for which the credential was originally issued, thereby bypassing project boundaries. **Recommendations** Update OpenStack Keystone to version 29.0.3 or later.

**Name of the Vulnerable Software and Affected Versions** OpenStack Swift versions prior to 2.37.2 **Description** The proxy-server fails to strip internal update headers from client requests before forwarding them to object-servers. An authenticated user with write access can inject the headers `X-Container-Host`, `X-Container-Device`, `X-Delete-At-Host`, and `X-Delete-At-Device` to redirect container update requests to an attacker-controlled server, resulting in server-side request forgery (SSRF). This allows the exposure of internal cluster metadata, such as storage policy indexes, partition mappings, device names, and, when at-rest encryption is active, cipher text and initialization vectors for the container-level encryption key. Additionally, the shard-range redirect mechanism can be used to create ghost listings in arbitrary containers. **Recommendations** Update to version 2.37.2 or later.

**Name of the Vulnerable Software and Affected Versions** OpenStack Horizon versions prior to 25.7.4 **Description** OpenStack Horizon produces scripts for OpenStack RC file downloading that may contain a crafted project name with shell metacharacters. Shell metacharacters are special characters interpreted by the command-line shell to perform specific actions, which could lead to unintended command execution if not properly handled. **Recommendations** Update to version 25.7.4.

**Name of the Vulnerable Software and Affected Versions** oslo.messaging versions 1.0.0 through 17.3.0 **Description** The RabbitMQ driver in oslo.messaging fails to perform TLS hostname verification when connecting to the message broker. While the driver enables certificate chain validation when `ssl ca file` is configured, it does not pass the expected broker hostname to the TLS stack. Consequently, any certificate signed by the deployment CA is accepted regardless of the hostname. This allows an attacker capable of intercepting control-plane traffic to impersonate the RabbitMQ broker and execute a man-in-the-middle attack on RPC and notification traffic. All OpenStack services utilizing oslo.messaging with RabbitMQ over TLS are impacted. **Recommendations** Update to version 18.1.0-1.1 or later.

**Name of the Vulnerable Software and Affected Versions** OpenStack Neutron versions 26.0.0 through 28.0.0 **Description** The tagging controller enforces plural policy action names on single-tag write operations, whereas the defined policy rules use singular names. This mismatch causes the default policy to evaluate the actions as allowed, enabling a project reader to create and update tags on resources within the same project. **Recommendations** Update to version 28.0.1.

**Name of the Vulnerable Software and Affected Versions** OpenStack Keystone versions 13 through 29 **Description** An issue exists where the 'POST /v3/credentials' endpoint fails to validate that the `project id` provided by the caller for an EC2-type credential matches the project of the authenticating application credential. This allows an attacker with an unrestricted application credential for one project to create an EC2 credential targeting a different project. A subsequent exchange via '/v3/ec2tokens' can then issue a Keystone token scoped to the target project while retaining the original `app cred id`, enabling cross-project lateral movement within the role footprint of the credential owner. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.