dbcve.org
D View 8Application · Dlink

CVE-2023-32167

MEDIUM · 6.5 CVSS v3.1 Published 2024-05-03
Fix available
A fix is available. Upgrade to 2.0.1.89 or later.
See remediation →
71/100
Remediation priority · Elevated
High EPSS Remotely reachable 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 uploadMib Directory Traversal Arbitrary File Creation or Deletion Vulnerability. This vulnerability allows remote attackers to create and delete arbitrary files on affected installations of D-Link D-View. Authentication is required to exploit this vulnerability. The specific flaw exists within the uploadMib function. 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 create or delete files in the context of SYSTEM. . Was ZDI-CAN-19529.

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 in D-Link D-View's uploadMib function allows authenticated remote attackers to create or delete arbitrary files on the system due to insufficient validation of user-supplied path parameters in file operations. This leads to SYSTEM-level code execution through file manipulation.

MitigationIf a vendor patch is unavailable, implement path validation and sanitization in the uploadMib function to restrict file operations to allowed directories; consider compensating controls like web application firewall rules or network segmentation.

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.89

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/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 installation and version
    Access the D-View web interface and navigate to the system information or about page to find the installed software version. Alternatively, check the application binaries or system dashboard for the version number.
    Affected if The installed version is D-View 8 and the version number is below 2.0.1.89
  2. Locate the uploadMib function
    In the D-View web interface, navigate to the MIB file management or network management section where MIB file uploads are handled. The vulnerable function is typically found under SNMP or network monitoring settings.
    Affected if The uploadMib function exists and is accessible in the web interface
  3. Verify authenticated access to the uploadMib endpoint
    Attempt to access the uploadMib functionality with valid administrator credentials. The vulnerability requires an authenticated session to exploit.
    Affected if A valid administrator account can log in and access the MIB upload functionality
  4. Check file operation permissions
    If you have access, attempt to interact with the uploadMib function to observe if arbitrary file paths can be specified in the upload parameters. Look for parameters that accept file paths without validation.
    Affected if The uploadMib function accepts user-supplied path parameters without proper validation or sanitization

Your environment is affected if you are running D-Link D-View 8 version below 2.0.1.89 and the uploadMib function is accessible to authenticated users without proper path validation.

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 2.0.1.89 or later
Fixed in 2.0.1.89
Interim mitigation

If a vendor patch is unavailable, implement path validation and sanitization in the uploadMib function to restrict file operations to allowed directories; consider compensating controls like web application firewall rules or network segmentation.

Recommended fix High confidence

D-View 8 version 2.0.1.89

  1. 1. Identify the current version of D-Link D-View 8 software installed
  2. 2. Navigate to the official D-Link support page or download portal
  3. 3. Download the D-View 8 version 2.0.1.89 or later firmware update
  4. 4. Follow D-Link's standard firmware upgrade procedure for D-View 8
  5. 5. After upgrade, verify the version number reflects 2.0.1.89 or higher
  6. 6. Confirm the uploadMib function is now properly validating user-supplied paths
Caveat Firmware upgrades may require downtime and should be tested in a staging environment before production deployment

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

Fix this in D View 8 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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