dbcve.org
Dir 2150 FirmwareOperating system · Dlink

CVE-2023-34275

HIGH · 8.0 CVSS v3.1 Published 2024-05-03
Fix available
A fix is available. Upgrade to 1.06 or later.
See remediation →
82/100
Remediation priority · High
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 DIR-2150 SetNTPServerSettings Command Injection Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of D-Link DIR-2150 routers. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed. The specific flaw exists within the SOAP API interface, which listens on TCP port 80 by default. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-20553.

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

The D-Link DIR-2150 router contains a command injection vulnerability in its SOAP API interface on TCP port 80. The flaw results from insufficient validation of user-supplied strings before passing them to system calls. While authentication is required, it can be bypassed, allowing attackers to execute arbitrary code with root privileges.

MitigationApply available firmware updates from D-Link; if no patch exists, disable remote SOAP API management, restrict access to port 80 via firewall, or consider replacing the affected device.

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
Dir 2150 FirmwareOperating system
Affected:< 1.06

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

CVSS:3.1/AV:A/AC:L/PR:L/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 DIR-2150
    Access router web interface or check device label/mac address OUI. The D-Link DIR-2150 is identifiable by its model name in the firmware or on the physical device.
    Affected if The device is a D-Link DIR-2150 router.
  2. Check firmware version
    Log into the router web interface and navigate to Status or Management section to view the firmware version. Compare against 1.06.
    Affected if Firmware version is below 1.06.
  3. Verify SOAP API service is listening on port 80
    From a remote system, run 'nc -zv <router_ip> 80' or 'nmap -p 80 <router_ip>' to confirm TCP port 80 is open and responding.
    Affected if Port 80 is open and accessible from an attacker's network location.
  4. Confirm remote management is enabled
    In the router web interface, check Settings > Management or similar section for 'Enable Remote Management' or SOAP/UPnP settings. If disabled, the SOAP API may not be exploitable remotely.
    Affected if Remote management or SOAP API is enabled, allowing external access to the management interface on port 80.

A user is affected if they own a D-Link DIR-2150 device running firmware below version 1.06 with port 80 (SOAP API) accessible and remote management enabled.

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.06 or later
Fixed in 1.06
Interim mitigation

Apply available firmware updates from D-Link; if no patch exists, disable remote SOAP API management, restrict access to port 80 via firewall, or consider replacing the affected device.

Recommended fix Moderate confidence

D-Link DIR-2150 Firmware version 1.06

  1. 1. Access the D-Link DIR-2150 router web management interface via HTTP/HTTPS on the local network
  2. 2. Navigate to the firmware version check (typically under System > Firmware or Settings > Administration)
  3. 3. If current firmware version is below 1.06, download the firmware version 1.06 from the official D-Link support website (support.dlink.com)
  4. 4. Upload the firmware file through the router's web interface to apply the update
  5. 5. Wait for the upgrade process to complete and the router to reboot
  6. 6. Verify the new firmware version displays as 1.06 after reboot
  7. 7. Confirm the NTP server settings functionality works correctly post-upgrade
Caveat Standard firmware upgrade - backup router configuration before upgrading; router will reboot during update

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

Fix this in Dir 2150 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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