dbcve.org
HTTP ServerWeb server / proxy · Apache

CVE-2019-10097

HIGH · 7.2 CVSS v3.1 Published 2019-09-26
Fix available
A fix is available. Upgrade to after 17.3 or later.
See remediation →
78/100
Remediation priority · High
High EPSS Remotely reachable Zero-click

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.32-2.4.39, when mod_remoteip was configured to use a trusted intermediary proxy server using the "PROXY" protocol, a specially crafted PROXY header could trigger a stack buffer overflow or NULL pointer deference. This vulnerability could only be triggered by a trusted proxy and not by untrusted HTTP clients.

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

A stack buffer overflow or NULL pointer dereference exists in mod_remoteip when processing specially crafted PROXY protocol headers from a trusted proxy server. This memory corruption vulnerability in Apache HTTP Server 2.4.32-2.4.39 could allow a compromised trusted proxy to crash the server or potentially execute arbitrary code.

MitigationUpgrade Apache HTTP Server to version 2.4.40 or later, which contains the fix. Until then, ensure that only explicitly trusted proxies can send PROXY protocol headers, and consider disabling mod_remoteip PROXY protocol support if not required.

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.33= 2.4.34= 2.4.35= 2.4.37= 2.4.38
HTTP ServerWeb server / proxy
Affected:= 12.2.1.4.0
Communications Element ManagerApplication
Affected:= 8.0.0= 8.1.0= 8.1.1= 8.2.0
Communications Session Report ManagerApplication
Affected:= 8.1.1= 8.2.0= 8.2.1
Communications Session Route ManagerApplication
Affected:= 8.1.1= 8.2.0= 8.2.1
Enterprise Manager Ops CenterApplication
Affected:= 12.3.3= 12.4.0
Instantis EnterprisetrackApplication
Affected:>= 17.1, <= 17.3
Retail Xstore Point Of ServiceApplication
Affected:= 7.1

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
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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. Identify installed Apache HTTP Server version
    Run 'httpd -v' or 'apache2 -v' to get the server version, or check the package manager for the installed httpd/apache2 package version
    Affected if The installed version is 2.4.32 through 2.4.39 (specifically 2.4.33, 2.4.34, 2.4.35, 2.4.37, or 2.4.38)
  2. Verify mod_remoteip is loaded
    Run 'httpd -M' or 'apache2ctl -M' to list loaded modules, or check for 'LoadModule remoteip_module' in the httpd.conf/apache2.conf configuration files
    Affected if mod_remoteip is loaded and visible in the module list
  3. Confirm PROXY protocol support is enabled in mod_remoteip
    Search configuration files for 'RemoteIPProxyProtocol' directive (e.g., grep -r 'RemoteIPProxyProtocol' /etc/apache2/ /etc/httpd/)
    Affected if The RemoteIPProxyProtocol directive is present and enabled (value is 'on' or not explicitly set to 'off')
  4. Identify configured trusted proxy servers
    Search for 'RemoteIPTrustedProxy' or 'RemoteIPTrustedProxyList' directives in Apache configuration to list allowed proxy IP addresses or networks
    Affected if Any trusted proxy is configured, meaning the server accepts PROXY protocol headers from those sources
  5. Check Oracle product installations for affected versions
    For Oracle products, use the vendor's version reporting tools or check installed software inventory for: Oracle HTTP Server 12.2.1.4.0, Oracle Communications Element Manager 8.0.0-8.2.0, Oracle Communications Session Report Manager 8.1.1-8.2.1, Oracle Communications Session Route Manager 8.1.1-8.2.1, Oracle Enterprise Manager Ops Center 12.3.3-12.4.0, Oracle Instantis Enterprisetrack 17.1-17.3, or Oracle Retail Xstore Point Of Service 7.1
    Affected if Any of the listed Oracle products are installed at the specified versions

You are affected if you run Apache HTTP Server 2.4.32-2.4.39 with mod_remoteip loaded and PROXY protocol support enabled, or use any of the listed Oracle products at the affected versions, AND you accept PROXY protocol headers from any trusted proxy.

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.

From vendor data
Upgrade available Upgrade to a release after 17.3
Interim mitigation

Upgrade Apache HTTP Server to version 2.4.40 or later, which contains the fix. Until then, ensure that only explicitly trusted proxies can send PROXY protocol headers, and consider disabling mod_remoteip PROXY protocol support if not required.

Fix this in HTTP Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-10097 — 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-10097 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