dbcve.org
Dir505 Shareport Mobile Companion FirmwareOperating system · Dlink

CVE-2014-3936

HIGH · 10.0 CVSS v2.0 Published 2014-06-02
Fix available
A fix is available. Upgrade to after 1.07 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Public exploit 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
Stack-based buffer overflow in the do_hnap function in www/my_cgi.cgi in D-Link DSP-W215 (Rev. A1) with firmware 1.01b06 and earlier, DIR-505 with firmware before 1.08b10, and DIR-505L with firmware 1.01 and earlier allows remote attackers to execute arbitrary code via a long Content-Length header in a GetDeviceSettings action in an HNAP request.

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

Stack-based buffer overflow in the do_hnap function in www/my_cgi.cgi allows remote attackers to execute arbitrary code by sending a crafted HNAP request with an oversized Content-Length header in a GetDeviceSettings action. This affects D-Link DSP-W215 (A1), DIR-505, and DIR-505L devices with older firmware versions.

MitigationNetwork segmentation and restricting access to the web interface from untrusted networks is recommended. Since firmware updates may not be available for these legacy devices, consider replacing affected devices with currently supported models.

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
Dir505 Shareport Mobile Companion FirmwareOperating system
Affected:<= 1.07
Dir505 Shareport Mobile CompanionHardware / appliance
Affected:= a1
Dir505l Shareport Mobile Companion FirmwareOperating system
Affected:<= 1.01
Dir 505l Shareport Mobile CompanionHardware / appliance
Affected:= a1
Dsp W215 FirmwareOperating system
Affected:<= 1.01
Dsp W215Hardware / appliance
Affected:= a1

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 exact D-Link device model
    Check the device label, web interface footer, or system info page to confirm the model is DIR-505, DIR-505L, or DSP-W215
    Affected if The device is not one of these three models, then it is not affected by this CVE
  2. Check the firmware version
    Log into the web interface and navigate to the Status or System section to view the firmware version, or check the device documentation
    Affected if For DIR-505: firmware version > 1.07 (1.08 or later) is NOT affected; for DIR-505L: firmware version > 1.01 (1.02 or later) is NOT affected; for DSP-W215: firmware version > 1.01 (1.02 or later) is NOT affected. Only versions at or below these thresholds are affected
  3. Verify the web interface is accessible
    Attempt to access the device web interface via HTTP/HTTPS (typically at the device IP address on port 80 or 443). Confirm that www/my_cgi.cgi is present by checking if HNAP requests respond
    Affected if The device web interface must be reachable for exploitation; if the web interface is disabled or not accessible externally, the attack surface is reduced but the vulnerability may still exist in the firmware
  4. Confirm HNAP functionality is enabled
    Send an HTTP request to the device with an HNAP1 header (such as 'HNAP1' or a SOAPAction header typical of HNAP requests) to the my_cgi.cgi endpoint. A valid response indicates HNAP is active
    Affected if HNAP is enabled and responding; if HNAP is disabled in the device settings, the specific attack vector for GetDeviceSettings may not be available

The device is affected if it is a D-Link DIR-505 (firmware <= 1.07), DIR-505L (firmware <= 1.01), or DSP-W215 A1 (firmware <= 1.01), the web interface with my_cgi.cgi is accessible, and HNAP functionality is 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 a release after 1.07
Interim mitigation

Network segmentation and restricting access to the web interface from untrusted networks is recommended. Since firmware updates may not be available for these legacy devices, consider replacing affected devices with currently supported models.

Recommended fix Moderate confidence

DIR-505: firmware 1.08b10 or later; DIR-505L: latest available firmware; DSP-W215 Rev A1: latest available firmware

  1. 1. Identify the exact D-Link device model (DIR-505, DIR-505L, or DSP-W215 Rev A1) from the affected device
  2. 2. Visit the official D-Link support page for your device model
  3. 3. Navigate to the firmware/downloads section
  4. 4. Download the latest available firmware version for your device
  5. 5. Access the device's web management interface
  6. 6. Locate the firmware upgrade section (usually under Administration or Maintenance)
  7. 7. Upload and apply the new firmware file
  8. 8. After reboot, verify the firmware version has been updated
Caveat Firmware upgrades on embedded devices can sometimes reset configuration to defaults; backup current configuration before upgrading if possible

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

Fix this in Dir505 Shareport Mobile Companion Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing4.0 h
  • Review / QA2.0 h
30.0 hours of engineering $5,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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