CVE-2017-9232

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 81.6%, top 1% of all CVEs by exploit prediction. 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
Weaponized
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 49%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

Juju before 1.25.12, 2.0.x before 2.0.4, and 2.1.x before 2.1.3 uses a UNIX domain socket without setting appropriate permissions, allowing privilege escalation by users on the system to root.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
98.7%
KEV
Not listed

Published

May 28, 2017

Last Modified

May 13, 2026

Advisory Details (2)

Auto-updated May 17, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

Juju-run Agent - Privilege Escalation (Metasploit) - Linux local Exploit

https://www.exploit-db.com/exploits/44023/
generic
http://www.securityfocus.com/bid/98737

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntujuju-2.0 (2.0.2-0ubuntu0.16.04.2) @ xenial2026-05-20ubuntu

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

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/juju/juju—0.0.0-20170524231039-0417178a3c28—

All Vendor Advisories

(1)

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 7× in last 7d / 33× 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.

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

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 Metasploit module) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-44023✓ verified
    First seen Feb 12, 2018

    Juju-run Agent - Privilege Escalation (Metasploit)

    Open source ↗
  • Metasploitexploit/linux/local/juju_run_agent_priv_esc✓ verified
    First seen Apr 13, 2017

    Juju-run Agent Privilege Escalation

    Open source ↗

Frequently asked(5)

What is CVE-2017-9232?
CVE-2017-9232 is a critical vulnerability published on May 28, 2017. Juju before 1.25.12, 2.0.x before 2.0.4, and 2.1.x before 2.1.3 uses a UNIX domain socket without setting appropriate permissions, allowing privilege escalation by users on the system to root.
When was CVE-2017-9232 disclosed?
CVE-2017-9232 was first published in the National Vulnerability Database on May 28, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-9232 actively exploited?
CVE-2017-9232 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-9232?
CVE-2017-9232 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-9232?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-9232, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2017-9232?

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

Start Free Scan →Browse All CVEs