Skip to content

Duplicate Advisory: Juju makes Use of Weak Credentials

High severity GitHub Reviewed Published Oct 2, 2024 to the GitHub Advisory Database • Updated Oct 2, 2024
Withdrawn This advisory was withdrawn on Oct 2, 2024

Package

gomod github.com/juju/juju (Go)

Affected versions

< 0.0.0-20241001032836-2af7bd8e310b

Patched versions

0.0.0-20241001032836-2af7bd8e310b

Description

Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-mh98-763h-m9v4. This link is maintained to preserve external references.

Original 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.

References

Published by the National Vulnerability Database Oct 2, 2024
Published to the GitHub Advisory Database Oct 2, 2024
Reviewed Oct 2, 2024
Withdrawn Oct 2, 2024
Last updated Oct 2, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H

Weaknesses

CVE ID

No known CVE

GHSA ID

GHSA-phh4-3hmm-24rx

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.