CVE-2011-4356GHSA-RPC6-H455-3RX5PYSEC-2011-17
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 th
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.2.8, 2.3.4, 2.4.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- n/a n/a
Version range not reported
- celeryPyPI
From 2.1.0 · fixed in 2.2.8
- celeryPyPI
From 2.3.0 · fixed in 2.3.4
- celeryPyPI
From 2.4.0 · fixed in 2.4.4
- celeryPyPI
From 2.1 · fixed in 2.2.8; From 2.3 · fixed in 2.3.4; From 2.4 · fixed in 2.4.4