dbcve.org
Dcs 8300lhv2 FirmwareOperating system · Dlink

CVE-2023-51625

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 SetSystemDateAndTime Command Injection 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 implementation of the ONVIF API, which listens on TCP port 80. When parsing the sch:TZ XML element, the process does not properly validate a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-21319.

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

The D-Link DCS-8300LHV2 IP camera has a command injection vulnerability in its ONVIF API (TCP port 80). The sch:TZ XML element in SetSystemDateAndTime requests is not validated before being passed to a system call, allowing authenticated attackers (authentication can be bypassed) to execute arbitrary commands as root.

MitigationReplace the affected D-Link camera with a currently-supported model from a vendor providing security updates, or network isolate the device and disable ONVIF if not required.

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. Identify the device model
    Access the device web interface or check the device label/metadata to confirm the model is D-Link DCS-8300LHV2
    Affected if The device is a DCS-8300LHV2 model
  2. Check the firmware version
    Log into the camera web interface and navigate to Setup > System > Device Info, or check via ONVIF GetDeviceInformation request, and note the firmware version
    Affected if The firmware version is below 1.07.02 (for example, 1.06.01 or earlier)
  3. Verify ONVIF service is accessible
    Check if TCP port 80 is open and responding to ONVIF requests by sending a GetCapabilities SOAP request to the device
    Affected if ONVIF service is exposed on port 80 and accepting requests
  4. Confirm ONVIF authentication is active
    Attempt to access the ONVIF API without credentials or with default credentials to verify if authentication can be bypassed
    Affected if ONVIF API is accessible without valid authentication or with weak/default credentials

You are affected if you have a D-Link DCS-8300LHV2 camera running firmware version below 1.07.02 with ONVIF service enabled and accessible on port 80, especially if ONVIF authentication can be bypassed.

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

Replace the affected D-Link camera with a currently-supported model from a vendor providing security updates, or network isolate the device and disable ONVIF if not required.

Recommended fix Moderate confidence

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

  1. Navigate to D-Link's official support website (supportannouncement.us.dlink.com) and download firmware version 1.07.02 or later for the DCS-8300LHV2 device
  2. Access the camera's web interface by entering the device IP address in a web browser
  3. Log into the camera's administration panel with administrator credentials
  4. Locate the firmware upgrade section in the settings menu (typically under 'Maintenance' or 'System' > 'Firmware Upgrade')
  5. Upload the downloaded firmware file (1.07.02 or later) and initiate the upgrade process
  6. Wait for the firmware upload and installation to complete - do not power off the device during this process
  7. After the upgrade completes, the device will automatically restart
  8. Verify the firmware version has been updated by checking the device status page

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

Fix this in Dcs 8300lhv2 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,150
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-51625 — 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-51625 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