dbcve.org
Ininet WebserverApplication · Spidercontrol

CVE-2017-13995

CRITICAL · 10.0 CVSS v3.0 Published 2017-10-05
Fix available
A fix is available. Upgrade to after 2.02.0000 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
An Improper Authentication issue was discovered in iniNet Solutions iniNet Webserver, all versions prior to V2.02.0100. The webserver does not properly authenticate users, which may allow a malicious attacker to access sensitive information such as HMI pages or modify PLC variables.

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 confidence

The iniNet Webserver has improper authentication that allows unauthenticated attackers to access HMI pages and modify PLC variables. This is a critical authentication bypass affecting all versions prior to V2.02.0100.

MitigationUpgrade to version V2.02.0100 or later to remediate. Until upgrade is possible, implement compensating controls such as network segmentation, firewall rules restricting webserver access to trusted networks, and monitoring for unauthorized access attempts.

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
Ininet WebserverApplication
Affected:<= 2.02.0000

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
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/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. Identify the Spidercontrol iniNet Webserver version
    Locate the webserver installation and check the version information, typically found in the software's about page, version file, or server banner response
    Affected if The installed version is 2.02.0000 or any version prior to V2.02.0100
  2. Verify webserver is running and accessible
    Confirm the webserver is operational by accessing its base URL or checking if the HTTP service is listening on the configured port
    Affected if The webserver is running and reachable (required for exploitation)
  3. Confirm authentication is enforced on HMI endpoints
    Attempt to access HMI pages and PLC variable modification interfaces without providing credentials
    Affected if HMI pages and PLC variable modification features are accessible without authentication
  4. Check network exposure of the web interface
    Review firewall rules, network configuration, or NAT settings to determine if the webserver is exposed to untrusted networks
    Affected if The webserver is accessible from networks outside the trusted administrative zone

If the installed version is 2.02.0000 or lower and the webserver is network-accessible, the authentication bypass vulnerability is present and exploitable.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2.02.0000
Interim mitigation

Upgrade to version V2.02.0100 or later to remediate. Until upgrade is possible, implement compensating controls such as network segmentation, firewall rules restricting webserver access to trusted networks, and monitoring for unauthorized access attempts.

Recommended fix High confidence

V2.02.0100 (or latest available version)

  1. 1. Identify all deployments of iniNet Solutions iniNet Webserver versions prior to V2.02.0100 in the environment.
  2. 2. Obtain the patched version V2.02.0100 or later from the vendor (iniNet Solutions).
  3. 3. Test the upgrade in a non-production environment to verify functionality.
  4. 4. Schedule maintenance window for production upgrade.
  5. 5. Back up current configuration and data before performing upgrade.
  6. 6. Upgrade iniNet Webserver to version V2.02.0100 or latest available version.
  7. 7. Verify the upgrade was successful and authentication is functioning properly.
  8. 8. Confirm that HMI pages and PLC variable access now require proper authentication.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ininet Webserver Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-13995 — 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-13995 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