Cyber Resilience

CVE-2024-7558

Crypto Weakness in Canonical Juju ≤ 2.9.51

Public PoCCrypto Weakness
Published
02 October 2024
Modified
26 August 2025
Patch / advisory
View advisory
CVSS Score v3.1 8.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H
EPSS Score 0.0050 40th percentile
Risk Priority 60 floored blend · peak EPSS

Summary

CVE-2024-7558 is a high-severity PRNG (CWE-337) vulnerability in Canonical Juju. Its CVSS base score is 8.7 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Default Accounts (T1078.001); ranked at the 40th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to IA-5 (Authenticator Management) and SA-11 (Developer Testing and Evaluation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A04:2025 Cryptographic FailuresA07:2025 Authentication Failures

EU & UK References

Vulnerability Data

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…

more

unprivileged user access to the same information and tools as the Juju charm.

CWE(s)
CWE-337CWE-340CWE-1391CWE-330CWE-335

Related Threats

MITRE ATT&CK Enterprise Techniques

T1078.001 Default Accounts Stealth
Adversaries may obtain and abuse credentials of a default account as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
attack.mitre.org →
T1110 Brute Force Credential Access
Adversaries may use brute force techniques to gain access to accounts when passwords are unknown or when password hashes are obtained.
attack.mitre.org →
T1110.001 Password Guessing Credential Access
Adversaries with no prior knowledge of legitimate credentials within the system or environment may guess passwords to attempt access to accounts.
attack.mitre.org →
T1078 Valid Accounts Stealth
Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
attack.mitre.org →
T1110.002 Password Cracking Credential Access
Adversaries may use password cracking to attempt to recover usable credentials, such as plaintext passwords, when credential material such as password hashes are obtained.
attack.mitre.org →
T1600 Weaken Encryption Defense Impairment
Adversaries may compromise a network device’s encryption capability in order to bypass encryption that would otherwise protect data communications.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-32694Same product: Canonical Juju
CVE-2026-4370Same product: Canonical Juju
CVE-2023-0092Same product: Canonical Juju
CVE-2025-53513Same product: Canonical Juju
CVE-2026-32693Same product: Canonical Juju
CVE-2025-68153Same product: Canonical Juju
CVE-2025-68152Same product: Canonical Juju
CVE-2026-32692Same product: Canonical Juju
CVE-2026-5412Same product: Canonical Juju
CVE-2025-0928Same product: Canonical Juju

Affected Assets

canonical
juju
≤ 2.9.51 · 3.1.0 — 3.1.10 · 3.2.0 — 3.2.4

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 26 hardening rules · 5 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V6.2.2
  • V7.2.3
  • V6.3.1
  • V6.3.2

Mitigating Controls (NIST 800-53 r5) AI

IA-5 Authenticator Management good match

IA-5 directly requires management of authenticator strength, distribution, and replacement, stopping default or guessable credentials from being introduced or used.

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover use of predictable seeds such as time or PID.

SC-12 Cryptographic Key Establishment and Management good match

Proper cryptographic key establishment and management includes using unpredictable seeds for PRNGs that feed key generation.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles can require cryptographically secure PRNGs seeded from high-entropy sources.

SC-13 Cryptographic Protection partial match

SC-13 requires selection and implementation of approved cryptographic algorithms and methods, which inherently depend on and enforce sufficiently random values.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-01 mostly match
prevents

PR.AA-01's credential issuance and key-management processes directly block most weak/default credential usage, yet leave hard-coded or product-design instances of CWE-1391 only partially addressed.

PR.AA-03 mostly match
prevents

Password-strength policies in PR.AA-03 directly block weak authenticators, but the control leaves hard-coded/default credentials largely unaddressed.

PR.PS-01 mostly match
prevents

Hardened baselines and default-setting reviews directly block default/hard-coded creds (mostly), yet leave algorithmic guessing, reuse, and non-config sources of weak credentials untouched (partial).

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require cryptographically secure PRNG seeding, preventing predictable seeds while the control addresses many additional weaknesses.

PR.AT-01 partial match
prevents

Training raises password-hygiene awareness and can therefore reduce some weak-credential mistakes, yet supplies no enforcement mechanism and leaves the dominant technical sources of CWE-1391 untouched.

PR.AT-02 partial match
prevents

Role-based awareness training can reduce the chance developers or admins introduce weak credentials but supplies no enforcement or verification, leaving the bulk of CWE-1391 risk untouched.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.5.17 Authentication information full match
degrades

Directly requires secure generation, distribution and storage of authentication credentials, eliminating default/hard-coded weak passwords.

A.8.5 Secure authentication full match
degrades

Mandates secure authentication mechanisms that preclude use of weak or default credentials.

A.8.24 Use of cryptography mostly match
prevents

Cryptographic controls require use of approved, sufficiently random algorithms and key-generation methods, directly mitigating predictable number/identifier weaknesses.

A.8.28 Secure coding mostly match
prevents

Secure-coding rules can prohibit hard-coded passwords, yet coverage depends on specific coding standards adopted.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect and prevent use of weak or predictable PRNG seeds.

A.8.9 Configuration management mostly match
prevents

Enforces secure baseline configurations that should remove default credentials, yet does not guarantee credential strength.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (7 rules)
  • V-248524 OL 8 must implement NIST FIPS-validated cryptography for the following: To provision digital signatures, to generate cryptographic hashes, and to protect data requiring data-at-rest protections in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. prevents CWE-340
  • V-248563 The OL 8 SSH server must be configured to use strong entropy. prevents CWE-330, CWE-335, CWE-337
  • V-248599 OL 8 must enable the hardware random number generator entropy gatherer service. prevents CWE-330, CWE-337
Oracle Linux 9 (1 rule)
  • V-271511 OL 9 must enable the hardware random number generator entropy gatherer service. prevents CWE-330
RHEL 7 (2 rules)
  • V-204497 The Red Hat Enterprise Linux operating system must implement NIST FIPS-validated cryptography for the following: to provision digital signatures, to generate cryptographic hashes, and to protect data requiring data-at-rest protections in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. prevents CWE-340
  • V-204442 The Red Hat Enterprise Linux operating system must not have the rsh-server package installed. prevents CWE-1391
RHEL 8 (4 rules)
  • V-244527 RHEL 8 must have the packages required to use the hardware random number generator entropy gatherer service. prevents CWE-330, CWE-340
  • V-230253 RHEL 8 must ensure the SSH server uses strong entropy. prevents CWE-330, CWE-335
  • V-230285 RHEL 8 must enable the hardware random number generator entropy gatherer service. prevents CWE-330
RHEL 9 (1 rule)
  • V-257782 RHEL 9 must enable the hardware random number generator entropy gatherer service. prevents CWE-330

References