ModelScope through 1.40.0 Unsafe YAML Deserialization in Model Config Loading
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| modelscope | modelscope | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Modelscope | Modelscope |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.682% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Modelscope
Modelscope modelscope |
|
| Vendors & Products |
Modelscope
Modelscope modelscope |
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-94 | |
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | ModelScope uses PyYAML's unsafe yaml.Loader to parse model configuration files, allowing arbitrary code execution through Python object construction tags. Attackers can craft malicious model repositories with poisoned configuration files that execute code when loaded by users. | |
| Title | ModelScope through 1.40.0 Unsafe YAML Deserialization in Model Config Loading | |
| Weaknesses | CWE-502 | |
| References |
|
|
| Metrics |
cvssV3_1
|