# CVE-2021-43284: Hardcoded credentials in n/a

> Attackers can gain root control of Victure WR1200 routers via SSH using the static default password, regardless of web interface changes.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/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:** 30 Nov 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-xr37-95p8-x373

## What is CVE-2021-43284?

CVE-2021-43284 is a high-severity vulnerability in n/a, published on 30 Nov 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered on Victure WR1200 devices through 1.0.3. The root SSH password never gets updated from its default value of admin. This enables an attacker to gain control of the device through SSH (regardless of whether the admin password was changed on the web interface).

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2021-43284?

It affects 1 product.


Products: Govicture Wr1200 Firmware.

## How do I fix CVE-2021-43284?

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

## Is CVE-2021-43284 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-43283](https://insights.sbomify.com/CVE-2021-43283/): Command injection in n/a (high 8.8)
- [CVE-2021-43282](https://insights.sbomify.com/CVE-2021-43282/): Hardcoded credentials in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-43284 and fix it if it is affected.

What it is: CVE-2021-43284 is a high-severity vulnerability in n/a, published on 30 Nov 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-43284 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-2021-43284/ (Markdown: https://insights.sbomify.com/CVE-2021-43284/index.md)
```

## Sources

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

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