CVE-2024-44341
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 · uneditedD-Link DIR-846W A1 FW100A43 was discovered to contain a remote command execution (RCE) vulnerability via the lan(0)_dhcps_staticlist 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 confidenceD-Link DIR-846W A1 router firmware FW100A43 contains an unauthenticated remote command execution vulnerability in the DHCP static lease configuration parameter lan(0)_dhcps_staticlist. Attackers achieve RCE by sending crafted POST requests with malicious command payloads to this parameter.
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= fw100a43CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the router modelAccess the router web interface or physically inspect the device label to confirm the model is D-Link DIR-846W A1Affected if The device is a D-Link DIR-846W A1 unit
-
Check the installed firmware versionLog into the router web interface and navigate to the Status or Management section to view the firmware version. Compare against FW100A43Affected if The firmware version is FW100A43
-
Verify if the router web interface is remotely accessibleCheck the router administration settings for any 'Remote Management' or 'Web Access' options that allow access from WAN/outside the local networkAffected if Remote management is enabled and the router admin interface is accessible from WAN
-
Check if the DHCP static lease feature is exposedAttempt to access the DHCP settings page in the router web interface and locate the static lease configuration parameter lan(0)_dhcps_staticlistAffected if The lan(0)_dhcps_staticlist parameter exists and is reachable via the web interface
-
Confirm network exposure of management interfaceTest if the router's web administration port (typically 80/443) is reachable from outside the local network by attempting a connection to the public IPAffected if The router admin interface responds to requests from external IPs
A user is affected if they are running firmware FW100A43 on a D-Link DIR-846W router with the web interface exposed to network locations where an attacker can reach the lan(0)_dhcps_staticlist parameter.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor firmware update if available; if no update exists, disable remote administration interfaces, implement network segmentation to restrict access to router management plane, and monitor for exploitation attempts.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-44341 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-44341 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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