# CVE-2025-3577: Path traversal in AMG1302-T10B firmware

> An authenticated administrator can access restricted directories on Zyxel AMG1302-T10B devices via crafted HTTP requests.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Apr 2025
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-2jx2-x46f-wj52

## What is CVE-2025-3577?

CVE-2025-3577 is a medium-severity path traversal vulnerability in Zyxel AMG1302-T10B firmware, published on 22 Apr 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

**UNSUPPORTED WHEN ASSIGNED** A path traversal vulnerability in the web management interface of the Zyxel AMG1302-T10B firmware version 2.00(AAJC.16)C0 could allow an authenticated attacker with administrator privileges to access restricted directories by sending a crafted HTTP request to an affected device.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-3577?

It affects 1 product.


Products: Zyxel Amg1302-T10b Firmware.

## How do I fix CVE-2025-3577?

No fix has been published for CVE-2025-3577 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-3577 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3577 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3577 and fix it if it is affected.

What it is: CVE-2025-3577 is a medium-severity path traversal vulnerability in Zyxel AMG1302-T10B firmware, published on 22 Apr 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3577 exists.

Affected product: Zyxel AMG1302-T10B firmware. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-3577/ (Markdown: https://insights.sbomify.com/CVE-2025-3577/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-3577
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-3577
- OSV: https://osv.dev/vulnerability/CVE-2025-3577

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-3577/
Summaries are generated and may contain mistakes; the official description above is the record.