# CVE-2024-50636: Code injection in n/a

> Attackers can execute arbitrary Python code via malicious .PYM files in PyMOL, leading to remote command execution on the user's system.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 11 Nov 2024
- **Updated:** 19 Nov 2024
- **Also known as:** GHSA-wq8w-m2g8-mv57, UBUNTU-CVE-2024-50636

## What is CVE-2024-50636?

CVE-2024-50636 is a critical code injection vulnerability in n/a, published on 11 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PyMOL 2.5.0 contains a vulnerability in its "Run Script" function, which allows the execution of arbitrary Python code embedded within .PYM files. Attackers can craft a malicious .PYM file containing a Python reverse shell payload and exploit the function to achieve Remote Command Execution (RCE). This vulnerability arises because PyMOL treats .PYM files as Python scripts without properly validating or restricting the commands within the script, enabling attackers to run unauthorized commands in the context of the user running the application.

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

## Which versions are affected by CVE-2024-50636?


## How do I fix CVE-2024-50636?

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

## Is CVE-2024-50636 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-50636 and fix it if it is affected.

What it is: CVE-2024-50636 is a critical code injection vulnerability in n/a, published on 11 Nov 2024. 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-2024-50636 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-2024-50636/ (Markdown: https://insights.sbomify.com/CVE-2024-50636/index.md)
```

## Sources

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

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