Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Aleju | Imgaug |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-g82g-j283-hj97 | imgaug contains an insecure deserialization vulnerability in BackgroundAugmenter class within multicore.py module |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.473% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Insecure Deserialization in imgaug BackgroundAugmenter Allows Remote or Local Code Execution |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Aleju
Aleju imgaug |
|
| Vendors & Products |
Aleju
Aleju imgaug |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Insecure Deserialization in imgaug BackgroundAugmenter Allows Remote or Local Code Execution | |
| Weaknesses | CWE-502 |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The imgaug library thru 0.4.0 contains an insecure deserialization vulnerability in its BackgroundAugmenter class within the multicore.py module. The class uses Python's pickle module to deserialize data received via a multiprocessing queue in the _augment_images_worker() method without any safety checks. An attacker who can influence the data placed into this queue (e.g., through social engineering, malicious input scripts, or a compromised shared queue) can provide a malicious pickle payload. When deserialized, this payload can execute arbitrary code in the context of the worker process, leading to remote or local code execution depending on the deployment scenario. | |
| References |
|