PYSEC-2017-23
Vulnerability from pysec - Published: 2017-11-08 03:29 - Updated: 2021-07-05 00:01An exploitable vulnerability exists in the YAML parsing functionality in the YAMLParser method in Interfaces.py in PyAnyAPI before 0.6.1. A YAML parser can execute arbitrary Python commands resulting in command execution because load is used where safe_load should have been used. An attacker can insert Python into loaded YAML to trigger this vulnerability.
| Name | purl | pyanyapi | pkg:pypi/pyanyapi |
|---|
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "pyanyapi",
"purl": "pkg:pypi/pyanyapi"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.6.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.4",
"0.5",
"0.5.1",
"0.5.2",
"0.5.3",
"0.5.4",
"0.5.5",
"0.5.6",
"0.5.7",
"0.5.8",
"0.6.0"
]
}
],
"aliases": [
"CVE-2017-16616",
"GHSA-vg8g-jpm9-jh8r"
],
"details": "An exploitable vulnerability exists in the YAML parsing functionality in the YAMLParser method in Interfaces.py in PyAnyAPI before 0.6.1. A YAML parser can execute arbitrary Python commands resulting in command execution because load is used where safe_load should have been used. An attacker can insert Python into loaded YAML to trigger this vulnerability.",
"id": "PYSEC-2017-23",
"modified": "2021-07-05T00:01:24.581595Z",
"published": "2017-11-08T03:29:00Z",
"references": [
{
"type": "WEB",
"url": "https://pypi.python.org/pypi/pyanyapi/0.6.1"
},
{
"type": "WEB",
"url": "https://github.com/Stranger6667/pyanyapi/releases/tag/0.6.1"
},
{
"type": "REPORT",
"url": "https://github.com/Stranger6667/pyanyapi/issues/41"
},
{
"type": "ARTICLE",
"url": "https://joel-malwarebenchmark.github.io/blog/2017/11/08/cve-2017-16616-yamlparser-in-pyanyapi/"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-vg8g-jpm9-jh8r"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
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.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
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.