Safety CI > metakermit/generator-django-rest

pyup-scheduled-update-2019-10-01

5 years, 7 months ago

Update pillow from 5.3.0 to 6.1.0

requests 2.19.1 and whitenoise 4.1 have known security vulnerabilities.

Package	Installed	Affected	Info
requests	2.19.1	>=2.3.0,<2.31.0	show Affected versions of Requests are vulnerable to proxy credential leakage. When redirected to an HTTPS endpoint, the Proxy-Authorization header is forwarded to the destination server due to the use of rebuild_proxies to reattach the header. This may allow a malicious actor to exfiltrate sensitive information.
requests	2.19.1	<=2.19.1	show Requests before 2.20.0 sends an HTTP Authorization header to an http URI upon receiving a same-hostname https-to-http redirect, which makes it easier for remote attackers to discover credentials by sniffing the network.
requests	2.19.1	<2.32.2	show Affected versions of Requests, when making requests through a Requests `Session`, if the first request is made with `verify=False` to disable cert verification, all subsequent requests to the same host will continue to ignore cert verification regardless of changes to the value of `verify`. This behavior will continue for the lifecycle of the connection in the connection pool. Requests 2.32.0 fixes the issue, but versions 2.32.0 and 2.32.1 were yanked due to conflicts with CVE-2024-35195 mitigation.
whitenoise	4.1	<4.1.3	show Whitenoise 4.1.3 fixes potential path traversal attack while running in autorefresh mode on Windows. https://github.com/evansd/whitenoise/commit/4d8a3ab1e97d7ddb18b3fa8b4909c92bad5529c6

pyup-scheduled-update-2019-10-01

5 years, 7 months ago

bf157970

Update pexpect from 4.6.0 to 4.7.0

requests 2.19.1 and whitenoise 4.1 have known security vulnerabilities.

Package	Installed	Affected	Info
requests	2.19.1	>=2.3.0,<2.31.0	show Affected versions of Requests are vulnerable to proxy credential leakage. When redirected to an HTTPS endpoint, the Proxy-Authorization header is forwarded to the destination server due to the use of rebuild_proxies to reattach the header. This may allow a malicious actor to exfiltrate sensitive information.
requests	2.19.1	<=2.19.1	show Requests before 2.20.0 sends an HTTP Authorization header to an http URI upon receiving a same-hostname https-to-http redirect, which makes it easier for remote attackers to discover credentials by sniffing the network.
requests	2.19.1	<2.32.2	show Affected versions of Requests, when making requests through a Requests `Session`, if the first request is made with `verify=False` to disable cert verification, all subsequent requests to the same host will continue to ignore cert verification regardless of changes to the value of `verify`. This behavior will continue for the lifecycle of the connection in the connection pool. Requests 2.32.0 fixes the issue, but versions 2.32.0 and 2.32.1 were yanked due to conflicts with CVE-2024-35195 mitigation.
whitenoise	4.1	<4.1.3	show Whitenoise 4.1.3 fixes potential path traversal attack while running in autorefresh mode on Windows. https://github.com/evansd/whitenoise/commit/4d8a3ab1e97d7ddb18b3fa8b4909c92bad5529c6

pyup-scheduled-update-2019-10-01

5 years, 7 months ago

05c0d92a

Update parso from 0.3.1 to 0.5.1

requests 2.19.1 and whitenoise 4.1 have known security vulnerabilities.

