Backend request forgery via invalid HTTP/2 pseudo-headers
Published Nov 9, 2022 · Updated May 1, 2025
HTTP request forgery in affected Varnish Cache releases allows remote attackers to forge requests to backend servers over HTTP/2. HTTP/2 pseudo-header values populate req.url and req.method without rejection of spaces, tabs, or empty values before HTTP/1 serialization. HTTP/2 must be enabled, and impact depends on a backend that interprets the malformed request in an exploitable way.
Summary
What happened
HTTP request forgery in affected Varnish Cache releases allows remote attackers to forge requests to backend servers over HTTP/2. HTTP/2 pseudo-header values populate req.url and req.method without rejection of spaces, tabs, or empty values before HTTP/1 serialization. HTTP/2 must be enabled, and impact depends on a backend that interprets the malformed request in an exploitable way.
The record
- CVE
- CVE-2022-45060
- Published
- Nov 9, 2022
- Updated
- May 1, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 9, 2022CVE publishedPublication date reported by the CVE source.
- May 1, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo