# CVE-2024-10193: WAVLINK WN530H4/WN530HG4/WN572HG3 internet.cgi ping_ddns command injection

> Remote attackers can execute arbitrary commands on WAVLINK routers via the ping_ddns function in internet.cgi due to improper input validation.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Oct 2024
- **Updated:** 21 Oct 2024
- **Also known as:** GHSA-v3v3-w3mf-mjc9

## What is CVE-2024-10193?

CVE-2024-10193 is a medium-severity command injection vulnerability in WAVLINK WN530H4, published on 20 Oct 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability was found in WAVLINK WN530H4, WN530HG4 and WN572HG3 up to 20221028 and classified as critical. This issue affects the function ping_ddns of the file internet.cgi. The manipulation of the argument DDNS leads to command injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 3 products.


Products: Wavlink Wn530h4 Firmware, Wavlink Wn530hg4 Firmware, Wavlink Wn572hg3 Firmware.

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

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

## Is CVE-2024-10193 being exploited?

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

## Other vulnerabilities in WAVLINK WN530H4

- [CVE-2022-35519](https://insights.sbomify.com/CVE-2022-35519/): Command injection in n/a (critical 9.8)
- [CVE-2022-35520](https://insights.sbomify.com/CVE-2022-35520/): Command injection in n/a (critical 9.8)
- [CVE-2022-35521](https://insights.sbomify.com/CVE-2022-35521/): Command injection in n/a (critical 9.8)
- [CVE-2022-35522](https://insights.sbomify.com/CVE-2022-35522/): Command injection in n/a (critical 9.8)
- [CVE-2022-35523](https://insights.sbomify.com/CVE-2022-35523/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-10193 is a medium-severity command injection vulnerability in WAVLINK WN530H4, published on 20 Oct 2024. 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-2024-10193 exists.

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

## Sources

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

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