# CVE-2018-1999023: Code injection in n/a

> Attackers can execute arbitrary code outside the sandbox by tricking users into loading malicious saved games, replays, or networked content in Wesnoth.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 23 Jul 2018
- **Updated:** 17 Sep 2024
- **Also known as:** AZL-38656, CVE-2018-1000213, DEBIAN-CVE-2018-1999023, GHSA-rv2w-5cww-2mqm, MGASA-2018-0325, UBUNTU-CVE-2018-1999023, openSUSE-SU-2024:11509-1

## What is CVE-2018-1999023?

CVE-2018-1999023 is a high-severity code injection vulnerability in n/a, published on 23 Jul 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Battle for Wesnoth Project version 1.7.0 through 1.14.3 contains a Code Injection vulnerability in the Lua scripting engine that can result in code execution outside the sandbox. This attack appear to be exploitable via Loading specially-crafted saved games, networked games, replays, and player content.

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

## Which versions are affected by CVE-2018-1999023?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wesnoth` | openSUSE:Tumbleweed | All versions | 1.15.17-1.3 |

Products: Wesnoth the Battle for Wesnoth.

## How do I fix CVE-2018-1999023?

Upgrade to a fixed version.

## Is CVE-2018-1999023 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1999023 and fix it if it is affected.

What it is: CVE-2018-1999023 is a high-severity code injection vulnerability in n/a, published on 23 Jul 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-1999023 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-2018-1999023/ (Markdown: https://insights.sbomify.com/CVE-2018-1999023/index.md)
```

## Sources

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

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