LiveActive security incident?Get immediate response
CVE Record

CVE-2022-38150: In 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 a...

In 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.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw can make affected Varnish Cache servers crash and restart when they process a malformed HTTP/1 response from a backend. The main business risk is service disruption, not data theft. Fixed releases are available for the named affected branches.

Executive priority

Treat as a targeted availability risk for internet-facing or business-critical caching layers. Patch in normal vulnerability cycles, faster where Varnish outages would affect revenue, customer access, or operational resilience.

Technical view

Varnish Cache 7.0.0, 7.0.1, 7.0.2, and 7.1.0 can assert and automatically restart after handling forged HTTP/1 backend responses with a crafted reason phrase in the status line. The CVSS 3.1 score is 6.5, driven by high availability impact.

Likely exposure

Exposure is likely limited to organizations running the listed Varnish Cache versions, especially where backend responses can be forged, influenced, or returned by less-trusted services. The source bundle does not identify other affected products.

Exploitation context

The source bundle and KEV status do not support active exploitation claims. The described attack path involves forged HTTP/1 backend responses and affects availability through server assertion and restart, with no stated confidentiality or integrity impact.

Researcher notes

Evidence is clear on affected upstream versions and fixed releases, but incomplete on real-world exploitation and compensating mitigations. Validate backend trust boundaries and package backports carefully; do not assume unaffected status from package version strings alone.

Mitigation direction

  • Upgrade Varnish Cache 7.0.x deployments to 7.0.3 or later.
  • Upgrade Varnish Cache 7.1.0 deployments to 7.1.1 or later.
  • Apply distribution security updates where Varnish is managed by OS packages.
  • Check Varnish and distribution vendor guidance before relying on compensating controls.

Validation and detection

  • Inventory Varnish Cache versions and flag 7.0.0, 7.0.1, 7.0.2, and 7.1.0.
  • Confirm fixed versions: 7.0.3, 7.1.1, or vendor backported package builds.
  • Review Varnish restart and assertion logs for unexplained availability events.
  • Check package changelogs or advisories for CVE-2022-38150 coverage.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-400: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-38150 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2022-38150Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-400 · source CWE mapping

Uncontrolled Resource Consumption

Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.