CVE-2017-12440

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 2.1% (81st percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2.1%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
39
EG Risk 39/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation2% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
2.1%
EPSS %ILE
81st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 18, 2017

Last Modified

June 17, 2026

References (16)

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatopenstack-aodh-0:4.0.2-3.el7ost2018-02-13redhat
redhatopenstack-aodh-0:3.0.4-1.el7ost2017-11-15redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 6 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
aodh—
  • every version up to 5.0.0-2: fixed in 5.0.0-2
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
aodh—
  • every version up to 5.0.0-2: fixed in 5.0.0-2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
aodh—
  • every version up to 5.0.0-2: fixed in 5.0.0-2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
aodh—
  • every version up to 5.0.0-2: fixed in 5.0.0-2
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
aodh3.0.0-4
  • every version up to 3.0.0-4+deb9u1: fixed in 3.0.0-4+deb9u1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
aodh0.0.1.dev4004 ... 6.0.0 (32 versions)
  • every version up to 6.0.1: fixed in 6.0.1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 22× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 159 total refreshes for this CVE.

  1. 2026-10-10 19:55 UTCEPSS rescore
  2. 2026-10-09 20:02 UTCEPSS rescore
  3. 2026-10-08 16:35 UTCEPSS rescore
  4. 2026-10-08 01:24 UTCOSV refresh
  5. 2026-10-07 23:41 UTCEPSS rescore
  6. 2026-10-06 15:11 UTCEPSS rescore
  7. 2026-10-05 17:38 UTCEPSS rescore
  8. 2026-10-04 23:18 UTCEPSS rescore
  9. 2026-10-03 14:21 UTCEPSS rescore
  10. 2026-09-30 14:58 UTCEPSS rescore
  11. 2026-09-30 09:24 UTCEG score recompute
  12. 2026-09-27 13:40 UTCEPSS rescore
  13. 2026-09-26 15:53 UTCEPSS rescore
  14. 2026-09-24 13:59 UTCEPSS rescore
  15. 2026-09-19 15:36 UTCEPSS rescore
  16. 2026-09-18 19:22 UTCEPSS rescore
  17. 2026-09-18 07:20 UTCOSV refresh
  18. 2026-09-17 19:22 UTCEPSS rescore
  19. 2026-09-15 03:05 UTCEPSS rescore
  20. 2026-09-13 16:42 UTCEPSS rescore
  21. 2026-09-12 14:55 UTCEPSS rescore
  22. 2026-09-11 09:31 UTCEPSS rescore
  23. 2026-09-10 09:26 UTCEPSS rescore
  24. 2026-09-07 15:56 UTCEPSS rescore
  25. 2026-09-04 13:56 UTCEPSS rescore
Show 75 more
  1. 2026-09-04 05:01 UTCEPSS rescore
  2. 2026-09-02 14:07 UTCEPSS rescore
  3. 2026-09-01 13:48 UTCEPSS rescore
  4. 2026-09-01 03:31 UTCEPSS rescore
  5. 2026-08-30 19:13 UTCEPSS rescore
  6. 2026-08-30 08:00 UTCOSV refresh
  7. 2026-08-28 21:36 UTCEPSS rescore
  8. 2026-08-27 14:20 UTCEPSS rescore
  9. 2026-08-26 14:41 UTCEPSS rescore
  10. 2026-08-25 13:44 UTCEPSS rescore
  11. 2026-08-24 14:10 UTCEPSS rescore
  12. 2026-08-21 23:44 UTCEPSS rescore
  13. 2026-08-20 22:50 UTCEPSS rescore
  14. 2026-08-19 16:59 UTCEPSS rescore
  15. 2026-08-18 13:43 UTCEPSS rescore
  16. 2026-08-17 13:42 UTCEPSS rescore
  17. 2026-08-16 14:51 UTCEPSS rescore
  18. 2026-08-16 02:10 UTCEPSS rescore
  19. 2026-08-15 01:26 UTCEPSS rescore
  20. 2026-08-13 22:50 UTCOSV refresh
  21. 2026-08-13 21:56 UTCEPSS rescore
  22. 2026-08-09 13:42 UTCEPSS rescore
  23. 2026-08-08 16:32 UTCEPSS rescore
  24. 2026-08-07 16:22 UTCEPSS rescore
  25. 2026-08-06 13:42 UTCEPSS rescore
  26. 2026-08-05 19:12 UTCEPSS rescore
  27. 2026-08-04 15:05 UTCEPSS rescore
  28. 2026-08-04 10:32 UTCEPSS rescore
  29. 2026-08-03 10:30 UTCEPSS rescore
  30. 2026-08-02 02:23 UTCEPSS rescore
  31. 2026-08-01 04:11 UTCEPSS rescore
  32. 2026-07-30 16:24 UTCEPSS rescore
  33. 2026-07-30 01:26 UTCEPSS rescore
  34. 2026-07-29 02:21 UTCOSV refresh
  35. 2026-07-28 15:32 UTCEPSS rescore
  36. 2026-07-26 14:51 UTCEPSS rescore
  37. 2026-07-25 14:13 UTCEPSS rescore
  38. 2026-07-23 14:15 UTCEPSS rescore
  39. 2026-07-23 01:26 UTCEG score recompute
  40. 2026-07-22 22:05 UTCEG score recompute
  41. 2026-07-22 14:04 UTCEPSS rescore
  42. 2026-07-21 15:21 UTCEPSS rescore
  43. 2026-07-21 15:21 UTCEPSS rescore
  44. 2026-07-20 17:04 UTCEPSS rescore
  45. 2026-07-20 17:04 UTCEPSS rescore
  46. 2026-07-19 14:28 UTCEPSS rescore
  47. 2026-07-19 14:28 UTCEPSS rescore
  48. 2026-07-19 02:26 UTCEPSS rescore
  49. 2026-07-19 02:26 UTCEPSS rescore
  50. 2026-07-18 10:00 UTCEPSS rescore
  51. 2026-07-16 16:59 UTCEPSS rescore
  52. 2026-07-16 16:59 UTCEPSS rescore
  53. 2026-07-15 16:54 UTCEPSS rescore
  54. 2026-07-15 16:54 UTCEPSS rescore
  55. 2026-07-15 01:56 UTCEPSS rescore
  56. 2026-07-13 22:26 UTCEPSS rescore
  57. 2026-07-12 05:43 UTCEPSS rescore
  58. 2026-07-11 18:52 UTCOSV refresh
  59. 2026-07-11 08:24 UTCEPSS rescore
  60. 2026-07-09 19:06 UTCEPSS rescore
  61. 2026-07-08 15:10 UTCEPSS rescore
  62. 2026-07-07 13:42 UTCEPSS rescore
  63. 2026-07-06 16:24 UTCEPSS rescore
  64. 2026-07-06 02:20 UTCEPSS rescore
  65. 2026-07-05 02:27 UTCEPSS rescore
  66. 2026-07-04 06:28 UTCEPSS rescore
  67. 2026-07-01 15:02 UTCEPSS rescore
  68. 2026-07-01 15:02 UTCEPSS rescore
  69. 2026-06-30 23:19 UTCEPSS rescore
  70. 2026-06-30 23:19 UTCEPSS rescore
  71. 2026-06-28 14:04 UTCEPSS rescore
  72. 2026-06-28 04:53 UTCEPSS rescore
  73. 2026-06-27 03:05 UTCEPSS rescore
  74. 2026-06-25 13:47 UTCEPSS rescore
  75. 2026-06-25 13:47 UTCEPSS rescore

Related CVEs(same product + same CWE)

Same product

1 shown

Debian:12:aodh

Frequently asked(5)

What is CVE-2017-12440?
CVE-2017-12440 is a high vulnerability published on August 18, 2017. 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…
When was CVE-2017-12440 disclosed?
CVE-2017-12440 was first published on August 18, 2017, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-12440 actively exploited?
CVE-2017-12440 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.1% probability of exploitation in the next 30 days (81st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-12440?
CVE-2017-12440 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2017-12440?
A fix for CVE-2017-12440 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-12440

Explore →

Is Your Infrastructure Affected by CVE-2017-12440?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs