# CVE-2022-23530: GuardDog vulnerable to arbitrary file write when scanning a specially-crafted remote PyPI package

> An attacker can overwrite arbitrary files on the system by tricking a user into scanning a malicious PyPI package with GuardDog.

- **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 16 Dec 2022
- **Updated:** 17 Apr 2025
- **Also known as:** GHSA-78m5-jpmf-ch7v, PYSEC-2022-42993

## What is CVE-2022-23530?

CVE-2022-23530 is a medium-severity path traversal vulnerability in DataDog guarddog, published on 16 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

GuardDog is a CLI tool to identify malicious PyPI packages. Versions prior to v0.1.8 are vulnerable to arbitrary file write when scanning a specially-crafted remote PyPI package. Extracting files using shutil.unpack_archive() from a potentially malicious tarball without validating that the destination file path is within the intended destination directory can cause files outside the destination directory to be overwritten.  This issue is patched in version 0.1.8. Potential workarounds include using a safer module, like zipfile, and validating the location of the extracted files and discarding those with malicious paths.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2022-23530?

3 open source packages ship an affected version, including guarddog. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `guarddog` | PyPI | All versions | 0.1.8 |
| `guarddog` | PyPI | All versions | 0.1.8 |
| `guarddog` | PyPI | All versions | 0.1.8 |

Products: Datadoghq Guarddog.

## How do I fix CVE-2022-23530?

Upgrade guarddog to 0.1.8 or later.

## Is CVE-2022-23530 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-23530 exists.

## Other vulnerabilities in DataDog guarddog

- [CVE-2026-22871](https://insights.sbomify.com/CVE-2026-22871/): GuardDog Path Traversal Vulnerability Leads to Arbitrary File Overwrite and RCE (high 8.7)
- [CVE-2026-22870](https://insights.sbomify.com/CVE-2026-22870/): GuardDog Zip Bomb Vulnerability in safe_extract() Allows DoS (high 7.1)
- [CVE-2022-23531](https://insights.sbomify.com/CVE-2022-23531/): Arbitrary file write when scanning a specially-crafted local PyPI package (medium 5.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-23530 and fix it if it is affected.

What it is: CVE-2022-23530 is a medium-severity path traversal vulnerability in DataDog guarddog, published on 16 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-23530 exists.

Affected packages and fixed versions:
- guarddog (PyPI): affected all versions; fixed in 0.1.8
- guarddog (PyPI): affected all versions; fixed in 0.1.8
- guarddog (PyPI): affected all versions; fixed in 0.1.8

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-23530/ (Markdown: https://insights.sbomify.com/CVE-2022-23530/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-23530
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-23530
- OSV: https://osv.dev/vulnerability/CVE-2022-23530

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-23530/
Summaries are generated and may contain mistakes; the official description above is the record.