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.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - 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. (CVE-2017-12440)

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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. (CVE-2017-12440)

Note that Nessus relies on the presence of the package as reported by the vendor.

The remote Redhat Enterprise Linux 7 host has packages installed that are affected by a vulnerability as referenced in the RHSA-2018:0315 advisory.

    openstack-aodh provides the ability to trigger actions based on defined rules against metric or event data     collected by OpenStack Telemetry (ceilometer) or Time-Series-Database-as-a-Service (gnocchi).

    openstack-aodh has been rebased to the upstream 4.0.2-3 version.

    Security Fix(es):

    * A verification flaw was found in openstack-aodh. As part of an HTTP alarm action, a user could pass in a     trust ID. However, the trust could be from anyone because it was not verified. Because the trust was then     used by openstack-aodh to obtain a keystone token for the alarm action, a malicious user could pass in     another person's trust ID and obtain a keystone token containing the delegated authority of that user.
    (CVE-2017-12440)

    Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Zane     Bitter (Red Hat) as the original reporter.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote Redhat Enterprise Linux 7 host has packages installed that are affected by a vulnerability as referenced in the RHSA-2017:3227 advisory.

    openstack-aodh provides the ability to trigger actions based on defined rules against metric or event data     collected by OpenStack Telemetry (ceilometer) or Time-Series-Database-as-a-Service (gnocchi).

    Security Fix(es):

    * A verification flaw was found in openstack-aodh. As part of an HTTP alarm action, a user could pass in a     trust ID. However, the trust could be from anyone because it was not verified. Because the trust was then     used by openstack-aodh to obtain a keystone token for the alarm action, a malicious user could pass in     another person's trust ID and obtain a keystone token containing the delegated authority of that user.
    (CVE-2017-12440)

    This issue was discovered by Luke Hinds (Red Hat). Upstream acknowledges Zane Bitter (Red Hat) as the     original reporter.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

Zane Bitter from Red Hat discovered a vulnerability in Aodh, the alarm engine for OpenStack. Aodh does not verify that the user creating the alarm is the trustor or has the same rights as the trustor, nor that the trust is for the same project as the alarm. The bug allows that an authenticated user without a Keystone token with knowledge of trust IDs to perform unspecified authenticated actions by adding alarm actions.

ID	Name	Product	Family	Severity
433723	SCA: security update for aodh (GHSA-86cv-9gpx-6hwj)	Tenable Cloud Security	SCA Checks	high
433723	SCA: security update for aodh (GHSA-86cv-9gpx-6hwj)	Tenable Self-Hosted Container Security	SCA Checks	high
251434	Linux Distros Unpatched Vulnerability : CVE-2017-12440	Nessus	Misc.	high
194124	RHEL 7 : openstack-aodh (RHSA-2018:0315)	Nessus	Red Hat Local Security Checks	high
194047	RHEL 7 : openstack-aodh (RHSA-2017:3227)	Nessus	Red Hat Local Security Checks	high
102715	Debian DSA-3953-1 : aodh - security update	Nessus	Debian Local Security Checks	high

Detections

Analytics

CVE-2017-12440

high

Tenable Plugins

high

high

high

high

high

high