# CVE-2022-29622: File upload in n/a

> Attackers can execute arbitrary code via crafted filenames in formidable, though maintainers dispute validity due to intended functionality.

- **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:** Yes
- **Published:** 16 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2022-29622, ROOT-APP-NPM-CVE-2022-29622

## What is CVE-2022-29622?

CVE-2022-29622 is a critical vulnerability in n/a, published on 16 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An arbitrary file upload vulnerability in formidable v3.1.4 allows attackers to execute arbitrary code via a crafted filename. NOTE: some third parties dispute this issue because the product has common use cases in which uploading arbitrary files is the desired behavior. Also, there are configuration options in all versions that can change the default behavior of how files are handled. Strapi does not consider this to be a valid vulnerability.

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

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

It affects 1 product.


Products: Formidable Project Formidable.

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

No fix published yet.

## Is CVE-2022-29622 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-29622 exists.

Public exploit code:

- Hack this service to prove CVE-2022–29622 is valid (github_poc): https://github.com/keymandll/CVE-2022-29622

## Fix prompt for AI coding agents

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

What it is: CVE-2022-29622 is a critical vulnerability in n/a, published on 16 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-29622 exists.

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-2022-29622/ (Markdown: https://insights.sbomify.com/CVE-2022-29622/index.md)
```

## Sources

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

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