PYSEC-2026-619

Vulnerability from pysec - Published: 2026-07-02 14:13 - Updated: 2026-07-06 07:36
VLAI
Details

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.

Impacted products
Name purl
aodh pkg:pypi/aodh

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "aodh",
        "purl": "pkg:pypi/aodh"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.0.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "0.0.1.dev4004",
        "1.1.0",
        "1.1.1",
        "1.1.2",
        "1.1.3",
        "2.0.0",
        "2.0.0.0b1",
        "2.0.0.0b2",
        "2.0.0.0b3",
        "2.0.0.0rc1",
        "2.0.1",
        "2.0.2",
        "2.0.3",
        "2.0.4",
        "2.0.5",
        "2.0.6",
        "3.0.0",
        "3.0.0.0b2",
        "3.0.0.0b3",
        "3.0.0.0rc1",
        "3.0.1",
        "3.0.2",
        "3.0.3",
        "3.0.4",
        "4.0.0",
        "4.0.1",
        "4.0.2",
        "4.0.3",
        "5.0.0",
        "5.1.0",
        "5.1.1",
        "6.0.0"
      ]
    }
  ],
  "aliases": [
    "CVE-2017-12440",
    "GHSA-86cv-9gpx-6hwj"
  ],
  "details": "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.",
  "id": "PYSEC-2026-619",
  "modified": "2026-07-06T07:36:17.267393Z",
  "published": "2026-07-02T14:13:24.418168Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2017-12440"
    },
    {
      "type": "WEB",
      "url": "https://github.com/openstack/aodh/commit/149d3ad2193b4d17df801f82a0a6be62dba564db"
    },
    {
      "type": "WEB",
      "url": "https://github.com/openstack/aodh/commit/92182de328d1f088c5f5a68326d2b207b21e06ea"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/errata/RHSA-2017:3227"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/errata/RHSA-2018:0315"
    },
    {
      "type": "WEB",
      "url": "https://bugs.launchpad.net/ossn/+bug/1649333"
    },
    {
      "type": "WEB",
      "url": "https://review.openstack.org/#/c/493823"
    },
    {
      "type": "WEB",
      "url": "https://review.openstack.org/#/c/493824"
    },
    {
      "type": "WEB",
      "url": "https://review.openstack.org/#/c/493826"
    },
    {
      "type": "WEB",
      "url": "http://www.debian.org/security/2017/dsa-3953"
    },
    {
      "type": "WEB",
      "url": "http://www.securityfocus.com/bid/100455"
    },
    {
      "type": "PACKAGE",
      "url": "https://pypi.org/project/aodh"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/advisories/GHSA-86cv-9gpx-6hwj"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Openstack Aodh can be used to launder Keystone trusts"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…