dbcve.org
Dcs 8300lhv2 FirmwareOperating system · Dlink

CVE-2023-51626

HIGH · 8.8 CVSS v3.1 Published 2024-05-03
Fix available
A fix is available. Upgrade to 1.07.02 or later.
See remediation →
93/100
Remediation priority · Urgent
No privileges 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 RTSP ValidateAuthorizationHeader Username 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. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of the Authorization header by the RTSP server, which listens on TCP port 554. 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-21320.

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

A stack-based buffer overflow vulnerability exists in the RTSP server of D-Link DCS-8300LHV2 IP cameras. The ValidateAuthorizationHeader function on TCP port 554 fails to validate the length of user-supplied data in the Authorization header before copying it to a fixed-length stack buffer, allowing remote code execution as root without authentication.

MitigationRestrict network access to the RTSP service (port 554) through firewall rules or network segmentation. Contact D-Link for firmware updates; if unavailable, consider replacing affected 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/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 device model
    Access the device web interface or check the device label to confirm the model is DCS-8300LHV2
    Affected if Device is not a D-Link DCS-8300LHV2
  2. Check firmware version
    Log into the camera web interface and navigate to Settings > System > Firmware Upgrade, or check the version displayed on the status page
    Affected if Firmware version is below 1.07.02
  3. Verify RTSP service is accessible
    Attempt to connect to TCP port 554 (for example, using telnet or netcat: nc -zv <camera_ip> 554)
    Affected if Port 554 is open and reachable on the network

The device is affected if it is a DCS-8300LHV2 running firmware below version 1.07.02 and the RTSP service on port 554 is accessible on the network.

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 the RTSP service (port 554) through firewall rules or network segmentation. Contact D-Link for firmware updates; if unavailable, consider replacing affected devices.

Recommended fix High confidence

D-Link DCS-8300LHV2 Firmware version 1.07.02

  1. Identify the current firmware version of the D-Link DCS-8300LHV2 camera via the web management interface or RTSP server configuration
  2. Navigate to D-Link support website (support.dlink.com) and locate the DCS-8300LHV2 firmware download section
  3. Download firmware version 1.07.02 or later from the official D-Link support page
  4. Access the camera's web management interface and navigate to the firmware upgrade/settings section
  5. Upload the downloaded firmware file and initiate the upgrade process
  6. Wait for the upgrade to complete and the device to reboot
  7. Verify the new firmware version is 1.07.02 or later via the web interface
  8. Confirm the RTSP service is functioning normally after the upgrade

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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