Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency jinja2 to v3.1.4 [security] #803

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 11, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
jinja2 ==3.1.2 -> ==3.1.4 age adoption passing confidence

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 the xmlattr 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 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 has been generated by Mend Renovate. View repository job log here.

Copy link

what-the-diff bot commented Jan 11, 2024

PR Summary

  • 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.

Copy link

codecov bot commented Jan 11, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (ad09368) 33.67% compared to head (880f081) 33.67%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #803   +/-   ##
=======================================
  Coverage   33.67%   33.67%           
=======================================
  Files           5        5           
  Lines         677      677           
=======================================
  Hits          228      228           
  Misses        449      449           
Flag Coverage Δ
unittests 33.67% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot force-pushed the renovate/pypi-jinja2-vulnerability branch from 880f081 to 5d4b84e Compare May 6, 2024 20:14
@renovate renovate bot changed the title chore(deps): update dependency jinja2 to v3.1.3 [security] chore(deps): update dependency jinja2 to v3.1.4 [security] May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants