# CVE-2024-23692: Rejetto HTTP File Server Improper Neutralization of Special Elements Used in a Template Engine

> Remote unauthenticated attackers can execute arbitrary commands via template injection in Rejetto HTTP File Server, which is now end-of-life.

- **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:** Yes, since 9 Jul 2024 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 May 2024
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-cw5c-xm7f-wx63

## What is CVE-2024-23692?

CVE-2024-23692 is a critical code injection vulnerability in Rejetto HTTP File Server, published on 31 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Rejetto HTTP File Server, up to and including version 2.3m, is vulnerable to a template injection vulnerability. This vulnerability allows a remote, unauthenticated attacker to execute arbitrary commands on the affected system by sending a specially crafted HTTP request. As of the CVE assignment date, Rejetto HFS 2.3m is no longer supported.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine)

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

It affects 1 product.


Products: Rejetto Http File Server.

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

No fix has been published for CVE-2024-23692 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 30 Jul 2024.

## Is CVE-2024-23692 being exploited?

Yes. Attackers have exploited CVE-2024-23692 in the wild since at least 9 Jul 2024, including in ransomware campaigns.

Public exploit code:

- POC - Unauthenticated RCE Flaw in Rejetto HTTP File Server - CVE-2024-23692  (github_poc): https://github.com/verylazytech/CVE-2024-23692
- Unauthenticated RCE Flaw in Rejetto HTTP File Server (CVE-2024-23692) (github_poc): https://github.com/jakabakos/CVE-2024-23692-RCE-in-Rejetto-HFS
- CVE-2024-23692 Exploit (github_poc): https://github.com/0x20c/CVE-2024-23692-EXP
- https://github.com/vanboomqi/CVE-2024-23692 (github_poc): https://github.com/vanboomqi/CVE-2024-23692
- CVE-2024-23692 (github_poc): https://github.com/BBD-YZZ/CVE-2024-23692
- https://github.com/NanoWraith/CVE-2024-23692 (github_poc): https://github.com/NanoWraith/CVE-2024-23692

## Other vulnerabilities in Rejetto HTTP File Server

- [CVE-2014-6287](https://insights.sbomify.com/CVE-2014-6287/): Rejetto HTTP File Server (HFS) Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2024-39943](https://insights.sbomify.com/CVE-2024-39943/): rejetto HFS vulnerable to OS Command Execution by remote authenticated users (critical 9.9)
- [CVE-2020-13432](https://insights.sbomify.com/CVE-2020-13432/): Memory corruption in n/a (high 7.5)
- [CVE-2014-7226](https://insights.sbomify.com/CVE-2014-7226/): Code injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-23692 is a critical code injection vulnerability in Rejetto HTTP File Server, published on 31 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2024-23692 in the wild since at least 9 Jul 2024, including in ransomware campaigns.

Affected product: Rejetto HTTP File Server. 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-23692/ (Markdown: https://insights.sbomify.com/CVE-2024-23692/index.md)
```

## Sources

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

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