What is CVE-2019-0211?A high-severity flaw criminals are using now.
CVE-2019-0211 is a high-severity flaw (CVSS 7.8) in HTTP Server from Apache, published on 8 April 2019. It is on the list of flaws known to be exploited, so criminals are already using it. The latest forecast puts its chance of use in the next 30 days at 65%. If you run an affected version, patch it first.
Published 8 April 2019. Record last updated 22 October 2025. We keep this page's data up to date.
What is CVE-2019-0211? In plain terms.
An attacker has to be already on the device with an ordinary user account, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.
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.
What kind of flaw is it?
- CWE-416Use After Free
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAlready on the device
- How hard it is to pull offEasy: no special conditions
- Login needed firstAn ordinary user account
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan read data, change data and take it offline
Severity vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is CVE-2019-0211 being exploited? Yes.
Attackers are already using it. It is on the government list of flaws known to be exploited, and the latest forecast puts the chance of it being used in the next 30 days at 65%.
Timeline
- Published
- Record last updated
- Exploit likelihood fell
CVE-2019-0211 scores 74. Action: Emergency patch.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isKey context
- Real threat activity around itKey context
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2019-0211 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2019-0211? 27 products.
The published record lists 27 products from 8 vendors. If you run one of these, check your version, then go to the fix below.
- Application
HTTP Server
by Apache
Affected versions2.4.17 to 2.4.38 - Operating system
Enterprise Linux Eus
by Red Hat
Affected versions8.18.28.48.68.8 - Operating system
Enterprise Linux for Arm 64 Eus
by Red Hat
Affected versions8.1_aarch648.2_aarch648.4_aarch648.6_aarch648.8_aarch64 - Operating system
Enterprise Linux for Ibm Z Systems Eus
by Red Hat
Affected versions8.1_s390x8.2_s390x8.4_s390x8.6_s390x8.8_s390x - Operating system
Enterprise Linux for Power Little Endian Eus
by Red Hat
Affected versions8.1_ppc64le8.2_ppc64le8.4_ppc64le8.6_ppc64le8.8_ppc64le - Operating system
Enterprise Linux Update Services for Sap Solutions
by Red Hat
Affected versions8.08.18.48.68.8 - Application
Communications Session Report Manager
by Oracle
Affected versions8.0.08.1.08.1.18.2.0 - Application
Communications Session Route Manager
by Oracle
Affected versions8.0.08.1.08.1.18.2.0 - Operating system
Enterprise Linux Server Tus
by Red Hat
Affected versions8.28.48.68.8
How do I fix CVE-2019-0211? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? EdgeProtect can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Check it wasn’t used before you patchedBecause criminals are already using this flaw, look for signs of a break-in on affected systems using the vendor’s guidance.
References
50 links- R9f93cf6dde308d42a9c807784e8102600d0397f5f834890708bf6920@<cvs.httpd.apache.org> (opens in a new tab)apache.org
- Bugtraq (opens in a new tab)seclists.org · 2019
- Cpuapr2020 (opens in a new tab)oracle.com
- Cpujul2019 5072835 (opens in a new tab)oracle.com
- Cpuoct2019 5072832 (opens in a new tab)oracle.com
- CHANGES 2.4.39 (opens in a new tab)apache.org
Does CVE-2019-0211 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 flaw being exploited affects software Acme tracks
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 (includi...
- Matched to
- HTTP Server on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2019-0211 is a high-severity flaw in HTTP Server from Apache, published on 8 April 2019. An attacker has to be already on the device with an ordinary user account, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.
It scores 7.8 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2019-0211 is 74 out of 100, which is High. Its action is "Emergency patch". Attackers are using this flaw today. If you run an affected version, it goes to the top of your list.
Attackers are already using it. It is on the government list of flaws known to be exploited, and the latest forecast puts the chance of it being used in the next 30 days at 65%.
For HTTP Server from Apache: 2.4.17 to 2.4.38. The record lists 27 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. Because criminals are already using it, also check affected systems for signs of a break-in.