# CVE-2020-14939: Code injection in n/a

> Attackers can execute arbitrary code by modifying saved game files containing Lua scripts in FreedroidRPG.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 23 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2020-14939, GHSA-hv3g-p5v3-mrc5, UBUNTU-CVE-2020-14939

## What is CVE-2020-14939?

CVE-2020-14939 is a high-severity code injection vulnerability in n/a, published on 23 Jun 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

An issue was discovered in savestruct_internal.c in FreedroidRPG 1.0rc2. Saved game files are composed of Lua scripts that recover a game's state. A file can be modified to put any Lua code inside, leading to arbitrary code execution while loading.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Freedroid Freedroidrpg.

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

Upgrade to a fixed version.

## Is CVE-2020-14939 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-14938](https://insights.sbomify.com/CVE-2020-14938/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-14939 is a high-severity code injection vulnerability in n/a, published on 23 Jun 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-14939 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-14939/ (Markdown: https://insights.sbomify.com/CVE-2020-14939/index.md)
```

## Sources

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

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