MediumGHSA-rpc6-h455-3rx5CVE-2011-4356PYSEC-2011-17

Celery local privilege escalation vulnerability

Published 17 May 2022 · Updated 8 Dec 2024

Is your project on an affected celery?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

celeryPyPI
Affected
>=2.1.0 <2.2.8
Fixed in
2.2.8
Update to the fixed version for your release line, for example:pip install 'celery>=2.2.8'
celeryPyPI
Affected
>=2.3.0 <2.3.4
Fixed in
2.3.4
Update to the fixed version for your release line, for example:pip install 'celery>=2.3.4'
celeryPyPI
Affected
>=2.4.0 <2.4.4
Fixed in
2.4.4
Update to the fixed version for your release line, for example: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

celery security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.