Update dependency idna to v3 [SECURITY]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
idna (changelog)	==2.8 -> ==3.7

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

GitHub Vulnerability Alerts

CVE-2024-3651

Impact

A specially crafted argument to the idna.encode() function could consume significant resources. This may lead to a denial-of-service.

Patches

The function has been refined to reject such strings without the associated resource consumption in version 3.7.

Workarounds

Domain names cannot exceed 253 characters in length, if this length limit is enforced prior to passing the domain to the idna.encode() function it should no longer consume significant resources. This is triggered by arbitrarily large inputs that would not occur in normal usage, but may be passed to the library assuming there is no preliminary input validation by the higher-level application.

References

• https://huntr.com/bounties/93d78d07-d791-4b39-a845-cbfabc44aadb

---

Release Notes

kjd/idna (idna)

v3.7

Compare Source

What's Changed

• Fix issue where specially crafted inputs to encode() could take exceptionally long amount of time to process. [CVE-2024-3651]

Thanks to Guido Vranken for reporting the issue.

Full Changelog: kjd/idna@v3.6...v3.7

v3.6

Compare Source

v3.5

Compare Source

v3.4

Compare Source

v3.3

Compare Source

v3.2

Compare Source

v3.1

Compare Source

v3.0

Compare Source

v2.10

Compare Source

v2.9

Compare Source

---

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.

[sweep-ai]

Apply Sweep Rules to your PR?

• Apply: All docstrings and comments should be up to date.
• Apply: Code should be properly indented and follow consistent indentation style.
• Apply: Variable and function names should be descriptive and follow a consistent naming convention.
• Apply: There should be no commented out code or unused code in the repository.
• Apply: Code should be organized into logical modules and classes.
• Apply: There should be no hard-coded values in the code. Use constants or configuration files instead.

This is an automated message generated by Sweep AI.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud