dbcve.org
Dsr 150 FirmwareOperating system · Dlink

CVE-2013-5945

CRITICAL · 9.8 CVSS v3.1 Published 2020-02-11
Fix available
A fix is available. Upgrade to 1.05b64 / 1.08b44 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Multiple SQL injection vulnerabilities in D-Link DSR-150 with firmware before 1.08B44; DSR-150N with firmware before 1.05B64; DSR-250 and DSR-250N with firmware before 1.08B44; and DSR-500, DSR-500N, DSR-1000, and DSR-1000N with firmware before 1.08B77 allow remote attackers to execute arbitrary SQL commands via the password to (1) the login.authenticate function in share/lua/5.1/teamf1lualib/login.lua or (2) captivePortal.lua.

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
How this class of weakness works · CWE-89

User input is woven into a database query, letting an attacker rewrite the query's logic. From there they can read, alter, or destroy data — frequently the entire database. The reliable fix is parameterised queries (prepared statements), so input is always treated as data and never as SQL.

General guidance for the sql injection class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
Dsr 150 FirmwareOperating system
Affected:< 1.08b44
Dsr 150n FirmwareOperating system
Affected:< 1.05b64
Dsr 250 FirmwareOperating system
Affected:< 1.08b44
Dsr 250n FirmwareOperating system
Affected:< 1.08b44
Dsr 500 FirmwareOperating system
Affected:< 1.08b77
Dsr 500n FirmwareOperating system
Affected:< 1.08b77
Dsr 1000 FirmwareOperating system
Affected:< 1.08b77
Dsr 1000n FirmwareOperating system
Affected:< 1.08b77

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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.05b64 / 1.08b44 / 1.08b77 or later
Fixed in 1.05b641.08b441.08b77
Recommended fix High confidence

DSR-150: firmware 1.08B44+ | DSR-150N: firmware 1.05B64+ | DSR-250/250N: firmware 1.08B44+ | DSR-500/500N/1000/1000N: firmware 1.08B77+

  1. 1. Identify the specific DSR model (150, 150n, 250, 250n, 500, 500n, 1000, or 1000n) in use
  2. 2. Access the D-Link router web interface or CLI to check the current firmware version
  3. 3. Navigate to D-Link's official support page (support.dlink.com) and locate the firmware download section for the specific model
  4. 4. Download the fixed firmware version: for DSR-150 use 1.08B44 or later; for DSR-150N use 1.05B64 or later; for DSR-250/250N use 1.08B44 or later; for DSR-500/500N/1000/1000N use 1.08B77 or later
  5. 5. Follow D-Link's standard firmware upgrade procedure (typically via web interface under Maintenance > Firmware Upgrade or via FTP/TFTP for bulk updates)
  6. 6. After upgrade, verify the new firmware version is installed and confirm the login.authenticate function in share/lua/5.1/teamf1lualib/login.lua and captivePortal.lua have been patched
Caveat Standard firmware upgrade risks apply - ensure stable power during upgrade; back up configuration if possible; some legacy settings may not persist across major version changes

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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