Upgrade Jinja2 dependency version specification to address CVE-2024-22195 #55
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We wanted to move this project to the latest dbt-core version to ensure it operates on a version of dbt-core that has addressed the security issue (CVE-2024-22195) with Jinja2. By association we also had to upgrade the version of dbt-duckdb being used. Tangentially we also upgraded the version of sqlfluff.
…ncies The `requirements.txt` was regenerated by first deleting the existing `requirements.txt` and then running `$ pip-compile`.
QMalcolm
commented
Mar 11, 2024
| iniconfig==2.0.0 | ||
| # via pytest | ||
| isodate==0.6.1 | ||
| # via | ||
| # agate | ||
| # dbt-core | ||
| jinja2==3.1.2 | ||
| jinja2==3.1.3 |
There was a problem hiding this comment.
This is the line we care the most about 🙂
gshank
approved these changes
Mar 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
CVE-2024-22195 identified an issue in Jinja2 versions <= 3.1.2. To move this project off of
Jinja2==3.1.2, we had to upgrade to the latest version of dbt-core (1.7.9) or greater. Doing so required us to also upgrade thedbt-duckdbversion.