dbcve.org
FedoraOperating system · Fedoraproject

CVE-2022-45060

HIGH · 7.5 CVSS v3.1 Published 2022-11-09
Fix available
A fix is available. Upgrade to 6.0.11 / 7.1.2 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
An HTTP Request Forgery issue was discovered in Varnish Cache 5.x and 6.x before 6.0.11, 7.x before 7.1.2, and 7.2.x before 7.2.1. An attacker may introduce characters through HTTP/2 pseudo-headers that are invalid in the context of an HTTP/1 request line, causing the Varnish server to produce invalid HTTP/1 requests to the backend. This could, in turn, be used to exploit vulnerabilities in a server behind the Varnish server. Note: the 6.0.x LTS series (before 6.0.11) is affected.

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

Varnish Cache does not properly sanitize HTTP/2 pseudo-headers during conversion to HTTP/1 when proxying requests to backends. Attackers can inject invalid characters via HTTP/2 requests that result in malformed HTTP/1 request lines being forwarded to backend servers, potentially exploiting vulnerabilities in those backends.

MitigationUpgrade Varnish Cache to version 6.0.11, 7.1.2, 7.2.1 or later to patch the HTTP/2 to HTTP/1 header sanitization flaw.

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
FedoraOperating system
Affected:= 35= 36= 37
Debian LinuxOperating system
Affected:= 10.0= 11.0
Varnish CacheApplication
Affected:>= 6.0.0, < 6.0.11
Varnish Cache PlusApplication
Affected:= 6.0.0= 6.0.1= 6.0.2= 6.0.3= 6.0.4= 6.0.5= 6.0.6= 6.0.7= 6.0.8= 6.0.9= 6.0.10
Varnish CacheApplication
Affected:>= 5.0.0, < 6.0.11>= 7.0.0, < 7.1.2= 7.2.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

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 installed Varnish version
    Run 'varnishd -V' or check package manager output (e.g., 'rpm -q varnish' on Fedora/RHEL, 'dpkg -l varnish' on Debian)
    Affected if Version is 5.x, 6.0.0-6.0.10, 7.0.0-7.1.1, or 7.2.0 (falls within the affected ranges)
  2. Verify HTTP/2 protocol is enabled on the frontend
    Inspect VCL configuration file (typically /etc/varnish/default.vcl) for 'h2' parameter in the 'vcl_recv' or frontend listener section, or check running config with 'varnishd -C' and search for 'h2' or 'proto' settings
    Affected if HTTP/2 (h2) is enabled as a frontend protocol - the flaw only triggers when HTTP/2 requests are received
  3. Confirm backend connections use HTTP/1
    Inspect VCL for backend definitions and check the 'proxy_header' or 'proto' settings. Look for backends defined without explicit HTTP/2 protocol, which default to HTTP/1 for backend connections
    Affected if Backends are configured to use HTTP/1 (the default) while frontend accepts HTTP/2 - this creates the HTTP/2 to HTTP/1 conversion path that triggers the flaw
  4. Check for HTTP/2 to backend proxying
    Review VCL backend probe configurations and the 'http' block settings. The vulnerability activates when HTTP/2 frontend connections are proxied to HTTP/1 backends
    Affected if Frontend accepts HTTP/2 traffic AND proxies to HTTP/1 backends simultaneously

You are affected if running a vulnerable Varnish version AND HTTP/2 is enabled on the frontend while backends use HTTP/1, enabling the conversion path where malformed request lines can be injected.

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 6.0.11 / 7.1.2 or later
Fixed in 6.0.117.1.2
Interim mitigation

Upgrade Varnish Cache to version 6.0.11, 7.1.2, 7.2.1 or later to patch the HTTP/2 to HTTP/1 header sanitization flaw.

Recommended fix High confidence

6.0.11 (for 6.x), 7.1.2 (for 7.0-7.1.x), or 7.2.1 (for 7.2.x)

  1. Identify the currently installed Varnish Cache version using 'varnishd -V'
  2. For Varnish Cache 6.0.x: upgrade to version 6.0.11 or later
  3. For Varnish Cache 7.0.x - 7.1.x: upgrade to version 7.1.2 or later
  4. For Varnish Cache 7.2.0: upgrade to version 7.2.1 or later
  5. Verify the upgrade was successful by running 'varnishd -V'
  6. Restart the Varnish service to load the new version using 'systemctl restart varnish'

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

Fix this in Fedora Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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