Package	Installed	Affected	Info
requests	2.19.1	>=2.3.0,<2.31.0	show Affected versions of Requests are vulnerable to proxy credential leakage. When redirected to an HTTPS endpoint, the Proxy-Authorization header is forwarded to the destination server due to the use of rebuild_proxies to reattach the header. This may allow a malicious actor to exfiltrate sensitive information.
requests	2.19.1	<=2.19.1	show Requests before 2.20.0 sends an HTTP Authorization header to an http URI upon receiving a same-hostname https-to-http redirect, which makes it easier for remote attackers to discover credentials by sniffing the network.
requests	2.19.1	<2.32.2	show Affected versions of Requests, when making requests through a Requests `Session`, if the first request is made with `verify=False` to disable cert verification, all subsequent requests to the same host will continue to ignore cert verification regardless of changes to the value of `verify`. This behavior will continue for the lifecycle of the connection in the connection pool. Requests 2.32.0 fixes the issue, but versions 2.32.0 and 2.32.1 were yanked due to conflicts with CVE-2024-35195 mitigation.
whitenoise	4.1	<4.1.3	show Whitenoise 4.1.3 fixes potential path traversal attack while running in autorefresh mode on Windows. https://github.com/evansd/whitenoise/commit/4d8a3ab1e97d7ddb18b3fa8b4909c92bad5529c6

pyup-scheduled-update-2019-10-01

5 years, 7 months ago

3ed3f4fb

Update kombu from 4.2.1 to 4.6.5

requests 2.19.1 and whitenoise 4.1 have known security vulnerabilities.

Package	Installed	Affected	Info
requests	2.19.1	>=2.3.0,<2.31.0	show Affected versions of Requests are vulnerable to proxy credential leakage. When redirected to an HTTPS endpoint, the Proxy-Authorization header is forwarded to the destination server due to the use of rebuild_proxies to reattach the header. This may allow a malicious actor to exfiltrate sensitive information.
requests	2.19.1	<=2.19.1	show Requests before 2.20.0 sends an HTTP Authorization header to an http URI upon receiving a same-hostname https-to-http redirect, which makes it easier for remote attackers to discover credentials by sniffing the network.
requests	2.19.1	<2.32.2	show Affected versions of Requests, when making requests through a Requests `Session`, if the first request is made with `verify=False` to disable cert verification, all subsequent requests to the same host will continue to ignore cert verification regardless of changes to the value of `verify`. This behavior will continue for the lifecycle of the connection in the connection pool. Requests 2.32.0 fixes the issue, but versions 2.32.0 and 2.32.1 were yanked due to conflicts with CVE-2024-35195 mitigation.
whitenoise	4.1	<4.1.3	show Whitenoise 4.1.3 fixes potential path traversal attack while running in autorefresh mode on Windows. https://github.com/evansd/whitenoise/commit/4d8a3ab1e97d7ddb18b3fa8b4909c92bad5529c6

pyup-scheduled-update-2019-10-01

5 years, 7 months ago

19af631d

Update jedi from 0.12.1 to 0.15.1

requests 2.19.1 and whitenoise 4.1 have known security vulnerabilities.

Package	Installed	Affected	Info
requests	2.19.1	>=2.3.0,<2.31.0	show Affected versions of Requests are vulnerable to proxy credential leakage. When redirected to an HTTPS endpoint, the Proxy-Authorization header is forwarded to the destination server due to the use of rebuild_proxies to reattach the header. This may allow a malicious actor to exfiltrate sensitive information.
requests	2.19.1	<=2.19.1	show Requests before 2.20.0 sends an HTTP Authorization header to an http URI upon receiving a same-hostname https-to-http redirect, which makes it easier for remote attackers to discover credentials by sniffing the network.
requests	2.19.1	<2.32.2	show Affected versions of Requests, when making requests through a Requests `Session`, if the first request is made with `verify=False` to disable cert verification, all subsequent requests to the same host will continue to ignore cert verification regardless of changes to the value of `verify`. This behavior will continue for the lifecycle of the connection in the connection pool. Requests 2.32.0 fixes the issue, but versions 2.32.0 and 2.32.1 were yanked due to conflicts with CVE-2024-35195 mitigation.
whitenoise	4.1	<4.1.3	show Whitenoise 4.1.3 fixes potential path traversal attack while running in autorefresh mode on Windows. https://github.com/evansd/whitenoise/commit/4d8a3ab1e97d7ddb18b3fa8b4909c92bad5529c6

