dbcve.org
Dsr 150 FirmwareOperating system · Dlink

CVE-2024-57376

HIGH · 8.8 CVSS v3.1 Published 2025-01-28
Fix available
A fix is available. Upgrade to after 3.17b901c or later.
See remediation →
93/100
Remediation priority · Urgent
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
Buffer Overflow vulnerability in D-Link DSR-150, DSR-150N, DSR-250, DSR-250N, DSR-500N, DSR-1000N from 3.13 to 3.17B901C allows unauthenticated users to execute remote code execution.

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 · moderate confidence

Buffer overflow vulnerability in D-Link DSR series routers (DSR-150 through DSR-1000N) running firmware versions 3.13 to 3.17B901C allows unauthenticated remote attackers to execute arbitrary code by overflowing a buffer in the firmware, likely through a network service handling user input without proper bounds checking.

MitigationReplace affected D-Link DSR routers with supported hardware, as these devices have likely reached end-of-life and no official patch is expected; until replacement, segment affected devices behind a firewall and disable exposed network services.

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
Dsr 150 FirmwareOperating system
Affected:>= 3.13, <= 3.17B901C
Dsr 150n FirmwareOperating system
Affected:>= 3.13, <= 3.17B901C
Dsr 250 FirmwareOperating system
Affected:>= 3.13, <= 3.17B901C
Dsr 250n FirmwareOperating system
Affected:>= 3.13, <= 3.17B901C
Dsr 500 FirmwareOperating system
Affected:>= 3.13, <= 3.17B901C
Dsr 1000n FirmwareOperating system
Affected:>= 3.13, <= 3.17b901c

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

CVSS:3.1/AV:A/AC:L/PR:N/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 DSR model
    Access the router web management interface and navigate to Status > System Information, or use CLI command 'show system' to identify the exact model (DSR-150, DSR-150N, DSR-250, DSR-250N, DSR-500N, or DSR-1000N).
    Affected if Device is one of: DSR-150, DSR-150N, DSR-250, DSR-250N, DSR-500N, DSR-1000N
  2. Check firmware version
    In the web UI, go to Maintenance > Firmware Upgrade or Status > System Information to view the firmware version. Alternatively, use CLI command 'show version' to confirm the installed firmware version.
    Affected if Firmware version is any version >= 3.13 and <= 3.17B901C (including 3.13, 3.14, 3.15, 3.16, 3.17, 3.17B901C)
  3. Verify web management interface exposure
    Attempt to reach the router HTTP/HTTPS ports (typically 80/443) from an external network, or review firewall rules to determine if the web management interface is accessible from untrusted networks.
    Affected if Web management interface is accessible from the internet or untrusted networks
  4. Confirm remote management setting
    In the web UI, navigate to System > Management > Remote Management and verify whether remote management access is enabled.
    Affected if Remote management is enabled and the web interface is exposed to untrusted networks

You are affected if your device is a DSR model with firmware between 3.13 and 3.17B901C and the web management interface is accessible from untrusted networks.

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 3.17b901c
Interim mitigation

Replace affected D-Link DSR routers with supported hardware, as these devices have likely reached end-of-life and no official patch is expected; until replacement, segment affected devices behind a firewall and disable exposed network services.

Recommended fix Moderate confidence

Firmware version newer than 3.17B901C (check D-Link support for the latest available version for your specific DSR model)

  1. 1. Identify the exact D-Link DSR model (DSR-150, DSR-150N, DSR-250, DSR-250N, DSR-500, or DSR-1000N) currently deployed.
  2. 2. Navigate to the official D-Link support website (www.dlink.com) and locate the firmware download section for your specific model.
  3. 3. Download the latest available firmware version for your DSR model. Note: The provided CVE description covers versions 3.13 through 3.17B901C, so any version newer than 3.17B901C may contain the fix.
  4. 4. Consult the D-Link firmware upgrade guide for your model to understand the upgrade procedure.
  5. 5. Back up the current device configuration before performing the firmware upgrade.
  6. 6. Upload and apply the new firmware via the device's web management interface or appropriate method specified in the documentation.
  7. 7. After upgrade, verify the device is functioning correctly and confirm the new firmware version is installed.
  8. 8. Validate that the vulnerability is remediated by confirming the device responds normally and reviewing any security release notes if available.
Caveat Review D-Link release notes for any configuration or feature changes between versions; firmware upgrades may require reconfiguration or have compatibility considerations

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

Fix this in Dsr 150 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing8.0 h
  • Review / QA4.0 h
44.0 hours of engineering $7,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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