dbcve.org
HTTP ServerWeb server / proxy · Apache

CVE-2022-28615

CRITICAL · 9.1 CVSS v3.1 Published 2022-06-09
Fix available
A fix is available. Upgrade to 2.4.54 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Apache HTTP Server 2.4.53 and earlier may crash or disclose information due to a read beyond bounds in ap_strcmp_match() when provided with an extremely large input buffer. While no code distributed with the server can be coerced into such a call, third-party modules or lua scripts that use ap_strcmp_match() may hypothetically be 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 · moderate confidence

Out-of-bounds read vulnerability in ap_strcmp_match() function in Apache HTTP Server 2.4.53 and earlier allows crash or information disclosure when provided with extremely large input buffers. While core server code cannot be coerced into calling this function unsafely, third-party modules or Lua scripts that use ap_strcmp_match() are potentially affected.

MitigationUpgrade to Apache HTTP Server 2.4.54 or later; audit and review any third-party modules or Lua scripts that utilize ap_strcmp_match() for similar input validation issues.

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.54
FedoraOperating system
Affected:= 35= 36
Clustered Data OntapApplication
Affected:all versions

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 installed Apache HTTP Server version
    Run 'httpd -v' or 'apache2 -v' to display the server version, or check the package version via your system's package manager (e.g., 'rpm -q httpd', 'dpkg -l apache2')
    Affected if Version is earlier than 2.4.54 (e.g., 2.4.53 or older)
  2. Identify loaded third-party modules
    Review the configuration files (httpd.conf, conf.d) for 'LoadModule' directives pointing to non-standard modules, and list all .so files in the modules directory that are not part of the core Apache distribution
    Affected if Any third-party modules (not included with default Apache installation) are loaded and may call ap_strcmp_match()
  3. Audit Lua scripts in the server environment
    Search for .lua files in web-accessible directories, ScriptAlias paths, and any custom include directories configured for Lua scripting (e.g., via mod_lua)
    Affected if Lua scripts are present and could invoke ap_strcmp_match() through Apache API calls
  4. Search custom module source code for ap_strcmp_match usage
    If you have access to source code of any custom or third-party modules, grep for 'ap_strcmp_match' to determine if the vulnerable function is being called
    Affected if Custom module source code contains calls to ap_strcmp_match() with user-controlled input

You are affected if your Apache version is earlier than 2.4.54 AND you have third-party modules or Lua scripts that utilize the ap_strcmp_match() function with external input.

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 2.4.54 or later
Fixed in 2.4.54
Interim mitigation

Upgrade to Apache HTTP Server 2.4.54 or later; audit and review any third-party modules or Lua scripts that utilize ap_strcmp_match() for similar input validation issues.

Recommended fix High confidence

Apache HTTP Server 2.4.54 or later

  1. 1. Identify the current Apache HTTP Server version installed by running: httpd -v or apache2 -v
  2. 2. For upstream Apache installations: Download Apache HTTP Server version 2.4.54 or later from httpd.apache.org or your distribution's package repository
  3. 3. For Fedora systems: Update the system using 'dnf update httpd' to receive the patched version, or upgrade to a newer Fedora release that includes the fix
  4. 4. For NetApp Clustered Data ONTAP: Apply the appropriate patch or upgrade as specified in the NetApp security advisory at security.netapp.com
  5. 5. After upgrading, restart the Apache service: systemctl restart httpd (or apache2)
  6. 6. Verify the new version is running: httpd -v or apache2 -v
Caveat Minimal risk - the vulnerability is in ap_strcmp_match() and the description indicates no code distributed with the server can be coerced into the vulnerable call; third-party modules/lua scripts that use this function may need review

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

Fix this in HTTP Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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