CVE-2013-4855
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-865L has SMB Symlink Traversal due to misconfiguration in the SMB service allowing symbolic links to be created to locations outside of the Samba share.
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 · moderate confidenceThe D-Link DIR-865L router has a misconfigured SMB service that allows symbolic links to traverse outside the designated Samba share, enabling attackers to access arbitrary files on the device's filesystem.
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 dataall 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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 modelCheck the router label or web interface for the exact model number (DIR-865L). Access the admin panel at the default gateway IP and look for the model/version information in the status or system settings.Affected if The device is a D-Link DIR-865L router (all firmware versions are affected)
-
Verify SMB service is enabledAttempt to connect to the router on TCP port 445 (SMB) or port 139 (NetBIOS) using a tool like smbclient or by mounting the share: smbclient -L //<router-ip>/Affected if The SMB service responds and accepts connections, indicating it is enabled on the device
-
Check for anonymous/guest SMB accessUse smbclient with no credentials or as guest: smbclient -L //<router-ip>/ -U guest or smbclient -L //<router-ip>/ -NAffected if Anonymous or guest access is allowed, confirming the SMB service is exposed without authentication
-
Test for symlink traversal vulnerabilityMount or browse the SMB share and attempt to access paths outside the share root (e.g., try to access /../ or traverse to parent directories). Use a tool like smbclient to navigate: cd .. or attempt to access absolute paths like /etc/Affected if Symbolic link traversal is possible and files outside the designated share can be accessed or listed
-
Inspect SMB configuration if accessibleIf you have admin access to the router, check the Samba/SMB configuration files (typically /etc/smb.conf or similar) for 'wide links' or 'follow symlinks' settings. On the web interface, look for SMB sharing settings.Affected if The configuration shows 'wide links = yes' or 'follow symlinks = yes' without proper 'wide links = no' restrictions, or no symlink containment is configured
If the device is a D-Link DIR-865L with SMB service enabled and accessible, the symlink traversal vulnerability is present and arbitrary filesystem access is possible.
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 dataDisable the SMB service if not required, or configure Samba to disallow symlinks pointing outside the share. Apply any vendor firmware updates if available.
- 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-4855 — 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-4855 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