# CVE-2018-20325: Code injection in Danijar Definitions

> Attackers can execute arbitrary Python commands via the load method in the definitions package, potentially compromising the host system.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 21 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-v4x4-98cg-wr4g, PYSEC-2018-82

## What is CVE-2018-20325?

CVE-2018-20325 is a critical code injection vulnerability in n/a, published on 21 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

There is a vulnerability in load() method in definitions/parser.py in the Danijar Hafner definitions package for Python. It can execute arbitrary python commands resulting in command execution.

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

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

3 open source packages ship an affected version, including definitions. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `definitions` | PyPI | All versions | None |
| `definitions` | PyPI | All versions to 0.2.0 | None |
| `definitions` | PyPI | All versions to 0.2.0 | None |

Products: Definitions Project Definitions.

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

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

## Is CVE-2018-20325 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-20325 is a critical code injection vulnerability in n/a, published on 21 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-20325 in the wild and no public exploit code.

Affected packages and fixed versions:
- definitions (PyPI): affected all versions; no fix listed
- definitions (PyPI): affected all versions up to 0.2.0; no fix listed
- definitions (PyPI): affected all versions up to 0.2.0; no fix listed

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

## Sources

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

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