Dir 846w FirmwareOperating system · Dlink

CVE-2024-44342

CRITICAL · 9.8 CVSS v3.1 Published 2024-08-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
D-Link DIR-846W A1 FW100A43 was discovered to contain a remote command execution (RCE) vulnerability via the wl(0).(0)_ssid parameter. This vulnerability is exploited 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-846W A1 firmware FW100A43 contains a command injection vulnerability in the wl(0).(0)_ssid wireless SSID parameter. Attackers can achieve remote command execution by sending a crafted POST request with malicious commands embedded in this parameter.

MitigationThis is an end-of-life router with no available patch. Replace the device with a supported model or, as an interim measure, isolate the device on a restricted network segment and disable remote management access from untrusted networks.

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 846w FirmwareOperating system
Affected:= fw100a43

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

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. Confirm device model is D-Link DIR-846W
    Log into the router web interface and check the device information page, or check the physical device label for the model number
    Affected if The device is not a D-Link DIR-846W unit
  2. Identify the installed firmware version
    In the router web interface, go to Status or System Information page and look for the firmware version field
    Affected if The firmware version is FW100A43
  3. Verify the wireless SSID configuration interface is accessible
    In the router web interface, navigate to Wireless Settings or Wi-Fi Configuration section to confirm the SSID parameters can be viewed or modified
    Affected if The wireless configuration interface is accessible without authentication
  4. Check if remote web management is enabled
    In the router web interface, go to Management or Administration settings and check the Remote Management/HTTP Access setting. Determine if it allows access from external IPs or the WAN interface
    Affected if Remote management is enabled and the router web interface is accessible from untrusted networks

You are affected if you have a D-Link DIR-846W router running firmware FW100A43 with its web interface accessible, as the command injection vulnerability exists in the wl(0).(0)_ssid parameter regardless of wireless configuration.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

This is an end-of-life router with no available patch. Replace the device with a supported model or, as an interim measure, isolate the device on a restricted network segment and disable remote management access from untrusted networks.

Fix this in Dir 846w Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-44342 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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