← Back
CVE-2025-68152
medium
CVSS 4.9
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**incorrect authorization** (CWE-863) exists in github.com/juju/juju.
📍 Affected scope
github.com/juju/juju — .
🔥 Severity
Severity: Medium (CVSS 4.9/10). Confidential information can be exposed externally
🔧 How to fix
Update to **0.0.0-20250623030540-c91a1f404695**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/juju/juju to 0.0.0-20250623030540-c91a1f404695ステージング環境で 0.0.0-20250623030540-c91a1f404695 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Go
github.com/juju/juju
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.0.0-20250623030540-c91a1f404695"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-68152
- package https://github.com/juju/juju
- web https://github.com/juju/juju/commit/22cdcf6b54c2f371822e1c203d4f341be6c9589e
- web https://github.com/juju/juju/commit/c91a1f4046956874ba77c8b398aecee3d61a2dc3
- web https://github.com/juju/juju/security/advisories/GHSA-j6f6-jp3p-53mw