PYSEC-2021-858
Vulnerability from pysec - Published: 2021-12-29 17:15 - Updated: 2021-12-29 19:23
VLAI?
Details
This affects the package celery before 5.2.2. It by default trusts the messages and metadata stored in backends (result stores). When reading task metadata from the backend, the data is deserialized. Given that an attacker can gain access to, or somehow manipulate the metadata within a celery backend, they could trigger a stored command injection vulnerability and potentially gain further access to the system.
Impacted products
| Name | purl | celery | pkg:pypi/celery |
|---|
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "celery",
"purl": "pkg:pypi/celery"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.2.2"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.1.10",
"0.1.11",
"0.1.12",
"0.1.13",
"0.1.14",
"0.1.15",
"0.1.2",
"0.1.4",
"0.1.6",
"0.1.7",
"0.1.8",
"0.2.0",
"0.3.0",
"0.3.20",
"0.3.7",
"0.4.0",
"0.4.1",
"0.6.0",
"0.8.0",
"0.8.1",
"0.8.2",
"0.8.3",
"0.8.4",
"1.0.0",
"1.0.1",
"1.0.2",
"1.0.3",
"1.0.4",
"1.0.5",
"1.0.6",
"2.0.0",
"2.0.1",
"2.0.2",
"2.0.3",
"2.1.0",
"2.1.1",
"2.1.2",
"2.1.3",
"2.1.4",
"2.2.0",
"2.2.1",
"2.2.10",
"2.2.2",
"2.2.3",
"2.2.4",
"2.2.5",
"2.2.6",
"2.2.7",
"2.2.8",
"2.2.9",
"2.3.0",
"2.3.1",
"2.3.2",
"2.3.3",
"2.3.4",
"2.3.5",
"2.4.0",
"2.4.1",
"2.4.2",
"2.4.3",
"2.4.4",
"2.4.5",
"2.4.6",
"2.4.7",
"2.5.0",
"2.5.1",
"2.5.2",
"2.5.3",
"2.5.5",
"3.0.0",
"3.0.1",
"3.0.10",
"3.0.11",
"3.0.12",
"3.0.13",
"3.0.14",
"3.0.15",
"3.0.16",
"3.0.17",
"3.0.18",
"3.0.19",
"3.0.2",
"3.0.20",
"3.0.21",
"3.0.22",
"3.0.23",
"3.0.24",
"3.0.25",
"3.0.3",
"3.0.4",
"3.0.5",
"3.0.6",
"3.0.7",
"3.0.8",
"3.0.9",
"3.1.0",
"3.1.1",
"3.1.10",
"3.1.11",
"3.1.12",
"3.1.13",
"3.1.14",
"3.1.15",
"3.1.16",
"3.1.17",
"3.1.18",
"3.1.19",
"3.1.2",
"3.1.20",
"3.1.21",
"3.1.22",
"3.1.23",
"3.1.24",
"3.1.25",
"3.1.26-1",
"3.1.26.post2",
"3.1.3",
"3.1.4",
"3.1.5",
"3.1.6",
"3.1.7",
"3.1.8",
"3.1.9",
"4.0.0",
"4.0.0rc3",
"4.0.0rc4",
"4.0.0rc5",
"4.0.0rc6",
"4.0.0rc7",
"4.0.1",
"4.0.2",
"4.1.0",
"4.1.1",
"4.2.0",
"4.2.0rc1",
"4.2.0rc2",
"4.2.0rc3",
"4.2.0rc4",
"4.2.1",
"4.2.2",
"4.3.0",
"4.3.0rc1",
"4.3.0rc2",
"4.3.0rc3",
"4.3.1",
"4.4.0",
"4.4.0rc1",
"4.4.0rc2",
"4.4.0rc3",
"4.4.0rc4",
"4.4.0rc5",
"4.4.1",
"4.4.2",
"4.4.3",
"4.4.4",
"4.4.5",
"4.4.6",
"4.4.7",
"5.0.0",
"5.0.0a1",
"5.0.0a2",
"5.0.0b1",
"5.0.0rc1",
"5.0.0rc2",
"5.0.0rc3",
"5.0.1",
"5.0.2",
"5.0.3",
"5.0.4",
"5.0.5",
"5.0.6",
"5.1.0",
"5.1.0b1",
"5.1.0b2",
"5.1.0rc1",
"5.1.1",
"5.1.2",
"5.2.0",
"5.2.0b1",
"5.2.0b2",
"5.2.0b3",
"5.2.0rc1",
"5.2.0rc2",
"5.2.1"
]
}
],
"aliases": [
"CVE-2021-23727",
"SNYK-PYTHON-CELERY-2314953",
"GHSA-q4xr-rc97-m4xx"
],
"details": "This affects the package celery before 5.2.2. It by default trusts the messages and metadata stored in backends (result stores). When reading task metadata from the backend, the data is deserialized. Given that an attacker can gain access to, or somehow manipulate the metadata within a celery backend, they could trigger a stored command injection vulnerability and potentially gain further access to the system.",
"id": "PYSEC-2021-858",
"modified": "2021-12-29T19:23:51.138646Z",
"published": "2021-12-29T17:15:00Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/celery/celery/blob/master/Changelog.rst%23522"
},
{
"type": "ADVISORY",
"url": "https://snyk.io/vuln/SNYK-PYTHON-CELERY-2314953"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-q4xr-rc97-m4xx"
}
]
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…