JUJU_CONTEXT_ID is a predictable authentication secret

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.2 · CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:H/SA:H · score source

EPSS

• CVE-2024-7558: 0.50% estimated exploitation activity in the next 30 days; percentile 43.05 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

JUJUCONTEXTID is the authentication measure on the unit hook tool abstract domain socket. It looks like JUJUCONTEXTID=appname/0-update-status-6073989428498739633. This value looks fairly unpredictable, but due to the random source used, it is highly predictable. JUJUCONTEXTID has the following components: - the application name - the unit number - the hook being currently run - a uint63 decimal number On a system the application name and unit number can be deduced by reading the structure of the filesystem. The current hook being run is not easily deduce-able, but is a limited set of possible values, so one could try them all. Finally the random number, this is generated from a non cryptographically secure random source. Specifically the random number generator built into the go standard library, using the current unix time in seconds (at startup) as the seed. There is no rate limiting on the abstract domain socket, the only limiting factor is time (window of time the hook is run)…

Published by the source

3 Oct 2024, 16:49 UTC

Last modified by the source

9 Oct 2024, 22:48 UTC

Source last checked

26 Oct 2026, 15:05 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-mh98-763h-m9v4

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-7558

Advisory: JUJU_CONTEXT_ID is a predictable authentication secret
IDs: CVE-2024-7558, GHSA-mh98-763h-m9v4
Record: https://patchnext.com/advisories/cve-2024-7558 (revision 1, source checked 26 Oct 2026, 15:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/juju/juju 0.0.0-20240826044107-ecd7e2d0e986. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/juju/juju: affected < 0.0.0-20240826044107-ecd7e2d0e986; fixed in 0.0.0-20240826044107-ecd7e2d0e986

## Suggested inspection (read-only)
- Go github.com/juju/juju: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/juju/juju.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-mh98-763h-m9v4 (GitHub-reviewed advisory GHSA-mh98-763h-m9v4 lists affected ranges: Go github.com/juju/juju >=0 <0.0.0-20240826044107-ecd7e2d0e986)

Commands are suggestions: review each one before running it.