PyTorch torch.jit.annotations.parse_type_line command injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in PyTorch. It has been rated as problematic. Impacted is the function torch.jit.annotations.parse_type_line. This manipulation causes an unknown weakness.
This vulnerability is tracked as CVE-2022-45907. No exploit exists.
Upgrading the affected component is advised.
Details
A vulnerability classified as problematic was found in PyTorch (version unknown). The CWE definition for the vulnerability is CWE-77. The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
In PyTorch before trunk/89695, torch.jit.annotations.parse_type_line can cause arbitrary code execution because eval is used unsafely.
The weakness was disclosed 11/26/2022 as 88868. The advisory is shared at github.com. This vulnerability is known as CVE-2022-45907 since 11/26/2022. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1202 for this issue.
Upgrading eliminates this vulnerability. Applying the patch 767f6aa49fe20a2766b9843d01e3b7f7793df6a3 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2022-0340). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
License
Website
- Product: https://github.com/pytorch/pytorch/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Command injectionCWE: CWE-77 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Patch: 767f6aa49fe20a2766b9843d01e3b7f7793df6a3
Timeline
11/26/2022 🔍11/26/2022 🔍
11/26/2022 🔍
03/09/2026 🔍
Sources
Product: github.comAdvisory: 88868
Status: Confirmed
CVE: CVE-2022-45907 (🔍)
GCVE (CVE): GCVE-0-2022-45907
GCVE (VulDB): GCVE-100-214417
EUVD: 🔍
Entry
Created: 11/26/2022 08:27Updated: 03/09/2026 10:54
Changes: 11/26/2022 08:27 (38), 12/23/2022 14:47 (12), 04/26/2025 04:05 (16), 03/09/2026 10:54 (2)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.