# CVE-2022-1664: directory traversal for in-place extracts with untrusted v2 and v3 source packages with debian.tar > Attackers can exploit directory traversal in dpkg source package extraction to write files outside intended directories, potentially leading to code execution. - **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 26 May 2022 - **Updated:** 17 Sep 2024 - **Also known as:** ALPINE-CVE-2022-1664, AZL-9853, CLSA-2022-1654717100, DEBIAN-CVE-2022-1664, DLA-3022-1, DSA-5147-1, GHSA-q7pv-fjh6-6xq6, MGASA-2022-0327, OESA-2022-1703, SUSE-SU-2022:2689-1, SUSE-SU-2022:4081-1, UBUNTU-CVE-2022-1664, USN-5446-1, USN-5446-2, openSUSE-SU-2024:12110-1 ## What is CVE-2022-1664? CVE-2022-1664 is a critical path traversal vulnerability in Debian Debian Linux, published on 26 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Dpkg::Source::Archive in dpkg, the Debian package management system, before version 1.21.8, 1.20.10, 1.19.8, 1.18.26 is prone to a directory traversal vulnerability. When extracting untrusted source packages in v2 and v3 source package formats that include a debian.tar, the in-place extraction can lead to directory traversal situations on specially crafted orig.tar and debian.tar tarballs. Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2022-1664? It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `dpkg` | SUSE:Enterprise Storage 6 | All versions | 1.19.0.4-150000.4.4.1 | | `update-alternatives` | SUSE:Enterprise Storage 6 | All versions | 1.19.0.4-150000.4.4.1 | | `dpkg` | SUSE:Enterprise Storage 7 | All versions | 1.19.0.4-150000.4.4.1 | | `update-alternatives` | SUSE:Enterprise Storage 7 | All versions | 1.19.0.4-150000.4.4.1 | | `dpkg` | SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS | All versions | 1.19.0.4-150000.4.4.1 | | `update-alternatives` | SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS | All versions | 1.19.0.4-150000.4.4.1 | | `dpkg` | SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS | All versions | 1.19.0.4-150000.4.4.1 | | `update-alternatives` | SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS | All versions | 1.19.0.4-150000.4.4.1 | | `dpkg` | SUSE:Linux Enterprise High Performance Computing 15 SP2-ESPOS | All versions | 1.19.0.4-150000.4.4.1 | | `update-alternatives` | SUSE:Linux Enterprise High Performance Computing 15 SP2-ESPOS | All versions | 1.19.0.4-150000.4.4.1 | | `dpkg` | SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | All versions | 1.19.0.4-150000.4.4.1 | | `update-alternatives` | SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | All versions | 1.19.0.4-150000.4.4.1 | | `dpkg` | SUSE:Linux Enterprise High Performance Computing 15-ESPOS | All versions | 1.19.0.4-150000.4.4.1 | | `update-alternatives` | SUSE:Linux Enterprise High Performance Computing 15-ESPOS | All versions | 1.19.0.4-150000.4.4.1 | | `dpkg` | SUSE:Linux Enterprise High Performance Computing 15-LTSS | All versions | 1.19.0.4-150000.4.4.1 | | `update-alternatives` | SUSE:Linux Enterprise High Performance Computing 15-LTSS | All versions | 1.19.0.4-150000.4.4.1 | | `update-alternatives` | SUSE:Linux Enterprise Micro 5.1 | All versions | 1.19.0.4-150000.4.4.1 | | `update-alternatives` | SUSE:Linux Enterprise Micro 5.2 | All versions | 1.19.0.4-150000.4.4.1 | | `update-alternatives` | SUSE:Linux Enterprise Micro 5.3 | All versions | 1.19.0.4-150000.4.4.1 | | `update-alternatives` | SUSE:Linux Enterprise Module for Basesystem 15 SP3 | All versions | 1.19.0.4-150000.4.4.1 | | `update-alternatives` | SUSE:Linux Enterprise Module for Basesystem 15 SP4 | All versions | 1.19.0.4-150000.4.4.1 | | `dpkg` | SUSE:Linux Enterprise Module for Development Tools 15 SP3 | All versions | 1.19.0.4-150000.4.4.1 | | `dpkg` | SUSE:Linux Enterprise Module for Development Tools 15 SP4 | All versions | 1.19.0.4-150000.4.4.1 | | `update-alternatives` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 1.18.4-16.3.5 | | `dpkg` | SUSE:Linux Enterprise Server 15 SP1-BCL | All versions | 1.19.0.4-150000.4.4.1 | | `update-alternatives` | SUSE:Linux Enterprise Server 15 SP1-BCL | All versions | 1.19.0.4-150000.4.4.1 | | `dpkg` | SUSE:Linux Enterprise Server 15 SP1-LTSS | All versions | 1.19.0.4-150000.4.4.1 | | `update-alternatives` | SUSE:Linux Enterprise Server 15 SP1-LTSS | All versions | 1.19.0.4-150000.4.4.1 | | `dpkg` | SUSE:Linux Enterprise Server 15 SP2-BCL | All versions | 1.19.0.4-150000.4.4.1 | | `update-alternatives` | SUSE:Linux Enterprise Server 15 SP2-BCL | All versions | 1.19.0.4-150000.4.4.1 | | `dpkg` | SUSE:Linux Enterprise Server 15 SP2-LTSS | All versions | 1.19.0.4-150000.4.4.1 | | `update-alternatives` | SUSE:Linux Enterprise Server 15 SP2-LTSS | All versions | 1.19.0.4-150000.4.4.1 | | `dpkg` | SUSE:Linux Enterprise Server 15-LTSS | All versions | 1.19.0.4-150000.4.4.1 | | `update-alternatives` | SUSE:Linux Enterprise Server 15-LTSS | All versions | 1.19.0.4-150000.4.4.1 | | `update-alternatives` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 1.18.4-16.3.5 | | `dpkg` | SUSE:Linux Enterprise Server for SAP Applications 15 | All versions | 1.19.0.4-150000.4.4.1 | | `update-alternatives` | SUSE:Linux Enterprise Server for SAP Applications 15 | All versions | 1.19.0.4-150000.4.4.1 | | `dpkg` | SUSE:Linux Enterprise Server for SAP Applications 15 SP1 | All versions | 1.19.0.4-150000.4.4.1 | | `update-alternatives` | SUSE:Linux Enterprise Server for SAP Applications 15 SP1 | All versions | 1.19.0.4-150000.4.4.1 | | `dpkg` | SUSE:Linux Enterprise Server for SAP Applications 15 SP2 | All versions | 1.19.0.4-150000.4.4.1 | Products: Debian Debian Linux, Debian Dpkg, Netapp Ontap Select Deploy Administration Utility. ## How do I fix CVE-2022-1664? Upgrade to a fixed version. ## Is CVE-2022-1664 being exploited? There is no known exploitation of CVE-2022-1664 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-1664 and fix it if it is affected. What it is: CVE-2022-1664 is a critical path traversal vulnerability in Debian Debian Linux, published on 26 May 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-1664 in the wild and no public exploit code. Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page. 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-1664/ (Markdown: https://insights.sbomify.com/CVE-2022-1664/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-1664 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-1664 - OSV: https://osv.dev/vulnerability/CVE-2022-1664 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-1664/ Summaries are generated and may contain mistakes; the official description above is the record.