CVE-2025-53513
Juju zip slip vulnerability via authenticated endpoint
Overview
Description
The /charms endpoint on a Juju controller lacked sufficient authorization checks, allowing any user with an account on the controller to upload a charm. Uploading a malicious charm that exploits a Zip Slip vulnerability could allow an attacker to gain access to a machine running a unit through the affected charm.
Source: OX vulnerability database
Severity
6.5 · MEDIUM
CVSS 3.1 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Weakness: CWE-24, CWE-22
Affected packages · 1
| Ecosystem | Package | Vulnerable | Fixed in |
|---|---|---|---|
| Go | github.com/juju/juju | <0.0.0-20250619215741-6356e984b82a | 0.0.0-20250619215741-6356e984b82a |
Open a package to see all its vulnerabilities.
Operating systems · 1 fix
openSUSE 1 release · 1 package
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Tumbleweed | govulncheck-vulndb | 0.0.20250730T213748-1.1 | openSUSE-SU-2025:15405-1 |
References
- drive.google.com https://drive.google.com/file/d/1pHRNiaA8LyMVJYwIyTqelsqJ9FmImDf0/view
- github.com https://github.com/juju/juju
- github.com https://github.com/juju/juju/blob/3.6/apiserver/apiserver.go#L754
- github.com https://github.com/juju/juju/blob/3.6/apiserver/apiserver.go#L897
- github.com https://github.com/juju/juju/blob/3.6/apiserver/apiserver.go#L990
- github.com https://github.com/juju/juju/commit/6356e984b82a4a7b9771ff5e51e297ad62f3b405
- github.com https://github.com/juju/juju/commit/ff39557a137c0e95d4cd3553b0f19c859c6f5d8e
- github.com https://github.com/juju/juju/security/advisories/GHSA-24ch-w38v-xmh8
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2025-53513
- pkg.go.dev https://pkg.go.dev/vuln/GO-2025-3804
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.