FedoraOperating system · Fedoraproject
CVE-2022-38150
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 · uneditedIn Varnish Cache 7.0.0, 7.0.1, 7.0.2, and 7.1.0, it is possible to cause the Varnish Server to assert and automatically restart through forged HTTP/1 backend responses. An attack uses a crafted reason phrase of the backend response status line. This is fixed in 7.0.3 and 7.1.1.
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.0.0 through 7.1.0 contain a vulnerability in HTTP/1 backend response parsing. An attacker who can control backend responses can send a specially crafted reason phrase in the HTTP status line that triggers an assertion failure, causing the Varnish server to crash and automatically restart, resulting in denial of service.
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= 7.0.0= 7.0.1= 7.0.2= 7.1.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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Check installed Varnish Cache versionRun `varnishd -V` or `varnishstat -V` to display the version numberAffected if Version is 7.0.0, 7.0.1, 7.0.2, or 7.1.0
-
Identify configured backend serversReview Varnish configuration files (typically in /etc/varnish/ or defined via varnishadm) for 'backend' or 'director' definitions that specify HTTP/1 serversAffected if Any HTTP/1 backend is configured and active
-
Verify backend network exposureInspect backend configuration for bind addresses and network ACLs; check firewall rules or VCL access control lists that govern which systems can respond as backendsAffected if Backends are reachable from untrusted network segments or non-administered systems
System is affected if Varnish Cache version is 7.0.0 through 7.1.0 and the system processes HTTP/1 responses from backends that could be controlled by an attacker.
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 · scopedUpgrade Varnish Cache to version 7.0.3, 7.1.1, or later. Until patched, restrict access to backend servers to trusted sources only and implement network segmentation to prevent untrusted actors from injecting malicious backend responses.
Varnish Cache 7.0.3 or 7.1.1 (or newer stable release)
- Check the currently installed Varnish Cache version using 'varnishd -V' or 'rpm -q varnish'
- For Fedora systems, run 'sudo dnf update varnish' to upgrade to the fixed version
- For standalone Varnish installations, download and install Varnish Cache 7.0.3 or 7.1.1 from the official Varnish cache repository
- After upgrading, restart the Varnish service using 'sudo systemctl restart varnish'
- Verify the installed version is now 7.0.3, 7.1.1, or newer using 'varnishd -V'
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fedora
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38150 — 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-38150 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