# CVE-2021-46418: File upload in n/a

> An attacker can create CGI scripts via PUT method on Telesquare TLR-2855KS6 routers, potentially leading to remote code execution.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Apr 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-7xg4-44vr-vrjp

## What is CVE-2021-46418?

CVE-2021-46418 is a high-severity vulnerability in n/a, published on 7 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unauthorized file creation vulnerability in Telesquare TLR-2855KS6 via PUT method can allow creation of CGI scripts.

## Which versions are affected by CVE-2021-46418?

It affects 1 product.


Products: Telesquare Tlr-2855ks6 Firmware.

## How do I fix CVE-2021-46418?

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

## Is CVE-2021-46418 being exploited?

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

Public exploit code:

- Telesquare TLR-2855KS6 - Arbitrary File Creation (exploitdb)
- Telesquare TLR-2855KS6 - Arbitrary File Creation (nuclei): http/cves/2021/CVE-2021-46418.yaml

## Other vulnerabilities in n/a

- [CVE-2021-46419](https://insights.sbomify.com/CVE-2021-46419/): Missing authorization in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-46418 and fix it if it is affected.

What it is: CVE-2021-46418 is a high-severity vulnerability in n/a, published on 7 Apr 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-2021-46418 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-2021-46418/ (Markdown: https://insights.sbomify.com/CVE-2021-46418/index.md)
```

## Sources

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

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