# CVE-2024-45171: File upload in n/a

> Authenticated users can upload malicious PHP files via the backup feature, leading to remote code execution on the C-MOR Video Surveillance system.

- **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:** 5 Sep 2024
- **Updated:** 6 Sep 2024
- **Also known as:** GHSA-5qmx-gqwp-wvwm

## What is CVE-2024-45171?

CVE-2024-45171 is a high-severity vulnerability in n/a, published on 5 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in za-internet C-MOR Video Surveillance 5.2401. Due to improper user input validation, it is possible to upload dangerous files, for instance PHP code, to the C-MOR system. By analyzing the C-MOR web interface, it was found out that the upload functionality for backup files allows an authenticated user to upload arbitrary files. The only condition is that the filename contains a .cbkf string. Therefore, webshell.cbkf.php is considered a valid file name for the C-MOR web application. Uploaded files are stored within the directory "/srv/www/backups" on the C-MOR system, and can thus be accessed via the URL https://<HOST>/backup/upload_<FILENAME>. Due to broken access control, low-privileged authenticated users can also use this file upload functionality.

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

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

It affects 1 product.


Products: C-Mor C-Mor Video Surveillance.

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

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

## Is CVE-2024-45171 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-45173](https://insights.sbomify.com/CVE-2024-45173/): Privilege escalation in n/a (high 8.8)
- [CVE-2024-45175](https://insights.sbomify.com/CVE-2024-45175/): Information disclosure in n/a (high 8.8)
- [CVE-2024-45170](https://insights.sbomify.com/CVE-2024-45170/): Missing authorization in n/a (high 8.1)
- [CVE-2024-45174](https://insights.sbomify.com/CVE-2024-45174/): SQL injection in n/a (high 8.1)
- [CVE-2024-45179](https://insights.sbomify.com/CVE-2024-45179/): Command injection in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-45171 is a high-severity vulnerability in n/a, published on 5 Sep 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-45171 in the wild and no public exploit code.

Affected product: n/a. 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-45171/ (Markdown: https://insights.sbomify.com/CVE-2024-45171/index.md)
```

## Sources

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

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