openstack-aodh: Aodh can be used to launder Keystone trusts
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat OpenStack Platform 10.0 (Newton) | |||
| openstack-aodh-0:3.0.4-1.el7ost | cpe:/a:redhat:openstack:10::el7 | RHSA-2017:3227 | 2017-11-15T00:00:00Z |
| Red Hat OpenStack Platform 11.0 (Ocata) | |||
| openstack-aodh-0:4.0.2-3.el7ost | cpe:/a:redhat:openstack:11::el7 | RHSA-2018:0315 | 2018-02-13T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DSA |
DSA-3953-1 | aodh security update |
EUVD |
EUVD-2022-3123 | Aodh as packaged in Openstack Ocata and Newton before change-ID I8fd11a7f9fe3c0ea5f9843a89686ac06713b7851 and before Pike-rc1 does not verify that trust IDs belong to the user when creating alarm action with the scheme trust+http, which allows remote authenticated users with knowledge of trust IDs where Aodh is the trustee to obtain a Keystone token and perform unspecified authenticated actions by adding an alarm action with the scheme trust+http, and providing a trust id where Aodh is the trustee. |
Github GHSA |
GHSA-86cv-9gpx-6hwj | Openstack Aodh can be used to launder Keystone trusts |
No CVSS v4.0
No CVSS v3.1
This CVE is not in the KEV list.
Exploit prediction score: 2.1% (2.146% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.