| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.2 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Pallets Jinja up to 2.8.0. The affected element is an unknown function of the component Sandbox. Performing a manipulation results in format string. This vulnerability is known as CVE-2016-10745. Remote exploitation of the attack is possible. No exploit is available. It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as critical, was found in Pallets Jinja up to 2.8.0. This affects an unknown code of the component Sandbox. The manipulation with an unknown input leads to a format string vulnerability. CWE is classifying the issue as CWE-134. The product uses a function that accepts a format string as an argument, but the format string originates from an external source. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
In Pallets Jinja before 2.8.1, str.format allows a sandbox escape.
The bug was discovered 12/29/2016. The weakness was published 04/08/2019 (Website). It is possible to read the advisory at access.redhat.com. This vulnerability is uniquely identified as CVE-2016-10745 since 04/08/2019. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 830 days. During that time the estimated underground price was around $0-$5k. The commercial vulnerability scanner Qualys is able to test this issue with plugin 172384 (OpenSUSE Security Update for python-Jinja2 (openSUSE-SU-2019:1395-1)).
Upgrading to version 2.8.1 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 105396†). Similar entries are available at VDB-109585, VDB-113041, VDB-119652 and VDB-119653. Be aware that VulDB is the high quality source for vulnerability data.
Product
Vendor
Name
Version
License
Website
- Product: https://github.com/pallets/jinja/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.4VulDB Meta Temp Score: 8.2
VulDB Base Score: 8.3
VulDB Temp Score: 7.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.6
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Format stringCWE: CWE-134 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Jinja 2.8.1
Patch: github.com
Timeline
12/29/2016 🔍09/22/2018 🔍
04/08/2019 🔍
04/08/2019 🔍
04/08/2019 🔍
08/27/2023 🔍
Sources
Product: github.comAdvisory: RHSA-2019:1022
Status: Confirmed
CVE: CVE-2016-10745 (🔍)
GCVE (CVE): GCVE-0-2016-10745
GCVE (VulDB): GCVE-100-133095
SecurityFocus: 105396 - Python CVE-2018-14647 Remote Denial of Service Vulnerability
See also: 🔍
Entry
Created: 04/08/2019 18:02Updated: 08/27/2023 09:33
Changes: 04/08/2019 18:02 (61), 05/27/2020 09:21 (4), 08/27/2023 09:33 (5)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.