pyup-scheduled-update-2019-10-01

5 years, 7 months ago

512aa3f2

Update ipython from 7.0.1 to 7.8.0

requests 2.19.1 and whitenoise 4.1 have known security vulnerabilities.

Package	Installed	Affected	Info
requests	2.19.1	>=2.3.0,<2.31.0	show Affected versions of Requests are vulnerable to proxy credential leakage. When redirected to an HTTPS endpoint, the Proxy-Authorization header is forwarded to the destination server due to the use of rebuild_proxies to reattach the header. This may allow a malicious actor to exfiltrate sensitive information.
requests	2.19.1	<=2.19.1	show Requests before 2.20.0 sends an HTTP Authorization header to an http URI upon receiving a same-hostname https-to-http redirect, which makes it easier for remote attackers to discover credentials by sniffing the network.
requests	2.19.1	<2.32.2	show Affected versions of Requests, when making requests through a Requests `Session`, if the first request is made with `verify=False` to disable cert verification, all subsequent requests to the same host will continue to ignore cert verification regardless of changes to the value of `verify`. This behavior will continue for the lifecycle of the connection in the connection pool. Requests 2.32.0 fixes the issue, but versions 2.32.0 and 2.32.1 were yanked due to conflicts with CVE-2024-35195 mitigation.
whitenoise	4.1	<4.1.3	show Whitenoise 4.1.3 fixes potential path traversal attack while running in autorefresh mode on Windows. https://github.com/evansd/whitenoise/commit/4d8a3ab1e97d7ddb18b3fa8b4909c92bad5529c6

pyup-scheduled-update-2019-10-01

5 years, 7 months ago

d9d7647b

Update ipdb from 0.11 to 0.12.2

requests 2.19.1 and whitenoise 4.1 have known security vulnerabilities.

Package	Installed	Affected	Info
requests	2.19.1	>=2.3.0,<2.31.0	show Affected versions of Requests are vulnerable to proxy credential leakage. When redirected to an HTTPS endpoint, the Proxy-Authorization header is forwarded to the destination server due to the use of rebuild_proxies to reattach the header. This may allow a malicious actor to exfiltrate sensitive information.
requests	2.19.1	<=2.19.1	show Requests before 2.20.0 sends an HTTP Authorization header to an http URI upon receiving a same-hostname https-to-http redirect, which makes it easier for remote attackers to discover credentials by sniffing the network.
requests	2.19.1	<2.32.2	show Affected versions of Requests, when making requests through a Requests `Session`, if the first request is made with `verify=False` to disable cert verification, all subsequent requests to the same host will continue to ignore cert verification regardless of changes to the value of `verify`. This behavior will continue for the lifecycle of the connection in the connection pool. Requests 2.32.0 fixes the issue, but versions 2.32.0 and 2.32.1 were yanked due to conflicts with CVE-2024-35195 mitigation.
whitenoise	4.1	<4.1.3	show Whitenoise 4.1.3 fixes potential path traversal attack while running in autorefresh mode on Windows. https://github.com/evansd/whitenoise/commit/4d8a3ab1e97d7ddb18b3fa8b4909c92bad5529c6

pyup-scheduled-update-2019-10-01

5 years, 7 months ago

bc585c5e

Update idna from 2.7 to 2.8

requests 2.19.1 and whitenoise 4.1 have known security vulnerabilities.

