CVE-2013-4707
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 · uneditedThe SSH implementation on D-Link Japan DES-3810 devices with firmware before R2.20.011 allows remote authenticated users to cause a denial of service (device hang) by leveraging login access.
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 confidenceThe SSH implementation on D-Link Japan DES-3810 network switches with firmware before R2.20.011 contains a denial of service vulnerability. Remote authenticated users with login access can exploit the SSH service to cause the device to hang or become unresponsive. The vulnerability is triggered through specific SSH commands or sequences sent by an authenticated user.
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<= r2.15.004= r2.00.009all versionsCVSS 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
- M
- Authentication
- Single
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:M/Au:S/C:N/I:N/A:C
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 model is D-Link DES-3810Access the switch CLI or web management interface and verify the model number displays as DES-3810. In CLI, this is typically shown in the startup banner or via 'show version' command.Affected if The device is not a DES-3810 switch, then this CVE does not apply.
-
Identify the installed firmware versionRun 'show version' in the switch CLI or check the firmware version in the web interface under the System or Administration section. Compare the firmware revision number against the affected versions: any version <= r2.15.004 or exactly r2.00.009, or if the version cannot be determined and the device is a DES-3810.Affected if Firmware version is r2.15.004 or lower, or is exactly r2.00.009, or the firmware version cannot be verified on a DES-3810 device.
-
Verify if SSH service is enabledIn the switch CLI, run 'show ip ssh' or 'show service' to check if SSH is currently enabled. Alternatively, check the web interface under SSH or Remote Access settings.Affected if SSH is enabled and accessible, providing an attack vector for the authenticated DoS vulnerability.
-
Check SSH access scopeReview the switch configuration for SSH access controls. Run 'show running-config | include ssh' or check the access list applied to the SSH service to determine if SSH is reachable from untrusted networks.Affected if SSH is enabled and accessible from untrusted or external networks, allowing remote authenticated attackers to trigger the DoS condition.
A user is affected if they are running a D-Link DES-3810 switch with firmware version r2.15.004 or lower (or exactly r2.00.009), and SSH is enabled and accessible to authenticated users.
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 dataUpgrade the device firmware to R2.20.011 or later to patch the SSH vulnerability. If immediate upgrading is not feasible, restrict SSH access to a limited set of trusted, authorized users only to reduce the attack surface.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-4707 — 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-2013-4707 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