# CVE-2021-36708: Auth bypass in n/a

> An attacker can reset the administrative password via the login.cgi binary, gaining unauthorized access to the router's management interface.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-58pm-rqvv-hw49

## What is CVE-2021-36708?

CVE-2021-36708 is a high-severity authentication bypass vulnerability in n/a, published on 6 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In ProLink PRC2402M V1.0.18 and older, the set_sys_init function in the login.cgi binary allows an attacker to reset the password to the administrative interface of the router.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password)

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

It affects 1 product.


Products: Prolink Prc2402m Firmware.

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

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

## Is CVE-2021-36708 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-36705](https://insights.sbomify.com/CVE-2021-36705/): Command injection in n/a (critical 9.8)
- [CVE-2021-36706](https://insights.sbomify.com/CVE-2021-36706/): Command injection in n/a (critical 9.8)
- [CVE-2021-36707](https://insights.sbomify.com/CVE-2021-36707/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-36708 is a high-severity authentication bypass vulnerability in n/a, published on 6 Aug 2021. 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-2021-36708 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-36708/ (Markdown: https://insights.sbomify.com/CVE-2021-36708/index.md)
```

## Sources

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

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