CVE-2023-34278
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 EmailFrom 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-20556.
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 interface (TCP port 80). The SetSysEmailSettings function fails to validate the EmailFrom parameter before using it in a system call, allowing authenticated attackers to inject arbitrary shell commands and execute code as root. Although authentication is required, it can be bypassed.
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.
-
Confirm device model is D-Link DIR-2150Access the router's web interface or check the device label/menu to verify the exact model numberAffected if The device is not a D-Link DIR-2150 model, then this specific CVE does not apply
-
Check firmware versionLog into the router's admin interface and locate the firmware version information, typically found under Status, System Info, or Maintenance sectionsAffected if The installed firmware version is 1.06 or higher, then the device is patched; versions below 1.06 are affected
-
Verify SOAP API accessibilityAttempt to access the router on TCP port 80 (HTTP) and check if the SOAP service responds; you can also check if port 80 is listening on the device using network scanning toolsAffected if Port 80 is accessible from an untrusted network and the router is running affected firmware (<1.06), the vulnerability is potentially exploitable
-
Check remote management settingsIn the router admin interface, look for Remote Management, WAN Access, or Administration settings to determine if remote access to the management interface is enabledAffected if Remote management is enabled on an affected device, attackers from the WAN side could potentially reach the SOAP API
-
Identify if email notification features are configuredIn the router settings, look for Email Settings, SysEmail, or Notification settings under the Administration or Advanced configuration menusAffected if The SetSysEmailSettings function is available and the email feature can be configured on the affected firmware, the command injection point exists in that function
A user is affected if they are running D-Link DIR-2150 firmware below version 1.06 with the SOAP API accessible (port 80 open), regardless of remote management setting since the authentication can be bypassed.
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 the vendor-supplied firmware patch when available. Until then, restrict network access to the router's management interface and consider disabling remote administration to reduce exposure to network-adjacent attackers.
DIR-2150 firmware version 1.06 or later
- 1. Access the D-Link DIR-2150 router web interface via HTTP/HTTPS on the default IP address (typically 192.168.0.1)
- 2. Navigate to the Administration or System settings section
- 3. Locate the firmware update/upgrade option
- 4. Download the firmware version 1.06 or later from the official D-Link support website (support.dlink.com)
- 5. Upload the firmware file through the router's web interface
- 6. Wait for the firmware upgrade process to complete - do not power off the router during this process
- 7. After the router reboots, verify the firmware version has been updated successfully
- 8. Confirm the SetSysEmailSettings functionality works correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34278 — 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-34278 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