CVE-2022-45907 json
PyTorch vulnerable to arbitrary code execution
published 3y ago modified 2mo ago also BIT-pytorch-2022-45907 , EUVD-2022-0340 , GHSA-47fc-vmwq-366v , PYSEC-2022-43015
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 71%
- public exploits
- 0
- none known
Summary
In PyTorch before trunk/89695, torch.jit.annotations.parse_type_line can cause arbitrary code execution because eval is used unsafely.
Patch / fix
- pypi torch 1.13.1
- bitnami pytorch 1.13.1
- linuxfoundation pytorch 1.13.1
- pytorch Debian 14, Debian 13, Debian 12 1.13.1+dfsg-1
debian advisories DEBIAN-CVE-2022-45907
- github.com/pytorch/pytorch@767f6aa commit
- github.com/pytorch/pytorch#89189 pull request
- github.com/pytorch/pytorch/releases/tag/v1.13.1 release
- github.com/pytorch/pytorch/issues/88868 advisory
Is CVE-2022-45907 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
1.33% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/pytorch/pytorch/issues/88868 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | torch | <1.13.1 |
1.13.1 |
| bitnami | pytorch | <1.13.1 |
1.13.1 |
Classification
References
-
github.com
/pytorch/pytorch/commit/767f6aa49fe20a2766b9843d01e3b7f7793df6a3
web, patch, third-party-advisory, advisory
-
github.com
/pytorch/pytorch/issues/88868
web, exploit, issue-tracking, patch, third-party-advisory, advisory, evidence, report
-
github.com
/pytorch/pytorch/pull/89189
web
-
nvd.nist.gov
/vuln/detail/CVE-2022-45907
advisory, web
-
github.com
/pytorch/pytorch/issues/89855
web
-
github.com
/pypa/advisory-database/tree/main/vulns/torch/PYSEC-2022-43015.yaml
web
-
github.com
/pytorch/pytorch
package
-
github.com
/pytorch/pytorch/releases/tag/v1.13.1
web
-
github.com
/advisories/GHSA-47fc-vmwq-366v
advisory
Sources
- CVE List CVE-2022-45907
- GitHub Advisory GHSA-47fc-vmwq-366v
- NVD CVE-2022-45907
- OSV BIT-pytorch-2022-45907
- OSV PYSEC-2022-43015
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.