# CVE-2024-7558: JUJU_CONTEXT_ID is a predictable authentication secret

> An unprivileged user can guess a predictable authentication secret to access Juju charm tools and information, leading to privilege escalation.

- **Severity:** High 8.7 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Oct 2024
- **Updated:** 2 Oct 2024
- **Also known as:** GHSA-mh98-763h-m9v4, GO-2024-3173

## What is CVE-2024-7558?

CVE-2024-7558 is a high-severity vulnerability in Canonical Ltd. Juju, published on 2 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

JUJU_CONTEXT_ID is a predictable authentication secret. On a Juju machine (non-Kubernetes) or Juju charm container (on Kubernetes), an unprivileged user in the same network namespace can connect to an abstract domain socket and guess the JUJU_CONTEXT_ID value. This gives the unprivileged user access to the same information and tools as the Juju charm.

Weakness: CWE-335 (Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG)), CWE-330 (Use of Insufficiently Random Values), CWE-340 (Generation of Predictable Numbers or Identifiers), CWE-337 (Predictable Seed in Pseudo-Random Number Generator (PRNG)), CWE-1391 (Use of Weak Credentials)

## Which versions are affected by CVE-2024-7558?

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-20240826044107-ecd7e2d0e986 |
| `github.com/juju/juju` | Go | All versions | 0.0.0-20240826044107-ecd7e2d0e986 |
| `github.com/juju/juju` | Go | All versions | 0.0.0-20240826044107-ecd7e2d0e986 |

Products: Canonical Juju.

## How do I fix CVE-2024-7558?

Upgrade github.com/juju/juju to 0.0.0-20240826044107-ecd7e2d0e986 or later.

## Is CVE-2024-7558 being exploited?

There is no known exploitation of CVE-2024-7558 in the wild and no public exploit code.

## Other vulnerabilities in Canonical Ltd. Juju

- [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-2017-9232](https://insights.sbomify.com/CVE-2017-9232/): Juju uses a UNIX domain socket without setting appropriate permissions (critical 9.8)
- [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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-7558 and fix it if it is affected.

What it is: CVE-2024-7558 is a high-severity vulnerability in Canonical Ltd. Juju, published on 2 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-7558 in the wild and no public exploit code.

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

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-2024-7558/ (Markdown: https://insights.sbomify.com/CVE-2024-7558/index.md)
```

## Sources

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

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