Bump lxml from 5.2.1 to 5.2.2

[dependabot]

Bumps lxml from 5.2.1 to 5.2.2.

Release notes

Sourced from lxml's releases.

lxml-5.2.2

5.2.2 (2024-05-12)

Bugs fixed

• GH#417: The test_feed_parser test could fail if lxml_html_clean was not installed. It is now skipped in that case.

• LP#2059910: The minimum CPU architecture for the Linux x86 binary wheels was set back to "core2", without SSE 4.2.

• If libxml2 uses iconv, the compile time version is available as etree.ICONV_COMPILED_VERSION.

Changelog

Sourced from lxml's changelog.

5.2.2 (2024-??-??)

Bugs fixed

• GH#417: The test_feed_parser test could fail if lxml_html_clean was not installed. It is now skipped in that case.

• LP#2059910: The minimum CPU architecture for the Linux x86 binary wheels was set back to "core2", without SSE 4.2.

• If libxml2 uses iconv, the compile time version is available as etree.ICONV_COMPILED_VERSION.

Commits

• 8e4b14c Prepare release of lxml 5.2.2.
• ddaa6ed Provide compile time version of libiconv as "etree.ICONV_COMPILED_VERSION".
• 1ab00bd CI: Do not install lxml as dependency of "lxml_html_clean".
• b325054 CI: Stop building LTO wheels to avoid messing with the library build cache.
• 81624c2 CI: Exclude now-unsupported Python versions 3.6/7 from macOS jobs.
• 069fa36 Fix typo.
• e0df2ba Fix typo.
• df55eaf Update changelog.
• f3e77fa Remove dependency on SSE4 instructions, reverting back to "core2" as a target...
• a22e83c Update changelog.
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dryrunsecurity]

Hi there 👋, @DryRunSecurity here, below is a summary of our analysis and findings.

DryRun Security	Status	Findings
Configured Codepaths Analyzer	✅	0 findings
Sensitive Files Analyzer	❕	1 finding
AppSec Analyzer	✅	0 findings
Authn/Authz Analyzer	✅	0 findings
Secrets Analyzer	✅	0 findings

Note

🟢 Risk threshold not exceeded.

Change Summary (click to expand)

The following is a summary of changes in this pull request made by me, your security buddy 🤖.
Note that this summary is auto-generated and not meant to be a definitive list of security issues
but rather a helpful summary from a security perspective.

Summary:

The provided code change is an update to the requirements.txt file for the DefectDojo application, which is a web application for managing software vulnerabilities. The key change is an update to the lxml library from version 5.2.1 to 5.2.2.

From an application security perspective, keeping the lxml library up-to-date is important, as it has had several security vulnerabilities in the past. Additionally, the requirements.txt file lists a large number of dependencies for the DefectDojo application, which is common for a complex web application. Regularly reviewing and updating all dependencies to ensure the application is using the latest versions with known security fixes is a good security practice.

Overall, this code change appears to be a routine update to the project's dependencies, which is a positive step in maintaining the security of the application. However, it's always important to thoroughly test any dependency updates to ensure they don't introduce any regressions or new vulnerabilities into the application.

Files Changed:

• requirements.txt: The requirements.txt file has been updated to include the latest version of the lxml library, which is a popular XML and HTML parser for Python. Keeping this library up-to-date is important to address any known security issues.

Powered by DryRun Security

[mtesauro]

Approved