dbcve.org
Dcs 8300lhv2 FirmwareOperating system · Dlink

CVE-2023-51624

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 Nonce 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-20072.

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 the RTSP server's ValidateAuthorizationHeader function on D-Link DCS-8300LHV2 IP cameras. The flaw allows unauthenticated, network-adjacent attackers to overflow a fixed-length stack buffer via a malformed Authorization header and execute arbitrary code as root.

MitigationApply vendor firmware patch if available; otherwise, implement network segmentation to restrict access to TCP port 554, as the device may be end-of-life with no patch.

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. Confirm device model is D-Link DCS-8300LHV2
    Access the camera's web interface or check the device label/metadata to verify the exact model number
    Affected if The device is not a D-Link DCS-8300LHV2 model, then this CVE does not apply
  2. Check installed firmware version
    Log into the camera's web interface and navigate to the System or Settings page to view the firmware version, or use the manufacturer's discovery/tool to query the device
    Affected if Firmware version is below 1.07.02 (for example, 1.06.x or earlier)
  3. Verify RTSP server is enabled
    Check the camera's settings page for RTSP configuration, or scan TCP port 554 on the device to confirm the RTSP service is listening
    Affected if RTSP server is enabled and port 554 is accessible on the network
  4. Assess network exposure
    Determine if the device is directly accessible from untrusted networks by checking NAT configurations, firewall rules, or VLAN placement
    Affected if The RTSP port (TCP 554) is reachable from network segments that include untrusted or adjacent attackers

A user is affected if they have a D-Link DCS-8300LHV2 camera running firmware below version 1.07.02 with RTSP enabled and accessible from a network-adjacent attacker position.

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 patch if available; otherwise, implement network segmentation to restrict access to TCP port 554, as the device may be end-of-life with no patch.

Recommended fix High confidence

Firmware version 1.07.02 or later

  1. 1. Identify the current firmware version of the D-Link DCS-8300LHV2 camera by accessing the web interface or using the D-Link app.
  2. 2. Navigate to the D-Link support website (support.dlink.com) and locate the DCS-8300LHV2 product page.
  3. 3. Download firmware version 1.07.02 or later from the official D-Link support page.
  4. 4. Access the camera's web management interface and navigate to the firmware upgrade section (typically under Settings > Maintenance > Firmware Upgrade).
  5. 5. Upload the downloaded firmware file and initiate the upgrade process.
  6. 6. Wait for the upgrade to complete and the camera to reboot. Do not power off the device during the upgrade.
  7. 7. After reboot, verify the firmware version has been updated to 1.07.02 or later.
  8. 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
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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