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

> Attackers can execute arbitrary code on D-Link DIR-890L routers due to hardcoded credentials in the Wake-On-Lan configuration parameter.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jun 2022
- **Updated:** 28 Oct 2024
- **Also known as:** GHSA-5cg6-qf6g-ch83

## What is CVE-2022-29778?

CVE-2022-29778 is a high-severity vulnerability in n/a, published on 3 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

D-Link DIR-890L 1.20b01 allows attackers to execute arbitrary code due to the hardcoded option Wake-On-Lan for the parameter 'descriptor' at SetVirtualServerSettings.php

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

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

It affects 1 product.


Products: Dlink Dir-890l Firmware.

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

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

## Is CVE-2022-29778 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-29778 exists.

Public exploit code:

- Analysis and PoC for D-Link DIR-890L RCE (CVE-2022-29778) (github_poc): https://github.com/TyeYeah/DIR-890L-1.20-RCE

## Other vulnerabilities in n/a

- [CVE-2022-30521](https://insights.sbomify.com/CVE-2022-30521/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-30063](https://insights.sbomify.com/CVE-2023-30063/): Auth bypass in n/a (high 7.5)
- [CVE-2025-8231](https://insights.sbomify.com/CVE-2025-8231/): D-Link DIR-890L UART Port rgbin hard-coded credentials (high 7.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-29778 is a high-severity vulnerability in n/a, published on 3 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-29778 exists.

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-29778/ (Markdown: https://insights.sbomify.com/CVE-2022-29778/index.md)
```

## Sources

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

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