Skip to content
OpenAdvisories
High · 7.5 CVE-2017-12440 EUVD-2022-3123GHSA-86cv-9gpx-6hwjPYSEC-2026-619

Openstack Aodh can be used to launder Keystone trusts

Published Aug 18, 2017 · Updated Aug 5, 2024 · Assigned by mitre

Description

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.

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

ReleasePackageFixed inAdvisory
Debian 14 aodh 5.0.0-2 —
Debian 13 aodh 5.0.0-2 —
Debian 12 aodh 5.0.0-2 —
Debian 9 aodh 3.0.0-4+deb9u1 DSA-3953-1
ReleasePackageFixed inAdvisory
Ubuntu 16.04 LTS aodh No fix yet —
ReleasePackageFixed inAdvisory
Red Hat OpenStack 11 python-aodh +9 4.0.2-3.el7ost RHSA-2018:0315
Red Hat OpenStack 10 python-aodh +9 3.0.4-1.el7ost RHSA-2017:3227
ReleasePackageFixed inAdvisory
SUSE OpenStack Cloud 7 openstack-aodh +1 3.0.4~a0~dev1-2.3.1 SUSE-SU-2017:2627-1

Affected packages

EcosystemPackageAffectedFixedRecord
PyPI aodh < 6.0.1 6.0.1 GHSA-86cv-9gpx-6hwj

Advisories 4

References