CVE-2024-35199High· 8.2▾ TwilightTorchServe gRPC Port Exposure
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 45.1 · likelihood 0.1 · 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 Jul 8.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
0.6%
0.6% → 0.6%
Last analysed / modified upstream
The two gRPC ports 7070 and 7071, are not bound to localhost by default, so when TorchServe is launched, these two interfaces are bound to all interfaces. Customers using PyTorch inference Deep Learning Containers (DLC) through Amazon SageMaker and EKS are not affected.
This issue in TorchServe has been fixed in #3083.
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.3.0, < 0.11.0Upgrade to a patched release:
torchserve 0.11.0Connected by shared product, vendor, weakness, or advisory.
CVE-2024-35198Critical· 9.8TorchServe vulnerable to bypass of allowed_urls configuration
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