PYSEC-2022-42999
Vulnerability from pysec - Published: 2022-05-04 22:15 - Updated: 2023-05-04 04:29** DISPUTED ** In the python-libnmap package through 0.7.2 for Python, remote command execution can occur (if used in a client application that does not validate arguments). NOTE: the vendor believes it would be unrealistic for an application to call NmapProcess with arguments taken from input data that arrived over an untrusted network, and thus the CVSS score corresponds to an unrealistic use case. None of the NmapProcess documentation implies that this is an expected use case.
| Name | purl | python-libnmap | pkg:pypi/python-libnmap |
|---|
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "python-libnmap",
"purl": "pkg:pypi/python-libnmap"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.7.3"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.2.3",
"0.2.4",
"0.2.7",
"0.2.8",
"0.4.0",
"0.4.6",
"0.5.0",
"0.5.1",
"0.6",
"0.6.1",
"0.6.2",
"0.6.3",
"0.7.0",
"0.7.2"
]
}
],
"aliases": [
"CVE-2022-30284",
"GHSA-qwqv-j7jr-4hp6"
],
"details": "** DISPUTED ** In the python-libnmap package through 0.7.2 for Python, remote command execution can occur (if used in a client application that does not validate arguments). NOTE: the vendor believes it would be unrealistic for an application to call NmapProcess with arguments taken from input data that arrived over an untrusted network, and thus the CVSS score corresponds to an unrealistic use case. None of the NmapProcess documentation implies that this is an expected use case.",
"id": "PYSEC-2022-42999",
"modified": "2023-05-04T04:29:28.652969Z",
"published": "2022-05-04T22:15:00Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/savon-noir/python-libnmap/releases"
},
{
"type": "EVIDENCE",
"url": "https://www.swascan.com/security-advisory-libnmap-2/"
},
{
"type": "ADVISORY",
"url": "https://www.swascan.com/security-advisory-libnmap-2/"
},
{
"type": "PACKAGE",
"url": "https://pypi.org/project/python-libnmap/"
},
{
"type": "EVIDENCE",
"url": "https://libnmap.readthedocs.io/en/latest/process.html#using-libnmap-process"
},
{
"type": "WEB",
"url": "https://libnmap.readthedocs.io/en/latest/process.html#using-libnmap-process"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-qwqv-j7jr-4hp6"
}
]
}
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.