CVE-2021-46457
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 ChgSambaUserSettings. This vulnerability allows attackers to execute arbitrary commands via the samba_name 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 confidenceCommand injection vulnerability in D-Link DIR-823-Pro v1.0.2 router allows remote attackers to execute arbitrary OS commands via the samba_name parameter in the ChgSambaUserSettings function. The lack of input sanitization on this parameter enables attackers to inject shell metacharacters and achieve full device compromise 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.
-
Identify device model and firmware versionAccess the router web interface (usually at 192.168.0.1) and navigate to Status or System Settings to find the firmware version. Alternatively, use the command 'cat /proc/version' or 'cat /etc/os-release' via telnet/ssh if available, or extract the firmware binary and search for version strings.Affected if The device is a D-Link DIR-823-Pro and the firmware version is 1.0.2 or lower.
-
Verify Samba service is enabledIn the router web interface, look for 'USB Settings' or 'Sharing' or 'Samba' under Advanced or USB Storage settings. Check if the Samba file sharing feature is turned ON or enabled.Affected if The Samba/Sharing service is enabled on the device.
-
Confirm web management interface is accessibleAttempt to access the router's HTTP/HTTPS management interface from the network. Check if port 80 or 443 is open and responding. From a remote perspective, test if the router's public IP on ports 80/443 accepts connections.Affected if The router's web management interface (port 80/443) is accessible from the network where the attacker would be.
-
Check for exposure of management interfaceReview any port forwarding rules or firewall configurations that may expose the router's web interface to the WAN/Internet. Use an external port scanner to check if ports 80/443 are open to the public Internet.Affected if The router management interface is exposed to the WAN (Internet) or an untrusted network.
A user is affected if they have a D-Link DIR-823-Pro router running firmware version 1.0.2 or lower with the Samba/Sharing service enabled and its management interface accessible to the attacker.
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.
dbcve · scopedIf available, apply vendor firmware update from D-Link. Otherwise, disable the affected Samba/Sharing service if possible, restrict management interface access to trusted IPs only via firewall rules, or replace the end-of-life device.
D-Link DIR-823 Pro firmware version > 1.0.2 (check D-Link support for latest available version)
- 1. Visit D-Link's official support page at www.dlink.com or supportannouncement.us.dlink.com
- 2. Search for the DIR-823 Pro product and check for available firmware updates
- 3. Download the latest available firmware version (version higher than 1.0.2)
- 4. Access the device web management interface
- 5. Navigate to the firmware upgrade or administration section
- 6. Upload and apply the new firmware file
- 7. After the upgrade completes, verify the device is functioning normally
- 8. Confirm the samba_name parameter functionality works as expected
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2021-46457 — 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-46457 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