# CVE-2019-11043: PHP FastCGI Process Manager (FPM) Buffer Overflow

> Remote attackers can achieve code execution via buffer underflow in PHP-FPM when specific configurations are enabled.

- **Severity:** High 8.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Yes, since 25 Mar 2022 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Oct 2019
- **Updated:** 21 Oct 2025
- **Also known as:** ALSA-2019:3735, ALSA-2019:3736, DLA-1970-1, DSA-4552-1, DSA-4553-1, GHSA-6qjm-m8fp-j2mm, MGASA-2019-0307, RHSA-2019:3286, RHSA-2019:3287, RHSA-2019:3300, RHSA-2019:3724, RHSA-2019:3735, RHSA-2019:3736, RHSA-2020:0322, RHSA-2020:2835, RLSA-2019:3735, RLSA-2019:3736, SUSE-SU-2019:2809-1, SUSE-SU-2019:2819-1, SUSE-SU-2019:2909-1, UBUNTU-CVE-2019-11043, USN-4166-1, USN-4166-2, openSUSE-SU-2019:2441-1, openSUSE-SU-2019:2457-1

## What is CVE-2019-11043?

CVE-2019-11043 is a high-severity memory corruption vulnerability in Canonical Ubuntu Linux, published on 28 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it is possible to cause FPM module to write past allocated buffers into the space reserved for FCGI protocol data, thus opening the possibility of remote code execution.

Weakness: CWE-787 (Out-of-bounds Write), CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2019-11043?

It affects 23 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `apcu-panel` | AlmaLinux:8 | All versions | 5.1.12-2.module_el8.3.0+2010+7c76a223 |
| `apcu-panel` | AlmaLinux:8 | All versions | 5.1.17-1.module_el8.3.0+2009+b272fdef |
| `libzip` | AlmaLinux:8 | All versions | 1.5.1-2.module_el8.3.0+2010+7c76a223 |
| `libzip` | AlmaLinux:8 | All versions | 1.5.1-2.module_el8.4.0+2228+7c76a223 |
| `libzip` | AlmaLinux:8 | All versions | 1.5.1-2.module_el8.5.0+53+9945c2af |
| `libzip` | AlmaLinux:8 | All versions | 1.5.2-1.module_el8.3.0+2009+b272fdef |
| `libzip` | AlmaLinux:8 | All versions | 1.5.2-1.module_el8.4.0+2229+b272fdef |
| `libzip` | AlmaLinux:8 | All versions | 1.5.2-1.module_el8.5.0+152+112d3b8c |
| `libzip-devel` | AlmaLinux:8 | All versions | 1.5.1-2.module_el8.3.0+2010+7c76a223 |
| `libzip-devel` | AlmaLinux:8 | All versions | 1.5.1-2.module_el8.4.0+2228+7c76a223 |
| `libzip-devel` | AlmaLinux:8 | All versions | 1.5.1-2.module_el8.5.0+53+9945c2af |
| `libzip-devel` | AlmaLinux:8 | All versions | 1.5.2-1.module_el8.3.0+2009+b272fdef |
| `libzip-devel` | AlmaLinux:8 | All versions | 1.5.2-1.module_el8.4.0+2229+b272fdef |
| `libzip-devel` | AlmaLinux:8 | All versions | 1.5.2-1.module_el8.5.0+152+112d3b8c |
| `libzip-tools` | AlmaLinux:8 | All versions | 1.5.1-2.module_el8.3.0+2010+7c76a223 |
| `libzip-tools` | AlmaLinux:8 | All versions | 1.5.1-2.module_el8.4.0+2228+7c76a223 |
| `libzip-tools` | AlmaLinux:8 | All versions | 1.5.1-2.module_el8.5.0+53+9945c2af |
| `libzip-tools` | AlmaLinux:8 | All versions | 1.5.2-1.module_el8.3.0+2009+b272fdef |
| `libzip-tools` | AlmaLinux:8 | All versions | 1.5.2-1.module_el8.4.0+2229+b272fdef |
| `libzip-tools` | AlmaLinux:8 | All versions | 1.5.2-1.module_el8.5.0+152+112d3b8c |
| `php-pear` | AlmaLinux:8 | All versions | 1:1.10.5-9.module_el8.3.0+2010+7c76a223 |
| `php-pear` | AlmaLinux:8 | All versions | 1:1.10.9-1.module_el8.3.0+2009+b272fdef |
| `php-pecl-apcu` | AlmaLinux:8 | All versions | 5.1.12-2.module_el8.3.0+2010+7c76a223 |
| `php-pecl-apcu` | AlmaLinux:8 | All versions | 5.1.12-2.module_el8.4.0+2228+7c76a223 |
| `php-pecl-apcu` | AlmaLinux:8 | All versions | 5.1.12-2.module_el8.5.0+53+9945c2af |
| `php-pecl-apcu` | AlmaLinux:8 | All versions | 5.1.17-1.module_el8.3.0+2009+b272fdef |
| `php-pecl-apcu` | AlmaLinux:8 | All versions | 5.1.17-1.module_el8.4.0+2229+b272fdef |
| `php-pecl-apcu` | AlmaLinux:8 | All versions | 5.1.17-1.module_el8.5.0+152+112d3b8c |
| `php-pecl-apcu-devel` | AlmaLinux:8 | All versions | 5.1.12-2.module_el8.3.0+2010+7c76a223 |
| `php-pecl-apcu-devel` | AlmaLinux:8 | All versions | 5.1.12-2.module_el8.4.0+2228+7c76a223 |
| `php-pecl-apcu-devel` | AlmaLinux:8 | All versions | 5.1.12-2.module_el8.5.0+53+9945c2af |
| `php-pecl-apcu-devel` | AlmaLinux:8 | All versions | 5.1.17-1.module_el8.3.0+2009+b272fdef |
| `php-pecl-apcu-devel` | AlmaLinux:8 | All versions | 5.1.17-1.module_el8.4.0+2229+b272fdef |
| `php-pecl-apcu-devel` | AlmaLinux:8 | All versions | 5.1.17-1.module_el8.5.0+152+112d3b8c |
| `php-pecl-zip` | AlmaLinux:8 | All versions | 1.15.3-1.module_el8.3.0+2010+7c76a223 |
| `php-pecl-zip` | AlmaLinux:8 | All versions | 1.15.3-1.module_el8.4.0+2228+7c76a223 |
| `php-pecl-zip` | AlmaLinux:8 | All versions | 1.15.3-1.module_el8.5.0+53+9945c2af |
| `php-pecl-zip` | AlmaLinux:8 | All versions | 1.15.4-1.module_el8.3.0+2009+b272fdef |
| `php-pecl-zip` | AlmaLinux:8 | All versions | 1.15.4-1.module_el8.4.0+2229+b272fdef |
| `php-pecl-zip` | AlmaLinux:8 | All versions | 1.15.4-1.module_el8.5.0+152+112d3b8c |

