# CVE-2023-51629: D-Link DCS-8300LHV2 ONVIF Hardcoded PIN Authentication Bypass Vulnerability

> Network-adjacent attackers can bypass authentication on D-Link IP cameras by exploiting a hardcoded PIN in the ONVIF API configuration.

- **Severity:** Medium 6.3 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **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:** 3 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-cw65-c3g7-7rw3

## What is CVE-2023-51629?

CVE-2023-51629 is a medium-severity vulnerability in D-Link DCS-8300LHV2, published on 3 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

D-Link DCS-8300LHV2 ONVIF Hardcoded PIN Authentication Bypass Vulnerability. This vulnerability allows network-adjacent attackers to bypass authentication on affected installations of D-Link DCS-8300LHV2 IP cameras. Authentication is not required to exploit this vulnerability.

The specific flaw exists within the configuration of the ONVIF API. The issue results from the use of a hardcoded PIN. An attacker can leverage this vulnerability to bypass authentication on the system. Was ZDI-CAN-21492.

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

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

It affects 1 product.


Products: Dlink Dcs-8300lhv2 Firmware.

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

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

## Is CVE-2023-51629 being exploited?

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

## Other vulnerabilities in D-Link DCS-8300LHV2

- [CVE-2023-51624](https://insights.sbomify.com/CVE-2023-51624/): Memory corruption in DCS-8300LHV2 (high 8.8)
- [CVE-2023-51626](https://insights.sbomify.com/CVE-2023-51626/): Memory corruption in DCS-8300LHV2 (high 8.8)
- [CVE-2023-51625](https://insights.sbomify.com/CVE-2023-51625/): D-Link DCS-8300LHV2 ONVIF SetSystemDateAndTime Command Injection Remote Code Execution Vulnerability (high 8.0)
- [CVE-2023-51627](https://insights.sbomify.com/CVE-2023-51627/): D-Link DCS-8300LHV2 ONVIF Duration Stack-Based Buffer Overflow Remote Code Execution Vulnerability (high 8.0)
- [CVE-2023-51628](https://insights.sbomify.com/CVE-2023-51628/): D-Link DCS-8300LHV2 ONVIF SetHostName Stack-Based Buffer Overflow Remote Code Execution Vulnerability (high 8.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-51629 is a medium-severity vulnerability in D-Link DCS-8300LHV2, published on 3 May 2024. 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-2023-51629 in the wild and no public exploit code.

Affected product: D-Link DCS-8300LHV2. 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-51629/ (Markdown: https://insights.sbomify.com/CVE-2023-51629/index.md)
```

## Sources

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

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