dbcve.org
D View 8Application · Dlink

CVE-2023-32165

CRITICAL · 9.8 CVSS v3.0 Published 2024-05-03
Fix available
A fix is available. Upgrade to after 2.0.1.27 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Remotely reachable 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 D-View TftpReceiveFileHandler Directory Traversal Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of D-Link D-View. Authentication is not required to exploit this vulnerability. The specific flaw exists within the TftpReceiveFileHandler class. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to execute code in the context of SYSTEM. Was ZDI-CAN-19497.

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 directory traversal vulnerability exists in D-Link D-View's TftpReceiveFileHandler component due to insufficient validation of user-supplied file paths. Attackers can manipulate path traversal sequences (e.g., ../) to write files to arbitrary locations on the system, achieving unauthenticated remote code execution with SYSTEM privileges.

MitigationApply vendor-supplied patches immediately; if unavailable, restrict network access to the TFTP service or disable it if not required, and implement input validation filters for path parameters.

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
D View 8Application
Affected:<= 2.0.1.27

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/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 D-Link D-View 8 installation and version
    Locate the D-Link D-View installation directory and check the version information, typically found in the application executable, installer logs, or system registry entries related to the software.
    Affected if The installed version is D-Link D-View 8 at version 2.0.1.27 or lower.
  2. Verify TFTP service status
    Check whether the TFTP service or TftpReceiveFileHandler component is enabled or running on the D-View server. This may be visible in the D-View administrative interface, Windows Services console, or through netstat commands listening on port 69 (TFTP).
    Affected if The TFTP service is enabled and accessible on the network.
  3. Inspect TFTP transfer directories for suspicious files
    Examine the directories used for TFTP file transfers (typically the TFTP root or configured transfer folder) for unexpected or newly created files, especially executable files, scripts, or configuration files in system directories.
    Affected if Unexpected files appear in the TFTP transfer directory or in parent directories accessed via path traversal sequences (../).

A system is affected if D-Link D-View 8 version 2.0.1.27 or lower is installed with the TFTP service enabled and accessible.

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 a release after 2.0.1.27
Interim mitigation

Apply vendor-supplied patches immediately; if unavailable, restrict network access to the TFTP service or disable it if not required, and implement input validation filters for path parameters.

Recommended fix Moderate confidence

D-View 8 version greater than 2.0.1.27 (refer to D-Link security advisory for exact fixed release number)

  1. 1. Check the current D-View version installed on the device
  2. 2. Visit D-Link's official support announcement page at supportannouncement.us.dlink.com to locate the security advisory for CVE-2023-32165
  3. 3. Download the firmware version that fixes CVE-2023-32197 (ZDI-CAN-19497) from D-Link's official support website
  4. 4. Follow D-Link's standard firmware upgrade procedure for D-View 8, typically via the web administration interface or dedicated upgrade tool
  5. 5. After upgrading, verify the TftpReceiveFileHandler component has been updated and the path traversal vulnerability is resolved
  6. 6. Confirm the new version is greater than 2.0.1.27

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

Fix this in D View 8 Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA5.0 h
33.0 hours of engineering $5,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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