Skip to main content
No exploitation reportedFix available

CVE-2019-10081

No exploitation reported by the sources we read.

  • Published2019-08-15
  • WeaknessCWE-787

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

HTTP/2 (2.4.20 through 2.4.39) very early pushes, for example configured with "H2PushResource", could lead to an overwrite of memory in the pushing request's pool, leading to crashes. The memory copied is that of the configured push link header values, not data supplied by the client.

Timeline

dates in UTC
  1. 2019-08-1522:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-11-03 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2019-10081?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2019-10081?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Apache HTTP Server
BranchAffectedFixed in
2.4≥ 2.4.20, ≤ 2.4.39no fix published
Debian debian linux
BranchAffectedFixed in
9.0= 9.0no fix published
10.0= 10.0no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • apacheMageia:7all versions · fixed in 2.4.41-1.2.mga7
  • apache2Ubuntu:18.04:LTSall versions · fixed in 2.4.29-1ubuntu4.10
  • apache2Ubuntu:16.04:LTSall versions · fixed in 2.4.18-2ubuntu3.12
  • apache2SUSE:Linux Enterprise Software Development Kit 12 SP4all versions · fixed in 2.4.23-29.43.1
  • apache2SUSE:Linux Enterprise Server for SAP Applications 12 SP4all versions · fixed in 2.4.23-29.43.1
  • apache2SUSE:Linux Enterprise Server 12 SP4all versions · fixed in 2.4.23-29.43.1
  • apache2SUSE:Linux Enterprise Module for Server Applications 15 SP1all versions · fixed in 2.4.33-3.21.1
  • apache2SUSE:Linux Enterprise Module for Server Applications 15all versions · fixed in 2.4.33-3.21.1

49 more package ranges on OSV.dev

Vendor advisories

  • CVE-2019-10081 Red Hat Product Security175 products fixed · 15 known affected

    httpd: memory corruption on early pushes

    httpd22 as a component of Red Hat JBoss Enterprise Web Server 2 · jbcs-httpd24 as a component of Red Hat JBoss Enterprise Web Server 2 · jbcs-httpd24-runtime as a component of Red Hat JBoss Enterprise Web Server 2 · +12 more

  • RHSA-2020:4751 Red Hat Product Security85 products fixed

    Red Hat Security Advisory: httpd:2.4 security, bug fix, and enhancement update

  • RHSA-2020:1337 Red Hat Product Security89 products fixed

    Red Hat Security Advisory: Red Hat JBoss Core Services Apache HTTP Server 2.4.37 SP2 security update

  • RHSA-2020:1336 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: Red Hat JBoss Core Services Apache HTTP Server 2.4.37 SP2 security update

Full record on NVD

Fix

  1. Vendor fix Red Hat Product Security RHSA-2020:4751 · 85 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the updated packages, the httpd daemon will be restarted automatically.
  2. Vendor fix Red Hat Product Security RHSA-2020:1337 · 89 productsBefore applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
  3. Vendor fix Red Hat Product Security RHSA-2020:1336 · 1 productThe References section of this erratum contains a download link (you must log in to download the update). Before applying the update, back up your existing Red Hat JBoss Core Services installation (including all applications and configuration files).
  4. Workaround from the vendor Red Hat Product Security RHSA-2020:4751 · 85 productsThis flaw is only exploitable if Apache httpd is configured to respond to HTTP/2 requests, which is done by including "h2" or "h2c" in the "Protocols" list in a configuration file. The following command can be used to search for possible vulnerable configurations: grep -R '^\s*Protocols\>.*\…
  5. No fix planned, says the vendor Red Hat Product Security CVE-2019-10081 · 5 productsOut of support scope
  6. No fix planned, says the vendor Red Hat Product Security CVE-2019-10081 · 10 productsWill not fix

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVSS 3.07.5read 2026-10-23
  • NVDCVSS 2.05read 2026-10-23
  • NVDweakness (CWE)CWE-787read 2026-10-23
  • FIRST EPSSEPSS score14.6 %read 2026-11-03
  • OSVaffected packages—

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Published
2019-08-15
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2019-10081?

HTTP/2 (2.4.20 through 2.4.39) very early pushes, for example configured with "H2PushResource", could lead to an overwrite of memory in the pushing request's pool, leading to crashes. The memory copied is that of the configured push link header values, not data supplied by the client.

Is CVE-2019-10081 actively exploited?

Active exploitation of CVE-2019-10081 has not been confirmed. Its EPSS score was 14.6% on 2026-11-03, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2019-10081?

CVE-2019-10081 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Running Apache HTTP Server? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record