# CVE-2020-11549: Hardcoded credentials in n/a

> Hardcoded root credentials allow remote code execution with root privileges on NETGEAR Orbi Business WiFi devices.

- **Severity:** High 8.3 (`CVSS:3.0/AC:H/AV:A/A:H/C:H/I:H/PR:N/S:C/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-v59x-rqxr-74j5

## What is CVE-2020-11549?

CVE-2020-11549 is a high-severity vulnerability in n/a, published on 18 May 2020. 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 NETGEAR Orbi Tri-Band Business WiFi Add-on Satellite (SRS60) AC3000 V2.5.1.106, Outdoor Satellite (RBS50Y) V2.5.1.106, and Pro Tri-Band Business WiFi Router (SRR60) AC3000 V2.5.1.106. The root account has the same password as the Web-admin component. Thus, by exploiting CVE-2020-11551, it is possible to achieve remote code execution with root privileges on the embedded Linux system.

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

## Which versions are affected by CVE-2020-11549?

It affects 3 products.


Products: Netgear Rbs50y Firmware, Netgear Srr60 Firmware, Netgear Srs60 Firmware.

## How do I fix CVE-2020-11549?

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

## Is CVE-2020-11549 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-11551](https://insights.sbomify.com/CVE-2020-11551/): Missing authorization in n/a (critical 9.6)
- [CVE-2021-45645](https://insights.sbomify.com/CVE-2021-45645/): Misconfiguration in n/a (high 8.2)
- [CVE-2020-11550](https://insights.sbomify.com/CVE-2020-11550/): Information disclosure in n/a (high 7.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-11549 and fix it if it is affected.

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

## Sources

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

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