CVE-2023-34277
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 · uneditedD-Link DIR-2150 SetSysEmailSettings AccountName 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-20555.
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 confidenceThe D-Link DIR-2150 router contains a command injection vulnerability in its SOAP API service listening on TCP port 80. The SetSysEmailSettings function fails to properly validate the AccountName parameter before passing it to a system call, allowing authenticated attackers (with authentication bypassed) to execute arbitrary commands as root.
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< 1.06CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify D-Link DIR-2150 device on your networkLocate the router in your network inventory or physically inspect the device label for the model number DIR-2150Affected if The device is a D-Link DIR-2150 router
-
Check installed firmware versionAccess the router admin panel or use nmap/ssh to query the firmware version (often shown on status page or via grep /proc/mtd for firmware partition)Affected if Firmware version is below 1.06 (versions like 1.04, 1.05, or earlier are affected)
-
Verify SOAP API service is exposedScan the router IP on TCP port 80 (e.g., curl http://router-ip or nmap -p 80 router-ip)Affected if Port 80 is open and responds to HTTP requests
-
Confirm SOAP endpoint is accessibleSend a SOAP request to the router (POST to /soap or /HNAP1) and check for SOAPAction header handlingAffected if SOAP API endpoint responds, indicating the vulnerable service is enabled
You are affected if you have a D-Link DIR-2150 router running firmware version 1.05 or lower with the SOAP API on port 80 exposed on your network.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.06
Apply available firmware updates from D-Link; if unavailable, restrict network access to the router's management interface to trusted sources only.
D-Link DIR-2150 Firmware version 1.06 or later
- Download the latest firmware version 1.06 or later from the official D-Link support website
- Access the router's web management interface via HTTP on TCP port 80
- Navigate to the Administration or System settings section
- Locate the firmware upgrade option and upload the downloaded firmware file
- Wait for the upgrade process to complete and the router to reboot
- Verify the firmware version has been updated to 1.06 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34277 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-34277 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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