# CVE-2022-23959: Other in n/a > Attackers can perform HTTP request smuggling on Varnish Cache, potentially bypassing security controls or poisoning caches. - **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 26 Jan 2022 - **Updated:** 3 Aug 2024 - **Also known as:** ALPINE-CVE-2022-23959, ALSA-2022:0418, BIT-varnish-2022-23959, DEBIAN-CVE-2022-23959, DLA-2920-1, GHSA-fcqv-r8cv-f88h, MGASA-2022-0079, OESA-2022-1623, RHSA-2022:0418, RHSA-2022:0420, RHSA-2022:0421, RHSA-2022:0422, RHSA-2022:4745, RLSA-2022:0418, UBUNTU-CVE-2022-23959, openSUSE-SU-2024:12086-1 ## What is CVE-2022-23959? CVE-2022-23959 is a critical vulnerability in Debian Debian Linux, published on 26 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description In Varnish Cache before 6.6.2 and 7.x before 7.0.2, Varnish Cache 6.0 LTS before 6.0.10, and and Varnish Enterprise (Cache Plus) 4.1.x before 4.1.11r6 and 6.0.x before 6.0.9r4, request smuggling can occur for HTTP/1 connections. Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests) ## Which versions are affected by CVE-2022-23959? 1 open source package ship an affected version, including varnish. It affects 6 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `varnish` | Bitnami | From 7.0.0 | 7.0.2 | | `varnish` | AlmaLinux:8 | All versions | 6.0.8-1.module_el8.5.0+2620+03a0c2cc.1 | | `varnish` | AlmaLinux:8 | All versions | 6.0.8-1.module_el8.5.0+76+a10ffa55 | | `varnish-devel` | AlmaLinux:8 | All versions | 6.0.8-1.module_el8.5.0+2620+03a0c2cc.1 | | `varnish-devel` | AlmaLinux:8 | All versions | 6.0.8-1.module_el8.5.0+76+a10ffa55 | | `varnish-docs` | AlmaLinux:8 | All versions | 6.0.8-1.module_el8.5.0+2620+03a0c2cc.1 | | `varnish-docs` | AlmaLinux:8 | All versions | 6.0.8-1.module_el8.5.0+76+a10ffa55 | | `varnish-modules` | AlmaLinux:8 | All versions | 0.15.0-6.module_el8.5.0+2620+03a0c2cc | | `varnish-modules` | AlmaLinux:8 | All versions | 0.15.0-6.module_el8.5.0+76+a10ffa55 | | `varnish` | Red Hat:enterprise_linux:8::appstream | All versions | 0:6.0.8-1.module+el8.5.0+14089+03a0c2cc.1 | | `varnish-devel` | Red Hat:enterprise_linux:8::appstream | All versions | 0:6.0.8-1.module+el8.5.0+14089+03a0c2cc.1 | | `varnish-docs` | Red Hat:enterprise_linux:8::appstream | All versions | 0:6.0.8-1.module+el8.5.0+14089+03a0c2cc.1 | | `varnish-modules` | Red Hat:enterprise_linux:8::appstream | All versions | 0:0.15.0-6.module+el8.5.0+11976+0b4af72d | | `varnish-modules-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:0.15.0-6.module+el8.5.0+11976+0b4af72d | | `varnish-modules-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:0.15.0-6.module+el8.5.0+11976+0b4af72d | | `varnish` | Red Hat:rhel_e4s:8.1::appstream | All versions | 0:6.0.2-2.module+el8.1.0+14093+aa8ea65f.1 | | `varnish-devel` | Red Hat:rhel_e4s:8.1::appstream | All versions | 0:6.0.2-2.module+el8.1.0+14093+aa8ea65f.1 | | `varnish-docs` | Red Hat:rhel_e4s:8.1::appstream | All versions | 0:6.0.2-2.module+el8.1.0+14093+aa8ea65f.1 | | `varnish-modules` | Red Hat:rhel_e4s:8.1::appstream | All versions | 0:0.15.0-4.module+el8+2481+4078e9d2 | | `varnish-modules-debuginfo` | Red Hat:rhel_e4s:8.1::appstream | All versions | 0:0.15.0-4.module+el8+2481+4078e9d2 | | `varnish-modules-debugsource` | Red Hat:rhel_e4s:8.1::appstream | All versions | 0:0.15.0-4.module+el8+2481+4078e9d2 | | `varnish` | Red Hat:rhel_eus:8.2::appstream | All versions | 0:6.0.2-2.module+el8.2.0+14091+b587eafb.1 | | `varnish-devel` | Red Hat:rhel_eus:8.2::appstream | All versions | 0:6.0.2-2.module+el8.2.0+14091+b587eafb.1 | | `varnish-docs` | Red Hat:rhel_eus:8.2::appstream | All versions | 0:6.0.2-2.module+el8.2.0+14091+b587eafb.1 | | `varnish-modules` | Red Hat:rhel_eus:8.2::appstream | All versions | 0:0.15.0-4.module+el8+2481+4078e9d2 | | `varnish-modules-debuginfo` | Red Hat:rhel_eus:8.2::appstream | All versions | 0:0.15.0-4.module+el8+2481+4078e9d2 | | `varnish-modules-debugsource` | Red Hat:rhel_eus:8.2::appstream | All versions | 0:0.15.0-4.module+el8+2481+4078e9d2 | | `varnish` | Red Hat:rhel_eus:8.4::appstream | All versions | 0:6.0.6-2.module+el8.4.0+14090+331e4860.2 | | `varnish-devel` | Red Hat:rhel_eus:8.4::appstream | All versions | 0:6.0.6-2.module+el8.4.0+14090+331e4860.2 | | `varnish-docs` | Red Hat:rhel_eus:8.4::appstream | All versions | 0:6.0.6-2.module+el8.4.0+14090+331e4860.2 | | `varnish-modules` | Red Hat:rhel_eus:8.4::appstream | All versions | 0:0.15.0-5.module+el8.3.0+6843+b3b42fcc | | `varnish-modules-debuginfo` | Red Hat:rhel_eus:8.4::appstream | All versions | 0:0.15.0-5.module+el8.3.0+6843+b3b42fcc | | `varnish-modules-debugsource` | Red Hat:rhel_eus:8.4::appstream | All versions | 0:0.15.0-5.module+el8.3.0+6843+b3b42fcc | | `rh-varnish6-varnish` | Red Hat:rhel_software_collections:3::el7 | All versions | 0:6.0.8-2.el7.1 | | `rh-varnish6-varnish-devel` | Red Hat:rhel_software_collections:3::el7 | All versions | 0:6.0.8-2.el7.1 | | `rh-varnish6-varnish-docs` | Red Hat:rhel_software_collections:3::el7 | All versions | 0:6.0.8-2.el7.1 | | `rh-varnish6-varnish-libs` | Red Hat:rhel_software_collections:3::el7 | All versions | 0:6.0.8-2.el7.1 | | `varnish` | Rocky Linux:8 | All versions | 0:6.0.8-1.module+el8.5.0+677+2a78a869 | | `varnish` | Rocky Linux:8 | All versions | 0:6.0.8-1.module+el8.5.0+736+fec10e21.1 | | `varnish-modules` | Rocky Linux:8 | All versions | 0:0.15.0-6.module+el8.5.0+677+2a78a869 | Products: Debian Debian Linux, Fedoraproject Fedora, Varnish-Software Varnich Cache, Varnish-Software Varnish Cache, Varnish-Software Varnish Cache Plus, Varnish Cache Project Varnish Cache. ## How do I fix CVE-2022-23959? Upgrade varnish to 7.0.2 or later. ## Is CVE-2022-23959 being exploited? There is no known exploitation of CVE-2022-23959 in the wild and no public exploit code. ## Other vulnerabilities in Debian Debian Linux - [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild) - [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild) - [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild) - [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild) - [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-23959 and fix it if it is affected. What it is: CVE-2022-23959 is a critical vulnerability in Debian Debian Linux, published on 26 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2022-23959 in the wild and no public exploit code. Affected packages and fixed versions: - varnish (Bitnami): affected from 7.0.0; fixed in 7.0.2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-23959/ (Markdown: https://insights.sbomify.com/CVE-2022-23959/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-23959 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-23959 - OSV: https://osv.dev/vulnerability/CVE-2022-23959 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-23959/ Summaries are generated and may contain mistakes; the official description above is the record.