CVE-2016-1140
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 · uneditedKDDI HOME SPOT CUBE devices before 2 allow remote attackers to conduct clickjacking attacks via unspecified vectors.
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 · moderate confidenceKDDI HOME SPOT CUBE devices prior to version 2 contain a clickjacking vulnerability in their web interface. Attackers can exploit this by overlaying invisible or disguised iframe elements atop legitimate interface controls, tricking users into performing unintended actions such as changing router settings or credentials.
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= 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 the device modelConfirm you are using a KDDI HOME SPOT CUBE router by checking the device label or admin interface.Affected if Device is not a KDDI HOME SPOT CUBE, the vulnerability does not apply.
-
Check the firmware versionAccess the router's web admin interface (typically at http://192.168.0.1 or http://192.168.1.1) and navigate to the system or status page to view the firmware version. Alternatively, check the device documentation or label for the firmware version.Affected if Firmware version is before 2.0 (or is the affected version 2.0 if that is the vulnerable release). Compare your installed version to the affected ranges provided.
-
Verify if the web interface is accessibleAttempt to access the router's web admin interface over HTTP/HTTPS from a browser.Affected if The web interface is not accessible, the clickjacking vulnerability cannot be exploited.
-
Inspect X-Frame-Options headerUse browser developer tools or a command-line tool (e.g., curl -I http://<router-ip>) to inspect the HTTP response headers from the router's web interface. Look for the X-Frame-Options header.Affected if The X-Frame-Options header is missing or set to a value other than DENY or SAMEORIGIN (e.g., ALLOW-FROM uri), indicating the page can be framed.
-
Inspect Content-Security-Policy headerUsing the same method as step 4, inspect the Content-Security-Policy header in HTTP responses from the router. Look for the frame-ancestors directive.Affected if The Content-Security-Policy header is missing or does not include frame-ancestors directive restricting framing, allowing the page to be embedded in iframes.
The device is affected if it is a KDDI HOME SPOT CUBE with a vulnerable firmware version AND its web interface lacks X-Frame-Options and CSP frame-ancestors protections, allowing the page to be framed by attackers.
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 dataImplement X-Frame-Options: DENY or SAMEORIGIN header and Content Security Policy with frame-ancestors directive in all HTTP responses from the device's web server. Deploy firmware update to all affected devices.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1140 — 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-2016-1140 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