dbcve.org
HTTP ServerWeb server / proxy · Apache

CVE-2022-31813

CRITICAL · 9.8 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 not send the X-Forwarded-* headers to the origin server based on client side Connection header hop-by-hop mechanism. This may be used to bypass IP based authentication on the origin server/application.

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 fails to properly forward X-Forwarded-* headers to origin servers when acting as a reverse proxy. Attackers can manipulate the hop-by-hop Connection header to prevent X-Forwarded-For, X-Forwarded-Host, and similar headers from being sent to backend applications, enabling bypass of IP-based access controls and authentication mechanisms.

MitigationUpgrade Apache HTTP Server to version 2.4.54 or later. Review and harden reverse proxy configurations to ensure X-Forwarded-* headers are explicitly forwarded to origin servers, and implement additional authentication controls beyond IP-based filtering.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Check Apache HTTP Server version
    Run 'httpd -v' or 'apache2 -v' to obtain the installed version number
    Affected if Version is 2.4.53 or earlier
  2. Confirm reverse proxy modules are loaded
    Inspect the Apache configuration for loaded proxy modules (proxy_module, proxy_http_module) or check loaded modules with 'httpd -M' | grep proxy
    Affected if Proxy modules are enabled and the server is configured as a reverse proxy
  3. Identify reverse proxy configuration
    Search Apache config files (httpd.conf, included .conf files) for ProxyPass, ProxyPassReverse, or similar reverse proxy directives
    Affected if The server uses ProxyPass/ProxyPassReverse to forward requests to backend origin servers
  4. Verify X-Forwarded-* header handling
    Examine the proxy configuration for ProxyPreserveHost, RequestHeader set directives, or custom header manipulation rules related to X-Forwarded-For, X-Forwarded-Host, or X-Forwarded-Proto
    Affected if No explicit configuration exists to ensure X-Forwarded-* headers are preserved and forwarded to backend applications
  5. Check Fedora version if applicable
    If running on Fedora, run 'cat /etc/fedora-release' to confirm the distribution version
    Affected if Running Fedora 35 or 36 with bundled Apache version below 2.4.54
  6. Confirm NetApp storage system if applicable
    For NetApp Clustered Data Ontap systems, verify the Apache component version through NetApp documentation or system diagnostics
    Affected if Any version of NetApp Clustered Data Ontap containing the vulnerable Apache component

The environment is affected if Apache HTTP Server version is below 2.4.54 and the server is configured as a reverse proxy without explicit X-Forwarded-* header forwarding rules.

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 Apache HTTP Server to version 2.4.54 or later. Review and harden reverse proxy configurations to ensure X-Forwarded-* headers are explicitly forwarded to origin servers, and implement additional authentication controls beyond IP-based filtering.

Recommended fix High confidence

2.4.54

  1. For Apache HTTP Server installations: Upgrade to version 2.4.54 or later
  2. For Fedora systems: Run 'dnf update httpd' or 'dnf update' to apply the patched package
  3. Restart the Apache HTTP Server service after updating (e.g., 'systemctl restart httpd')
  4. For NetApp Clustered Data ONTAP: Apply the appropriate patch from security.netapp.com (reference advisory NTAP-20220616-0001)
  5. Verify the fix by checking that X-Forwarded-* headers are now properly forwarded to backend servers

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

Fix this in HTTP Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
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,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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