# CVE-2022-41217: Cloudflow - Unauthenticated file upload vulnerability

> An unauthenticated attacker can upload malicious files to Cloudflow's storage, potentially leading to code execution or data modification.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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:** 22 Feb 2023
- **Updated:** 1 Apr 2025
- **Also known as:** GHSA-r459-f967-5328

## What is CVE-2022-41217?

CVE-2022-41217 is a critical vulnerability in Hybrid Software Cloudflow, published on 22 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cloudflow contains a unauthenticated file upload vulnerability, which makes it possible for an attacker to upload malicious files to the CLOUDFLOW PROOFSCOPE built-in storage.

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

## Which versions are affected by CVE-2022-41217?

It affects 1 product.


Products: Hybridsoftware Cloudflow.

## How do I fix CVE-2022-41217?

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

## Is CVE-2022-41217 being exploited?

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

## Other vulnerabilities in Hybrid Software Cloudflow

- [CVE-2022-41216](https://insights.sbomify.com/CVE-2022-41216/): Cloudflow - Local File Inclusion Vulnerability (high 8.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41217 and fix it if it is affected.

What it is: CVE-2022-41217 is a critical vulnerability in Hybrid Software Cloudflow, published on 22 Feb 2023. 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-2022-41217 in the wild and no public exploit code.

Affected product: Hybrid Software Cloudflow. 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-2022-41217/ (Markdown: https://insights.sbomify.com/CVE-2022-41217/index.md)
```

## Sources

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

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