Safety CI > cookiecutter/cookiecutter-django

master

5 months, 3 weeks ago

ad632484

Update Contributors

jinja2 3.1.4 and django-allauth 0.63.2 have known security vulnerabilities.

Package	Installed	Affected	Info
django-allauth	0.63.2	<0.63.6	show In Django-allauth, a vulnerability allows attackers to inject arbitrary JavaScript into the login page when configuring the Facebook provider to use the `js_sdk` method, potentially compromising user sessions or stealing sensitive information.
django-allauth	0.63.2	<0.63.3	show Affected versions of Django-allauth are vulnerable to CSRF and replay attacks in the SAML login flow. RelayStatewas used to keep track of whether or not the login flow was IdP or SP initiated. As RelayState is a separate field, not part of the SAMLResponse payload, it was not signed, causing the vulnerability.

Package

Installed

Affected

Info

django-allauth

0.63.2

<0.63.6

show

In Django-allauth, a vulnerability allows attackers to inject arbitrary JavaScript into the login page when configuring the Facebook provider to use the `js_sdk` method, potentially compromising user sessions or stealing sensitive information.

django-allauth

0.63.2

<0.63.3

show

Affected versions of Django-allauth are vulnerable to CSRF and replay attacks in the SAML login flow. RelayStatewas used to keep track of whether or not the login flow was IdP or SP initiated. As RelayState is a separate field, not part of the SAMLResponse payload, it was not signed, causing the vulnerability.

master

5 months, 3 weeks ago

b6656379

