# CVE-2023-30063: Auth bypass in n/a

> Attackers can bypass authentication on D-Link DIR-890L routers, gaining unauthorized access to the device 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:** 1 May 2023
- **Updated:** 30 Jan 2025
- **Also known as:** GHSA-vf3v-3g7g-88rm

## What is CVE-2023-30063?

CVE-2023-30063 is a high-severity authentication bypass vulnerability in n/a, published on 1 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

D-Link DIR-890L FW1.10 A1 is vulnerable to Authentication bypass.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2023-30063?

It affects 1 product.


Products: Dlink Dir-890l Firmware.

## How do I fix CVE-2023-30063?

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

## Is CVE-2023-30063 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-30521](https://insights.sbomify.com/CVE-2022-30521/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-29778](https://insights.sbomify.com/CVE-2022-29778/): Hardcoded credentials in n/a (high 8.8)
- [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-2023-30063 and fix it if it is affected.

What it is: CVE-2023-30063 is a high-severity authentication bypass vulnerability in n/a, published on 1 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-30063 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-2023-30063/ (Markdown: https://insights.sbomify.com/CVE-2023-30063/index.md)
```

## Sources

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

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