Package	Installed	Affected	Info
requests	2.19.1	>=2.3.0,<2.31.0	show Affected versions of Requests are vulnerable to proxy credential leakage. When redirected to an HTTPS endpoint, the Proxy-Authorization header is forwarded to the destination server due to the use of rebuild_proxies to reattach the header. This may allow a malicious actor to exfiltrate sensitive information.
requests	2.19.1	<=2.19.1	show Requests before 2.20.0 sends an HTTP Authorization header to an http URI upon receiving a same-hostname https-to-http redirect, which makes it easier for remote attackers to discover credentials by sniffing the network.
requests	2.19.1	<2.32.2	show Affected versions of Requests, when making requests through a Requests `Session`, if the first request is made with `verify=False` to disable cert verification, all subsequent requests to the same host will continue to ignore cert verification regardless of changes to the value of `verify`. This behavior will continue for the lifecycle of the connection in the connection pool. Requests 2.32.0 fixes the issue, but versions 2.32.0 and 2.32.1 were yanked due to conflicts with CVE-2024-35195 mitigation.
whitenoise	4.1	<4.1.3	show Whitenoise 4.1.3 fixes potential path traversal attack while running in autorefresh mode on Windows. https://github.com/evansd/whitenoise/commit/4d8a3ab1e97d7ddb18b3fa8b4909c92bad5529c6

pyup-scheduled-update-2019-10-01

5 years, 7 months ago

87116654

Update graphql-relay from 0.4.5 to 2.0.0

requests 2.19.1 and whitenoise 4.1 have known security vulnerabilities.

Package	Installed	Affected	Info
requests	2.19.1	>=2.3.0,<2.31.0	show Affected versions of Requests are vulnerable to proxy credential leakage. When redirected to an HTTPS endpoint, the Proxy-Authorization header is forwarded to the destination server due to the use of rebuild_proxies to reattach the header. This may allow a malicious actor to exfiltrate sensitive information.
requests	2.19.1	<=2.19.1	show Requests before 2.20.0 sends an HTTP Authorization header to an http URI upon receiving a same-hostname https-to-http redirect, which makes it easier for remote attackers to discover credentials by sniffing the network.
requests	2.19.1	<2.32.2	show Affected versions of Requests, when making requests through a Requests `Session`, if the first request is made with `verify=False` to disable cert verification, all subsequent requests to the same host will continue to ignore cert verification regardless of changes to the value of `verify`. This behavior will continue for the lifecycle of the connection in the connection pool. Requests 2.32.0 fixes the issue, but versions 2.32.0 and 2.32.1 were yanked due to conflicts with CVE-2024-35195 mitigation.
whitenoise	4.1	<4.1.3	show Whitenoise 4.1.3 fixes potential path traversal attack while running in autorefresh mode on Windows. https://github.com/evansd/whitenoise/commit/4d8a3ab1e97d7ddb18b3fa8b4909c92bad5529c6

pyup-scheduled-update-2019-10-01

5 years, 7 months ago

7981054d

Update graphql-core from 2.1 to 2.2.1

requests 2.19.1 and whitenoise 4.1 have known security vulnerabilities.

Package	Installed	Affected	Info
requests	2.19.1	>=2.3.0,<2.31.0	show Affected versions of Requests are vulnerable to proxy credential leakage. When redirected to an HTTPS endpoint, the Proxy-Authorization header is forwarded to the destination server due to the use of rebuild_proxies to reattach the header. This may allow a malicious actor to exfiltrate sensitive information.
requests	2.19.1	<=2.19.1	show Requests before 2.20.0 sends an HTTP Authorization header to an http URI upon receiving a same-hostname https-to-http redirect, which makes it easier for remote attackers to discover credentials by sniffing the network.
requests	2.19.1	<2.32.2	show Affected versions of Requests, when making requests through a Requests `Session`, if the first request is made with `verify=False` to disable cert verification, all subsequent requests to the same host will continue to ignore cert verification regardless of changes to the value of `verify`. This behavior will continue for the lifecycle of the connection in the connection pool. Requests 2.32.0 fixes the issue, but versions 2.32.0 and 2.32.1 were yanked due to conflicts with CVE-2024-35195 mitigation.
whitenoise	4.1	<4.1.3	show Whitenoise 4.1.3 fixes potential path traversal attack while running in autorefresh mode on Windows. https://github.com/evansd/whitenoise/commit/4d8a3ab1e97d7ddb18b3fa8b4909c92bad5529c6

