PYSEC-2022-42994
Vulnerability from pysec - Published: 2022-12-17 00:15 - Updated: 2023-05-04 04:29GuardDog is a CLI tool to identify malicious PyPI packages. Versions prior to 0.1.5 are vulnerable to Relative Path Traversal when scanning a specially-crafted local PyPI package. Running GuardDog against a specially-crafted package can allow an attacker to write an arbitrary file on the machine where GuardDog is executed due to a path traversal vulnerability when extracting the .tar.gz file of the package being scanned, which exists by design in the tarfile.TarFile.extractall function. This issue is patched in version 0.1.5.
| Name | purl | guarddog | pkg:pypi/guarddog |
|---|
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "guarddog",
"purl": "pkg:pypi/guarddog"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "a56aff58264cb6b7855d71b00dc10c39a5dbd306"
}
],
"repo": "https://github.com/DataDog/guarddog",
"type": "GIT"
},
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.1.5"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.1.1",
"0.1.3",
"0.1.4"
]
}
],
"aliases": [
"CVE-2022-23531",
"GHSA-rp2v-v467-q9vq"
],
"details": "GuardDog is a CLI tool to identify malicious PyPI packages. Versions prior to 0.1.5 are vulnerable to Relative Path Traversal when scanning a specially-crafted local PyPI package. Running GuardDog against a specially-crafted package can allow an attacker to write an arbitrary file on the machine where GuardDog is executed due to a path traversal vulnerability when extracting the .tar.gz file of the package being scanned, which exists by design in the tarfile.TarFile.extractall function. This issue is patched in version 0.1.5.",
"id": "PYSEC-2022-42994",
"modified": "2023-05-04T04:29:25.595529Z",
"published": "2022-12-17T00:15:00Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/DataDog/guarddog/releases/tag/v0.1.5"
},
{
"type": "ADVISORY",
"url": "https://github.com/DataDog/guarddog/security/advisories/GHSA-rp2v-v467-q9vq"
},
{
"type": "FIX",
"url": "https://github.com/DataDog/guarddog/pull/89/commits/a56aff58264cb6b7855d71b00dc10c39a5dbd306"
},
{
"type": "WEB",
"url": "https://github.com/DataDog/guarddog/pull/89/commits/a56aff58264cb6b7855d71b00dc10c39a5dbd306"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.