PYSEC-2021-873
Vulnerability from pysec - Published: 2021-12-15 20:15 - Updated: 2023-05-25 05:07Gradio is an open source framework for building interactive machine learning models and demos. In versions prior to 2.5.0 there is a vulnerability that affects anyone who creates and publicly shares Gradio interfaces. File paths are not restricted and users who receive a Gradio link can access any files on the host computer if they know the file names or file paths. This is limited only by the host operating system. Paths are opened in read only mode. The problem has been patched in gradio 2.5.0.
| Name | purl | gradio | pkg:pypi/gradio |
|---|
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "gradio",
"purl": "pkg:pypi/gradio"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "41bd3645bdb616e1248b2167ca83636a2653f781"
}
],
"repo": "https://github.com/gradio-app/gradio",
"type": "GIT"
},
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.5.0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.1.0",
"0.1.1",
"0.1.2",
"0.1.3",
"0.1.4",
"0.1.5",
"0.1.6",
"0.1.7",
"0.1.8",
"0.1.9",
"0.2.0",
"0.2.1",
"0.3.0",
"0.3.1",
"0.3.2",
"0.3.3",
"0.3.4",
"0.3.5",
"0.4.0",
"0.4.1",
"0.4.2",
"0.4.4",
"0.5.0",
"0.7.0",
"0.7.1",
"0.7.2",
"0.7.3",
"0.7.4",
"0.7.5",
"0.7.6",
"0.7.7",
"0.7.8",
"0.8.0",
"0.8.1",
"0.9.0",
"0.9.1",
"0.9.2",
"0.9.3",
"0.9.4",
"0.9.5",
"0.9.6",
"0.9.7",
"0.9.8",
"0.9.9.2",
"0.9.9.3",
"0.9.9.5",
"0.9.9.6",
"0.9.9.7",
"0.9.9.8",
"0.9.9.9",
"0.9.9.9.2",
"1.0.0",
"1.0.0a1",
"1.0.0a3",
"1.0.0a4",
"1.0.1",
"1.0.2",
"1.0.3",
"1.0.4",
"1.0.5",
"1.0.6",
"1.0.7",
"1.1.0",
"1.1.1",
"1.1.2",
"1.1.3",
"1.1.4",
"1.1.5",
"1.1.6",
"1.1.8",
"1.1.8.1",
"1.1.9",
"1.2.2",
"1.2.3",
"1.3.0",
"1.3.1",
"1.3.2",
"1.4.0",
"1.4.2",
"1.4.3",
"1.4.4",
"1.5.0",
"1.5.1",
"1.5.3",
"1.5.4",
"1.6.0",
"1.6.1",
"1.6.2",
"1.6.3",
"1.6.4",
"1.7.0",
"1.7.1",
"1.7.2",
"1.7.3",
"1.7.4",
"1.7.5",
"1.7.6",
"1.7.7",
"2.0.0",
"2.0.1",
"2.0.10",
"2.0.2",
"2.0.4",
"2.0.5",
"2.0.6",
"2.0.7",
"2.0.8",
"2.0.9",
"2.1.0",
"2.1.1",
"2.1.2",
"2.1.4",
"2.1.6",
"2.1.7",
"2.2.0",
"2.2.1",
"2.2.10",
"2.2.11",
"2.2.12",
"2.2.13",
"2.2.14",
"2.2.15",
"2.2.2",
"2.2.3",
"2.2.4",
"2.2.5",
"2.2.6",
"2.2.7",
"2.2.8",
"2.2.9a0",
"2.2.9a2",
"2.3.0",
"2.3.0a0",
"2.3.0b101",
"2.3.0b102",
"2.3.0b99",
"2.3.3",
"2.3.4",
"2.3.5",
"2.3.5b0",
"2.3.6",
"2.3.7",
"2.3.7b0",
"2.3.7b1",
"2.3.7b2",
"2.3.8b0",
"2.3.9",
"2.4.0",
"2.4.0a0",
"2.4.1",
"2.4.2",
"2.4.4",
"2.4.5",
"2.4.6",
"2.4.7b0",
"2.4.7b2",
"2.4.7b3",
"2.4.7b4",
"2.4.7b5",
"2.4.7b6",
"2.4.7b7",
"2.4.7b8",
"2.4.7b9"
]
}
],
"aliases": [
"CVE-2021-43831",
"GHSA-rhq2-3vr9-6mcr"
],
"details": "Gradio is an open source framework for building interactive machine learning models and demos. In versions prior to 2.5.0 there is a vulnerability that affects anyone who creates and publicly shares Gradio interfaces. File paths are not restricted and users who receive a Gradio link can access any files on the host computer if they know the file names or file paths. This is limited only by the host operating system. Paths are opened in read only mode. The problem has been patched in gradio 2.5.0.",
"id": "PYSEC-2021-873",
"modified": "2023-05-25T05:07:00Z",
"published": "2021-12-15T20:15:00Z",
"references": [
{
"type": "FIX",
"url": "https://github.com/gradio-app/gradio/commit/41bd3645bdb616e1248b2167ca83636a2653f781"
},
{
"type": "ADVISORY",
"url": "https://github.com/gradio-app/gradio/security/advisories/GHSA-rhq2-3vr9-6mcr"
}
]
}
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.
