Описание
Jinja is an extensible templating engine. In versions on the 3.x branch prior to 3.1.5, 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. This vulnerability is fixed in 3.1.5.
| Релиз | Статус | Примечание |
|---|---|---|
| devel | not-affected | 3.1.5-2 |
| esm-infra-legacy/trusty | released | 2.7.2-2ubuntu0.1~esm6 |
| esm-infra/bionic | released | 2.10-1ubuntu0.18.04.1+esm3 |
| esm-infra/focal | not-affected | 2.10.1-2ubuntu0.4 |
| esm-infra/xenial | released | 2.8-1ubuntu0.1+esm5 |
| focal | released | 2.10.1-2ubuntu0.4 |
| jammy | released | 3.0.3-1ubuntu0.3 |
| noble | released | 3.1.2-1ubuntu1.2 |
| oracular | released | 3.1.3-1ubuntu1.24.10.1 |
| plucky | not-affected | 3.1.5-2 |
Показывать по
Ссылки на источники
Связанные уязвимости
Jinja is an extensible templating engine. In versions on the 3.x branch prior to 3.1.5, 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. This vulnerability is fixed in 3.1.5.
Jinja is an extensible templating engine. In versions on the 3.x branch prior to 3.1.5, 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. This vulnerability is fixed in 3.1.5.
Jinja is an extensible templating engine. In versions on the 3.x branc ...
Jinja has a sandbox breakout through malicious filenames