CVE-2017-8877
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 · uneditedASUS RT-AC* and RT-N* devices with firmware through 3.0.0.4.380.7378 allow JSONP Information Disclosure such as the SSID.
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 confidenceASUS RT-AC* and RT-N* routers with firmware through 3.0.0.4.380.7378 contain a JSONP information disclosure vulnerability. The affected devices expose sensitive network configuration data such as SSIDs through JSONP endpoints that can be accessed by unauthorized users due to improper cross-origin request handling.
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= 3.0.0.4.380.7266CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/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.
-
Confirm router model and firmware versionAccess the router's web administration interface (typically at 192.168.1.1) and navigate to the Administration > Firmware Upgrade or System section to view the current firmware version. Alternatively, check the ASUS support website for your specific model.Affected if Firmware version matches 3.0.0.4.380.7266 or falls within the affected range up to 3.0.0.4.380.7378
-
Identify exposed JSONP endpointsSend HTTP requests to common ASUS router API endpoints such as /router_info.xml, /jsonp/SSLVPNConfig, /applydb.cgi with parameters that typically return network configuration data (e.g., need to check for .jsonp or callback parameters in the response).Affected if The router returns JSONP responses containing sensitive data like SSIDs, wireless passwords, or network configuration when queried without authentication or with cross-origin headers
-
Test for cross-origin request vulnerabilitySend a request to the JSONP endpoint with an Origin header set to an arbitrary domain (e.g., Origin: http://malicious-site.com). Check if the response includes Access-Control-Allow-Origin headers that allow cross-origin access, or if the JSONP callback executes regardless of origin.Affected if The router returns Access-Control-Allow-Origin headers reflecting the requested origin, or returns JSONP data that can be accessed by scripts from any domain
-
Verify unauthorized access to sensitive dataWithout logging in, attempt to access endpoints that typically require authentication (like those returning WPS PIN, SSID, or WPA keys). Observe if the router returns this information in JSONP format without requiring proper authentication.Affected if Sensitive network configuration data (SSIDs, wireless keys, WPS PINs) is returned in JSONP responses without authentication
A user is affected if they are running firmware version 3.0.0.4.380.7266 up to 3.0.0.4.380.7378 on an ASUS RT-AC or RT-N router and the JSONP endpoints return sensitive network configuration data to unauthenticated or cross-origin requests.
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 dataUpdate ASUS router firmware to a version beyond 3.0.0.4.380.7378. If no patch is available, restrict external access to the router's web management interface and consider network segmentation.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8877 — 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-8877 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