Safety CI > tiagocordeiro/lme

pyup-update-flake8-6.1.0-to-7.0.0

4 months ago

1845ca9b

Update flake8 from 6.1.0 to 7.0.0

No dependencies with known security vulnerabilities.

pyup-update-pytest-7.4.3-to-7.4.4

4 months ago

5cffac32

Update pytest from 7.4.3 to 7.4.4

No dependencies with known security vulnerabilities.

pyup-update-coverage-7.3.2-to-7.4.0

4 months, 1 week ago

434c2126

Update coverage from 7.3.2 to 7.4.0

No dependencies with known security vulnerabilities.

pyup-update-coverage-7.3.2-to-7.3.4

4 months, 2 weeks ago

b2d735ca

Update coverage from 7.3.2 to 7.3.4

No dependencies with known security vulnerabilities.

pyup-update-coverage-7.3.2-to-7.3.3

4 months, 3 weeks ago

4de3bd68

Update coverage from 7.3.2 to 7.3.3

No dependencies with known security vulnerabilities.

pyup-update-rich-13.6.0-to-13.7.0

5 months, 3 weeks ago

d4ebaf09

Update rich from 13.6.0 to 13.7.0

No dependencies with known security vulnerabilities.

master

6 months, 1 week ago

50a7d760

Update Dependencies - Atualiza dependencias - Atualiza setup.py - Atualiza versão do pacote This c

No dependencies with known security vulnerabilities.

397-UpdateDependencies

6 months, 1 week ago

67a5ca50

Update Dependencies - Atualiza dependencias - Atualiza setup.py - Atualiza versão do pacote This c

No dependencies with known security vulnerabilities.

pyup-update-pytest-6.2.5-to-7.4.3

6 months, 1 week ago

52f3e1ec

Update pytest from 6.2.5 to 7.4.3

requests 2.26.0 has known security vulnerabilities.

Package	Installed	Affected	Info
requests	2.26.0	>=2.3.0,<2.31.0	show Requests 2.31.0 includes a fix for CVE-2023-32681: Since Requests 2.3.0, Requests has been leaking Proxy-Authorization headers to destination servers when redirected to an HTTPS endpoint. This is a product of how we use 'rebuild_proxies' to reattach the 'Proxy-Authorization' header to requests. For HTTP connections sent through the tunnel, the proxy will identify the header in the request itself and remove it prior to forwarding to the destination server. However when sent over HTTPS, the 'Proxy-Authorization' header must be sent in the CONNECT request as the proxy has no visibility into the tunneled request. This results in Requests forwarding proxy credentials to the destination server unintentionally, allowing a malicious actor to potentially exfiltrate sensitive information.

Package

Installed

Affected

Info

requests

2.26.0

>=2.3.0,<2.31.0

show

Requests 2.31.0 includes a fix for CVE-2023-32681: Since Requests 2.3.0, Requests has been leaking Proxy-Authorization headers to destination servers when redirected to an HTTPS endpoint. This is a product of how we use 'rebuild_proxies' to reattach the 'Proxy-Authorization' header to requests. For HTTP connections sent through the tunnel, the proxy will identify the header in the request itself and remove it prior to forwarding to the destination server. However when sent over HTTPS, the 'Proxy-Authorization' header must be sent in the CONNECT request as the proxy has no visibility into the tunneled request. This results in Requests forwarding proxy credentials to the destination server unintentionally, allowing a malicious actor to potentially exfiltrate sensitive information.

pyup-update-coverage-6.0.2-to-7.3.2

7 months ago

dba47477

Update coverage from 6.0.2 to 7.3.2

requests 2.26.0 has known security vulnerabilities.

Package	Installed	Affected	Info
requests	2.26.0	>=2.3.0,<2.31.0	show Requests 2.31.0 includes a fix for CVE-2023-32681: Since Requests 2.3.0, Requests has been leaking Proxy-Authorization headers to destination servers when redirected to an HTTPS endpoint. This is a product of how we use 'rebuild_proxies' to reattach the 'Proxy-Authorization' header to requests. For HTTP connections sent through the tunnel, the proxy will identify the header in the request itself and remove it prior to forwarding to the destination server. However when sent over HTTPS, the 'Proxy-Authorization' header must be sent in the CONNECT request as the proxy has no visibility into the tunneled request. This results in Requests forwarding proxy credentials to the destination server unintentionally, allowing a malicious actor to potentially exfiltrate sensitive information.

Package

Installed

Affected

Info

requests

2.26.0

>=2.3.0,<2.31.0

show