pyup-scheduled-update-2019-10-01

5 years, 7 months ago

08b68a9e

Update graphene from 2.1.3 to 2.1.8

requests 2.19.1 and whitenoise 4.1 have known security vulnerabilities.

Package	Installed	Affected	Info
requests	2.19.1	>=2.3.0,<2.31.0	show Affected versions of Requests are vulnerable to proxy credential leakage. When redirected to an HTTPS endpoint, the Proxy-Authorization header is forwarded to the destination server due to the use of rebuild_proxies to reattach the header. This may allow a malicious actor to exfiltrate sensitive information.
requests	2.19.1	<=2.19.1	show Requests before 2.20.0 sends an HTTP Authorization header to an http URI upon receiving a same-hostname https-to-http redirect, which makes it easier for remote attackers to discover credentials by sniffing the network.
requests	2.19.1	<2.32.2	show Affected versions of Requests, when making requests through a Requests `Session`, if the first request is made with `verify=False` to disable cert verification, all subsequent requests to the same host will continue to ignore cert verification regardless of changes to the value of `verify`. This behavior will continue for the lifecycle of the connection in the connection pool. Requests 2.32.0 fixes the issue, but versions 2.32.0 and 2.32.1 were yanked due to conflicts with CVE-2024-35195 mitigation.
whitenoise	4.1	<4.1.3	show Whitenoise 4.1.3 fixes potential path traversal attack while running in autorefresh mode on Windows. https://github.com/evansd/whitenoise/commit/4d8a3ab1e97d7ddb18b3fa8b4909c92bad5529c6

pyup-scheduled-update-2019-10-01

5 years, 7 months ago

a99be16b

Update eventlet from 0.24.1 to 0.25.1

requests 2.19.1 and whitenoise 4.1 have known security vulnerabilities.

Package	Installed	Affected	Info
requests	2.19.1	>=2.3.0,<2.31.0	show Affected versions of Requests are vulnerable to proxy credential leakage. When redirected to an HTTPS endpoint, the Proxy-Authorization header is forwarded to the destination server due to the use of rebuild_proxies to reattach the header. This may allow a malicious actor to exfiltrate sensitive information.
requests	2.19.1	<=2.19.1	show Requests before 2.20.0 sends an HTTP Authorization header to an http URI upon receiving a same-hostname https-to-http redirect, which makes it easier for remote attackers to discover credentials by sniffing the network.
requests	2.19.1	<2.32.2	show Affected versions of Requests, when making requests through a Requests `Session`, if the first request is made with `verify=False` to disable cert verification, all subsequent requests to the same host will continue to ignore cert verification regardless of changes to the value of `verify`. This behavior will continue for the lifecycle of the connection in the connection pool. Requests 2.32.0 fixes the issue, but versions 2.32.0 and 2.32.1 were yanked due to conflicts with CVE-2024-35195 mitigation.
whitenoise	4.1	<4.1.3	show Whitenoise 4.1.3 fixes potential path traversal attack while running in autorefresh mode on Windows. https://github.com/evansd/whitenoise/commit/4d8a3ab1e97d7ddb18b3fa8b4909c92bad5529c6

pyup-scheduled-update-2019-10-01

5 years, 7 months ago

b335c720

Update dnspython from 1.15.0 to 1.16.0

requests 2.19.1 and whitenoise 4.1 have known security vulnerabilities.

