CVE-2017-3192
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 · uneditedD-Link DIR-130 firmware version 1.23 and DIR-330 firmware version 1.12 do not sufficiently protect administrator credentials. The tools_admin.asp page discloses the administrator password in base64 encoding in the returned web page. A remote attacker with access to this page (potentially through a authentication bypass such as CVE-2017-3191) may obtain administrator credentials for the device.
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 confidenceThe D-Link DIR-130 (firmware 1.23) and DIR-330 (firmware 1.12) routers have a credential disclosure vulnerability in the tools_admin.asp web page. This page returns the administrator password in base64-encoded format within the HTML response, allowing remote attackers who can access the page to obtain plaintext admin 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= 1.23= 1.12CVSS 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 modelCheck the device label or web interface to confirm it is a D-Link DIR-130 or DIR-330 routerAffected if Device is not a DIR-130 or DIR-330 model
-
Check firmware versionAccess the router web interface and navigate to the Status or Administration section to view the firmware version. Alternatively, check the device label or use the router's upgrade page.Affected if Firmware version is 1.23 for DIR-130 or 1.12 for DIR-330
-
Access the vulnerable pageUsing a web browser or HTTP client, navigate to the tools_admin.asp page on the router's web interface (typically http://<router_ip>/tools_admin.asp)Affected if Page is accessible without authentication or with low-privilege credentials
-
Inspect HTML response for base64 passwordView the page source or HTTP response body and search for a base64-encoded string that decodes to the administrator password. Look for patterns like 'admin' or similar credentials in base64 format within hidden form fields or script blocks.Affected if A base64-encoded password string is present in the HTML response that decodes to the admin password
A user is affected if they have a D-Link DIR-130 (firmware 1.23) or DIR-330 (firmware 1.12) router where the tools_admin.asp page displays a base64-encoded administrator password in the HTML source.
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 dataUpgrade affected devices to patched firmware if available; if no patch exists, replace devices or restrict web management interface access to trusted networks only. The description indicates this vulnerability may be exploitable through authentication bypass CVE-2017-3191, so addressing that as well is recommended.
- Consultation4.0 h
- Implementation8.0 h
- Testing3.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3192 — 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-3192 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