# CVE-2014-6287: Rejetto HTTP File Server (HFS) Remote Code Execution

> Remote attackers can execute arbitrary programs on Rejetto HTTP File Server by injecting null bytes into search actions.

- **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 25 Mar 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Oct 2014
- **Updated:** 22 Oct 2025
- **Also known as:** GHSA-2hx5-63mq-crfj

## What is CVE-2014-6287?

CVE-2014-6287 is a critical code injection vulnerability in n/a, published on 7 Oct 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The findMacroMarker function in parserLib.pas in Rejetto HTTP File Server (aks HFS or HttpFileServer) 2.3x before 2.3c allows remote attackers to execute arbitrary programs via a %00 sequence in a search action.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2014-6287?

It affects 1 product.


Products: Rejetto Http File Server.

## How do I fix CVE-2014-6287?

No fix has been published for CVE-2014-6287 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 15 Apr 2022.

## Is CVE-2014-6287 being exploited?

Yes. Attackers have exploited CVE-2014-6287 in the wild since at least 25 Mar 2022.

Public exploit code:

- CVE-2014-6287 (github_poc): https://github.com/randallbanner/Rejetto-HTTP-File-Server-HFS-2.3.x---Remote-Command-Execution
- https://github.com/Nicoslo/Windows-exploitation-Rejetto-HTTP-File-Server-HFS-2.3.x-CVE-2014-6287 (github_poc): https://github.com/Nicoslo/Windows-exploitation-Rejetto-HTTP-File-Server-HFS-2.3.x-CVE-2014-6287
- a python3 version of the exploit written for CVE-2014-6287. Useful for completing the "Steel Mountain" room on TryHackMe.com without the use of metasploit. (github_poc): https://github.com/mrintern/thm_steelmountain_CVE-2014-6287
- Rejetto HttpFileServer Remote Command Execution (metasploit)
- Rejetto HTTP File Server (HFS) 2.3.x - Remote Command Execution (1) (exploitdb)
- Rejetto HTTP File Server (HFS) - Remote Command Execution (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2024-23692](https://insights.sbomify.com/CVE-2024-23692/): Rejetto HTTP File Server Improper Neutralization of Special Elements Used in a Template Engine (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-2014-6287 and fix it if it is affected.

What it is: CVE-2014-6287 is a critical code injection vulnerability in n/a, published on 7 Oct 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2014-6287 in the wild since at least 25 Mar 2022.

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

## Sources

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

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