# CVE-2020-7062: Null Pointer Dereference in PHP Session Upload Progress

> A null pointer dereference in PHP's session upload progress tracking can cause a crash when file uploads fail under specific non-default configurations.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 27 Feb 2020
- **Updated:** 16 Sep 2024
- **Also known as:** BIT-libphp-2020-7062, BIT-php-2020-7062, BIT-php-min-2020-7062, DEBIAN-CVE-2020-7062, GHSA-rrwc-c46p-f3v6, UBUNTU-CVE-2020-7062

## What is CVE-2020-7062?

CVE-2020-7062 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 27 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In PHP versions 7.2.x below 7.2.28, 7.3.x below 7.3.15 and 7.4.x below 7.4.3, when using file upload functionality, if upload progress tracking is enabled, but session.upload_progress.cleanup is set to 0 (disabled), and the file upload fails, the upload procedure would try to clean up data that does not exist and encounter null pointer dereference, which would likely lead to a crash.

Weakness: CWE-476 (NULL Pointer Dereference)

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

3 open source packages ship an affected version, including libphp, php and php-min. It affects 4 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libphp` | Bitnami | From 7.2.0 | 7.2.28, 7.3.15, 7.4.3 |
| `php` | Bitnami | From 7.2.0 | 7.2.28, 7.3.15, 7.4.3 |
| `php-min` | Bitnami | From 7.2.0 | 7.2.28, 7.3.15, 7.4.3 |

Products: Canonical Ubuntu Linux, Debian Debian Linux, Opensuse Leap, Php Php.

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

Upgrade libphp to a fixed version for your release line: 7.2.28, 7.3.15 or 7.4.3.

## Is CVE-2020-7062 being exploited?

There is no known exploitation of CVE-2020-7062 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-7062 and fix it if it is affected.

What it is: CVE-2020-7062 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 27 Feb 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-7062 in the wild and no public exploit code.

Affected packages and fixed versions:
- libphp (Bitnami): affected from 7.2.0; fixed in 7.2.28, 7.3.15, 7.4.3
- php (Bitnami): affected from 7.2.0; fixed in 7.2.28, 7.3.15, 7.4.3
- php-min (Bitnami): affected from 7.2.0; fixed in 7.2.28, 7.3.15, 7.4.3

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

## Sources

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

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