Path Traversal in github.com/juju/juju (CVE-2025-53513)

Summary

Path traversal in github.com/juju/juju (CVE-2025-53513). Successful exploitation can lead to full system takeover. Exploitable via PUT /model-34bb5ef0-5a3e-41d7-873c-2f884adf606d/charms/pathtw-5c9f25c. Mitigation: upgrade to 0.0.0-20250619215741-6356e984b82a or later.

Original description

The description as published by the source.

Impact

Any user with a Juju account on a controller can upload a charm to the /charms endpoint.
No specific permissions are required - it's just sufficient for the user to exist in the controller user database.
A charm which exploits the zip slip vulnerability may be used to allow such a user to get access to a machine running a unit using the affected charm.

Details

A controller exposes three charm-related HTTP API endpoints, as follows:

PUT/GET https://:17070/model-/charms/-
POST/GET https://:17070/model-/charms
GET https://:17070/charms

These endpoints require Basic HTTP authentication credentials and will accept any valid user within the context of the controller. A user that has no specific permission or access granted can call all of these APIs.

To reproduce:

juju bootstrap
juju add-user testuser
juju change-user-password testuser

Download the ZIP file of an arbitrary charm eg https://github.com/juju/hello-juju-charm

Download and install the following tool: https://github.com/usdAG/slipit

Run the following command to generate a new SSH key pair: ssh-keygen

Copy the contents of the newly created public key into a file called authorized_keys

Run the following command to inject the malicious path into the ZIP file:

slipit hello.zip authorized_keys --separator ../../../../../../home/
ubuntu/.ssh/

Send the PUT request below to a model on the target con…

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-2025-53513 has been found in github.com/juju/juju.
Attackers can target a specific entry point like PUT /model-34bb5ef0-5a3e-41d7-873c-2f884adf606d/charms/pathtw-5c9f25c over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: upgrade github.com/juju/juju to 0.0.0-20250619215741-6356e984b82a or later.
If unsure, ask your IT team or search "github.com/juju/juju CVE-2025-53513" on the vendor's site.

CVE-2025-53513 (github.com/juju/juju) — CWE-22
Attack vector: remote (network-reachable) / no user interaction
Attack surface: PUT /model-34bb5ef0-5a3e-41d7-873c-2f884adf606d/charms/pathtw-5c9f25c / Authorization header / authorized_keys
Patched: 0.0.0-20250619215741-6356e984b82a — apply immediately
Workaround: There are no known workarounds.
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

Path traversal (CWE-22) exists in github.com/juju/juju. Attackers reach the vulnerable code path via PUT /model-34bb5ef0-5a3e-41d7-873c-2f884adf606d/charms/pathtw-5c9f25c.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/juju/juju. Attack surface: PUT /model-34bb5ef0-5a3e-41d7-873c-2f884adf606d/charms/pathtw-5c9f25c / Authorization header / authorized_keys.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 0.0.0-20250619215741-6356e984b82a.

🛡️ Workaround

Workaround: There are no known workarounds.

🔍 Detection

Search webserver/proxy logs for unusual PUT /model-34bb5ef0-5a3e-41d7-873c-2f884adf606d/charms/pathtw-5c9f25c requests with malformed payloads or SQL meta-characters. 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

1
Identify 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 し、稼働しているサービス・バージョンを把握する。
2
Hunt for indicators of compromise detect
```
grep 'PUT /model-34bb5ef0-5a3e-41d7-873c-2f884adf606d/charms/pathtw-5c9f25c' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'
```
アクセスログで PUT /model-34bb5ef0-5a3e-41d7-873c-2f884adf606d/charms/pathtw-5c9f25c への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
3
Apply temporary workaround mitigate
```
There are no known workarounds.
```
パッチが適用されるまでの応急処置として、There are no known workarounds. を実施。回避策の副作用 (機能低下) を確認した上で。
4
Apply patch patch
```
Upgrade github.com/juju/juju to 0.0.0-20250619215741-6356e984b82a
```
ステージング環境で 0.0.0-20250619215741-6356e984b82a に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
5
Post-deployment verification verify
```
Replay attack against PUT /model-34bb5ef0-5a3e-41d7-873c-2f884adf606d/charms/pathtw-5c9f25c on staging to confirm patch closes the vector
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

Go github.com/juju/juju

[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.0.0-20250619215741-6356e984b82a"}]}]