CVE-2018-13311
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 · uneditedSystem command injection in formDlna in TOTOLINK A3002RU version 1.0.8 allows attackers to execute system commands via the "sambaUser" POST 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 confidenceTOTOLINK A3002RU firmware 1.0.8 contains a command injection vulnerability in the formDlna handler. The 'sambaUser' POST parameter is not properly sanitized before being passed to a system call, allowing an attacker to inject arbitrary shell commands. This is a pre-authentication or easily exploitable flaw given the CVSS vector suggests network-level access without user interaction.
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.8CVSS 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.0/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 model is TOTOLINK A3002RUAccess the device web interface or check the device label/marketing to identify the exact model numberAffected if Device is not a TOTOLINK A3002RU (different models are not affected by this specific CVE)
-
Check installed firmware versionLog into the device web interface and navigate to System Status or Administration > Firmware Upgrade to view the current firmware version; alternatively, check via command line if SSH/Telnet access is availableAffected if Firmware version is exactly 1.0.8 (this is the only version listed as affected)
-
Verify web management interface is accessibleAttempt to access the device IP address via HTTP/HTTPS in a web browser to confirm the web interface is reachableAffected if Web interface is exposed on the network (the vulnerability is exploitable through the formDlna handler on the web interface)
-
Check if DLNA or Samba service is enabledLog into the web interface and look for DLNA or Media Sharing settings under Network or USB/Storage sections; the vulnerability exists in the formDlna handlerAffected if DLNA or Samba service is enabled (the flaw is in the formDlna handler that processes these settings)
A user is affected if they have a TOTOLINK A3002RU device running firmware version 1.0.8 with the web management interface accessible and DLNA/Samba service 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 dataApply vendor firmware update if available; otherwise, disable the DLNA/samba service or restrict network access to the device's management interface. Implement strict input validation on all form parameters before passing to shell commands.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13311 — 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-2018-13311 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