dbcve.org
HTTP ServerWeb server / proxy · Apache

CVE-2022-28614

MEDIUM · 5.3 CVSS v3.1 Published 2022-06-09
Fix available
A fix is available. Upgrade to after 2.4.53 or later.
See remediation →
62/100
Remediation priority · Elevated
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
The ap_rwrite() function in Apache HTTP Server 2.4.53 and earlier may read unintended memory if an attacker can cause the server to reflect very large input using ap_rwrite() or ap_rputs(), such as with mod_luas r:puts() function. Modules compiled and distributed separately from Apache HTTP Server that use the 'ap_rputs' function and may pass it a very large (INT_MAX or larger) string must be compiled against current headers to resolve the issue.

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 memory disclosure vulnerability in Apache HTTP Server 2.4.53 and earlier allows the ap_rwrite() function to read unintended memory when processing very large (INT_MAX or larger) inputs via ap_rwrite() or ap_rputs(). The mod_lua module's r:puts() function can be exploited to trigger this condition, and separately compiled modules using ap_rputs may also be vulnerable if not recompiled against current headers.

MitigationUpgrade Apache HTTP Server to version 2.4.54 or later, and recompile any third-party modules against current headers to resolve the ap_rputs() issue. If mod_lua is in use, audit any r:puts() calls for potential abuse.

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.53
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
Low
Integrity
None
Availability
None

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

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 Apache HTTP Server version
    Run 'httpd -v' (or 'apache2 -v' on Debian/Ubuntu) and note the server version number
    Affected if Version is 2.4.53 or earlier
  2. Verify mod_lua module status
    Run 'httpd -M' (or 'apache2ctl -M') and search for 'lua_module' in the output
    Affected if The lua_module is loaded and mod_lua is active
  3. Identify third-party modules
    Run 'httpd -M' (or 'apache2ctl -M') and review all loaded modules for any that are not part of the standard Apache distribution (third-party or custom-built)
    Affected if Any third-party or custom modules are loaded that may use ap_rputs() and were compiled against older headers
  4. Confirm OS package version (if applicable)
    Check the installed package version via 'rpm -q httpd' (RHEL/CentOS) or 'dpkg -l apache2' (Debian/Ubuntu)
    Affected if The packaged version number corresponds to Apache 2.4.53 or earlier

You are affected if your Apache HTTP Server version is 2.4.53 or earlier, especially if mod_lua is enabled or any third-party modules compiled against older headers are in use.

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.53
Interim mitigation

Upgrade Apache HTTP Server to version 2.4.54 or later, and recompile any third-party modules against current headers to resolve the ap_rputs() issue. If mod_lua is in use, audit any r:puts() calls for potential abuse.

Recommended fix High confidence

Apache HTTP Server 2.4.54 or later

  1. Upgrade Apache HTTP Server to version 2.4.54 or later
  2. If using mod_lua or any third-party modules that use ap_rwrite() or ap_rputs(), recompile those modules against the updated Apache headers
  3. Restart the Apache HTTP Server after applying the upgrade
  4. Verify the fix by testing that large input to mod_lua r:puts() or similar functions no longer causes unexpected memory reads
Caveat Modules using ap_rwrite() or ap_rputs() must be recompiled against the new headers - this is required per the official description

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-28614 — 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-28614 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