Safety CI > AJOliveiraRN/libpythonpro

master

5 years ago

94b6b2af

Update attrs from 19.3.0 to 20.1.0

No dependencies with known security vulnerabilities.

master

5 years ago

a9a6630c

Merge branch 'adjoli-19' into master

No dependencies with known security vulnerabilities.

pyup-update-attrs-19.3.0-to-20.1.0

5 years ago

fe7a2892

Update attrs from 19.3.0 to 20.1.0

No dependencies with known security vulnerabilities.

master

5 years ago

b01cb805

Inserido teste com o pytest close #16

No dependencies with known security vulnerabilities.

master

5 years ago

fccf24c0

Adicionadas linhas em branco no final dos arquivos setup.py e __init__.py

No dependencies with known security vulnerabilities.

master

5 years ago

ab51f8ca

Update requests from 2.18.3 to 2.24.0

No dependencies with known security vulnerabilities.

pyup-update-requests-2.18.3-to-2.24.0

5 years ago

2fefa7ef

Update requests from 2.18.3 to 2.24.0

No dependencies with known security vulnerabilities.

master

5 years ago

a723deab

Integrado com PyUp

requests 2.18.3 has known security vulnerabilities.

Package	Installed	Affected	Info
requests	2.18.3	<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.
requests	2.18.3	<2.32.4	show Requests is an HTTP library. Due to a URL parsing issue, Requests releases prior to 2.32.4 may leak .netrc credentials to third parties for specific maliciously-crafted URLs. Users should upgrade to version 2.32.4 to receive a fix. For older versions of Requests, use of the .netrc file can be disabled with `trust_env=False` on one's Requests Session.
requests	2.18.3	<=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.18.3	>=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.

master

5 years ago

2f8dec24

Fazendo downgrade da lib requests

requests 2.18.3 has known security vulnerabilities.

Package	Installed	Affected	Info
requests	2.18.3	<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.
requests	2.18.3	<2.32.4	show Requests is an HTTP library. Due to a URL parsing issue, Requests releases prior to 2.32.4 may leak .netrc credentials to third parties for specific maliciously-crafted URLs. Users should upgrade to version 2.32.4 to receive a fix. For older versions of Requests, use of the .netrc file can be disabled with `trust_env=False` on one's Requests Session.
requests	2.18.3	<=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.18.3	>=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.