dbcve.org
4gt101w SoftwareApplication · Netcomm

CVE-2017-11646

HIGH · 8.8 CVSS v3.0 Published 2017-07-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
NetComm Wireless 4GT101W routers with Hardware: 0.01 / Software: V1.1.8.8 / Bootloader: 1.1.3 are vulnerable to CSRF attacks, as demonstrated by using administration.html to disable the firewall. They does not contain any token that can mitigate CSRF vulnerabilities within 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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in NetComm Wireless 4GT101W routers allows remote attackers to trick authenticated administrators into unknowingly executing administrative actions (such as disabling the firewall) via malicious web pages. The device's web interface at administration.html lacks anti-CSRF tokens, providing no protection against this attack vector.

MitigationSince this is a firmware-level vulnerability in an older embedded device and the vendor may not provide patches, recommended mitigations include network segmentation to isolate the router, enforcing browser-side CSRF protections if available, and potentially replacing the affected device with a newer model that receives security updates. The primary fix requires vendor-supplied firmware with CSRF token implementation.

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
4gt101w SoftwareApplication
Affected:= 1.1.8.8
4gt101w BootloaderOperating system
Affected:= 1.1.3

CVSS 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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device model
    Access the router's web interface or check the device label to verify the model is NetComm 4GT101W
    Affected if The device is not a NetComm 4GT101W router, then it is not affected by this specific CVE
  2. Check firmware version
    Log into the router web interface and navigate to the status or system information page to view the installed Software version
    Affected if The installed Software version is exactly 1.1.8.8 - this version is affected
  3. Check bootloader version
    Log into the router web interface and navigate to the status or system information page to view the installed Bootloader version
    Affected if The installed Bootloader version is exactly 1.1.3 - this version is affected
  4. Verify web administration is accessible
    Attempt to access the router's web interface at the administration.html endpoint using HTTP
    Affected if The web interface is accessible remotely and the device is running affected firmware versions, the CSRF vulnerability can be exploited
  5. Check for CSRF token presence
    View the HTML source code of the administration.html page and examine forms to determine if anti-CSRF tokens or unique request tokens are included in administrative form submissions
    Affected if No anti-CSRF tokens are present in administrative forms, the device is vulnerable to CVE-2017-11646

If the device is a NetComm 4GT101W running Software version 1.1.8.8 or Bootloader version 1.1.3 and the administration.html page lacks CSRF tokens, the environment is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since this is a firmware-level vulnerability in an older embedded device and the vendor may not provide patches, recommended mitigations include network segmentation to isolate the router, enforcing browser-side CSRF protections if available, and potentially replacing the affected device with a newer model that receives security updates. The primary fix requires vendor-supplied firmware with CSRF token implementation.

Fix this in 4gt101w Software Scoped from the published advisory
  • Consultation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,610
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,576.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-11646 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-11646 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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