dbcve.org
Dir 882 FirmwareOperating system · Dlink

CVE-2024-48635

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 VLANID:2/VID parameter in the SetVLANSettings 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 contain a command injection vulnerability in the SetVLANSettings function. Attackers can inject arbitrary OS commands through the VLANID:2/VID parameter via a crafted POST request, achieving remote code execution with HIGH severity (CVSS 8).

MitigationApply vendor firmware updates when available; in the meantime, restrict network access to the device's management interface and disable WAN management access to limit exposure to unauthenticated attackers.

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 on the router or log into the admin interface to confirm the exact model (DIR_882 or DIR_878)
    Affected if Model is D-Link DIR_882 or DIR_878
  2. Check firmware version
    Log into the router admin interface (typically 192.168.0.1) and navigate to Status or Management section to view the firmware version, or use command 'cat /proc/version' if SSH access is available
    Affected if Firmware version is 1.30b06 (for DIR_882) or 1.30b08 (for DIR_878)
  3. Verify web management interface is enabled
    Check router settings under Administration or Management to confirm the HTTP/HTTPS web interface is accessible
    Affected if Web management interface is enabled and reachable on LAN or WAN
  4. Check remote management exposure
    Inspect router settings for 'Remote Management', 'WAN Management', or 'Web Access' options to determine if the admin interface is exposed to WAN
    Affected if Remote management or WAN web access is enabled, allowing unauthenticated attackers to reach the vulnerable function

You are affected if you have a DIR_882 running firmware 1.30b06 or a DIR_878 running firmware 1.30b08, and the router web management interface is network-accessible (especially from WAN).

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; in the meantime, restrict network access to the device's management interface and disable WAN management access to limit exposure to unauthenticated attackers.

Recommended fix Moderate confidence

Latest available firmware from D-Link support website (check for versions newer than 1.30b06 for DIR 882 and newer than 1.30b08 for DIR 878)

  1. 1. Visit the official D-Link support website at www.dlink.com and navigate to the product support page for your specific model (DIR 882 or DIR 878).
  2. 2. Locate the firmware download section and check for the latest available firmware version.
  3. 3. Download the most recent firmware version listed for your device model.
  4. 4. Access the router's web management interface by entering the router's IP address in a web browser.
  5. 5. Navigate to the Administration or System settings section of the router interface.
  6. 6. Look for a Firmware Upgrade or Router Update option.
  7. 7. Upload the downloaded firmware file and follow the on-screen instructions to complete the upgrade.
  8. 8. After the upgrade completes, verify the new firmware version in the router status page.
Caveat firmware upgrade may reset 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
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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