# CVE-2023-3329: CVE-2023-3329

> Administrative attackers can exploit path traversal in the file upload feature to overwrite system files, causing denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Aug 2023
- **Updated:** 29 Oct 2024
- **Also known as:** GHSA-jgvj-jh34-hqv3

## What is CVE-2023-3329?

CVE-2023-3329 is a medium-severity path traversal vulnerability in iniNet SCADAWebServer, published on 2 Aug 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

SpiderControl SCADA Webserver versions 2.08 and prior are vulnerable to path traversal. An attacker with administrative privileges could overwrite files on the webserver using the HMI's upload file feature. This could create size zero files anywhere on the webserver, potentially overwriting system files and creating a denial-of-service condition.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2023-3329?

It affects 1 product.


Products: Spidercontrol Scadawebserver.

## How do I fix CVE-2023-3329?

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

## Is CVE-2023-3329 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-3329 and fix it if it is affected.

What it is: CVE-2023-3329 is a medium-severity path traversal vulnerability in iniNet SCADAWebServer, published on 2 Aug 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-3329 in the wild and no public exploit code.

Affected product: iniNet SCADAWebServer. 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-2023-3329/ (Markdown: https://insights.sbomify.com/CVE-2023-3329/index.md)
```

## Sources

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

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