CVE-2017-3191
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 are vulnerable to authentication bypass of the remote login page. A remote attacker that can access the remote management login page can manipulate the POST request in such a manner as to access some administrator-only pages such as tools_admin.asp without credentials.
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 confidenceD-Link DIR-130 (firmware 1.23) and DIR-330 (firmware 1.12) routers contain an authentication bypass vulnerability in their remote management web interface. A remote attacker can manipulate POST requests to the login page to bypass authentication and access administrator-only pages such as tools_admin.asp without valid 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 the router model and firmware versionAccess the router's web administration interface and navigate to the Status or Device Info page to view the firmware version. Alternatively, check the label on the device or consult the administration documentation.Affected if The device is a D-Link DIR-130 running firmware 1.23 or a D-Link DIR-330 running firmware 1.12.
-
Confirm remote management is enabledIn the router web interface, go to the Remote Management or Web Management settings (usually under Advanced or Tools) and verify if remote access from the WAN/Internet is permitted.Affected if Remote management access from untrusted networks is enabled on the device.
-
Check if the login page is exposed to the networkAttempt to access the router's login page from an external network by entering the router's public IP address in a web browser. Look for the login.php or similar login endpoint.Affected if The router's web administration interface is reachable from untrusted networks.
-
Verify access to protected administrative pagesAttempt to navigate directly to tools_admin.asp or similar administrator-only pages without providing credentials to see if authentication is bypassed.Affected if Protected pages are accessible without authentication.
You are affected if you have a D-Link DIR-130 (firmware 1.23) or DIR-330 (firmware 1.12) router with remote management enabled and the web interface is accessible from untrusted networks.
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 dataIf devices are still in production, disable remote management access from the internet immediately. Contact D-Link for available firmware patches; if no patch exists, replace end-of-life devices with supported hardware.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3191 — 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-3191 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