Replace deprecated `uvicorn.workers` with `uvicorn-worker` (#5110) * chore: Replace deprecated uvic

jinja2 3.1.4 and django-allauth 0.63.2 have known security vulnerabilities.

Package	Installed	Affected	Info
django-allauth	0.63.2	<0.63.6	show In Django-allauth, a vulnerability allows attackers to inject arbitrary JavaScript into the login page when configuring the Facebook provider to use the `js_sdk` method, potentially compromising user sessions or stealing sensitive information.
django-allauth	0.63.2	<0.63.3	show Affected versions of Django-allauth are vulnerable to CSRF and replay attacks in the SAML login flow. RelayStatewas used to keep track of whether or not the login flow was IdP or SP initiated. As RelayState is a separate field, not part of the SAMLResponse payload, it was not signed, causing the vulnerability.

Package

Installed

Affected

Info

django-allauth

0.63.2

<0.63.6

show

In Django-allauth, a vulnerability allows attackers to inject arbitrary JavaScript into the login page when configuring the Facebook provider to use the `js_sdk` method, potentially compromising user sessions or stealing sensitive information.

django-allauth

0.63.2

<0.63.3

show

Affected versions of Django-allauth are vulnerable to CSRF and replay attacks in the SAML login flow. RelayStatewas used to keep track of whether or not the login flow was IdP or SP initiated. As RelayState is a separate field, not part of the SAMLResponse payload, it was not signed, causing the vulnerability.

pyup-update-sentry-sdk-2.5.0-to-2.5.1

5 months, 3 weeks ago

c49c395e

Update sentry-sdk from 2.5.0 to 2.5.1

jinja2 3.1.4 and django-allauth 0.63.2 have known security vulnerabilities.

Package	Installed	Affected	Info
django-allauth	0.63.2	<0.63.6	show In Django-allauth, a vulnerability allows attackers to inject arbitrary JavaScript into the login page when configuring the Facebook provider to use the `js_sdk` method, potentially compromising user sessions or stealing sensitive information.
django-allauth	0.63.2	<0.63.3	show Affected versions of Django-allauth are vulnerable to CSRF and replay attacks in the SAML login flow. RelayStatewas used to keep track of whether or not the login flow was IdP or SP initiated. As RelayState is a separate field, not part of the SAMLResponse payload, it was not signed, causing the vulnerability.

Package

Installed

Affected

Info

django-allauth

0.63.2

<0.63.6

show

In Django-allauth, a vulnerability allows attackers to inject arbitrary JavaScript into the login page when configuring the Facebook provider to use the `js_sdk` method, potentially compromising user sessions or stealing sensitive information.

django-allauth

0.63.2

<0.63.3

show

Affected versions of Django-allauth are vulnerable to CSRF and replay attacks in the SAML login flow. RelayStatewas used to keep track of whether or not the login flow was IdP or SP initiated. As RelayState is a separate field, not part of the SAMLResponse payload, it was not signed, causing the vulnerability.

master

5 months, 3 weeks ago

db38d8b0

Release 2024.06.06

jinja2 3.1.4 and django-allauth 0.63.2 have known security vulnerabilities.

Package	Installed	Affected	Info
django-allauth	0.63.2	<0.63.6	show In Django-allauth, a vulnerability allows attackers to inject arbitrary JavaScript into the login page when configuring the Facebook provider to use the `js_sdk` method, potentially compromising user sessions or stealing sensitive information.
django-allauth	0.63.2	<0.63.3	show Affected versions of Django-allauth are vulnerable to CSRF and replay attacks in the SAML login flow. RelayStatewas used to keep track of whether or not the login flow was IdP or SP initiated. As RelayState is a separate field, not part of the SAMLResponse payload, it was not signed, causing the vulnerability.

Package

Installed

Affected

Info

django-allauth

0.63.2

<0.63.6

show

In Django-allauth, a vulnerability allows attackers to inject arbitrary JavaScript into the login page when configuring the Facebook provider to use the `js_sdk` method, potentially compromising user sessions or stealing sensitive information.

django-allauth

0.63.2

<0.63.3

show

Affected versions of Django-allauth are vulnerable to CSRF and replay attacks in the SAML login flow. RelayStatewas used to keep track of whether or not the login flow was IdP or SP initiated. As RelayState is a separate field, not part of the SAMLResponse payload, it was not signed, causing the vulnerability.

master

5 months, 3 weeks ago

33c36f17

Update sentry-sdk to 2.5.0 (#5126)

jinja2 3.1.4 and django-allauth 0.63.2 have known security vulnerabilities.

Package	Installed	Affected	Info
django-allauth	0.63.2	<0.63.6	show In Django-allauth, a vulnerability allows attackers to inject arbitrary JavaScript into the login page when configuring the Facebook provider to use the `js_sdk` method, potentially compromising user sessions or stealing sensitive information.
django-allauth	0.63.2	<0.63.3	show Affected versions of Django-allauth are vulnerable to CSRF and replay attacks in the SAML login flow. RelayStatewas used to keep track of whether or not the login flow was IdP or SP initiated. As RelayState is a separate field, not part of the SAMLResponse payload, it was not signed, causing the vulnerability.

Package

Installed

Affected

Info

django-allauth

0.63.2

<0.63.6

show

In Django-allauth, a vulnerability allows attackers to inject arbitrary JavaScript into the login page when configuring the Facebook provider to use the `js_sdk` method, potentially compromising user sessions or stealing sensitive information.

django-allauth

0.63.2

<0.63.3

show

Affected versions of Django-allauth are vulnerable to CSRF and replay attacks in the SAML login flow. RelayStatewas used to keep track of whether or not the login flow was IdP or SP initiated. As RelayState is a separate field, not part of the SAMLResponse payload, it was not signed, causing the vulnerability.

pyup-update-sentry-sdk-2.4.0-to-2.5.0

5 months, 3 weeks ago

fec416f2

Update sentry-sdk from 2.4.0 to 2.5.0

jinja2 3.1.4 and django-allauth 0.63.2 have known security vulnerabilities.

Package	Installed	Affected	Info
django-allauth	0.63.2	<0.63.6	show In Django-allauth, a vulnerability allows attackers to inject arbitrary JavaScript into the login page when configuring the Facebook provider to use the `js_sdk` method, potentially compromising user sessions or stealing sensitive information.
django-allauth	0.63.2	<0.63.3	show Affected versions of Django-allauth are vulnerable to CSRF and replay attacks in the SAML login flow. RelayStatewas used to keep track of whether or not the login flow was IdP or SP initiated. As RelayState is a separate field, not part of the SAMLResponse payload, it was not signed, causing the vulnerability.

Package

Installed

Affected

Info

django-allauth

0.63.2

<0.63.6

show

In Django-allauth, a vulnerability allows attackers to inject arbitrary JavaScript into the login page when configuring the Facebook provider to use the `js_sdk` method, potentially compromising user sessions or stealing sensitive information.

django-allauth

0.63.2

<0.63.3

show

Affected versions of Django-allauth are vulnerable to CSRF and replay attacks in the SAML login flow. RelayStatewas used to keep track of whether or not the login flow was IdP or SP initiated. As RelayState is a separate field, not part of the SAMLResponse payload, it was not signed, causing the vulnerability.

master

5 months, 3 weeks ago

690b1ad3

Update ruff to 0.4.8 (#5122) * Update ruff from 0.4.7 to 0.4.8 * Update ruff from 0.4.7 to 0.4.8

jinja2 3.1.4 and django-allauth 0.63.2 have known security vulnerabilities.

Package	Installed	Affected	Info
django-allauth	0.63.2	<0.63.6	show In Django-allauth, a vulnerability allows attackers to inject arbitrary JavaScript into the login page when configuring the Facebook provider to use the `js_sdk` method, potentially compromising user sessions or stealing sensitive information.
django-allauth	0.63.2	<0.63.3	show Affected versions of Django-allauth are vulnerable to CSRF and replay attacks in the SAML login flow. RelayStatewas used to keep track of whether or not the login flow was IdP or SP initiated. As RelayState is a separate field, not part of the SAMLResponse payload, it was not signed, causing the vulnerability.

Package

Installed

Affected

Info

django-allauth

0.63.2

<0.63.6

show

In Django-allauth, a vulnerability allows attackers to inject arbitrary JavaScript into the login page when configuring the Facebook provider to use the `js_sdk` method, potentially compromising user sessions or stealing sensitive information.

django-allauth

0.63.2

<0.63.3

show

Affected versions of Django-allauth are vulnerable to CSRF and replay attacks in the SAML login flow. RelayStatewas used to keep track of whether or not the login flow was IdP or SP initiated. As RelayState is a separate field, not part of the SAMLResponse payload, it was not signed, causing the vulnerability.

master

5 months, 3 weeks ago

e3adc356

Update tox to 4.15.1 (#5124)

jinja2 3.1.4 and django-allauth 0.63.2 have known security vulnerabilities.

Package	Installed	Affected	Info
django-allauth	0.63.2	<0.63.6	show In Django-allauth, a vulnerability allows attackers to inject arbitrary JavaScript into the login page when configuring the Facebook provider to use the `js_sdk` method, potentially compromising user sessions or stealing sensitive information.
django-allauth	0.63.2	<0.63.3	show Affected versions of Django-allauth are vulnerable to CSRF and replay attacks in the SAML login flow. RelayStatewas used to keep track of whether or not the login flow was IdP or SP initiated. As RelayState is a separate field, not part of the SAMLResponse payload, it was not signed, causing the vulnerability.

Package

Installed

Affected

Info

django-allauth

0.63.2

<0.63.6

show

In Django-allauth, a vulnerability allows attackers to inject arbitrary JavaScript into the login page when configuring the Facebook provider to use the `js_sdk` method, potentially compromising user sessions or stealing sensitive information.

django-allauth

0.63.2

<0.63.3

show

Affected versions of Django-allauth are vulnerable to CSRF and replay attacks in the SAML login flow. RelayStatewas used to keep track of whether or not the login flow was IdP or SP initiated. As RelayState is a separate field, not part of the SAMLResponse payload, it was not signed, causing the vulnerability.

master

5 months, 3 weeks ago

1e1255c9

Update redis to 5.0.5 (#5125)

jinja2 3.1.4 and django-allauth 0.63.2 have known security vulnerabilities.

Package	Installed	Affected	Info
django-allauth	0.63.2	<0.63.6	show In Django-allauth, a vulnerability allows attackers to inject arbitrary JavaScript into the login page when configuring the Facebook provider to use the `js_sdk` method, potentially compromising user sessions or stealing sensitive information.
django-allauth	0.63.2	<0.63.3	show Affected versions of Django-allauth are vulnerable to CSRF and replay attacks in the SAML login flow. RelayStatewas used to keep track of whether or not the login flow was IdP or SP initiated. As RelayState is a separate field, not part of the SAMLResponse payload, it was not signed, causing the vulnerability.

Package

Installed

Affected

Info

django-allauth

0.63.2

<0.63.6

show

In Django-allauth, a vulnerability allows attackers to inject arbitrary JavaScript into the login page when configuring the Facebook provider to use the `js_sdk` method, potentially compromising user sessions or stealing sensitive information.

django-allauth

0.63.2

<0.63.3

show

Affected versions of Django-allauth are vulnerable to CSRF and replay attacks in the SAML login flow. RelayStatewas used to keep track of whether or not the login flow was IdP or SP initiated. As RelayState is a separate field, not part of the SAMLResponse payload, it was not signed, causing the vulnerability.

pyup-update-ruff-0.4.7-to-0.4.8

5 months, 3 weeks ago

c45b3063

Update Ruff pre-commit hook (#5123) Co-authored-by: browniebroke <861044+browniebroke@users.noreply

jinja2 3.1.4 and django-allauth 0.63.2 have known security vulnerabilities.

Package	Installed	Affected	Info
django-allauth	0.63.2	<0.63.6	show In Django-allauth, a vulnerability allows attackers to inject arbitrary JavaScript into the login page when configuring the Facebook provider to use the `js_sdk` method, potentially compromising user sessions or stealing sensitive information.
django-allauth	0.63.2	<0.63.3	show Affected versions of Django-allauth are vulnerable to CSRF and replay attacks in the SAML login flow. RelayStatewas used to keep track of whether or not the login flow was IdP or SP initiated. As RelayState is a separate field, not part of the SAMLResponse payload, it was not signed, causing the vulnerability.

Package

Installed

Affected

Info

django-allauth

0.63.2

<0.63.6

show

In Django-allauth, a vulnerability allows attackers to inject arbitrary JavaScript into the login page when configuring the Facebook provider to use the `js_sdk` method, potentially compromising user sessions or stealing sensitive information.

django-allauth

0.63.2

<0.63.3

show

Affected versions of Django-allauth are vulnerable to CSRF and replay attacks in the SAML login flow. RelayStatewas used to keep track of whether or not the login flow was IdP or SP initiated. As RelayState is a separate field, not part of the SAMLResponse payload, it was not signed, causing the vulnerability.

pyup-update-redis-5.0.4-to-5.0.5

5 months, 3 weeks ago

f2a76ea7

Update redis from 5.0.4 to 5.0.5

jinja2 3.1.4 and django-allauth 0.63.2 have known security vulnerabilities.

Package	Installed	Affected	Info
django-allauth	0.63.2	<0.63.6	show In Django-allauth, a vulnerability allows attackers to inject arbitrary JavaScript into the login page when configuring the Facebook provider to use the `js_sdk` method, potentially compromising user sessions or stealing sensitive information.
django-allauth	0.63.2	<0.63.3	show Affected versions of Django-allauth are vulnerable to CSRF and replay attacks in the SAML login flow. RelayStatewas used to keep track of whether or not the login flow was IdP or SP initiated. As RelayState is a separate field, not part of the SAMLResponse payload, it was not signed, causing the vulnerability.

Package

Installed

Affected

Info

django-allauth

0.63.2

<0.63.6

show

In Django-allauth, a vulnerability allows attackers to inject arbitrary JavaScript into the login page when configuring the Facebook provider to use the `js_sdk` method, potentially compromising user sessions or stealing sensitive information.

django-allauth

0.63.2

<0.63.3

show

Affected versions of Django-allauth are vulnerable to CSRF and replay attacks in the SAML login flow. RelayStatewas used to keep track of whether or not the login flow was IdP or SP initiated. As RelayState is a separate field, not part of the SAMLResponse payload, it was not signed, causing the vulnerability.

update/pre-commit-autoupdate

5 months, 3 weeks ago

1ada8e39

Auto-update pre-commit hooks

jinja2 3.1.4 and django-allauth 0.63.2 have known security vulnerabilities.

Package	Installed	Affected	Info
django-allauth	0.63.2	<0.63.6	show In Django-allauth, a vulnerability allows attackers to inject arbitrary JavaScript into the login page when configuring the Facebook provider to use the `js_sdk` method, potentially compromising user sessions or stealing sensitive information.
django-allauth	0.63.2	<0.63.3	show Affected versions of Django-allauth are vulnerable to CSRF and replay attacks in the SAML login flow. RelayStatewas used to keep track of whether or not the login flow was IdP or SP initiated. As RelayState is a separate field, not part of the SAMLResponse payload, it was not signed, causing the vulnerability.

Package

Installed

Affected

Info

django-allauth

0.63.2

<0.63.6

show

In Django-allauth, a vulnerability allows attackers to inject arbitrary JavaScript into the login page when configuring the Facebook provider to use the `js_sdk` method, potentially compromising user sessions or stealing sensitive information.

django-allauth

0.63.2

<0.63.3

show

Affected versions of Django-allauth are vulnerable to CSRF and replay attacks in the SAML login flow. RelayStatewas used to keep track of whether or not the login flow was IdP or SP initiated. As RelayState is a separate field, not part of the SAMLResponse payload, it was not signed, causing the vulnerability.

pyup-update-tox-4.15.0-to-4.15.1

5 months, 3 weeks ago

33c9c83a

Update tox from 4.15.0 to 4.15.1

jinja2 3.1.4 and django-allauth 0.63.2 have known security vulnerabilities.

Package	Installed	Affected	Info
django-allauth	0.63.2	<0.63.6	show In Django-allauth, a vulnerability allows attackers to inject arbitrary JavaScript into the login page when configuring the Facebook provider to use the `js_sdk` method, potentially compromising user sessions or stealing sensitive information.
django-allauth	0.63.2	<0.63.3	show Affected versions of Django-allauth are vulnerable to CSRF and replay attacks in the SAML login flow. RelayStatewas used to keep track of whether or not the login flow was IdP or SP initiated. As RelayState is a separate field, not part of the SAMLResponse payload, it was not signed, causing the vulnerability.

Package

Installed

Affected

Info

django-allauth

0.63.2

<0.63.6

show

In Django-allauth, a vulnerability allows attackers to inject arbitrary JavaScript into the login page when configuring the Facebook provider to use the `js_sdk` method, potentially compromising user sessions or stealing sensitive information.

django-allauth

0.63.2

<0.63.3

show

Affected versions of Django-allauth are vulnerable to CSRF and replay attacks in the SAML login flow. RelayStatewas used to keep track of whether or not the login flow was IdP or SP initiated. As RelayState is a separate field, not part of the SAMLResponse payload, it was not signed, causing the vulnerability.

pyup-update-ruff-0.4.7-to-0.4.8

5 months, 3 weeks ago

81a5c7ff

Update ruff from 0.4.7 to 0.4.8

jinja2 3.1.4 and django-allauth 0.63.2 have known security vulnerabilities.

Package	Installed	Affected	Info
django-allauth	0.63.2	<0.63.6	show In Django-allauth, a vulnerability allows attackers to inject arbitrary JavaScript into the login page when configuring the Facebook provider to use the `js_sdk` method, potentially compromising user sessions or stealing sensitive information.
django-allauth	0.63.2	<0.63.3	show Affected versions of Django-allauth are vulnerable to CSRF and replay attacks in the SAML login flow. RelayStatewas used to keep track of whether or not the login flow was IdP or SP initiated. As RelayState is a separate field, not part of the SAMLResponse payload, it was not signed, causing the vulnerability.

Package

Installed

Affected

Info

django-allauth

0.63.2

<0.63.6

show

In Django-allauth, a vulnerability allows attackers to inject arbitrary JavaScript into the login page when configuring the Facebook provider to use the `js_sdk` method, potentially compromising user sessions or stealing sensitive information.

django-allauth

0.63.2

<0.63.3

show

Affected versions of Django-allauth are vulnerable to CSRF and replay attacks in the SAML login flow. RelayStatewas used to keep track of whether or not the login flow was IdP or SP initiated. As RelayState is a separate field, not part of the SAMLResponse payload, it was not signed, causing the vulnerability.

pyup-update-ruff-0.4.7-to-0.4.8

5 months, 3 weeks ago

0d205c68

Update ruff from 0.4.7 to 0.4.8

jinja2 3.1.4 and django-allauth 0.63.2 have known security vulnerabilities.

Package	Installed	Affected	Info
django-allauth	0.63.2	<0.63.6	show In Django-allauth, a vulnerability allows attackers to inject arbitrary JavaScript into the login page when configuring the Facebook provider to use the `js_sdk` method, potentially compromising user sessions or stealing sensitive information.
django-allauth	0.63.2	<0.63.3	show Affected versions of Django-allauth are vulnerable to CSRF and replay attacks in the SAML login flow. RelayStatewas used to keep track of whether or not the login flow was IdP or SP initiated. As RelayState is a separate field, not part of the SAMLResponse payload, it was not signed, causing the vulnerability.

Package

Installed

Affected

Info

django-allauth

0.63.2

<0.63.6

show

In Django-allauth, a vulnerability allows attackers to inject arbitrary JavaScript into the login page when configuring the Facebook provider to use the `js_sdk` method, potentially compromising user sessions or stealing sensitive information.

django-allauth

0.63.2

<0.63.3

show

Affected versions of Django-allauth are vulnerable to CSRF and replay attacks in the SAML login flow. RelayStatewas used to keep track of whether or not the login flow was IdP or SP initiated. As RelayState is a separate field, not part of the SAMLResponse payload, it was not signed, causing the vulnerability.