# CVE-2022-35521: Command injection in n/a

> Attackers can execute arbitrary commands on WAVLINK routers via unfiltered parameters in the firewall configuration interface.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-f8pr-3cr6-jp4c

## What is CVE-2022-35521?

CVE-2022-35521 is a critical command injection vulnerability in n/a, published on 9 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WAVLINK WN572HP3, WN533A8, WN530H4, WN535G3, WN531P3 firewall.cgi has no filtering on parameters: remoteManagementEnabled, blockPortScanEnabled, pingFrmWANFilterEnabled and blockSynFloodEnabled, which leads to command injection in page /man_security.shtml.

## Which versions are affected by CVE-2022-35521?

It affects 5 products.


Products: Wavlink Wn530h4 Firmware, Wavlink Wn531p3 Firmware, Wavlink Wn533a8 Firmware, Wavlink Wn535g3 Firmware, Wavlink Wn572hp3 Firmware.

## How do I fix CVE-2022-35521?

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

## Is CVE-2022-35521 being exploited?

There is no known exploitation of CVE-2022-35521 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [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-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)
- [CVE-2022-35524](https://insights.sbomify.com/CVE-2022-35524/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-35521 and fix it if it is affected.

What it is: CVE-2022-35521 is a critical command injection vulnerability in n/a, published on 9 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-35521 in the wild and no public exploit code.

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-2022-35521/ (Markdown: https://insights.sbomify.com/CVE-2022-35521/index.md)
```

## Sources

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

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