Remote Code Execution by Pickle Deserialization via FlightServer in pyquokka
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| marsupialtail | quokka | affected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Marsupialtail | Quokka | — |
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-f74j-gffq-vm9p | pyquokka is Vulnerable to Remote Code Execution by Pickle Deserialization via FlightServer |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.890% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Marsupialtail
Marsupialtail quokka |
|
| Vendors & Products |
Marsupialtail
Marsupialtail quokka |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | pyquokka is a framework for making data lakes work for time series. In versions 0.3.1 and prior, the FlightServer class directly uses pickle.loads() to deserialize action bodies received from Flight clients without any sanitization or validation in the do_action() method. The vulnerable code is located in pyquokka/flight.py at line 283 where arbitrary data from Flight clients is directly passed to pickle.loads(). When FlightServer is configured to listen on 0.0.0.0, this allows attackers across the entire network to perform arbitrary remote code execution by sending malicious pickled payloads through the set_configs action. Additional vulnerability points exist in the cache_garbage_collect, do_put, and do_get functions where pickle.loads is used to deserialize untrusted remote data. | |
| Title | Remote Code Execution by Pickle Deserialization via FlightServer in pyquokka | |
| Weaknesses | CWE-502 | |
| References |
| |
| Metrics |
cvssV3_1
|