fix(deps): update dependency urllib3 to v1.26.19 [security]

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
urllib3 (changelog)	1.26.18 -> 1.26.19

GitHub Vulnerability Alerts

CVE-2024-37891

When using urllib3's proxy support with ProxyManager, the Proxy-Authorization header is only sent to the configured proxy, as expected.

However, when sending HTTP requests without using urllib3's proxy support, it's possible to accidentally configure the Proxy-Authorization header even though it won't have any effect as the request is not using a forwarding proxy or a tunneling proxy. In those cases, urllib3 doesn't treat the Proxy-Authorization HTTP header as one carrying authentication material and thus doesn't strip the header on cross-origin redirects.

Because this is a highly unlikely scenario, we believe the severity of this vulnerability is low for almost all users. Out of an abundance of caution urllib3 will automatically strip the Proxy-Authorization header during cross-origin redirects to avoid the small chance that users are doing this on accident.

Users should use urllib3's proxy support or disable automatic redirects to achieve safe processing of the Proxy-Authorization header, but we still decided to strip the header by default in order to further protect users who aren't using the correct approach.

Affected usages

We believe the number of usages affected by this advisory is low. It requires all of the following to be true to be exploited:

• Setting the Proxy-Authorization header without using urllib3's built-in proxy support.
• Not disabling HTTP redirects.
• Either not using an HTTPS origin server or for the proxy or target origin to redirect to a malicious origin.

Remediation

• Using the Proxy-Authorization header with urllib3's ProxyManager.
• Disabling HTTP redirects using redirects=False when sending requests.
• Not using the Proxy-Authorization header.

---

Release Notes

urllib3/urllib3 (urllib3)

v1.26.19

Compare Source

====================

• Added the Proxy-Authorization header to the list of headers to strip from requests when redirecting to a different host. As before, different headers can be set via Retry.remove_headers_on_redirect.
• Fixed handling of OpenSSL 3.2.0 new error message for misconfiguring an HTTP proxy as HTTPS. (#&#8203;3405 <https://github.com/urllib3/urllib3/issues/3405>__)

---

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ ACTION	actionlint	2		0	0.03s
✅ JSON	eslint-plugin-jsonc	2	0	0	1.01s
✅ JSON	jsonlint	2		0	0.17s
✅ JSON	prettier	2	1	0	0.43s
✅ JSON	v8r	2		0	3.01s
✅ MAKEFILE	checkmake	1		0	0.0s
✅ MARKDOWN	markdownlint	3	0	0	0.52s
✅ MARKDOWN	markdown-link-check	3		0	1.09s
✅ MARKDOWN	markdown-table-formatter	3	0	0	0.29s
✅ PYTHON	black	22	1	0	0.82s
✅ PYTHON	flake8	22		0	0.56s
✅ PYTHON	isort	22	1	0	0.3s
✅ PYTHON	mypy	22		0	5.26s
✅ PYTHON	ruff	22	1	0	0.04s
✅ REPOSITORY	checkov	yes		no	8.19s
✅ REPOSITORY	gitleaks	yes		no	0.45s
✅ REPOSITORY	git_diff	yes		no	0.01s
✅ REPOSITORY	trivy-sbom	yes		no	1.22s
✅ YAML	prettier	2	2	0	0.45s
✅ YAML	v8r	2		0	2.58s
✅ YAML	yamllint	2		0	0.3s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by