dbcve.org
Dir 2150 FirmwareOperating system · Dlink

CVE-2023-34276

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 SetTriggerPPPoEValidate Username 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-20554.

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

Command injection vulnerability in D-Link DIR-2150 router's SOAP API service on TCP port 80. The flaw allows authenticated attackers (or those bypassing auth) to inject arbitrary commands through unsanitized user input that gets passed to system calls, executing code in root context.

MitigationApply vendor firmware patch if available; if not, disable SOAP API service, restrict access to management interface via firewall/ACLs, or replace end-of-life device; network segmentation to limit exposure to adjacent 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
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. Identify the device model
    Access the router's web interface or check the device label to confirm the model is D-Link DIR-2150
    Affected if Device is not a D-Link DIR-2150, then not affected by this specific CVE
  2. Check the installed firmware version
    Log into the router's web interface and navigate to the Status or Management page to view the firmware version, or use the command line and check via 'cat /proc/version' or similar if telnet/ssh is enabled
    Affected if Firmware version is 1.06 or higher, then the version is not in the affected range (< 1.06)
  3. Verify if SOAP API service is accessible on port 80
    Use a web browser or curl to access http://<router-ip>/ and check if SOAP/UPnP endpoints respond; also verify port 80 is listening with 'netstat -an | grep :80' or 'nmap -p 80 <router-ip>'
    Affected if Port 80 is open and SOAP API responds, the vulnerable service is exposed
  4. Check if management interface is accessible from untrusted networks
    Review router firewall settings, WAN access controls, or ACLs to determine if the web management interface (port 80/443) is reachable from external networks or less-trusted internal segments
    Affected if Management interface is exposed to untrusted networks or the internet, the device is at higher risk of exploitation

The device is affected if it is a D-Link DIR-2150 with firmware version below 1.06, has SOAP API running on port 80, and the management interface is accessible to attackers.

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 vendor firmware patch if available; if not, disable SOAP API service, restrict access to management interface via firewall/ACLs, or replace end-of-life device; network segmentation to limit exposure to adjacent attackers.

Recommended fix Moderate confidence

D-Link DIR-2150 Firmware version 1.06 or later

  1. 1. Identify the current firmware version of the D-Link DIR-2150 by accessing the router web interface at http://192.168.0.1 and navigating to the Status or Management section.
  2. 2. Navigate to D-Link's official support page for the DIR-2150 and locate the firmware download section.
  3. 3. Download the firmware version 1.06 or later from D-Link's official website.
  4. 4. Access the router's web interface and navigate to the Firmware Upgrade or Management section.
  5. 5. Upload the downloaded firmware file and wait for the upgrade process to complete - do not power off the router during this process.
  6. 6. After the router reboots, verify the new firmware version is installed by checking the Status page.
  7. 7. Consider performing a factory reset after firmware upgrade to ensure clean configuration.
Caveat Standard firmware upgrade risks apply - ensure stable power during upload; backup configuration if possible; some settings may not persist across major firmware changes

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

Fix this in Dir 2150 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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