dbcve.org
Dcs 8300lhv2 FirmwareOperating system · Dlink

CVE-2023-51628

HIGH · 8.0 CVSS v3.1 Published 2024-05-03
Fix available
A fix is available. Upgrade to 1.07.02 or later.
See remediation →
82/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
D-Link DCS-8300LHV2 ONVIF SetHostName Stack-Based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of D-Link DCS-8300LHV2 IP cameras. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed. The specific flaw exists within the handling of the SetHostName ONVIF call. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-21322.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a stack-based buffer overflow vulnerability in the ONVIF SetHostName function of D-Link DCS-8300LHV2 IP cameras. The flaw results from insufficient length validation of user-supplied input before copying it into a fixed-size stack buffer, allowing authenticated attackers to overflow the buffer and achieve arbitrary code execution in the root context.

MitigationApply vendor firmware updates when available; meanwhile, isolate affected devices from untrusted networks and disable ONVIF functionality if not required, as the authentication bypass increases exploitability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Dcs 8300lhv2 FirmwareOperating system
Affected:< 1.07.02

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device model is D-Link DCS-8300LHV2
    Access the camera's web interface or use ONVIF/SNMP discovery to verify the exact model number displayed in device information
    Affected if The device is not a D-Link DCS-8300LHV2
  2. Check firmware version
    Navigate to the camera's web interface System > Device Info or use the ONVIF GetDeviceInformation request to retrieve the firmware version
    Affected if Firmware version is below 1.07.02 (e.g., 1.06.01, 1.05.x, etc.)
  3. Verify ONVIF service is enabled
    Check the camera's web interface for ONVIF settings (usually under Network > ONVIF or similar) or use an ONVIF client to send a GetServices request
    Affected if ONVIF protocol is enabled and accessible on the device
  4. Confirm ONVIF authentication is configured
    Review ONVIF user accounts in the camera's web interface under User Management or ONVIF user settings
    Affected if ONVIF authentication is enabled (required for authenticated exploitation)

Device is affected if it is a D-Link DCS-8300LHV2 running firmware version below 1.07.02 with ONVIF functionality enabled and accessible with valid credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.07.02 or later
Fixed in 1.07.02
Interim mitigation

Apply vendor firmware updates when available; meanwhile, isolate affected devices from untrusted networks and disable ONVIF functionality if not required, as the authentication bypass increases exploitability.

Recommended fix Moderate confidence

D-Link DCS-8300LHV2 Firmware version 1.07.02 or later

  1. 1. Download the firmware version 1.07.02 or later for D-Link DCS-8300LHV2 from the official D-Link support website
  2. 2. Access the camera's web management interface by entering the camera's IP address in a web browser
  3. 3. Log in with administrator credentials
  4. 4. Navigate to the Settings or Maintenance section of the web interface
  5. 5. Find the Firmware Upgrade or Software Update option
  6. 6. Select the downloaded firmware file (1.07.02 or later) and initiate the upgrade
  7. 7. Wait for the firmware upload and installation to complete - do not power off the camera during this process
  8. 8. After the camera restarts, verify the firmware version has been updated to 1.07.02 or later in the system information page

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dcs 8300lhv2 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,790
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-51628 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-51628 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data