cve.bz

CVE-2024-7558 canonical juju: Use of Insufficiently Random Values

8.0 highExploit referenceEPSS 0.5%Fix available

High (8.0) in canonical juju. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/juju/juju 0.0.0-20240826044107-ecd7e2d0e986.

On this page
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.

Severity

CVSS 3.1

8.0 high
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 44th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2024-10-02. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-330 Use of Insufficiently Random Values
CWE-335 Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG)
CWE-337 Predictable Seed in Pseudo-Random Number Generator (PRNG)
CWE-340 Generation of Predictable Numbers or Identifiers
CWE-1391 Use of Weak Credentials
OWASP Top 10
A04:2025 Cryptographic Failures, A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-7558 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-7558?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-7558?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-7558 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Canonical Ltd. Jujufrom 3.5 before 3.5.4
Canonical Ltd. Jujufrom 3.4 before 3.4.6
Canonical Ltd. Jujufrom 3.3 before 3.3.7
Canonical Ltd. Jujufrom 3.1 before 3.1.10
Canonical Ltd. Jujufrom 2.9 before 2.9.51

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-mh98-763h-m9v4Gogithub.com/juju/juju<0.0.0-20240826044107-ecd7e2d0e9860.0.0-20240826044107-ecd7e2d0e986
GO-2024-3173Gogithub.com/juju/juju<0.0.0-20240826044107-ecd7e2d0e9860.0.0-20240826044107-ecd7e2d0e986

Linux distributions

DistributionReleasePackageFixed inAdvisory
SUSELinux Enterprise Module for Package Hub 15 SP5, Linux Enterprise Module for Package Hub 15 SP6govulncheck-vulndb0.0.20241030T212825-150000.1.9.1SUSE-SU-2024:3911-1
SUSEPackage Hub 12govulncheck-vulndb0.0.20241104T154416-5.1openSUSE-SU-2024:0350-1
openSUSELeap 15.5, Leap 15.6govulncheck-vulndb0.0.20241030T212825-150000.1.9.1SUSE-SU-2024:3911-1
openSUSETumbleweedgovulncheck-vulndb0.0.20241030T212825-1.1openSUSE-SU-2024:14447-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: SUSE · openSUSE.

Attack patterns (CAPEC)

  • CAPEC-59 Session Credential Falsification through Prediction Likelihood: High · Severity: High
  • CAPEC-112 Brute Force Severity: High
  • CAPEC-485 Signature Spoofing by Key Recreation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON