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.5 [security] #202

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 6, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
Jinja2 (changelog) ==3.0.1 -> ==3.1.5 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.

CVE-2024-56201

A bug in the Jinja compiler allows an attacker that controls both the content and filename of a template to execute arbitrary Python code, regardless of if Jinja's sandbox is used.

To exploit the vulnerability, an attacker needs to control both the filename and the contents of a template. Whether that is the case depends on the type of application using Jinja. This vulnerability impacts users of applications which execute untrusted templates where the template author can also choose the template filename.

CVE-2024-56326

An oversight in how the Jinja sandboxed environment detects calls to str.format allows an attacker that controls the content of a template to execute arbitrary Python code.

To exploit the vulnerability, an attacker needs to control the content of a template. Whether that is the case depends on the type of application using Jinja. This vulnerability impacts users of applications which execute untrusted templates.

Jinja's sandbox does catch calls to str.format and ensures they don't escape the sandbox. However, it's possible to store a reference to a malicious string's format method, then pass that to a filter that calls it. No such filters are built-in to Jinja, but could be present through custom filters in an application. After the fix, such indirect calls are also handled by the sandbox.


Release Notes

pallets/jinja (Jinja2)

v3.1.5

Compare Source

Unreleased

  • Calling sync render for an async template uses asyncio.run.
    :pr:1952
  • Avoid unclosed auto_aiter warnings. :pr:1960
  • Return an aclose-able AsyncGenerator from
    Template.generate_async. :pr:1960
  • Avoid leaving root_render_func() unclosed in
    Template.generate_async. :pr:1960
  • Avoid leaving async generators unclosed in blocks, includes and extends.
    :pr:1960

v3.1.4

Compare Source

Released 2024-05-05

  • The xmlattr filter does not allow keys with / solidus, >
    greater-than sign, or = equals sign, in addition to disallowing spaces.
    Regardless of any validation done by Jinja, user input should never be used
    as keys to this filter, or must be separately validated first.
    :ghsa:h75v-3vvj-5mfj

v3.1.3

Compare Source

Released 2024-01-10

  • Fix compiler error when checking if required blocks in parent templates are
    empty. :pr:1858
  • xmlattr filter does not allow keys with spaces. :ghsa:h5c8-rqwp-cp95
  • Make error messages stemming from invalid nesting of {% trans %} blocks
    more helpful. :pr:1918

v3.1.2

Compare Source

Released 2022-04-28

  • Add parameters to Environment.overlay to match __init__.
    :issue:1645
  • Handle race condition in FileSystemBytecodeCache. :issue:1654

v3.1.1

Compare Source

Released 2022-03-25

  • The template filename on Windows uses the primary path separator.
    :issue:1637

v3.1.0

Compare Source

Released 2022-03-24

  • Drop support for Python 3.6. :pr:1534

  • Remove previously deprecated code. :pr:1544

    • WithExtension and AutoEscapeExtension are built-in now.
    • contextfilter and contextfunction are replaced by
      pass_context. evalcontextfilter and
      evalcontextfunction are replaced by pass_eval_context.
      environmentfilter and environmentfunction are replaced
      by pass_environment.
    • Markup and escape should be imported from MarkupSafe.
    • Compiled templates from very old Jinja versions may need to be
      recompiled.
    • Legacy resolve mode for Context subclasses is no longer
      supported. Override resolve_or_missing instead of
      resolve.
    • unicode_urlencode is renamed to url_quote.
  • Add support for native types in macros. :issue:1510

  • The {% trans %} tag can use pgettext and npgettext by
    passing a context string as the first token in the tag, like
    {% trans "title" %}. :issue:1430

  • Update valid identifier characters from Python 3.6 to 3.7.
    :pr:1571

  • Filters and tests decorated with @async_variant are pickleable.
    :pr:1612

  • Add items filter. :issue:1561

  • Subscriptions ([0], etc.) can be used after filters, tests, and
    calls when the environment is in async mode. :issue:1573

  • The groupby filter is case-insensitive by default, matching
    other comparison filters. Added the case_sensitive parameter to
    control this. :issue:1463

  • Windows drive-relative path segments in template names will not
    result in FileSystemLoader and PackageLoader loading from
    drive-relative paths. :pr:1621

v3.0.3

Compare Source

Released 2021-11-09

  • Fix traceback rewriting internals for Python 3.10 and 3.11.
    :issue:1535
  • Fix how the native environment treats leading and trailing spaces
    when parsing values on Python 3.10. :pr:1537
  • Improve async performance by avoiding checks for common types.
    :issue:1514
  • Revert change to hash(Node) behavior. Nodes are hashed by id
    again :issue:1521
  • PackageLoader works when the package is a single module file.
    :issue:1512

v3.0.2

Compare Source

Released 2021-10-04

  • Fix a loop scoping bug that caused assignments in nested loops
    to still be referenced outside of it. :issue:1427
  • Make compile_templates deterministic for filter and import
    names. :issue:1452, 1453
  • Revert an unintended change that caused Undefined to act like
    StrictUndefined for the in operator. :issue:1448
  • Imported macros have access to the current template globals in async
    environments. :issue:1494
  • PackageLoader will not include a current directory (.) path
    segment. This allows loading templates from the root of a zip
    import. :issue:1467

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.

@renovate renovate bot force-pushed the renovate/pypi-jinja2-vulnerability branch from f66159f to 21a8583 Compare September 9, 2024 15:24
@renovate renovate bot force-pushed the renovate/pypi-jinja2-vulnerability branch from 21a8583 to 876b630 Compare September 9, 2024 21:52
@renovate renovate bot force-pushed the renovate/pypi-jinja2-vulnerability branch from 876b630 to 1041fa0 Compare September 16, 2024 21:36
displague
displague previously approved these changes Sep 26, 2024
Copy link
Contributor Author

renovate bot commented Sep 26, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@renovate renovate bot changed the title chore(deps): update dependency jinja2 to v3.1.4 [security] chore(deps): update dependency jinja2 to v3.1.5 [security] Dec 23, 2024
@renovate renovate bot force-pushed the renovate/pypi-jinja2-vulnerability branch from 5e0aaf9 to 03f5fdb Compare December 23, 2024 20:46
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.

1 participant