CELERYSA-0001.txt 2.8 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192
  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 and celeryev programs shipped
  19. with Celery versions 2.1 and later was not handled properly:
  20. only the effective user was changed, with the real id remaining
  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 available for all maintained versions (see below),
  31. and users are urged to upgrade, even if not directly
  32. affected.
  33. Systems affected
  34. ================
  35. Users of Celery versions 2.1, 2.2, 2.3, 2.4 except the recently
  36. released 2.2.8, 2.3.4 and 2.4.4, daemonizing the celery programs
  37. as the root user, using either:
  38. 1) the --uid or --gid arguments, or
  39. 2) the provided generic init scripts with the environment variables
  40. CELERYD_USER or CELERYD_GROUP defined,
  41. are affected.
  42. Users using the Debian init scripts, CentOS init scripts, OS X launchctl
  43. scripts, Supervisor, or users not starting the programs as the root user
  44. are *not* affected.
  45. Solution
  46. ========
  47. Users of the 2.4 series should upgrade to 2.4.4:
  48. * ``pip install -U celery``, or
  49. * ``easy_install -U celery``, or
  50. * http://pypi.python.org/pypi/celery/2.4.4
  51. Users of the 2.3 series should upgrade to 2.3.4:
  52. * ``pip install -U celery==2.3.4``, or
  53. * ``easy_install -U celery==2.3.4``, or
  54. * http://pypi.python.org/pypi/celery/2.3.4
  55. Users of the 2.2 series should upgrade to 2.2.8:
  56. * ``pip install -U celery==2.2.8``, or
  57. * ``easy_install -U celery==2.2.8``, or
  58. * http://pypi.python.org/pypi/celery/2.2.8
  59. The 2.1 series is no longer being maintained, so we urge users
  60. of that series to upgrade to a more recent version.
  61. Distribution package maintainers are urged to provide their users
  62. with updated packages.
  63. Please direct questions to the celery-users mailing-list:
  64. http://groups.google.com/group/celery-users/,
  65. or if you are planning to report a security issue we request that
  66. you keep the information confidential by contacting
  67. security@celeryproject.org, so that a fix can be issued as quickly as possible.
  68. Thank you!