dbcve.org
HTTP ServerWeb server / proxy · Apache

CVE-2022-30522

HIGH · 7.5 CVSS v3.1 Published 2022-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
High EPSS 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
If Apache HTTP Server 2.4.53 is configured to do transformations with mod_sed in contexts where the input to mod_sed may be very large, mod_sed may make excessively large memory allocations and trigger an abort.

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's mod_sed module makes excessively large memory allocations when configured to perform transformations on very large inputs, causing the server to abort. This results in a denial-of-service condition.

MitigationUpgrade Apache HTTP Server to version 2.4.54 or later, or disable mod_sed if not required, and implement input size limits on contexts using mod_sed transformations.

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. Check Apache HTTP Server version
    Run 'httpd -v' or 'apache2 -v' to retrieve the installed Apache version
    Affected if Version is exactly 2.4.53
  2. Verify mod_sed module is loaded
    Run 'httpd -M' or 'apache2ctl -M' and grep for 'sed_module', or check for 'LoadModule sed_module' in the httpd.conf configuration file
    Affected if mod_sed appears in the loaded modules list
  3. Inspect mod_sed configuration for active transformations
    Search configuration files (httpd.conf, included .conf files) for 'mod_sed' directives such as 'SedInputFile', 'SedOutputFile', 'SedAddOutputFilter', or 'SedSendTimeLimit' that are actively transforming data
    Affected if mod_sed transformation directives are configured and pointing to large input sources or files
  4. Check if running on affected Fedora version
    Run 'cat /etc/fedora-release' to identify the Fedora version
    Affected if Running Fedora 35 or 36 with Apache HTTP Server 2.4.53 and mod_sed enabled with transformations
  5. Check if running on affected NetApp ONTAP
    Identify the NetApp storage system and consult NetApp product documentation for the embedded Apache version used in the specific ONTAP version
    Affected if Any NetApp Clustered Data ONTAP version with mod_sed enabled and configured for transformations

You are affected if you are running Apache HTTP Server 2.4.53 (or the specific Fedora/NetApp products) with mod_sed loaded and actively configured to perform transformations on large inputs, as the vulnerability requires mod_sed to be both enabled and in use with substantial data.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Apache HTTP Server to version 2.4.54 or later, or disable mod_sed if not required, and implement input size limits on contexts using mod_sed transformations.

Recommended fix High confidence

Apache HTTP Server 2.4.54 or later

  1. Identify the current Apache HTTP Server version using: httpd -v or apache2 -v
  2. If running version 2.4.53, plan for upgrade to version 2.4.54 or later
  3. For source compilation: Download Apache HTTP Server 2.4.54 or newer from httpd.apache.org
  4. For package management: Run 'dnf update httpd' (Fedora) or 'apt-get update && apt-get upgrade apache2' (Debian/Ubuntu)
  5. For NetApp Clustered Data ONTAP: Follow the vendor-specific security advisory at security.netapp.com for patches or workarounds
  6. After upgrade, restart the Apache service: systemctl restart httpd (or apache2)
  7. Verify the new version is installed: httpd -v
  8. Test that mod_sed functionality works correctly with the new version
Caveat Minor: Ensure any custom mod_sed configurations are tested after upgrade as behavior may have changed

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
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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