Skip to content
This repository has been archived by the owner on May 22, 2024. It is now read-only.

[Snyk: High]: Celery Stored Command Injection(due 02/24/2022) #655

Closed
2 tasks done
Tracked by #137
pkfec opened this issue Jan 12, 2022 · 0 comments · Fixed by #665
Closed
2 tasks done
Tracked by #137

[Snyk: High]: Celery Stored Command Injection(due 02/24/2022) #655

pkfec opened this issue Jan 12, 2022 · 0 comments · Fixed by #665
Assignees
Labels
Security: general General security concern or issue Security: high Remediate within 30 days
Milestone

Comments

@pkfec
Copy link
Contributor

pkfec commented Jan 12, 2022

Overview

Affected versions of this package are vulnerable to Stored Command Injection. 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.

https://security.snyk.io/vuln/SNYK-PYTHON-CELERY-2314953

Detailed path:

Introduced through: project@0.0.0 › celery@4.1.0

Completion criteria:

  • Upgrade celery to version 5.2.2
  • parser functionality works
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Security: general General security concern or issue Security: high Remediate within 30 days
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant