Open renovate[bot] opened 10 months ago
Updated jinja2
version for Documentation
The version of jinja2
, that aids in rendering our documentation, has been updated both in docs/requirements.txt
and requirements-dev.txt
. The update moves the version from 3.1.2 to 3.1.3, which ensures we are keeping our software in line with the most recent dependencies to maintain stability and functionality in our documentation.
Updated keyring
version for Development
The version of keyring
in our development requirements (requirements-dev.txt
) has also been updated. The change lifts it from 21.4.0 to the latest version, 23.9.3. This update is key, as keyring
helps with securely managing secrets during development. By updating this component, we're enhancing the secure development environment and making it compatible with the latest standards.
All modified and coverable lines are covered by tests :white_check_mark:
Comparison is base (
ad09368
) 33.67% compared to head (880f081
) 33.67%.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
This PR contains the following updates:
==3.1.2
->==3.1.4
GitHub Vulnerability Alerts
CVE-2024-22195
The
xmlattr
filter in affected versions of Jinja accepts keys containing spaces. XML/HTML attributes cannot contain spaces, as each would then be interpreted as a separate attribute. If an application accepts keys (as opposed to only values) as user input, and renders these in pages that other users see as well, an attacker could use this to inject other attributes and perform XSS. Note that accepting keys as user input is not common or a particularly intended use case of thexmlattr
filter, and an application doing so should already be verifying what keys are provided regardless of this fix.CVE-2024-34064
The
xmlattr
filter in affected versions of Jinja accepts keys containing non-attribute characters. XML/HTML attributes cannot contain spaces,/
,>
, or=
, as each would then be interpreted as starting a separate attribute. If an application accepts keys (as opposed to only values) as user input, and renders these in pages that other users see as well, an attacker could use this to inject other attributes and perform XSS. The fix for the previous GHSA-h5c8-rqwp-cp95 CVE-2024-22195 only addressed spaces but not other characters.Accepting keys as user input is now explicitly considered an unintended use case of the
xmlattr
filter, and code that does so without otherwise validating the input should be flagged as insecure, regardless of Jinja version. Accepting values as user input continues to be safe.Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.