CVE-2019-0211: Apache HTTP Server Privilege Escalation
Apache HTTP Server · listed in the CISA catalog of actively exploited vulnerabilities since 2021-11-03.
- CVSS v3.1 (CVE record)
- 7.8
- high
- EPSS (exploit probability, 30 days)
- 65%
- higher than 99.2% of all CVEs
- Added to CISA KEV
- 2021-11-03
- US federal due date 2022-05-03
- Ubuntu priority
- high
CVE-2019-0211 explained
CVE-2019-0211 is a privilege escalation flaw in Apache HTTP Server 2.4 releases 2.4.17 to 2.4.38 using the event, worker or prefork MPM. Code running in a less-privileged child process or thread, including scripts run by an in-process interpreter, can manipulate the scoreboard and run code as the parent process, usually root. It is listed in CISA's Known Exploited Vulnerabilities catalog.
Impact
An attacker who can already run code inside an Apache child process or thread can gain the privileges of the parent process, usually root. This includes code in scripts run by an in-process scripting interpreter. The attack is local, needs low privileges and no user interaction. Success gives full control over confidentiality, integrity and availability of the system. Non-Unix systems are not affected.
Who is affected
The apache2 source package is affected on Ubuntu 16.04 LTS and Ubuntu 18.04 LTS. Both have fixed versions in the standard archive: 2.4.18-2ubuntu3.10 for Ubuntu 16.04 LTS and 2.4.29-1ubuntu4.6 for Ubuntu 18.04 LTS. Ubuntu 16.04 LTS is end of life. Standard support for Ubuntu 18.04 LTS has ended, and further fixes for it are only available with Ubuntu Pro (ESM).
Written with AI from the data on this page and checked against it automatically.
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.
CISA required action: Apply updates per vendor instructions.
CISA notes
Upstream versions (CVE record)
From the CVE record published by the vendor or CVE numbering authority.
- Apache HTTP ServerAffectedFixed in
- 2.4.17 to 2.4.38
not statedVersion statement as published by the CNA (free text).
| Product | Affected | Fixed in |
|---|---|---|
| Apache HTTP ServerVersion statement as published by the CNA (free text). |
| not stated |
Ubuntu and Debian releases
A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.
Ubuntu 18.04 LTS·apache2
Fixed: 2.4.29-1ubuntu4.6
Ubuntu 16.04 LTS·apache2
ESM ended
Fixed: 2.4.18-2ubuntu3.10
What to do
- Update
apache2to2.4.18-2ubuntu3.10on Ubuntu 16.04 LTS or2.4.29-1ubuntu4.6on Ubuntu 18.04 LTS, or later. - Restart the Apache service so the parent process runs the fixed code.
- Plan an upgrade of Ubuntu 16.04 LTS systems to a supported release, as it is end of life.
- Enable Ubuntu Pro (ESM) on Ubuntu 18.04 LTS systems, or upgrade them, to keep receiving security fixes.
- Review who can deploy scripts or modules that run inside Apache processes.
Written with AI from the data on this page and checked against it automatically.
Check and fix on a server
Run on each Ubuntu or Debian server. Replace apache2 with the source package from the table above.
1. Show installed packages built from the source package, with their versions
dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="apache2"'2. Compare each installed version with the fixed version for your release from the table
I=INSTALLED_VERSION; F=FIXED_VERSION # replace both
dpkg --compare-versions "$I" lt "$F"; case $? in 0) echo vulnerable ;; 1) echo "fixed or newer" ;; *) echo "check the versions" ;; esac3. Install the fix
sudo apt update && sudo apt install --only-upgrade $(dpkg-query -W -f='${binary:Package} ${source:Package}\n' | awk '$2=="apache2"{print $1}')Services keep running the old code until they are restarted – restart the affected service or check with needrestart.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-416 Use After Free
Questions about CVE-2019-0211
- Is this vulnerability being exploited?
- Yes. CISA added CVE-2019-0211 to its Known Exploited Vulnerabilities catalog on 2021-11-03. The required action is to apply updates per vendor instructions. Known ransomware use is listed as unknown.
- Can a remote attacker exploit this directly?
- The attack vector is local. The attacker must already be able to run code in a less-privileged Apache child process or thread, for example through a script run by an in-process interpreter. The flaw then lets that code gain the parent's privileges, usually root.
- Do I need to restart anything after updating?
- Yes. Running Apache processes keep using the old code until the service is restarted. Restart Apache after installing the fixed
apache2package.
Written with AI from the data on this page and checked against it automatically.
References
Vendor
- [httpd-users] 20190406 [users@httpd] CVE-2019-0211/0215/0217
- httpd.apache.org/security/vulnerabilities_24.html
- apache.org/dist/httpd/CHANGES_2.4.39
- [community-dev] 20190411 CVE-2019-0211 applicable to versions 2.2.x?
- [community-dev] 20190411 Re: CVE-2019-0211 applicable to versions 2.2.x?
- [community-dev] 20190411 RE: CVE-2019-0211 applicable to versions 2.2.x?
Other advisories
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.