Impact
Using the model/workflow management API, there is a chance of uploading potentially harmful archives that contain files that are extracted to any location on the filesystem that is within the process permissions. Leveraging this issue could aid third-party actors in hiding harmful code in open-source/public models, which can be downloaded from the internet, and take advantage of machines running Torchserve.
Patches
The ZipSlip issue in TorchServe has been fixed by validating the paths of files contained within a zip archive before extracting them: pytorch/serve#2634
TorchServe release 0.9.0 includes fixes to address the ZipSlip vulnerability:
https://github.com/pytorch/serve/releases/tag/v0.9.0
References
pytorch/serve#2634
https://github.com/pytorch/serve/releases/tag/v0.9.0
Credit
We would like to thank Oligo Security 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.
References
Impact
Using the model/workflow management API, there is a chance of uploading potentially harmful archives that contain files that are extracted to any location on the filesystem that is within the process permissions. Leveraging this issue could aid third-party actors in hiding harmful code in open-source/public models, which can be downloaded from the internet, and take advantage of machines running Torchserve.
Patches
The ZipSlip issue in TorchServe has been fixed by validating the paths of files contained within a zip archive before extracting them: pytorch/serve#2634
TorchServe release 0.9.0 includes fixes to address the ZipSlip vulnerability:
https://github.com/pytorch/serve/releases/tag/v0.9.0
References
pytorch/serve#2634
https://github.com/pytorch/serve/releases/tag/v0.9.0
Credit
We would like to thank Oligo Security 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.
References