# CVE-2017-9232: Juju uses a UNIX domain socket without setting appropriate permissions

> Local users can escalate privileges to root due to insecure permissions on Juju's UNIX domain socket.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-j3hp-pv6v-rgrx, GO-2025-3639, UBUNTU-CVE-2017-9232, USN-3300-1

## What is CVE-2017-9232?

CVE-2017-9232 is a critical vulnerability in n/a, published on 28 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2017-9232?

3 open source packages ship an affected version, including github.com/juju/juju. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/juju/juju` | Go | All versions | 0.0.0-20170524231039-0417178a3c28 |
| `github.com/juju/juju` | Go | All versions | 0.0.0-20170524231039-0417178a3c28 |
| `github.com/juju/juju` | Go | All versions | 0.0.0-20170524231039-0417178a3c28 |

Products: Canonical Juju.

## How do I fix CVE-2017-9232?

Upgrade github.com/juju/juju to 0.0.0-20170524231039-0417178a3c28 or later.

## Is CVE-2017-9232 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-9232 exists.

Public exploit code:

- Juju-run Agent Privilege Escalation (metasploit)
- Juju-run Agent - Privilege Escalation (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2026-4370](https://insights.sbomify.com/CVE-2026-4370/): Improper TLS Client/Server authentication and certificate verification on Database Cluster (critical 10.0)
- [CVE-2026-5412](https://insights.sbomify.com/CVE-2026-5412/): Juju CloudSpec API could leak senstive information (critical 9.9)
- [CVE-2026-32693](https://insights.sbomify.com/CVE-2026-32693/): Unauthorized access to Kubernetes secrets in Juju (high 8.8)
- [CVE-2025-0928](https://insights.sbomify.com/CVE-2025-0928/): Arbitrary executable upload via authenticated endpoint (high 8.8)
- [CVE-2025-53513](https://insights.sbomify.com/CVE-2025-53513/): Zip slip vulnerability in Juju (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-9232 and fix it if it is affected.

What it is: CVE-2017-9232 is a critical vulnerability in n/a, published on 28 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-9232 exists.

Affected packages and fixed versions:
- github.com/juju/juju (Go): affected all versions; fixed in 0.0.0-20170524231039-0417178a3c28
- github.com/juju/juju (Go): affected all versions; fixed in 0.0.0-20170524231039-0417178a3c28
- github.com/juju/juju (Go): affected all versions; fixed in 0.0.0-20170524231039-0417178a3c28

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-9232/ (Markdown: https://insights.sbomify.com/CVE-2017-9232/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-9232
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-9232
- OSV: https://osv.dev/vulnerability/CVE-2017-9232

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-9232/
Summaries are generated and may contain mistakes; the official description above is the record.