# CVE-2020-15929: Path traversal in n/a

> Attackers can write arbitrary CFM files via unvalidated parameters, leading to remote code execution in applications using TestBox.

- **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:** 24 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-cq82-f654-8cvc

## What is CVE-2020-15929?

CVE-2020-15929 is a critical path traversal vulnerability in n/a, published on 24 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Ortus TestBox 2.4.0 through 4.1.0, unvalidated query string parameters passed to system/runners/HTMLRunner.cfm allow an attacker to write an arbitrary CFM file (within the application's context) containing attacker-defined CFML tags, leading to Remote Code Execution.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2020-15929?

It affects 1 product.


Products: Ortussolutions Testbox.

## How do I fix CVE-2020-15929?

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

## Is CVE-2020-15929 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-15928](https://insights.sbomify.com/CVE-2020-15928/): Path traversal in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-15929 and fix it if it is affected.

What it is: CVE-2020-15929 is a critical path traversal vulnerability in n/a, published on 24 Nov 2020. 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-2020-15929 in the wild and no public exploit code.

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

## Sources

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

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