# CVE-2020-5312: PCX P mode buffer overflow in Pillow

> A buffer overflow in Pillow's PCX decoder allows attackers to execute arbitrary code or cause denial of service via crafted images.

- **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:** Yes
- **Published:** 3 Jan 2020
- **Updated:** 4 Aug 2024
- **Also known as:** ALPINE-CVE-2020-5312, BIT-pillow-2020-5312, DEBIAN-CVE-2020-5312, GHSA-p49h-hjvm-jg3h, PYSEC-2020-83, RHSA-2020:0898, UBUNTU-CVE-2020-5312

## What is CVE-2020-5312?

CVE-2020-5312 is a critical memory corruption vulnerability in Canonical Ubuntu Linux, published on 3 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

libImaging/PcxDecode.c in Pillow before 6.2.2 has a PCX P mode buffer overflow.

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

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

4 open source packages ship an affected version, including pillow. It affects 4 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pillow` | Bitnami | All versions | 6.2.2 |
| `pillow` | PyPI | All versions | 6.2.2 |
| `pillow` | PyPI | All versions | 6.2.2 |
| `pillow` | PyPI | All versions | 6.2.2 |
| `python-imaging` | Red Hat:enterprise_linux:6::client | All versions | 0:1.1.6-20.el6_10 |
| `python-imaging-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:1.1.6-20.el6_10 |
| `python-imaging-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:1.1.6-20.el6_10 |
| `python-imaging-sane` | Red Hat:enterprise_linux:6::client | All versions | 0:1.1.6-20.el6_10 |
| `python-imaging-tk` | Red Hat:enterprise_linux:6::client | All versions | 0:1.1.6-20.el6_10 |
| `python-imaging` | Red Hat:enterprise_linux:6::computenode | All versions | 0:1.1.6-20.el6_10 |
| `python-imaging-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:1.1.6-20.el6_10 |
| `python-imaging-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:1.1.6-20.el6_10 |
| `python-imaging-sane` | Red Hat:enterprise_linux:6::computenode | All versions | 0:1.1.6-20.el6_10 |
| `python-imaging-tk` | Red Hat:enterprise_linux:6::computenode | All versions | 0:1.1.6-20.el6_10 |
| `python-imaging` | Red Hat:enterprise_linux:6::server | All versions | 0:1.1.6-20.el6_10 |
| `python-imaging-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:1.1.6-20.el6_10 |
| `python-imaging-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:1.1.6-20.el6_10 |
| `python-imaging-sane` | Red Hat:enterprise_linux:6::server | All versions | 0:1.1.6-20.el6_10 |
| `python-imaging-tk` | Red Hat:enterprise_linux:6::server | All versions | 0:1.1.6-20.el6_10 |
| `python-imaging` | Red Hat:enterprise_linux:6::workstation | All versions | 0:1.1.6-20.el6_10 |
| `python-imaging-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 0:1.1.6-20.el6_10 |
| `python-imaging-devel` | Red Hat:enterprise_linux:6::workstation | All versions | 0:1.1.6-20.el6_10 |
| `python-imaging-sane` | Red Hat:enterprise_linux:6::workstation | All versions | 0:1.1.6-20.el6_10 |
| `python-imaging-tk` | Red Hat:enterprise_linux:6::workstation | All versions | 0:1.1.6-20.el6_10 |

Products: Canonical Ubuntu Linux, Debian Debian Linux, Fedoraproject Fedora, Python Pillow.

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

Upgrade pillow to 6.2.2 or later.

## Is CVE-2020-5312 being exploited?

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

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-5312 is a critical memory corruption vulnerability in Canonical Ubuntu Linux, published on 3 Jan 2020. 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-2020-5312 in the wild and no public exploit code.

Affected packages and fixed versions:
- pillow (Bitnami): affected all versions; fixed in 6.2.2
- pillow (PyPI): affected all versions; fixed in 6.2.2
- pillow (PyPI): affected all versions; fixed in 6.2.2
- pillow (PyPI): affected all versions; fixed in 6.2.2

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

## Sources

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

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