# CVE-2017-13995: Auth bypass in iniNet Solutions GmbH SCADA Webserver

> Attackers can bypass authentication to access sensitive HMI pages and modify PLC variables in iniNet Solutions SCADA Webserver.

- **Severity:** Critical 10.0 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mvv4-fjq9-c9h3

## What is CVE-2017-13995?

CVE-2017-13995 is a critical authentication bypass vulnerability in iniNet Solutions GmbH SCADA Webserver, published on 4 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2017-13995?

It affects 1 product.


Products: Spidercontrol Ininet Webserver.

## How do I fix CVE-2017-13995?

No fix has been published for CVE-2017-13995 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-13995 being exploited?

There is no known exploitation of CVE-2017-13995 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-13995 and fix it if it is affected.

What it is: CVE-2017-13995 is a critical authentication bypass vulnerability in iniNet Solutions GmbH SCADA Webserver, published on 4 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-13995 in the wild and no public exploit code.

Affected product: iniNet Solutions GmbH SCADA Webserver. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-13995/ (Markdown: https://insights.sbomify.com/CVE-2017-13995/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-13995
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-13995
- OSV: https://osv.dev/vulnerability/CVE-2017-13995

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-13995/
Summaries are generated and may contain mistakes; the official description above is the record.