CVE-2017-20224
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 · uneditedTelesquare SKT LTE Router SDT-CS3B1 version 1.2.0 contains an arbitrary file upload vulnerability that allows unauthenticated attackers to upload malicious content by exploiting enabled WebDAV HTTP methods. Attackers can use PUT, DELETE, MKCOL, MOVE, COPY, and PROPPATCH methods to upload executable code, delete files, or manipulate server content for remote code execution or denial of service.
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 Telesquare SKT LTE Router SDT-CS3B1 v1.2.0 has WebDAV enabled with unauthenticated write access, allowing attackers to use HTTP methods PUT, DELETE, MKCOL, MOVE, COPY, and PROPPATCH to upload executable files, delete content, or manipulate server data for remote code execution.
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.2.0CVSS 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.
-
Confirm device model and firmware versionAccess the router admin interface or check the device label for 'Telesquare SDT-CS3B1' and verify the firmware version is 1.2.0. This can also be done via SNMP, telnet, or by examining the device's web interface for version information.Affected if The device is a Telesquare SDT-CS3B1 router running firmware version 1.2.0
-
Identify if WebDAV service is enabledCheck the router's web configuration interface for WebDAV settings, or attempt to access the WebDAV service by sending a request to common WebDAV paths such as /webdav/ or /dav/ on the router's IP address.Affected if WebDAV is enabled and accessible on the router
-
Test unauthenticated WebDAV accessSend an HTTP OPTIONS request to the WebDAV endpoint without providing any authentication credentials. Alternatively, attempt a simple GET request to a known WebDAV path.Affected if The WebDAV service responds without requiring authentication
-
Verify write methods are allowed without authenticationTest each of the following HTTP methods against the WebDAV endpoint without authentication: PUT (upload), DELETE (remove), MKCOL (create directory), MOVE (rename/move), COPY (duplicate), PROPPATCH (modify properties). Use a tool like curl: curl -X PUT http://<router-ip>/webdav/test.txtAffected if Any of the methods PUT, DELETE, MKCOL, MOVE, COPY, or PROPPATCH succeed without authentication
The environment is affected if the Telesquare SDT-CS3B1 router is running firmware 1.2.0 and WebDAV with unauthenticated write access is enabled, allowing any of the listed HTTP methods without credentials.
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 WebDAV if not required, or implement authentication and restrict allowed HTTP methods; apply firmware updates if available.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-20224 — 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-2017-20224 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