Vulnerable juju introspection abstract UNIX domain socket
CVE-2024-8038GHSA-xwgj-vpm9-q2rq
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/juju/juju 0.0.0-20240829052008-43f0fc59790d), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
- Affected
- < 0.0.0-20240829052008-43f0fc59790d
- Fixed in
- 0.0.0-20240829052008-43f0fc59790d
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-xwgj-vpm9-q2rq lists affected ranges: Go github.com/juju/juju >=0 <0.0.0-20240829052008-43f0fc59790d
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- 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-8038: 0.21% estimated exploitation activity in the next 30 days; percentile 11.51 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Impact An abstract UNIX domain socket responsible for introspection is available without authentication locally to any user with access to the network namespace where the local juju agent is running. On a juju controller agent, denial of service can be performed by using the /leases/revoke endpoint. Revoking leases in juju can cause availability issues. On a juju machine agent that is hosting units, disabling the unit component can be performed using the /units endpoint with a "stop" action. Patches Patch: https://github.com/juju/juju/commit/43f0fc59790d220a457d4d305f484f62be556d3b Patched in: - 3.5.4 - 3.4.6 - 3.3.7 - 3.1.10 - 2.9.51 Workarounds No workaround. References https://github.com/juju/juju/blob/725800953aaa29dbeda4f806097bf838e61644dd/worker/introspection/worker.go#L125
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-xwgj-vpm9-q2rq
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2024-8038 Advisory: Vulnerable juju introspection abstract UNIX domain socket IDs: CVE-2024-8038, GHSA-xwgj-vpm9-q2rq Record: https://patchnext.com/advisories/cve-2024-8038 (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-20240829052008-43f0fc59790d. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/juju/juju: affected < 0.0.0-20240829052008-43f0fc59790d; fixed in 0.0.0-20240829052008-43f0fc59790d ## 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-xwgj-vpm9-q2rq (GitHub-reviewed advisory GHSA-xwgj-vpm9-q2rq lists affected ranges: Go github.com/juju/juju >=0 <0.0.0-20240829052008-43f0fc59790d) Commands are suggestions: review each one before running it.
Loading voting…