CVE-2018-15553
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 · uneditedfileshare.cmd on Telus Actiontec T2200H T2200H-31.128L.03 devices allows OS Command Injection via shell metacharacters in the smbdUserid or smbdPasswd field.
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 Telus Actiontec T2200H router firmware version T2200H-31.128L.03 contains an OS command injection vulnerability in the fileshare.cmd web interface. The smbdUserid and smbdPasswd parameters accept shell metacharacters without proper sanitization, allowing authenticated attackers to inject and execute arbitrary OS commands 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= t2200h-31.128l.03CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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 router model is Telus Actiontec T2200HLog into the router web interface and check the device info or status page, or look for the model label on the physical deviceAffected if The device is not a Telus Actiontec T2200H router
-
Check firmware version equals T2200H-31.128L.03In the router web interface, navigate to System Info or Firmware Version (typically under Maintenance or Status). Compare the displayed version string to T2200H-31.128L.03Affected if Firmware version is exactly T2200H-31.128L.03
-
Verify fileshare SMB feature is enabledNavigate to the fileshare or SMB configuration page in the web interface (often under USB/Storage or Shared Folders settings). Check if the SMB service is turned on or configuredAffected if Fileshare/SMB feature is enabled and accessible to the attacker
-
Confirm web management interface is accessibleAttempt to access the router login page at the device IP address (commonly 192.168.1.1). Verify the fileshare.cmd endpoint is reachableAffected if The router web interface and fileshare.cmd are accessible from the attacker's network location
You are affected if you have a Telus Actiontec T2200H router running firmware version T2200H-31.128L.03 with the fileshare/SMB feature enabled and the web interface accessible to an authenticated user.
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-supplied firmware update when available; if no update exists, consider network segmentation or device replacement to reduce exposure, as this vulnerability can be exploited by users with access to the fileshare configuration interface.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.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 $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-15553 — 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-15553 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