jinja2 3.1.4
PkgFire would install this release with a warning.·Checked 2 hours ago·Published 5 May 2024
Why
-
warnVulnerability
Jinja2 vulnerable to sandbox breakout through attr filter selecting format method (fixed in 3.1.6)
-
warnVulnerability
Jinja has a sandbox breakout through malicious filenames (fixed in 3.1.5)
-
warnVulnerability
Jinja has a sandbox breakout through indirect reference to format method (fixed in 3.1.5)
-
warnVulnerability
Jinja2 vulnerable to sandbox breakout through attr filter selecting format method (fixed in 3.1.6)
-
warnVulnerability
Jinja has a sandbox breakout through malicious filenames (fixed in 3.1.5)
-
warnVulnerability
Jinja has a sandbox breakout through indirect reference to format method (fixed in 3.1.5)
Provenance
A registry signature proves the registry served these bytes unaltered. Build provenance proves which workflow built them from which commit; a stolen publishing token can fake the first but not the second.
- Signature
- Not signed
- Build provenance
- None, and no earlier version had any
What the code does
On its own this is weak signal: plenty of honest libraries read files or talk to the network. What PkgFire watches is a release gaining something the one before it did not.
Code reading
PkgFire's own reading of the files: what the code can do.
Source patterns
Patterns found in the source, including those malware is known to use.
Other checked releases
Check every dependency before it installs
This page is one release. PkgFire checks every package in your lockfile, on every install and in every pull request, and blocks the bad ones before they run.