# CVE-2022-36524: Hardcoded credentials in n/a

> Attackers can gain unauthorized access to D-Link GO-RT-AC750 routers using static default credentials found in the telnet startup script.

- **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:** 15 Aug 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-rppv-f6hg-5x77

## What is CVE-2022-36524?

CVE-2022-36524 is a high-severity vulnerability in n/a, published on 15 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

D-Link GO-RT-AC750 GORTAC750_revA_v101b03 & GO-RT-AC750_revB_FWv200b02 is vulnerable to Static Default Credentials via /etc/init0.d/S80telnetd.sh.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Dlink Go-Rt-Ac750 Firmware.

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

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

## Is CVE-2022-36524 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-37055](https://insights.sbomify.com/CVE-2022-37055/): D-Link Routers Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-27683](https://insights.sbomify.com/CVE-2024-27683/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-22852](https://insights.sbomify.com/CVE-2024-22852/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-22853](https://insights.sbomify.com/CVE-2024-22853/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2024-22916](https://insights.sbomify.com/CVE-2024-22916/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-36524 is a high-severity vulnerability in n/a, published on 15 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-36524 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-36524/ (Markdown: https://insights.sbomify.com/CVE-2022-36524/index.md)
```

## Sources

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

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