Requests 2.31.0 includes a fix for CVE-2023-32681: Since Requests 2.3.0, Requests has been leaking Proxy-Authorization headers to destination servers when redirected to an HTTPS endpoint. This is a product of how we use 'rebuild_proxies' to reattach the 'Proxy-Authorization' header to requests. For HTTP connections sent through the tunnel, the proxy will identify the header in the request itself and remove it prior to forwarding to the destination server. However when sent over HTTPS, the 'Proxy-Authorization' header must be sent in the CONNECT request as the proxy has no visibility into the tunneled request. This results in Requests forwarding proxy credentials to the destination server unintentionally, allowing a malicious actor to potentially exfiltrate sensitive information.

pyup-update-rich-10.12.0-to-13.6.0

7 months, 1 week ago

50f09123

Update rich from 10.12.0 to 13.6.0

requests 2.26.0 has known security vulnerabilities.

Package	Installed	Affected	Info
requests	2.26.0	>=2.3.0,<2.31.0	show Requests 2.31.0 includes a fix for CVE-2023-32681: Since Requests 2.3.0, Requests has been leaking Proxy-Authorization headers to destination servers when redirected to an HTTPS endpoint. This is a product of how we use 'rebuild_proxies' to reattach the 'Proxy-Authorization' header to requests. For HTTP connections sent through the tunnel, the proxy will identify the header in the request itself and remove it prior to forwarding to the destination server. However when sent over HTTPS, the 'Proxy-Authorization' header must be sent in the CONNECT request as the proxy has no visibility into the tunneled request. This results in Requests forwarding proxy credentials to the destination server unintentionally, allowing a malicious actor to potentially exfiltrate sensitive information.

Package

Installed

Affected

Info

requests

2.26.0

>=2.3.0,<2.31.0

show

Requests 2.31.0 includes a fix for CVE-2023-32681: Since Requests 2.3.0, Requests has been leaking Proxy-Authorization headers to destination servers when redirected to an HTTPS endpoint. This is a product of how we use 'rebuild_proxies' to reattach the 'Proxy-Authorization' header to requests. For HTTP connections sent through the tunnel, the proxy will identify the header in the request itself and remove it prior to forwarding to the destination server. However when sent over HTTPS, the 'Proxy-Authorization' header must be sent in the CONNECT request as the proxy has no visibility into the tunneled request. This results in Requests forwarding proxy credentials to the destination server unintentionally, allowing a malicious actor to potentially exfiltrate sensitive information.

pyup-update-rich-10.12.0-to-13.5.3

7 months, 3 weeks ago

bfc2c74c

Update rich from 10.12.0 to 13.5.3

requests 2.26.0 has known security vulnerabilities.

Package	Installed	Affected	Info
requests	2.26.0	>=2.3.0,<2.31.0	show Requests 2.31.0 includes a fix for CVE-2023-32681: Since Requests 2.3.0, Requests has been leaking Proxy-Authorization headers to destination servers when redirected to an HTTPS endpoint. This is a product of how we use 'rebuild_proxies' to reattach the 'Proxy-Authorization' header to requests. For HTTP connections sent through the tunnel, the proxy will identify the header in the request itself and remove it prior to forwarding to the destination server. However when sent over HTTPS, the 'Proxy-Authorization' header must be sent in the CONNECT request as the proxy has no visibility into the tunneled request. This results in Requests forwarding proxy credentials to the destination server unintentionally, allowing a malicious actor to potentially exfiltrate sensitive information.

Package

Installed

Affected

Info

requests

2.26.0

>=2.3.0,<2.31.0

show

Requests 2.31.0 includes a fix for CVE-2023-32681: Since Requests 2.3.0, Requests has been leaking Proxy-Authorization headers to destination servers when redirected to an HTTPS endpoint. This is a product of how we use 'rebuild_proxies' to reattach the 'Proxy-Authorization' header to requests. For HTTP connections sent through the tunnel, the proxy will identify the header in the request itself and remove it prior to forwarding to the destination server. However when sent over HTTPS, the 'Proxy-Authorization' header must be sent in the CONNECT request as the proxy has no visibility into the tunneled request. This results in Requests forwarding proxy credentials to the destination server unintentionally, allowing a malicious actor to potentially exfiltrate sensitive information.

pyup-update-pytest-6.2.5-to-7.4.2

8 months ago

d394dffc

Update pytest from 6.2.5 to 7.4.2

requests 2.26.0 has known security vulnerabilities.

Package	Installed	Affected	Info
requests	2.26.0	>=2.3.0,<2.31.0	show Requests 2.31.0 includes a fix for CVE-2023-32681: Since Requests 2.3.0, Requests has been leaking Proxy-Authorization headers to destination servers when redirected to an HTTPS endpoint. This is a product of how we use 'rebuild_proxies' to reattach the 'Proxy-Authorization' header to requests. For HTTP connections sent through the tunnel, the proxy will identify the header in the request itself and remove it prior to forwarding to the destination server. However when sent over HTTPS, the 'Proxy-Authorization' header must be sent in the CONNECT request as the proxy has no visibility into the tunneled request. This results in Requests forwarding proxy credentials to the destination server unintentionally, allowing a malicious actor to potentially exfiltrate sensitive information.