Products: Canonical Ubuntu Linux, Debian Debian Linux, Fedoraproject Fedora, Php Php, Redhat Enterprise Linux, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Eus, Redhat Enterprise Linux Eus Compute Node, Redhat Enterprise Linux for Arm 64, Redhat Enterprise Linux for Arm 64 Eus, Redhat Enterprise Linux for Ibm Z Systems, Redhat Enterprise Linux for Ibm Z Systems Eus, Redhat Enterprise Linux for Power Big Endian, Redhat Enterprise Linux for Power Big Endian Eus, Redhat Enterprise Linux for Power Little Endian, Redhat Enterprise Linux for Power Little Endian Eus, Redhat Enterprise Linux for Scientific Computing, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Tus and 3 more.

## How do I fix CVE-2019-11043?

Upgrade to a fixed version. US federal agencies must fix it by 15 Apr 2022.

## Is CVE-2019-11043 being exploited?

Yes. Attackers have exploited CVE-2019-11043 in the wild since at least 25 Mar 2022, including in ransomware campaigns.

Public exploit code:

- Exploit for CVE-2019-11043 (github_poc): https://github.com/neex/phuip-fpizdam
- (PoC) Python version of CVE-2019-11043 exploit by neex (github_poc): https://github.com/theMiddleBlue/CVE-2019-11043
- php-fpm+Nginx RCE (github_poc): https://github.com/jas502n/CVE-2019-11043
- https://github.com/akamajoris/CVE-2019-11043-Docker (github_poc): https://github.com/akamajoris/CVE-2019-11043-Docker
- Ladon POC Moudle CVE-2019-11043 (PHP-FPM + Ngnix) (github_poc): https://github.com/k8gege/CVE-2019-11043
- CVE-2019-11043  PHP7.x  RCE (github_poc): https://github.com/0th3rs-Security-Team/CVE-2019-11043

## 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-2019-11043 and fix it if it is affected.

What it is: CVE-2019-11043 is a high-severity memory corruption vulnerability in Canonical Ubuntu Linux, published on 28 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2019-11043 in the wild since at least 25 Mar 2022, including in ransomware campaigns.

Affected product: Canonical Ubuntu Linux. 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-2019-11043/ (Markdown: https://insights.sbomify.com/CVE-2019-11043/index.md)
```

## Sources

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

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