CVE-2024-35198Critical· 9.8▾ MidnightTorchServe vulnerable to bypass of allowed_urls configuration
▾ Midnight zone — Critical, or high with PoC / in-the-wild
impact 53.9 · likelihood 0.2 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Sep 12.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
0.8%
TorchServe's check on allowed_urls configuration can be by-passed if the URL contains characters such as ".." but it does not prevent the model from being downloaded into the model store. Once a file is downloaded, it can be referenced without providing a URL the second time, which effectively bypasses the allowed_urls security check. Customers using PyTorch inference Deep Learning Containers (DLC) through Amazon SageMaker and EKS are not affected.
This issue in TorchServe has been fixed by validating the URL without characters such as ".." before downloading: #3082.
TorchServe release 0.11.0 includes the fix to address this vulnerability.
Thank Kroll Cyber Risk for for responsibly disclosing this issue.
If you have any questions or comments about this advisory, we ask that you contact AWS Security via our vulnerability reporting page or directly via email to [email protected]. Please do not create a public GitHub issue.
torchserve < 0.11.0Upgrade to a patched release:
torchserve 0.11.0Connected by shared product, vendor, weakness, or advisory.
CVE-2024-35199High· 8.2TorchServe gRPC Port Exposure
CVE-2023-43654Critical· 9.8TorchServe Server-Side Request Forgery vulnerability
CVE-2024-6577Medium· 6.3TorchServe script references S3 bucket without ensuring ownership or confirming accessibility
CVE-2023-48299Medium· 5.3TorchServe ZipSlip