Package

Installed

Affected

Info

requests

2.26.0

>=2.3.0,<2.31.0

show

Requests 2.31.0 includes a fix for CVE-2023-32681: Since Requests 2.3.0, Requests has been leaking Proxy-Authorization headers to destination servers when redirected to an HTTPS endpoint. This is a product of how we use 'rebuild_proxies' to reattach the 'Proxy-Authorization' header to requests. For HTTP connections sent through the tunnel, the proxy will identify the header in the request itself and remove it prior to forwarding to the destination server. However when sent over HTTPS, the 'Proxy-Authorization' header must be sent in the CONNECT request as the proxy has no visibility into the tunneled request. This results in Requests forwarding proxy credentials to the destination server unintentionally, allowing a malicious actor to potentially exfiltrate sensitive information.

pyup-update-coverage-6.0.2-to-7.3.1

8 months ago

09f5075d

Update coverage from 6.0.2 to 7.3.1

requests 2.26.0 has known security vulnerabilities.

Package	Installed	Affected	Info
requests	2.26.0	>=2.3.0,<2.31.0	show Requests 2.31.0 includes a fix for CVE-2023-32681: Since Requests 2.3.0, Requests has been leaking Proxy-Authorization headers to destination servers when redirected to an HTTPS endpoint. This is a product of how we use 'rebuild_proxies' to reattach the 'Proxy-Authorization' header to requests. For HTTP connections sent through the tunnel, the proxy will identify the header in the request itself and remove it prior to forwarding to the destination server. However when sent over HTTPS, the 'Proxy-Authorization' header must be sent in the CONNECT request as the proxy has no visibility into the tunneled request. This results in Requests forwarding proxy credentials to the destination server unintentionally, allowing a malicious actor to potentially exfiltrate sensitive information.

Package

Installed

Affected

Info

requests

2.26.0

>=2.3.0,<2.31.0

show

Requests 2.31.0 includes a fix for CVE-2023-32681: Since Requests 2.3.0, Requests has been leaking Proxy-Authorization headers to destination servers when redirected to an HTTPS endpoint. This is a product of how we use 'rebuild_proxies' to reattach the 'Proxy-Authorization' header to requests. For HTTP connections sent through the tunnel, the proxy will identify the header in the request itself and remove it prior to forwarding to the destination server. However when sent over HTTPS, the 'Proxy-Authorization' header must be sent in the CONNECT request as the proxy has no visibility into the tunneled request. This results in Requests forwarding proxy credentials to the destination server unintentionally, allowing a malicious actor to potentially exfiltrate sensitive information.

pyup-update-pytest-6.2.5-to-7.4.1

8 months ago

19ff23cc

Update pytest from 6.2.5 to 7.4.1

requests 2.26.0 has known security vulnerabilities.

Package	Installed	Affected	Info
requests	2.26.0	>=2.3.0,<2.31.0	show Requests 2.31.0 includes a fix for CVE-2023-32681: Since Requests 2.3.0, Requests has been leaking Proxy-Authorization headers to destination servers when redirected to an HTTPS endpoint. This is a product of how we use 'rebuild_proxies' to reattach the 'Proxy-Authorization' header to requests. For HTTP connections sent through the tunnel, the proxy will identify the header in the request itself and remove it prior to forwarding to the destination server. However when sent over HTTPS, the 'Proxy-Authorization' header must be sent in the CONNECT request as the proxy has no visibility into the tunneled request. This results in Requests forwarding proxy credentials to the destination server unintentionally, allowing a malicious actor to potentially exfiltrate sensitive information.

Package

Installed

Affected

Info

requests

2.26.0

>=2.3.0,<2.31.0

show

Requests 2.31.0 includes a fix for CVE-2023-32681: Since Requests 2.3.0, Requests has been leaking Proxy-Authorization headers to destination servers when redirected to an HTTPS endpoint. This is a product of how we use 'rebuild_proxies' to reattach the 'Proxy-Authorization' header to requests. For HTTP connections sent through the tunnel, the proxy will identify the header in the request itself and remove it prior to forwarding to the destination server. However when sent over HTTPS, the 'Proxy-Authorization' header must be sent in the CONNECT request as the proxy has no visibility into the tunneled request. This results in Requests forwarding proxy credentials to the destination server unintentionally, allowing a malicious actor to potentially exfiltrate sensitive information.