HTTP ServerWeb server / proxy · Apache
CVE-2022-36760
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 · uneditedInconsistent Interpretation of HTTP Requests ('HTTP Request Smuggling') vulnerability in mod_proxy_ajp of Apache HTTP Server allows an attacker to smuggle requests to the AJP server it forwards requests to. This issue affects Apache HTTP Server Apache HTTP Server 2.4 version 2.4.54 and prior versions.
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 confidenceHTTP Request Smuggling vulnerability in mod_proxy_ajp allows attackers to craft malicious HTTP requests that bypass front-end security controls by manipulating Content-Length headers or request boundaries, enabling injection of unauthorized requests through the AJP proxy to backend servers.
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
>= 2.4.0, < 2.4.55CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Apache versionRun 'httpd -v' or 'apache2 -v' to get the server versionAffected if Version is >= 2.4.0 and < 2.4.55
-
Verify mod_proxy_ajp is loadedCheck if the module is listed in the loaded modules: 'httpd -M' or 'apache2ctl -M' look for proxy_ajp_moduleAffected if mod_proxy_ajp appears in the loaded modules list
-
Check for AJP proxy configurationExamine Apache configuration files for 'ProxyRequests' or 'ProxyPass' directives using the ajp:// protocol schemeAffected if A proxy configuration using ajp:// protocol is present
A user is affected if they are running Apache 2.4.0 through 2.4.54 with mod_proxy_ajp enabled and configured to proxy AJP requests to a backend server.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.4.55
Update Apache HTTP Server to version 2.4.55 or later which contains the fix for this vulnerability. If immediate patching is not possible, consider disabling mod_proxy_ajp if not required or implementing additional WAF rules to detect smuggling patterns.
Apache HTTP Server 2.4.55 or later
- 1. Identify the current Apache HTTP Server version using: `httpd -v` or `apache2 -v`
- 2. Check if mod_proxy_ajp is in use by reviewing the Apache configuration files (httpd.conf, included conf files)
- 3. Stop the Apache HTTP Server service: `systemctl stop apache2` or `systemctl stop httpd`
- 4. Update the package repository and install the fixed version: `apt-get update && apt-get install apache2` (Debian/Ubuntu) or `yum update httpd` (RHEL/CentOS)
- 5. Verify the new version is >= 2.4.55 using: `httpd -v`
- 6. Start the Apache HTTP Server service: `systemctl start apache2` or `systemctl start httpd`
- 7. Test that the AJP proxy functionality continues to work correctly
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 / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36760 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-36760 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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