# CVE-2009-0367: Code injection in n/a

> Remote attackers can execute arbitrary code in Wesnoth by exploiting a sandbox escape in the Python AI module via unsafe module imports.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Mar 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hmxr-rwh4-hh58

## What is CVE-2009-0367?

CVE-2009-0367 is a critical code injection vulnerability in n/a, published on 5 Mar 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Python AI module in Wesnoth 1.4.x and 1.5 before 1.5.11 allows remote attackers to escape the sandbox and execute arbitrary code by using a whitelisted module that imports an unsafe module, then using a hierarchical module name to access the unsafe module through the whitelisted module.

Weakness: CWE-264

## Which versions are affected by CVE-2009-0367?

It affects 1 product.


Products: Wesnoth Wesnoth.

## How do I fix CVE-2009-0367?

Upgrade to a fixed version.

## Is CVE-2009-0367 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-0367 exists.

Public exploit code:

- Wesnoth 1.x - PythonAI Remote Code Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-5742](https://insights.sbomify.com/CVE-2007-5742/): Path traversal in n/a (critical 9.0)
- [CVE-2007-3917](https://insights.sbomify.com/CVE-2007-3917/): Denial of service in n/a (high 7.8)
- [CVE-2007-6201](https://insights.sbomify.com/CVE-2007-6201/): Denial of service in n/a (high 7.5)
- [CVE-2009-0878](https://insights.sbomify.com/CVE-2009-0878/): Denial of service in n/a (medium 5.0)
- [CVE-2009-0366](https://insights.sbomify.com/CVE-2009-0366/): Denial of service in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-0367 and fix it if it is affected.

What it is: CVE-2009-0367 is a critical code injection vulnerability in n/a, published on 5 Mar 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-0367 exists.

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

## Sources

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

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