dbcve.org
Dir 882 FirmwareOperating system · Dlink

CVE-2024-48631

HIGH · 8.0 CVSS v3.1 Published 2024-10-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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
D-Link DIR_882_FW130B06 and DIR_878 DIR_878_FW130B08 were discovered to contain a command injection vulnerability via the SSID parameter in the SetWLanRadioSettings function. This vulnerability allows attackers to execute arbitrary OS commands via a crafted POST 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

D-Link DIR_882 and DIR_878 routers running specific firmware versions contain an OS command injection vulnerability in the SetWLanRadioSettings function. The SSID parameter in wireless radio settings is not properly sanitized before being passed to system shell commands, allowing attackers to inject arbitrary OS commands via a crafted POST request to the web management interface.

MitigationApply available firmware updates from D-Link; if no update exists, disable remote web management, implement network segmentation, and deploy WAF rules to block suspicious POST requests with shell metacharacters in parameter values.

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
Dir 882 FirmwareOperating system
Affected:= 1.30b06
Dir 878 FirmwareOperating system
Affected:= 1.30b08

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify router model
    Locate the model number on the device label or check the web management interface status page for the exact model (DIR_882 or DIR_878)
    Affected if Model is not D-Link DIR_882 or DIR_878, then not affected by this specific CVE
  2. Check installed firmware version
    Access the router web management interface, navigate to Administration or Status section to view the firmware version. Compare against the affected versions: 1.30b06 for DIR_882 or 1.30b08 for DIR_878
    Affected if Firmware version exactly matches 1.30b06 (DIR_882) or 1.30b08 (DIR_878)
  3. Confirm web management interface accessibility
    Verify if the router web interface is accessible over the network (check remote management settings under Administration > Remote Management). Attempt to reach the HTTP/HTTPS interface from outside the local network
    Affected if Web management interface is accessible remotely, meaning the attack surface is present for this command injection vulnerability

If the device is a D-Link DIR_882 running firmware 1.30b06 or DIR_878 running firmware 1.30b08, and the web management interface is network-accessible, the environment is affected by this OS command injection vulnerability in the SetWLanRadioSettings function.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply available firmware updates from D-Link; if no update exists, disable remote web management, implement network segmentation, and deploy WAF rules to block suspicious POST requests with shell metacharacters in parameter values.

Recommended fix Moderate confidence

Check D-Link support for firmware version newer than 1.30b06 (DIR 882) or 1.30b08 (DIR 878) - specific fixed version not disclosed in available advisory

  1. 1. Navigate to the D-Link support website (www.dlink.com) and locate the firmware download section for your device model (DIR 882 or DIR 878)
  2. 2. Check for any available firmware updates newer than version 1.30b06 (for DIR 882) or 1.30b08 (for DIR 878)
  3. 3. If a newer firmware version is available, download it from the official D-Link support page
  4. 4. Access the router's web management interface and locate the firmware upgrade section (typically under Administration or System settings)
  5. 5. Upload and apply the new firmware version following the on-screen instructions
  6. 6. After the firmware update completes, verify the new version is installed and test that the SetWLanRadioSettings function operates correctly
  7. 7. If no firmware update is available from D-Link, consider implementing network segmentation to isolate the affected device or replacing the device with a currently supported model
Caveat Firmware updates may reset router configuration to defaults; back up current settings before upgrading

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

Fix this in Dir 882 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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