CELERYSA-0001.txt 2.5 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182
  1. =========================================
  2. CELERYSA-0001: Celery Security Advisory
  3. =========================================
  4. :contact: security@celeryproject.org
  5. :author: Ask Solem
  6. :date: 2011-11-25 04:35:00 P.M GMT
  7. Details
  8. =======
  9. :package: celery
  10. :vulnerability: privilege escalation
  11. :problem type: local
  12. :risk: medium
  13. :bug-no: Celery #544
  14. :versions-affected: 2.1, 2.2, 2.3, 2.4
  15. Description
  16. ===========
  17. The ``--uid`` and ``--gid`` arguments to the ``celeryd-multi``,
  18. ``celeryd_detach``, ``celerybeat``, ``celeryev`` programs shipped
  19. with Celery versions 2.1 and later was not handled properly
  20. in that only the effective user was changed, and the real id remained
  21. unchanged.
  22. In practice for affected users the vulnerability means that malicious code
  23. loaded in the worker process would be allowed to escalate privileges.
  24. We take this issue seriously since the Pickle serializer used by
  25. default makes it possible to execute arbitrary code.
  26. We recommend that users takes steps to secure their systems so that
  27. malicious users cannot abuse the message broker to send messages,
  28. or disable the pickle serializer used in Celery so that arbitrary code
  29. execution is not possible.
  30. Patches are now
  31. available to affected version series still maintained (see below).
  32. System affected
  33. ===============
  34. Users of Celery versions 2.1, 2.2, 2.3, 2.4 except the recently
  35. released 2.2.8, 2.3.4 and 2.4.4, daemonizing the celery programs
  36. as the root user using either:
  37. 1) the --uid or --gid arguments set,
  38. or 2) the provided generic init scripts with the environment variables
  39. CELERYD_USER or CELERYD_GROUP defined,
  40. are affected.
  41. Users using the Debian init scripts, CentOS init scripts, OS X launchctl
  42. scripts, Supervisor, or users not starting the programs as the root user
  43. are *not* affected.
  44. Solution
  45. ========
  46. Users of the 2.4 series should upgrade to 2.4.4:
  47. * ``pip install -U celery``, or
  48. * ``easy_install -U celery``, or
  49. * http://pypi.python.org/pypi/celery/2.4.4
  50. Users of the 2.3 series should upgrade to 2.3.4:
  51. * ``pip install -U celery==2.3.4``, or
  52. * ``easy_install -U celery==2.3.4``, or
  53. * http://pypi.python.org/pypi/celery/2.3.4
  54. Users of the 2.2 series should upgrade to 2.2.8:
  55. * ``pip install -U celery==2.2.8``, or
  56. * ``easy_install -U celery==2.2.8``, or
  57. * http://pypi.python.org/pypi/celery/2.2.8
  58. The 2.1 series is no longer being maintained, so we urge users
  59. of that series to upgrade to a more recent version.
  60. Distribution package maintainers are urged to provide their users
  61. with updated packages.