# CVE-2024-8232: iniNet Solutions SpiderControl SCADA Web Server Unrestricted Upload of File with Dangerous Type

> Attackers can upload malicious files to the SCADA web server without authentication, potentially leading to code execution.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Sep 2024
- **Updated:** 12 Sep 2024
- **Also known as:** GHSA-rqjx-229x-7jmc

## What is CVE-2024-8232?

CVE-2024-8232 is a high-severity vulnerability in iniNet Solutions GmbH SpiderControl SCADA Web Server, published on 10 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SpiderControl SCADA Web Server has a vulnerability that could allow an 
attacker to upload specially crafted malicious files without 
authentication.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2024-8232?


## How do I fix CVE-2024-8232?

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

## Is CVE-2024-8232 being exploited?

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

Public exploit code:

- SpiderControl SCADA Web Server File Upload Vulnerability (github_poc): https://github.com/z3usx01/CVE-2024-8232

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-8232 and fix it if it is affected.

What it is: CVE-2024-8232 is a high-severity vulnerability in iniNet Solutions GmbH SpiderControl SCADA Web Server, published on 10 Sep 2024. 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-2024-8232 in the wild and no public exploit code.

Affected product: iniNet Solutions GmbH SpiderControl SCADA Web Server. 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-2024-8232/ (Markdown: https://insights.sbomify.com/CVE-2024-8232/index.md)
```

## Sources

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

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