# CVE-2023-32222: D-Link DSL-G256DG firmware version vBZ_1.00.27 Authentication Bypass

> Attackers can bypass authentication on the D-Link DSL-G256DG web management interface, gaining unauthorized access to the device.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jun 2023
- **Updated:** 27 Nov 2024
- **Also known as:** GHSA-49vq-hvrf-jhjw

## What is CVE-2023-32222?

CVE-2023-32222 is a critical authentication bypass vulnerability in D-Link DSL-G256DG firmware version vBZ_1.00.27, published on 28 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

D-Link DSL-G256DG version vBZ_1.00.27 web management interface allows authentication bypass via an unspecified method.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Dlink Dsl-G256dg Firmware.

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

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

## Is CVE-2023-32222 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-32222 and fix it if it is affected.

What it is: CVE-2023-32222 is a critical authentication bypass vulnerability in D-Link DSL-G256DG firmware version vBZ_1.00.27, published on 28 Jun 2023. 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-2023-32222 in the wild and no public exploit code.

Affected product: D-Link DSL-G256DG firmware version vBZ_1.00.27. 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-32222/ (Markdown: https://insights.sbomify.com/CVE-2023-32222/index.md)
```

## Sources

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

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