Package	Installed	Affected	Info
requests	2.19.1	>=2.3.0,<2.31.0	show Affected versions of Requests are vulnerable to proxy credential leakage. When redirected to an HTTPS endpoint, the Proxy-Authorization header is forwarded to the destination server due to the use of rebuild_proxies to reattach the header. This may allow a malicious actor to exfiltrate sensitive information.
requests	2.19.1	<=2.19.1	show Requests before 2.20.0 sends an HTTP Authorization header to an http URI upon receiving a same-hostname https-to-http redirect, which makes it easier for remote attackers to discover credentials by sniffing the network.
requests	2.19.1	<2.32.2	show Affected versions of Requests, when making requests through a Requests `Session`, if the first request is made with `verify=False` to disable cert verification, all subsequent requests to the same host will continue to ignore cert verification regardless of changes to the value of `verify`. This behavior will continue for the lifecycle of the connection in the connection pool. Requests 2.32.0 fixes the issue, but versions 2.32.0 and 2.32.1 were yanked due to conflicts with CVE-2024-35195 mitigation.
whitenoise	4.1	<4.1.3	show Whitenoise 4.1.3 fixes potential path traversal attack while running in autorefresh mode on Windows. https://github.com/evansd/whitenoise/commit/4d8a3ab1e97d7ddb18b3fa8b4909c92bad5529c6

pyup-scheduled-update-2019-10-01

5 years, 7 months ago

815c1747

Update djangorestframework from 3.8.2 to 3.10.3

requests 2.19.1 and whitenoise 4.1 have known security vulnerabilities.

Package	Installed	Affected	Info
requests	2.19.1	>=2.3.0,<2.31.0	show Affected versions of Requests are vulnerable to proxy credential leakage. When redirected to an HTTPS endpoint, the Proxy-Authorization header is forwarded to the destination server due to the use of rebuild_proxies to reattach the header. This may allow a malicious actor to exfiltrate sensitive information.
requests	2.19.1	<=2.19.1	show Requests before 2.20.0 sends an HTTP Authorization header to an http URI upon receiving a same-hostname https-to-http redirect, which makes it easier for remote attackers to discover credentials by sniffing the network.
requests	2.19.1	<2.32.2	show Affected versions of Requests, when making requests through a Requests `Session`, if the first request is made with `verify=False` to disable cert verification, all subsequent requests to the same host will continue to ignore cert verification regardless of changes to the value of `verify`. This behavior will continue for the lifecycle of the connection in the connection pool. Requests 2.32.0 fixes the issue, but versions 2.32.0 and 2.32.1 were yanked due to conflicts with CVE-2024-35195 mitigation.
whitenoise	4.1	<4.1.3	show Whitenoise 4.1.3 fixes potential path traversal attack while running in autorefresh mode on Windows. https://github.com/evansd/whitenoise/commit/4d8a3ab1e97d7ddb18b3fa8b4909c92bad5529c6

pyup-scheduled-update-2019-10-01

5 years, 7 months ago

1cdfbebd

Update django-extensions from 2.1.3 to 2.2.1

requests 2.19.1 and whitenoise 4.1 have known security vulnerabilities.

Package	Installed	Affected	Info
requests	2.19.1	>=2.3.0,<2.31.0	show Affected versions of Requests are vulnerable to proxy credential leakage. When redirected to an HTTPS endpoint, the Proxy-Authorization header is forwarded to the destination server due to the use of rebuild_proxies to reattach the header. This may allow a malicious actor to exfiltrate sensitive information.
requests	2.19.1	<=2.19.1	show Requests before 2.20.0 sends an HTTP Authorization header to an http URI upon receiving a same-hostname https-to-http redirect, which makes it easier for remote attackers to discover credentials by sniffing the network.
requests	2.19.1	<2.32.2	show Affected versions of Requests, when making requests through a Requests `Session`, if the first request is made with `verify=False` to disable cert verification, all subsequent requests to the same host will continue to ignore cert verification regardless of changes to the value of `verify`. This behavior will continue for the lifecycle of the connection in the connection pool. Requests 2.32.0 fixes the issue, but versions 2.32.0 and 2.32.1 were yanked due to conflicts with CVE-2024-35195 mitigation.
whitenoise	4.1	<4.1.3	show Whitenoise 4.1.3 fixes potential path traversal attack while running in autorefresh mode on Windows. https://github.com/evansd/whitenoise/commit/4d8a3ab1e97d7ddb18b3fa8b4909c92bad5529c6