CVE-2021-46455
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 SetStationSettings. This vulnerability allows attackers to execute arbitrary commands via the station_access_enable 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 confidenceD-Link DIR-823-Pro v1.0.2 firmware contains a command injection vulnerability in the SetStationSettings function. The station_access_enable parameter is not properly sanitized before being passed to a system call, allowing an attacker to inject arbitrary shell commands with root privileges on the device.
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.
-
Identify the device modelAccess the device's web administration interface or check the device label/marketing to confirm the exact model is D-Link DIR-823-ProAffected if The device model is D-Link DIR-823-Pro
-
Check the firmware versionLog into the device's web interface and navigate to the Status or System Information page to view the firmware version, or use the command line if accessible (e.g., cat /proc/version or similar). Compare the version to the affected range: <= 1.0.2Affected if The firmware version is 1.0.2 or lower
-
Verify the vulnerable feature is accessibleLocate the wireless settings or Station Settings page in the device's web interface. The vulnerability exists in the SetStationSettings function where the station_access_enable parameter is processed.Affected if The wireless/station settings interface is accessible (typically via the device's web administration panel)
-
Confirm remote management is enabledCheck the device's Administration or Management settings to see if the web interface is exposed on WAN (remote management). The vulnerability can be exploited remotely if remote management is enabled.Affected if Remote management/WAN access to the web interface is enabled, allowing unauthenticated or low-privilege attackers to reach the vulnerable function
The device is affected if it is a D-Link DIR-823-Pro running firmware version 1.0.2 or lower, and the web administration interface (particularly the wireless/station settings) is accessible either locally or remotely.
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 the vendor-supplied firmware update when available. Until patched, disable remote management interfaces and restrict network access to the device's administration interface.
- Consultation2.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 $1,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-46455 — 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-46455 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