OS Command Injection in celery
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2021-23727US | high7.5 | — | ||
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 da… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/advisories/GHSA-q4xr-rc97-m4xxADVISORY
- https://github.com/celery/celeryPACKAGE
- https://github.com/celery/celery/blob/master/Changelog.rst%23522WEB
- https://github.com/celery/celery/commit/1f7ad7e6df1e02039b6ab9eec617d283598cad6bWEB
- https://github.com/pypa/advisory-database/tree/main/vulns/celery/PYSEC-2021-858.yamlWEB
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SYXRGHWHD2WWMHBWCVD5ULVINPKNY3P5WEB
- https://nvd.nist.gov/vuln/detail/CVE-2021-23727ADVISORY
- https://snyk.io/vuln/SNYK-PYTHON-CELERY-2314953WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan