dbcve.org
Dcs 8300lhv2 FirmwareOperating system · Dlink

CVE-2023-51627

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 Duration 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 parsing of Duration XML elements. 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-21321.

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

Stack-based buffer overflow in ONVIF Duration XML parsing on D-Link DCS-8300LHV2 IP cameras. The camera fails to validate the length of user-supplied data in Duration XML elements before copying to a fixed-size stack buffer, allowing adjacent attackers to execute arbitrary code as root. Authentication can be bypassed.

MitigationRestrict network access to IP cameras, disable ONVIF if unused, and monitor D-Link for firmware updates addressing this vulnerability and the authentication bypass. Consider network segmentation for IoT devices.

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 camera's web interface or check the device label/metadata to confirm it is a D-Link DCS-8300LHV2 IP camera.
    Affected if The device is not a D-Link DCS-8300LHV2, then this specific CVE does not apply.
  2. Determine the firmware version
    Log into the camera's web interface and navigate to the System or About section to view the firmware version. Alternatively, check via ONVIF device management or the D-Link mobile app.
    Affected if The firmware version is lower than 1.07.02, meaning the installed version falls within the affected range.
  3. Check if ONVIF service is enabled
    Access the camera's web interface and look for ONVIF settings under Network or Security configuration. Confirm the ONVIF protocol is turned on.
    Affected if ONVIF is disabled, the attack surface for this specific vulnerability is not present, though other vulnerabilities may still exist.
  4. Verify ONVIF authentication settings
    Review the ONVIF configuration to confirm whether authentication is required for ONVIF requests. Check if anonymous or unauthenticated access is permitted.
    Affected if ONVIF is enabled with authentication disabled or bypassed, combined with firmware < 1.07.02, the full exploit chain (buffer overflow plus auth bypass) is applicable.

You are affected if you have a D-Link DCS-8300LHV2 camera running firmware version lower than 1.07.02 with ONVIF enabled.

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

Restrict network access to IP cameras, disable ONVIF if unused, and monitor D-Link for firmware updates addressing this vulnerability and the authentication bypass. Consider network segmentation for IoT devices.

Recommended fix High confidence

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

  1. Obtain D-Link DCS-8300LHV2 firmware version 1.07.02 or later from D-Link's official support website (supportannouncement.us.dlink.com or dlink.com)
  2. Access the DCS-8300LHV2 web interface using administrator credentials
  3. Navigate to the System > Firmware Upgrade or Settings > Device Management section
  4. Upload the fixed firmware file (version 1.07.02 or later)
  5. Wait for the firmware upload and installation to complete, ensuring the device does not lose power
  6. After reboot, verify the firmware version has been updated to 1.07.02 or later in the device settings
Caveat Review D-Link release notes for any changes to features or configuration requirements before upgrading; ensure backup of device configuration

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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