CVE-2017-17463
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 · uneditedVivo modems allow remote attackers to obtain sensitive information by reading the index.cgi?page=wifi HTML source code, as demonstrated by ssid and psk_wepkey fields.
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 confidenceVivo modem web interface (index.cgi?page=wifi) exposes sensitive WiFi configuration parameters including SSID and PSK/WEP keys directly in the HTML source code. An unauthenticated remote attacker can retrieve this information by requesting the page and viewing the HTML, enabling WiFi credential theft.
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 dataall versionsCVSS 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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 if target is a Vivo modem web interfaceAccess the device's main web page and check for Vivo branding, or probe common Vivo modem IP ranges (such as 192.168.1.1/24) and check HTTP response headers for 'Vivo' or 'modem' identifiersAffected if The device is a Vivo modem with a web interface accessible on the local network
-
Access the wifi configuration endpoint without authenticationNavigate to index.cgi?page=wifi or similar paths like /wifi.htm, /wireless.htm, or /wireless.cgi on the modem's IP address using HTTP (no login required)Affected if The page loads and displays WiFi configuration without requiring authentication credentials
-
Inspect HTML source for exposed SSIDView the page source (right-click > View Page Source or use browser dev tools) and search for 'ssid' or 'SSID' in the HTML. The SSID value should be visible in an input field value or JavaScript variableAffected if The SSID is readable in plaintext within the HTML source without any server-side rendering or masking
-
Inspect HTML source for exposed wireless keysIn the page source, search for 'psk', 'wep', 'key', 'password', or 'passphrase' parameters. Check input field values and JavaScript variables for the WiFi password in plaintextAffected if PSK, WEP keys, or WiFi passwords appear in plaintext within the HTML source rather than being retrieved via server-side API calls
If you can access the wifi configuration page without authentication and view SSID and WiFi keys in plaintext within the HTML source, your environment is affected by this CVE.
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 unauthenticated access to the modem web interface, remove sensitive credentials from client-side HTML exposure, and implement server-side rendering for sensitive configuration data.
- 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-2017-17463 — 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-17463 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