FedoraOperating system · Fedoraproject
CVE-2022-45059
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 · uneditedAn issue was discovered in Varnish Cache 7.x before 7.1.2 and 7.2.x before 7.2.1. A request smuggling attack can be performed on Varnish Cache servers by requesting that certain headers are made hop-by-hop, preventing the Varnish Cache servers from forwarding critical headers to the backend.
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 confidenceVarnish Cache versions 7.x before 7.1.2 and 7.2.x before 7.2.1 are vulnerable to HTTP request smuggling via hop-by-hop header manipulation. Attackers can request that certain headers be treated as hop-by-hop, causing Varnish to strip critical headers before forwarding requests to backend servers, potentially allowing cache poisoning or bypass of security controls.
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
= 35= 36= 37>= 7.0.0, < 7.1.2= 7.2.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Varnish installationRun command 'varnishd -V' or check package manager for varnish-cache packageAffected if Varnish is not installed or version cannot be determined
-
Determine installed Varnish versionExecute 'varnishd -V' to retrieve version number; compare against affected ranges (7.0.0 through 7.1.1, or exactly 7.2.0)Affected if Version is 7.0.0 through 7.1.1, or version is exactly 7.2.0
-
Locate VCL configuration filesInspect default VCL configuration location (commonly /etc/varnish/ or path specified in varnishd startup parameters)Affected if Unable to locate VCL configuration files for review
-
Review VCL for custom hop-by-hop header handlingSearch VCL files for 'remove' or 'unset' directives targeting HTTP headers, or custom backend response processing that manipulates headersAffected if VCL contains explicit removal or manipulation of hop-by-hop headers (such as Connection, Keep-Alive, Transfer-Encoding, or custom headers defined as hop-by-hop)
User is affected if Varnish version is 7.0.0-7.1.1 or exactly 7.2.0, AND VCL configurations explicitly handle or remove hop-by-hop headers in a way that could be exploited for request smuggling.
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 · scoped7.1.2
Upgrade Varnish Cache to version 7.1.2 or 7.2.1 or later. Review VCL configurations for custom header handling that may interact with hop-by-hop headers.
Varnish Cache 7.1.2 or later (for 7.0.x-7.1.x); Varnish Cache 7.2.1 or later (for 7.2.0)
- 1. Check current Varnish Cache version: varnishd -V
- 2. For Varnish Cache 7.0.x - 7.1.x: Upgrade to version 7.1.2 or later (7.1.x series)
- 3. For Varnish Cache 7.2.0: Upgrade to version 7.2.1 or later (7.2.x series)
- 4. On Fedora systems: Run 'dnf update varnish' to apply the latest package
- 5. After upgrade, restart the Varnish service: systemctl restart varnish
- 6. Verify the new version is running: varnishd -V
- 7. Test that the vulnerability is remediated by ensuring hop-by-hop headers are properly forwarded to backends
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
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 locallyCheck whether your project pulls in CVE-2022-45059 — 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-45059 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