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

> Attackers can execute arbitrary Python code in Open edX Studio if the CodeJail security feature is disabled.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-hc63-fv38-p9mv

## What is CVE-2020-13144?

CVE-2020-13144 is a high-severity code injection vulnerability in n/a, published on 18 May 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Studio in Open edX Ironwood 2.5, when CodeJail is not used, allows a user to go to the "Create New course>New section>New subsection>New unit>Add new component>Problem button>Advanced tab>Custom Python evaluated code" screen, edit the problem, and execute Python code. This leads to arbitrary code execution.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Edx Open Edx Platform.

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

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

## Is CVE-2020-13144 being exploited?

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

Public exploit code:

- OpenEDX platform Ironwood 2.5 - Remote Code Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2020-13146](https://insights.sbomify.com/CVE-2020-13146/): Other in n/a (high 8.8)
- [CVE-2020-13145](https://insights.sbomify.com/CVE-2020-13145/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-13144 is a high-severity code injection vulnerability in n/a, published on 18 May 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-13144 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-13144/ (Markdown: https://insights.sbomify.com/CVE-2020-13144/index.md)
```

## Sources

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

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