CVE-2023-48299: TorchServe ZipSlip
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: https://github.com/pytorch/serve/pull/2634
TorchServe release 0.9.0 includes fixes to address the ZipSlip vulnerability: https://github.com/pytorch/serve/releases/tag/v0.9.0
References https://github.com/pytorch/serve/pull/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 aws-security@amazon.com. Please do not create a public GitHub issue.
Other sources
TorchServe is a tool for serving and scaling PyTorch models in production. Starting in version 0.1.0 and prior to version 0.9.0, 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. The ZipSlip issue in TorchServe has been fixed by validating the paths of files contained within a zip archive before extracting them. TorchServe release 0.9.0 includes fixes to address the ZipSlip vulnerability.
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the impact of CVE-2023-48299?
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.
How can leveraging CVE-2023-48299 aid third-party actors?
Leveraging this issue could aid third-party actors in hiding harmful code.
What is the severity of CVE-2023-48299?
The severity of CVE-2023-48299 is medium with a CVSS score of 5.3.
What is the affected software?
The affected software is torchserve version 0.1.0 to 0.9.0.
Where can I find more information about CVE-2023-48299?
You can find more information about CVE-2023-48299 in the following references: [link1](https://github.com/pytorch/serve/security/advisories/GHSA-m2mj-pr4f-h9jp), [link2](https://github.com/pytorch/serve/pull/2634), [link3](https://github.com/advisories/GHSA-m2mj-pr4f-h9jp).