# CVE-2022-39047: Memory corruption in n/a

> A buffer overflow in the Freeciv Modpack Installer allows attackers to execute arbitrary code via a malicious modpack URL.

- **Severity:** High 8.8 (`CVSS:3.1/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:** 31 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2022-39047, GHSA-v44g-gwm6-58cw, MGASA-2022-0293, UBUNTU-CVE-2022-39047

## What is CVE-2022-39047?

CVE-2022-39047 is a high-severity memory corruption vulnerability in n/a, published on 31 Aug 2022. 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

Freeciv before 2.6.7 and before 3.0.3 is prone to a buffer overflow vulnerability in the Modpack Installer utility's handling of the modpack URL.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2022-39047?

It affects 1 product.


Products: Freeciv Freeciv.

## How do I fix CVE-2022-39047?

Upgrade to a fixed version.

## Is CVE-2022-39047 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-2445](https://insights.sbomify.com/CVE-2010-2445/): Code injection in n/a (critical 10.0)
- [CVE-2012-6083](https://insights.sbomify.com/CVE-2012-6083/): Denial of service in freeciv (high 7.5)
- [CVE-2006-3913](https://insights.sbomify.com/CVE-2006-3913/): Memory corruption in n/a (high 7.5)
- [CVE-2006-0047](https://insights.sbomify.com/CVE-2006-0047/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-39047 and fix it if it is affected.

What it is: CVE-2022-39047 is a high-severity memory corruption vulnerability in n/a, published on 31 Aug 2022. 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-2022-39047 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-2022-39047/ (Markdown: https://insights.sbomify.com/CVE-2022-39047/index.md)
```

## Sources

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

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