# CVE-2019-7564: Missing authorization in n/a

> Unauthenticated attackers can change the WiFi password on Coship WM3300 routers by sending a specific POST request, bypassing authentication controls.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 7 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-7g2v-29mr-2f42

## What is CVE-2019-7564?

CVE-2019-7564 is a critical missing authorization vulnerability in n/a, published on 7 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on Shenzhen Coship WM3300 WiFi Router 5.0.0.55 devices. The password reset functionality of the Wireless SSID doesn't require any type of authentication. By making a POST request to the regx/wireless/wl_security_2G.asp URI, the attacker can change the password of the Wi-FI network.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2019-7564?

It affects 4 products.


Products: Coship Rt3050 Firmware, Coship Rt3052 Firmware, Coship Rt7620 Firmware, Coship Wm3300 Firmware.

## How do I fix CVE-2019-7564?

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

## Is CVE-2019-7564 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-6441](https://insights.sbomify.com/CVE-2019-6441/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-7564 and fix it if it is affected.

What it is: CVE-2019-7564 is a critical missing authorization vulnerability in n/a, published on 7 May 2019. 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-2019-7564 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-2019-7564/ (Markdown: https://insights.sbomify.com/CVE-2019-7564/index.md)
```

## Sources

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

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