Authorization Flaw in github.com/juju/juju (CVE-2025-68152)
Summary
Vulnerability in github.com/juju/juju (CVE-2025-68152). Confidential information can be exposed externally. Mitigation: upgrade to 0.0.0-20250623030540-c91a1f404695 or later.
Original description
The description as published by the source.
Juju is an open source application orchestration engine that enables any application operation on any infrastructure at any scale through special operators called ‘charms’. From versions 2.9 to before 2.9.56 and 3.6 to before 3.6.19, it is possible that a compromised workload machine under a Juju controller can read any log file for any entity in any model at any level. This issue has been patched in versions 2.9.56 and 3.6.19.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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-2025-68152 has been found in github.com/juju/juju.
Confidential information can be exposed externally. CVSS score: 4.9/10.
What to do: upgrade github.com/juju/juju to 0.0.0-20250623030540-c91a1f404695 or later.
If unsure, ask your IT team or search "github.com/juju/juju CVE-2025-68152" on the vendor's site.
CVE-2025-68152 (github.com/juju/juju) — CWE-863 / CVSS v3 4.9
Attack vector: remote (network-reachable) / no user interaction
Patched: 0.0.0-20250623030540-c91a1f404695 — 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.
Incorrect authorization (CWE-863) exists in github.com/juju/juju.
Check the vendor advisory for the affected versions of github.com/juju/juju.
Severity: Medium (CVSS 4.9/10). Confidential information can be exposed externally.
Update to 0.0.0-20250623030540-c91a1f404695.
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 0.0.0-20250623030540-c91a1f404695ステージング環境で 0.0.0-20250623030540-c91a1f404695 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com