CVE-2021-46453
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 device D-Link DIR-823-Pro v1.0.2 was discovered to contain a command injection vulnerability in the function SetStaticRouteSettings. This vulnerability allows attackers to execute arbitrary commands via the staticroute_list parameter.
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 confidenceA command injection vulnerability exists in the D-Link DIR-823-Pro v1.0.2 router firmware. The SetStaticRouteSettings function fails to properly sanitize input passed through the staticroute_list parameter, allowing an attacker to inject and execute arbitrary operating system commands with root privileges.
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<= 1.0.2CVSS 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.
-
Confirm device modelIdentify the router model through web interface, device label, or by accessing the management panel and checking the device info pageAffected if Device is not a D-Link DIR-823-Pro router - different models are not affected by this specific vulnerability
-
Check firmware versionAccess the router web management interface (typically at 192.168.0.1) and navigate to the firmware or status page to view the installed firmware version. Alternatively, check the device label or extract firmware from the device.Affected if Firmware version is 1.0.2 or lower - versions at or below this threshold are vulnerable
-
Verify web management interface is accessibleAttempt to reach the router web interface via HTTP on the local network. The vulnerability is exploited through the web management CGI interface.Affected if Web interface is accessible and responds - the command injection occurs through the HTTP POST request to SetStaticRouteSettings
-
Confirm static routing feature is presentNavigate to the router web management interface and locate the static routing or routing settings section. The vulnerability is triggered through the staticroute_list parameter in SetStaticRouteSettings.Affected if Static routing feature exists and is accessible in the web interface - this is the attack surface for the vulnerability
-
Assess network exposure of management interfaceCheck if the router web management interface is exposed to untrusted networks (WAN). The vulnerability can be exploited by anyone who can reach the management interface.Affected if Management interface is exposed beyond the local network - external attackers could exploit this vulnerability if the interface is WAN-accessible
A user is affected if they have a D-Link DIR-823-Pro router running firmware version 1.0.2 or lower, with the web management interface accessible and the static routing feature enabled.
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 dataD-Link has discontinued support for this device; no official firmware patch is available. Implement compensating controls such as network segmentation to isolate the device, disable the static routing feature if unused, or replace the end-of-life device with a currently supported model.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2021-46453 — 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-2021-46453 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