Skip to content

Juju's unprivileged user running on charm node can leak any secret or relation data accessible to the local charm

High severity GitHub Reviewed Published Aug 5, 2024 in juju/juju • Updated Aug 7, 2024

Package

gomod github.com/juju/juju (Go)

Affected versions

< 2.9.50
>= 3.0.0, < 3.1.9
>= 3.2.0, < 3.3.6
>= 3.4.0, < 3.4.5
>= 3.5.0, < 3.5.3

Patched versions

2.9.50
3.1.9
3.3.6
3.4.5
3.5.3

Description

An issue was discovered in Juju that resulted in the leak of the sensitive context ID, which allows a local unprivileged attacker to access other sensitive data or relation accessible to the local charm. A potential exploit where a user can run a bash loop attempting to execute hook tools. If running while another hook is executing, we log an error with the context ID, making it possible for the user to then use that ID in a following call successfully. This means an unprivileged user can access anything available via a hook tool such as config, relation data and secrets.

References

@anvial anvial published to juju/juju Aug 5, 2024
Published to the GitHub Advisory Database Aug 5, 2024
Reviewed Aug 5, 2024
Last updated Aug 7, 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
High
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:H/I:H/A:H

Weaknesses

CVE ID

No known CVE

GHSA ID

GHSA-6vjm-54vp-mxhx

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.