# CVE-2024-57357: Command injection in n/a

> A remote attacker can execute arbitrary code on TP-Link Wi-Fi extenders via command injection in the devpwd parameter.

- **Severity:** High 8.0 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Feb 2025
- **Updated:** 7 Feb 2025
- **Also known as:** GHSA-c9g2-8c6g-4whg

## What is CVE-2024-57357?

CVE-2024-57357 is a high-severity command injection vulnerability in n/a, published on 7 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue in TPLINK TL-WPA 8630 TL-WPA8630(US)_V2_2.0.4 Build 20230427 allows a remote attacker to execute arbitrary code via function sub_4256CC, which allows command injection by injecting 'devpwd'.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2024-57357?

It affects 1 product.


Products: Tp-Link Tl-Wpa8630 Firmware.

## How do I fix CVE-2024-57357?

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

## Is CVE-2024-57357 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-57357 and fix it if it is affected.

What it is: CVE-2024-57357 is a high-severity command injection vulnerability in n/a, published on 7 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-57357 exists.

Affected product: n/a. 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-2024-57357/ (Markdown: https://insights.sbomify.com/CVE-2024-57357/index.md)
```

## Sources

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

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