LiveActive security incident?Get immediate response
CVE Record

CVE-2017-20223: Telesquare SKT LTE Router SDT-CS3B1 Insecure Direct Object Reference

Telesquare SKT LTE Router SDT-CS3B1 firmware version 1.2.0 contains an insecure direct object reference vulnerability that allows attackers to bypass authorization and access resources by manipulating user-supplied input parameters. Attackers can directly reference objects in the system to retrieve sensitive information and access functionalities without proper access controls.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2017-20223 affects Telesquare SKT LTE Router SDT-CS3B1 firmware 1.2.0. It allows unauthenticated network attackers to bypass authorization by changing input parameters, potentially exposing sensitive information and router functions. Public exploit references exist, but the provided sources do not show confirmed active exploitation.

Executive priority

Treat as urgent if these routers are deployed or internet-accessible. The vulnerability is critical, remotely reachable, unauthenticated, and has public exploit references. If the product is not present, business risk is low.

Technical view

The issue is an insecure direct object reference, CWE-639, in SDT-CS3B1 firmware 1.2.0. The CVSS 3.1 score is 9.8, with network attack vector, low complexity, no privileges, and no user interaction. Impact is rated high for confidentiality, integrity, and availability.

Likely exposure

Exposure is limited to organizations using Telesquare SDT-CS3B1 routers running firmware 1.2.0, especially if management interfaces are reachable from untrusted networks. The sources do not identify other affected models or versions.

Exploitation context

Exploit listings are cited by Exploit-DB and Packet Storm, indicating public exploit information exists. CISA KEV status is not indicated, and the provided sources do not confirm exploitation in the wild.

Researcher notes

Sources describe an IDOR authorization bypass in firmware 1.2.0 but do not provide vendor remediation details in the bundle. Avoid assuming patch availability. Focus validation on asset presence, firmware version, management exposure, and access-control logs.

Mitigation direction

  • Identify any Telesquare SDT-CS3B1 devices and confirm firmware version.
  • Restrict router management access to trusted administrative networks only.
  • Remove direct internet exposure for affected management interfaces.
  • Check Telesquare or device-provider guidance for firmware updates or replacement advice.
  • Monitor affected devices for unauthorized configuration changes or access attempts.

Validation and detection

  • Inventory edge and cellular routers for SDT-CS3B1 model identifiers.
  • Confirm whether firmware version 1.2.0 is installed.
  • Review firewall rules for exposed router administration services.
  • Check logs for suspicious access to administrative resources.
  • Document compensating controls if no vendor fix is available.
Prepared
Confidence
high
Sources
8

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-639: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-20223 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
7Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2017-20223Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
TelesquareSDT-CS3B11.2.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-639 · source CWE mapping

Authorization Bypass Through User-Controlled Key

Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.