Scapy before 2.7.0 Insecure Deserialization RCE via Session Files
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| secdev | scapy | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Scapy | Scapy |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.242% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Scapy before 2.7.0 contains an insecure deserialization vulnerability in the load_session function that allows attackers to execute code by supplying a malicious pickle session file. Attackers can trick users into loading a crafted .pkl.gz file via the -s option or conf.session, executing embedded Python code through __reduce__(). | |
| Title | Scapy before 2.7.0 Insecure Deserialization RCE via Session Files | |
| First Time appeared |
Scapy
Scapy scapy |
|
| Weaknesses | CWE-502 | |
| CPEs | cpe:2.3:a:scapy:scapy:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Scapy
Scapy scapy |
|
| References |
| |
| Metrics |
cvssV3_1
|