CVE-2018-12526
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 SDT-CS3B1 and SDT-CW3B1 devices through 1.2.0 have a default factory account. Remote attackers can obtain access to the device via TELNET using a hardcoded account.
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 confidenceTelesquare SDT-CS3B1 and SDT-CW3B1 wireless router/IoT devices through firmware version 1.2.0 contain a hardcoded default account with static credentials. This account is accessible remotely via the TELNET service, allowing unauthenticated attackers to gain full device access.
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.0<= 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.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.
-
Identify device model and firmware versionAccess the device's web interface or check the device label to confirm the model is SDT-CS3B1 or SDT-CW3B1. Access the firmware version through the admin panel (typically under Status, System, or About section) or via TELNET using vendor-provided commands.Affected if The device is a Telesquare SDT-CS3B1 or SDT-CW3B1 with firmware version 1.2.0 or lower.
-
Verify TELNET service accessibilityAttempt to connect to the device's IP address on port 23 (TELNET) from an external or internal network location using a TELNET client or tool such as 'telnet <device_ip>' or 'nc -zv <device_ip> 23'.Affected if Port 23/TELNET is open and reachable on the device.
-
Check for the hardcoded default accountLog in via the exposed TELNET service using the known default credentials. If credentials are unknown, inspect any configuration dumps, backup files, or firmware images for hardcoded username/password strings.Affected if A default account exists and grants full device access via TELNET without requiring prior authentication changes.
-
Confirm credential persistenceAfter accessing the device, verify whether the default credentials have been changed by examining user accounts in the device firmware or admin panel, or by attempting to change the password through the web interface or CLI.Affected if The default hardcoded account credentials remain unchanged from the factory defaults.
The device is affected if it is a Telesquare SDT-CS3B1 or SDT-CW3B1 running firmware version 1.2.0 or lower, has TELNET port 23 exposed, and retains the hardcoded default account credentials without modification.
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 dataImmediately change default credentials for any exposed device and disable TELNET if not required. Contact Telesquare for firmware updates addressing the hardcoded account, and consider network segmentation to limit exposure of management interfaces.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-12526 — 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-12526 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