Vulnerability in github.com/juju/juju (CVE-2024-6984)
Summary
Vulnerability in github.com/juju/juju (CVE-2024-6984). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 3.5.3 or later.
Original description
The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2024-6984 has been found in github.com/juju/juju.
Successful exploitation can lead to full system takeover.
What to do: upgrade github.com/juju/juju to 3.5.3 or later.
If unsure, ask your IT team or search "github.com/juju/juju CVE-2024-6984" on the vendor's site.
CVE-2024-6984 (github.com/juju/juju) — CWE-209
Attack vector: local / no user interaction
Patched: 3.5.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-209) exists in github.com/juju/juju.
Check the vendor advisory for the affected versions of github.com/juju/juju.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 3.5.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/juju/juju' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/juju/juju' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/juju/jujuを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/juju/juju to 3.5.3ステージング環境で 3.5.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory cve.org
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web pkg.go.dev
- web pkg.go.dev