CVE-2017-20235
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 · uneditedProSoft Technology ICX35-HWC version 1.3 and prior cellular gateways contain an authentication bypass vulnerability in the web user interface that allows unauthenticated attackers to gain access to administrative functions without valid credentials. Attackers can bypass the authentication mechanism in affected firmware versions to obtain full administrative access to device configuration and settings.
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 ProSoft Technology ICX35-HWC cellular gateway versions 1.3 and prior contain an authentication bypass vulnerability in the web user interface. Attackers can exploit this flaw to bypass the authentication mechanism entirely and gain unauthenticated administrative access to device configuration and settings, including sensitive network parameters and 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.3CVSS 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.1/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.
-
Confirm device modelIdentify the ProSoft Technology ICX35-HWC cellular gateway in your inventory or network. Check device labels, network discovery, or management interfaces to verify the exact model number.Affected if The device is an ICX35-HWC unit
-
Determine installed firmware versionAccess the device's web-based management interface or use the device's CLI/console to retrieve the current firmware version. Look for a version field in system information or status pages.Affected if Firmware version is 1.3 or prior (any version number less than 1.3)
-
Verify web interface is enabledCheck the device configuration to determine if the web-based user interface is currently enabled. This may be visible in network settings, service settings, or management access configuration.Affected if Web interface is enabled and accessible
-
Assess network exposure of web interfaceDetermine if the device web management interface is reachable from network segments outside the trusted management network. Check firewall rules, ACLs, or NAT configurations that permit access to the device HTTP/HTTPS ports.Affected if Web interface is reachable from untrusted networks or the internet
You are affected if you have an ICX35-HWC device running firmware version 1.3 or prior with the web interface enabled and exposed to any network where untrusted users could access it.
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.
dbcve · scoped1.3
Update the ICX35-HWC firmware to a version beyond 1.3 that addresses the authentication bypass. If no patched firmware is available, restrict network access to the web interface using firewalls, VPNs, or network segmentation to prevent external attackers from reaching the device management ports.
ICX35-HWC Firmware version 1.3 or later
- 1. Identify the current firmware version of the ICX35-HWC device
- 2. Navigate to the ProSoft Technology or Belden support website for ICX35-HWC firmware downloads
- 3. Download firmware version 1.3 or later from the official vendor source
- 4. Access the device web interface or console to initiate firmware update
- 5. Upload and apply the firmware version 1.3 or newer
- 6. Verify the upgrade was successful by checking the firmware version in the device admin interface
- 7. Confirm the web UI authentication is now properly enforced
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-20235 — 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-20235 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