CVE-2017-2183
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 · uneditedHOME SPOT CUBE2 firmware V101 and earlier allows authenticated attackers to execute arbitrary OS commands via Clock Settings.
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 confidenceAuthenticated command injection vulnerability in HOME SPOT CUBE2 router firmware V101 and earlier. The Clock Settings functionality in the web interface fails to properly sanitize user input, allowing authenticated attackers to inject and execute arbitrary operating system 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= v100= v101CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:A/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 device model is HOME SPOT CUBE2Check the router device label, web interface header, or administrative status page to verify the exact model name. Compare against the affected product list.Affected if Device model is Kddi Home Spot Cube 2
-
Check installed firmware versionAccess the router web interface (typically at http://192.168.0.1 or http://192.168.1.1), navigate to the firmware version or system status page. Record the exact firmware version number displayed.Affected if Firmware version is v100 or v101
-
Verify Clock Settings feature existsLog into the router administrative interface and locate the Clock Settings or NTP configuration page within the web management interface.Affected if Clock Settings functionality is present and accessible in the web interface
-
Confirm web interface is remotely accessibleCheck if the router HTTP/HTTPS ports (80/443) are listening on external interfaces using 'netstat -an' or by scanning external IP ports.Affected if Web administration interface is exposed beyond the local network
-
Check if default credentials are in useAttempt login to the web interface using default administrative credentials (check vendor documentation for default username/password). Compare against credentials currently configured.Affected if Default credentials are still active or easily guessable credentials are in use
Device is affected if it is a Kddi Home Spot Cube 2 router running firmware v100 or v101 with the Clock Settings web feature accessible using default or weak 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 dataApply vendor firmware update when available. As a compensating control, restrict administrative access to the web interface to trusted IP addresses only and change default credentials.
- Consultation3.0 h
- Implementation6.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2183 — 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-2183 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