dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 3 May 2022.
HTTP ServerWeb server / proxy · Apache

CVE-2019-0211

HIGH · 7.8 CVSS v3.1 Published 2019-04-08
Fix available
A fix is available. Upgrade to after 2.4.38 or later.
See remediation →
96/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache HTTP Server 2.4.17-2.4.38 contains a privilege escalation vulnerability in the event, worker, and prefork MPM modules where child processes or threads running with lower privileges can manipulate the scoreboard to execute arbitrary code with parent process (root) privileges.

MitigationUpgrade to Apache HTTP Server 2.4.39 or later which contains the fix; alternatively, consider using MPM_ITK or other isolation mechanisms if upgrade is not immediately feasible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
HTTP ServerWeb server / proxy
Affected:>= 2.4.17, <= 2.4.38
FedoraOperating system
Affected:= 28= 29= 30
Ubuntu LinuxOperating system
Affected:= 14.04= 16.04= 18.04= 18.10
Debian LinuxOperating system
Affected:= 9.0
Jboss Core ServicesApplication
Affected:= 1.0
Openshift Container PlatformApplication
Affected:= 3.11
Openshift Container Platform For PowerApplication
Affected:= 3.11_ppc64le
Software CollectionsApplication
Affected:= 1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Apache HTTP Server is installed
    Run 'httpd -v' or 'apache2 -v' to display the installed Apache version
    Affected if Apache is installed and the version displayed is between 2.4.17 and 2.4.38 inclusive
  2. Identify the MPM module in use
    Run 'httpd -M' or 'apache2ctl -M' and look for 'mpm_' module in the output; alternatively, check the configuration file for 'LoadModule mpm_*' directive
    Affected if The MPM is event, worker, or prefork (mpm_event, mpm_worker, mpm_prefork)
  3. Verify the scoreboard file location and permissions
    Check the scoreboard file path in the configuration (directive 'ScoreboardFile') and verify its permissions with 'ls -la'; also check if the Apache process has write access to it
    Affected if The scoreboard file is writable by the Apache child processes or the default scoreboard location is used without restrictive permissions

A system is affected if Apache HTTP Server version 2.4.17-2.4.38 is running with event, worker, or prefork MPM, allowing child processes to manipulate the scoreboard for privilege escalation

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2.4.38
Vendor patch lists.apache.org →
Interim mitigation

Upgrade to Apache HTTP Server 2.4.39 or later which contains the fix; alternatively, consider using MPM_ITK or other isolation mechanisms if upgrade is not immediately feasible.

Recommended fix High confidence

Apache HTTP Server 2.4.39 or later (preferably latest 2.4.x stable release)

  1. Verify current Apache version with: httpd -v or apache2 -v
  2. For RHEL/CentOS/Fedora: sudo dnf update httpd or sudo yum update httpd
  3. For Debian/Ubuntu: sudo apt-get update && sudo apt-get install apache2
  4. For SUSE: sudo zypper update apache2
  5. Restart Apache service: sudo systemctl restart httpd or sudo systemctl restart apache2
  6. Verify the new version is >= 2.4.39 with httpd -v
Caveat Standard Apache upgrade - review release notes for any module or configuration changes; test configurations before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in HTTP Server Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-0211 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-0211 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data