cve.bz

CVE-2022-38150 Uncontrolled Resource Consumption

7.5 highEPSS 1.5%

High (7.5). EPSS 1.5% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
1.5% (unchanged from 1.5% a week ago; 1.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 75th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-10-20. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-400 Uncontrolled Resource Consumption
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-38150 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-38150?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-38150?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-38150 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
varnish_cache_project:varnish_cache7.0.0
varnish_cache_project:varnish_cache7.0.1
varnish_cache_project:varnish_cache7.0.2
varnish_cache_project:varnish_cache7.1.0
fedoraproject:fedora35
fedoraproject:fedora36

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13varnish7.1.1-1DEBIAN-CVE-2022-38150
SUSEPackage Hub 15 SP4varnish7.1.1-bp154.2.6.1openSUSE-SU-2022:10104-1
openSUSELeap 15.4varnish7.1.1-bp154.2.6.1openSUSE-SU-2022:10104-1
openSUSETumbleweedvarnish7.1.1-1.1openSUSE-SU-2024:12255-1
openSUSETumbleweedvinyl-cache9.0.0-1.1openSUSE-SU-2026:10751-1
Alpinev3.17varnish7.1.1-r0ALPINE-CVE-2022-38150
Alpinev3.18, v3.19, v3.20 and 4 morevarnish7.0.3-r0ALPINE-CVE-2022-38150

From the distributions' data via OSV.dev: the Debian Security Tracker; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · SUSE · openSUSE · Alpine.

Red Hat

Red Hat rates this Moderate.

Red Hat's mitigation

As mentioned in the upstream security advisory, If upgrading Varnish is not possible, it is possible to mitigate the problem by adding the following snippet at the beginning of the vcl_backend_response VCL function:

```

sub vcl_backend_response {

set beresp.status = beresp.status;

}

```

By setting the status code to itself as described above, the reason field will automatically be reset to the standard value for the given status code, or “Unknown HTTP Status” if no standard value exists for that code. This would overwrite any existing attack content in the reason field.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 8varnish:6/varnishNot affected
Red Hat Enterprise Linux 8varnish:6/varnish-modulesNot affected
Red Hat Enterprise Linux 8varnish-modulesNot affected
Red Hat Enterprise Linux 9varnishNot affected
Red Hat Enterprise Linux 9varnish-modulesNot affected
Red Hat Software Collectionsrh-varnish6-jemallocNot affected
Red Hat Software Collectionsrh-varnish6-varnishNot affected
Red Hat Software Collectionsrh-varnish6-varnish-modulesNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2022-38150.

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON