CVSS 3.1
7.5 highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HHigh (7.5). EPSS 1.5% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExplain 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.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| varnish_cache_project:varnish_cache | 7.0.0 |
| varnish_cache_project:varnish_cache | 7.0.1 |
| varnish_cache_project:varnish_cache | 7.0.2 |
| varnish_cache_project:varnish_cache | 7.1.0 |
| fedoraproject:fedora | 35 |
| fedoraproject:fedora | 36 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13 | varnish | 7.1.1-1 | DEBIAN-CVE-2022-38150 |
| SUSE | Package Hub 15 SP4 | varnish | 7.1.1-bp154.2.6.1 | openSUSE-SU-2022:10104-1 |
| openSUSE | Leap 15.4 | varnish | 7.1.1-bp154.2.6.1 | openSUSE-SU-2022:10104-1 |
| openSUSE | Tumbleweed | varnish | 7.1.1-1.1 | openSUSE-SU-2024:12255-1 |
| openSUSE | Tumbleweed | vinyl-cache | 9.0.0-1.1 | openSUSE-SU-2026:10751-1 |
| Alpine | v3.17 | varnish | 7.1.1-r0 | ALPINE-CVE-2022-38150 |
| Alpine | v3.18, v3.19, v3.20 and 4 more | varnish | 7.0.3-r0 | ALPINE-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 rates this Moderate.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 8 | varnish:6/varnish | Not affected | |
| Red Hat Enterprise Linux 8 | varnish:6/varnish-modules | Not affected | |
| Red Hat Enterprise Linux 8 | varnish-modules | Not affected | |
| Red Hat Enterprise Linux 9 | varnish | Not affected | |
| Red Hat Enterprise Linux 9 | varnish-modules | Not affected | |
| Red Hat Software Collections | rh-varnish6-jemalloc | Not affected | |
| Red Hat Software Collections | rh-varnish6-varnish | Not affected | |
| Red Hat Software Collections | rh-varnish6-varnish-modules | Not 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.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.