# CVE-2024-8330: Gether Technology 6SHR System - Unrestricted File Upload

> Remote attackers with regular privileges can upload web shells to execute arbitrary system commands due to improper file type validation.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Aug 2024
- **Updated:** 30 Aug 2024
- **Also known as:** GHSA-h3rg-qv35-27xm

## What is CVE-2024-8330?

CVE-2024-8330 is a high-severity vulnerability in Gether Technology 6SHR System, published on 30 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

6SHR system from Gether Technology does not properly validate uploaded file types, allowing remote attackers with regular privileges to upload web shell scripts and use them to execute arbitrary system commands on the server.

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

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

It affects 1 product.


Products: 6shr System Project 6shr System.

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

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

## Is CVE-2024-8330 being exploited?

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

## Other vulnerabilities in Gether Technology 6SHR System

- [CVE-2024-8329](https://insights.sbomify.com/CVE-2024-8329/): Gether Technology 6SHR System - SQL Injection (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-8330 is a high-severity vulnerability in Gether Technology 6SHR System, published on 30 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-8330 in the wild and no public exploit code.

Affected product: Gether Technology 6SHR System. 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-8330/ (Markdown: https://insights.sbomify.com/CVE-2024-8330/index.md)
```

## Sources

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

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