# CVE-2019-0211: Apache HTTP Server Privilege Escalation

> Attackers can escalate privileges to root and execute arbitrary code by manipulating the scoreboard in Apache HTTP Server.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Apr 2019
- **Updated:** 21 Oct 2025
- **Also known as:** ALPINE-CVE-2019-0211, CLEANSTART-2026-DX30733, DEBIAN-CVE-2019-0211, GHSA-w9rc-q752-88hf, UBUNTU-CVE-2019-0211

## What is CVE-2019-0211?

CVE-2019-0211 is a high-severity vulnerability in Apache Http Server, published on 8 Apr 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Apache HTTP Server 2.4 releases 2.4.17 to 2.4.38, with MPM event, worker or prefork, code executing in less-privileged child processes or threads (including scripts executed by an in-process scripting interpreter) could execute arbitrary code with the privileges of the parent process (usually root) by manipulating the scoreboard. Non-Unix systems are not affected.

Weakness: CWE-416 (Use After Free)

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

It affects 27 products.


Products: Apache Http Server, Canonical Ubuntu Linux, Debian Debian Linux, Fedoraproject Fedora, Netapp Oncommand Unified Manager, Opensuse Leap, Oracle Communications Session Report Manager, Oracle Communications Session Route Manager, Oracle Enterprise Manager Ops Center, Oracle Http Server, Oracle Instantis Enterprisetrack, Oracle Retail Xstore Point of Service, Redhat Enterprise Linux, Redhat Enterprise Linux Eus, 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 Little Endian, Redhat Enterprise Linux for Power Little Endian Eus and 7 more.

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

Upgrade to a fixed version. US federal agencies must fix it by 3 May 2022.

## Is CVE-2019-0211 being exploited?

Yes. Attackers have exploited CVE-2019-0211 in the wild since at least 3 Nov 2021.

Public exploit code:

- CVE-2019-0211-apache & CVE-2019-6977-imagecolormatch (github_poc): https://github.com/ozkanbilge/Apache-Exploit-2019
- Apache 2.4.17 < 2.4.38 - 'apache2ctl graceful' 'logrotate' Local Privilege Escalation (exploitdb)
- https://github.com/Jeanback1/CVE-2019-0211-exploit (github_poc): https://github.com/Jeanback1/CVE-2019-0211-exploit

## Other vulnerabilities in Apache Http Server

- [CVE-2021-42013](https://insights.sbomify.com/CVE-2021-42013/): Apache HTTP Server Path Traversal (critical 9.8, exploited in the wild)
- [CVE-2024-38475](https://insights.sbomify.com/CVE-2024-38475/): Apache HTTP Server Improper Escaping of Output (critical 9.1, exploited in the wild)
- [CVE-2021-40438](https://insights.sbomify.com/CVE-2021-40438/): Apache HTTP Server-Side Request Forgery (SSRF) (critical 9.0, exploited in the wild)
- [CVE-2021-41773](https://insights.sbomify.com/CVE-2021-41773/): Apache HTTP Server Path Traversal (high 7.5, exploited in the wild)
- [CVE-2010-0425](https://insights.sbomify.com/CVE-2010-0425/): Use after free in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-0211 and fix it if it is affected.

What it is: CVE-2019-0211 is a high-severity vulnerability in Apache Http Server, published on 8 Apr 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2019-0211 in the wild since at least 3 Nov 2021.

Affected product: Apache Http Server. 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-0211/ (Markdown: https://insights.sbomify.com/CVE-2019-0211/index.md)
```

## Sources

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

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