dbcve.org
Dir 882 FirmwareOperating system · Dlink

CVE-2024-48630

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 MacAddress parameter in the SetMACFilters2 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

Command injection vulnerability in D-Link DIR_882 and DIR_878 routers running firmware versions FW130B06 and FW130B08 respectively. The MacAddress parameter in the SetMACFilters2 function fails to properly sanitize user input, allowing arbitrary OS command execution via crafted POST requests.

MitigationApply vendor firmware updates when available. As an interim control, disable remote web management access and restrict the device's management interface to trusted networks only.

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
    Check the device label or web interface to confirm the exact model number is D-Link DIR_882 or DIR_878
    Affected if Model is not DIR_882 or DIR_878
  2. Check firmware version on DIR_882
    Navigate to the router web interface Status or Administration page, or log via SSH and run 'cat /proc/version' or check /etc/firmware_version to determine the installed firmware version
    Affected if Firmware version equals 1.30b06 on DIR_882
  3. Check firmware version on DIR_878
    Navigate to the router web interface Status or Administration page, or log via SSH and run 'cat /proc/version' or check /etc/firmware_version to determine the installed firmware version
    Affected if Firmware version equals 1.30b08 on DIR_878
  4. Determine if MAC filtering is accessible
    Access the router web interface and check if the MAC filtering or Wireless MAC Filter settings page is present and functional. This indicates the SetMACFilters2 function is available
    Affected if MAC filtering feature is enabled and accessible on the device

You are affected if you own a DIR_882 running firmware 1.30b06 or a DIR_878 running firmware 1.30b08, and the MAC filtering feature is enabled and reachable.

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 vendor firmware updates when available. As an interim control, disable remote web management access and restrict the device's management interface to trusted networks only.

Recommended fix Moderate confidence

Check D-Link support for DIR 882 and DIR 878 firmware updates beyond 1.30b06 and 1.30b08 respectively

  1. 1. Check D-Link's official support page (www.dlink.com) for the latest firmware version for DIR 882 and DIR 878 devices
  2. 2. If a newer firmware version is available that addresses CVE-2024-48630, download it from the official D-Link support site
  3. 3. Access the router's web management interface
  4. 4. Navigate to the firmware upgrade section (typically under Administration or System settings)
  5. 5. Upload and apply the new firmware file
  6. 6. After reboot, verify the firmware version matches the patched release
  7. 7. Consider resetting to factory defaults and reconfiguring after major firmware updates
Caveat Firmware upgrades may reset router configuration to defaults; backup settings before upgrading if possible

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

Fix this in Dir 882 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,790
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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