NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
CRITICAL severity

CVE-2017-9232 — juju

CRITICALFix: juju/juju@0417178

CVE-2017-9232 is a critical-severity (CVSS 9.8) CWE-862 vulnerability in github.com/juju/juju. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for github.com/juju/juju — see the affected versions and patch details below.

Juju uses a UNIX domain socket without setting appropriate permissions

Also known asGHSA-j3hp-pv6v-rgrxGO-2025-3639
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
3 known
Exploitation data as of Oct 30, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
48.5%probability of exploitation in next 30 days
High Risk0.00%
Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk
38.4%56.3%74.2%92.2%81.6%48.5%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐹github.com/juju/juju

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/juju/jujuall versions0.0.0-20170524231039-0417178a3c28go get github.com/juju/juju@v0.0.0-20170524231039-0417178a3c28

Affected Products

1 product · 38 configurations
Application
jujucanonical
≤ 1.25.12
7 versions
2.0.02.0.12.0.22.0.32.1.02.1.12.1.2
Exploits & PoCs
3

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-44023locallinux✓ Verified

Juju-run Agent - Privilege Escalation (Metasploit)

by Metasploit · Feb 12, 2018

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/juju/juju, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/juju/juju to 0.0.0-20170524231039-0417178a3c28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-9232 is resolved across your whole dependency graph.

  3. Workarounds

    Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2017-9232 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2017-9232: juju PrivEsc — Fix Available