Scp Py
Monthly
Path traversal in jbardin scp.py through 0.16.1 lets a malicious or compromised SCP server write or overwrite files outside the client's intended download directory when a client-side receive operation processes crafted SCP protocol file entries. This affects applications that use scp.py as a client to pull files, most impactfully during recursive gets, and requires the victim to initiate the download from an attacker-controlled endpoint (unauthenticated from the client's perspective, but dependent on passive user interaction). Impact is confined to integrity and availability of local files on the client through arbitrary write/overwrite, with no confidentiality disclosure; there is no confirmed active exploitation (CISA KEV) and no public exploit code identified at time of analysis, and the issue is best characterized as a moderate defense-in-depth-class weakness rather than an emergency. The vendor released a fixed version, 0.16.2.
Path traversal in jbardin scp.py through 0.16.1 lets a malicious or compromised SCP server write or overwrite files outside the client's intended download directory when a client-side receive operation processes crafted SCP protocol file entries. This affects applications that use scp.py as a client to pull files, most impactfully during recursive gets, and requires the victim to initiate the download from an attacker-controlled endpoint (unauthenticated from the client's perspective, but dependent on passive user interaction). Impact is confined to integrity and availability of local files on the client through arbitrary write/overwrite, with no confidentiality disclosure; there is no confirmed active exploitation (CISA KEV) and no public exploit code identified at time of analysis, and the issue is best characterized as a moderate defense-in-depth-class weakness rather than an emergency. The vendor released a fixed version, 0.16.2.