Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pytorch 1.7 contains vulnerability that is fixed in upgraded version #333

Open
cprocak3 opened this issue Mar 6, 2023 · 1 comment
Open

Comments

@cprocak3
Copy link

cprocak3 commented Mar 6, 2023

Hello,

Pytorch 1.7 has a vulnerability that can cause an arbitrary code execution when used. It is fixed in version 1.13.1. When can it be expected for Pytorch to be upgraded to a more recent version?

See the following for the details on the CVE:
https://avd.aquasec.com/nvd/2022/cve-2022-45907/

@jongwook
Copy link
Collaborator

jongwook commented Mar 6, 2023

Hi, I see the relevant issue is this one, and the vulnerability happens when JIT-compiling a module that contains function calls using the Python type hint syntax. While the released CLIP models are using the JIT-compiled format, I don't think any code paths used in this repo is vulnerable to this CVE. (happy to stand corrected though)

In any case, this package does not enforce a specific pytorch version, but I haven't tested if it's source-compatible with 1.13.1 (I'm guessing it is). We can consider adding a warning message if the pytorch version used is too old, but any security implications will ultimately be the responsibility of the entity using this library to deploy their services which may cause arbitrary code execution. See also the LICENSE.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants