Celery local privilege escalation vulnerability
Published 17 May 2022 · Updated 8 Dec 2024
Is your project on an affected celery?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=2.1.0 <2.2.8
- Fixed in
- 2.2.8
pip install 'celery>=2.2.8'- Affected
- >=2.3.0 <2.3.4
- Fixed in
- 2.3.4
pip install 'celery>=2.3.4'- Affected
- >=2.4.0 <2.4.4
- Fixed in
- 2.4.4
pip install 'celery>=2.4.4'Details
Celery 2.1 and 2.2 before 2.2.8, 2.3 before 2.3.4, and 2.4 before 2.4.4 changes the effective id but not the real id during processing of the --uid and --gid arguments to celerybeat, celeryd_detach, celeryd-multi, and celeryev, which allows local users to gain privileges via vectors involving crafted code that is executed by the worker process.
Is GHSA-rpc6-h455-3rx5 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected celery, and gives you the command that fixes it.
More advisories for celery
- HighCVE-2021-23727OS Command Injection in celery · 6 Jan 2022
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2011-4356
- Linkgithub.com/celery/celery/pull/544
- Linkgithub.com/celery/celery/commit/53514b158b743678d8993638be5920cd09ccc35c
- Linkgithub.com/celery/celery/commit/73388921731a0e6feb28ab0d389c4f7dc4d524f6
- Linkgithub.com/celery/celery/commit/e0767e40994754fe8482bf4ff622c5c6d0b9f671
- Packagegithub.com/celery/celery
- Linkgithub.com/celery/celery/blob/master/docs/sec/CELERYSA-0001.txt
- Linkgithub.com/pypa/advisory-database/tree/main/vulns/celery/PYSEC-2011-17.yaml
- Linkweb.archive.org/web/20140722114447/http://secunia.com/advisories/46973
- Linkweb.archive.org/web/20200305001706/http://www.securityfocus.com/bid/50825
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.