Safety CI > cookiecutter/cookiecutter-django

master

4 years, 5 months ago

cff947e8

Merge pull request #3392 from cookiecutter/pyup-update-sphinx-4.2.0-to-4.3.0

No dependencies with known security vulnerabilities.

pyup-update-black-21.9b0-to-21.10b0

4 years, 5 months ago

de39f8ec

Update black from 21.9b0 to 21.10b0

No dependencies with known security vulnerabilities.

pyup-update-black-21.9b0-to-21.10b0

4 years, 5 months ago

e42ce836

Update black from 21.9b0 to 21.10b0

No dependencies with known security vulnerabilities.

pyup-update-sphinx-4.2.0-to-4.3.0

4 years, 5 months ago

826016e5

Update sphinx from 4.2.0 to 4.3.0

No dependencies with known security vulnerabilities.

pyup-update-sphinx-4.2.0-to-4.3.0

4 years, 5 months ago

bc343204

Update sphinx from 4.2.0 to 4.3.0

No dependencies with known security vulnerabilities.

pyup-update-sphinx-4.2.0-to-4.3.0

4 years, 5 months ago

7f134f87

Update sphinx from 4.2.0 to 4.3.0

No dependencies with known security vulnerabilities.

pyup-update-sphinx-4.2.0-to-4.3.0

4 years, 5 months ago

01421fe6

Update sphinx from 4.2.0 to 4.3.0

No dependencies with known security vulnerabilities.

master

4 years, 5 months ago

16861687

Merge pull request #3389 from cookiecutter/update/pre-commit-autoupdate

No dependencies with known security vulnerabilities.

master

4 years, 5 months ago

b03e5746

Merge pull request #3388 from cookiecutter/pyup-update-jinja2-3.0.2-to-3.0.3

No dependencies with known security vulnerabilities.

master

4 years, 5 months ago

fd18aa68

Update Changelog

No dependencies with known security vulnerabilities.

update/pre-commit-autoupdate

4 years, 5 months ago

3679cb37

Auto-update pre-commit hooks

No dependencies with known security vulnerabilities.

pyup-update-jinja2-3.0.2-to-3.0.3

4 years, 5 months ago

c5f4193e

Update jinja2 from 3.0.2 to 3.0.3

No dependencies with known security vulnerabilities.

master

4 years, 5 months ago

3e0396c7

Merge pull request #3387 from browniebroke/scripts/repo-env Get GitHub repo from environment when r

celery 5.2.0 has known security vulnerabilities.

Package	Installed	Affected	Info
celery	5.2.0	<5.2.2	show Celery 5.2.2 includes a fix for CVE-2021-23727: Celery before 5.2.2. 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.

Package

Installed

Affected

Info

celery

5.2.0

<5.2.2

show

Celery 5.2.2 includes a fix for CVE-2021-23727: Celery before 5.2.2. 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.

master

4 years, 5 months ago

ceacee92

Merge pull request #3384 from cookiecutter/pyup-update-celery-5.1.2-to-5.2.0

celery 5.2.0 has known security vulnerabilities.

Package	Installed	Affected	Info
celery	5.2.0	<5.2.2	show Celery 5.2.2 includes a fix for CVE-2021-23727: Celery before 5.2.2. 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.

Package

Installed

Affected

Info

celery

5.2.0

<5.2.2

show

Celery 5.2.2 includes a fix for CVE-2021-23727: Celery before 5.2.2. 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.

master

4 years, 5 months ago

5e906a66

Merge pull request #3385 from danihodovic/refactor/remove-user-api-methods refactor: remove user AP

celery 5.1.2 has known security vulnerabilities.

Package	Installed	Affected	Info
celery	5.1.2	<5.2.0	show Celery 5.2.0 updates 'kombu' to v5.2.1, which includes dependencies updates that resolve security issues.
celery	5.1.2	<5.2.2	show Celery 5.2.2 includes a fix for CVE-2021-23727: Celery before 5.2.2. 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.

Package

Installed

Affected

Info

celery

5.1.2

<5.2.0

show

Celery 5.2.0 updates 'kombu' to v5.2.1, which includes dependencies updates that resolve security issues.

celery

5.1.2

<5.2.2

show

Celery 5.2.2 includes a fix for CVE-2021-23727: Celery before 5.2.2. 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.