dbcve.org
HTTP ServerWeb server / proxy · Apache

CVE-2022-29404

HIGH · 7.5 CVSS v3.1 Published 2022-06-09
Fix available
A fix is available. Upgrade to after 2.4.53 or later.
See remediation →
84/100
Remediation priority · High
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
In Apache HTTP Server 2.4.53 and earlier, a malicious request to a lua script that calls r:parsebody(0) may cause a denial of service due to no default limit on possible input size.

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.53 and earlier contains a vulnerability where lua scripts calling r:parsebody(0) lack a default limit on input size, allowing attackers to send arbitrarily large request bodies causing denial of service.

MitigationConfigure appropriate input size limits for lua r:parsebody() calls in affected scripts, or upgrade Apache HTTP Server to version 2.4.54 or later which includes a default limit.

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Identify Apache HTTP Server version
    Run 'httpd -v' or 'apache2 -v' to get the server version number
    Affected if version is 2.4.53 or earlier
  2. Verify lua module is loaded
    Check for 'mod_lua' in httpd -M output or in loaded modules configuration
    Affected if lua module is enabled and loaded
  3. Search for lua scripts using parsebody(0)
    Search source files (*.lua) and configuration files for the pattern 'r:parsebody(0)'
    Affected if lua scripts containing 'r:parsebody(0)' are found in the web root or configuration directories

Environment is affected if Apache HTTP Server version is 2.4.53 or earlier, the lua module is enabled, and lua scripts using r:parsebody(0) are deployed and accessible.

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

Configure appropriate input size limits for lua r:parsebody() calls in affected scripts, or upgrade Apache HTTP Server to version 2.4.54 or later which includes a default limit.

Recommended fix High confidence

Apache HTTP Server 2.4.54 or later

  1. 1. Identify the current Apache HTTP Server version (e.g., httpd -v or apache2 -v)
  2. 2. Upgrade Apache HTTP Server to version 2.4.54 or later which contains the fix for the lua r:parsebody(0) resource limit
  3. 3. For Fedora systems: update via 'dnf update httpd' to get the patched package for your Fedora release
  4. 4. For NetApp Clustered Data ONTAP: refer to NetApp's security advisory at security.netapp.com for specific patch instructions
  5. 5. After upgrading, restart the Apache service (e.g., systemctl restart httpd or systemctl restart apache2)
  6. 6. Verify the new version is installed and the service is running
Caveat Minimal risk - this is a bugfix release; however, test lua scripts that use r:parsebody(0) in a staging environment before production deployment as behavior may differ with the new limits

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
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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