D View 8Application · Dlink

CVE-2023-44413

HIGH · 7.5 CVSS v3.1 Published 2024-05-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 shutdown_coreserver Missing Authentication Denial-of-Service Vulnerability. This vulnerability allows remote attackers to create a denial-of-service condition on affected installations of D-Link D-View. Authentication is not required to exploit this vulnerability. The specific flaw exists within the shutdown_coreserver action. The issue results from the lack of authentication prior to allowing access to functionality. An attacker can leverage this vulnerability to create a denial-of-service condition on the system. Was ZDI-CAN-19572.

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

D-Link D-View contains a missing authentication vulnerability in the shutdown_coreserver action. Remote attackers can invoke this endpoint without any authentication credentials, causing the core server to shut down and resulting in a denial-of-service condition. The vulnerability stems from the lack of authentication checks before executing the shutdown functionality.

MitigationImplement proper authentication and authorization checks on the shutdown_coreserver endpoint to ensure only authorized users can execute this action. If available, apply vendor patches from D-Link. Consider network segmentation to limit exposure to unauthenticated attackers.

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:= 1.0.2.13

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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
    Check if D-Link D-View 8 is installed on the system. Look for the application in installed programs or check the D-View service status.
    Affected if D-Link D-View 8 version 1.0.2.13 is installed
  2. Verify the exact version number
    Access the D-View administrative interface or check the installed software version information. Compare the installed version against 1.0.2.13.
    Affected if Installed version is exactly 1.0.2.13
  3. Confirm the shutdown_coreserver endpoint is accessible
    Attempt to access the shutdown_coreserver endpoint via HTTP/HTTPS request without providing any authentication credentials. Check if the endpoint responds to unauthenticated requests.
    Affected if The endpoint responds to unauthenticated requests and accepts the shutdown command
  4. Check if core server shuts down without credentials
    Send a request to the shutdown_coreserver action without any authentication headers or session tokens. Observe if the core server shuts down or returns a success response.
    Affected if The server shuts down or returns success without requiring authentication

The environment is affected if D-Link D-View 8 version 1.0.2.13 is running and the shutdown_coreserver endpoint accepts unauthenticated requests, allowing remote attackers to shut down the core server.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authentication and authorization checks on the shutdown_coreserver endpoint to ensure only authorized users can execute this action. If available, apply vendor patches from D-Link. Consider network segmentation to limit exposure to unauthenticated attackers.

Fix this in D View 8 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-44413 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-44413 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