APTRS 1.0 Jinja2 Template self.class.mro[1].subclasses neutralization of directive
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.6 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in APTRS 1.0. The impacted element is the function self.class.mro[1].subclasses of the component Jinja2 Template Handler. Performing a manipulation results in neutralization of directive.
This vulnerability is reported as CVE-2024-56363. The attack requires a local approach. No exploit exists.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability classified as critical has been found in APTRS 1.0. This affects the function self.class.mro[1].subclasses of the component Jinja2 Template Handler. The manipulation with an unknown input leads to a neutralization of directive vulnerability. CWE is classifying the issue as CWE-97. The product generates a web page, but does not neutralize or incorrectly neutralizes user-controllable input that could be interpreted as a server-side include (SSI) directive. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
APTRS (Automated Penetration Testing Reporting System) is a Python and Django-based automated reporting tool designed for penetration testers and security organizations. In 1.0, there is a vulnerability in the web application's handling of user-supplied input that is incorporated into a Jinja2 template. Specifically, when user input is improperly sanitized or validated, an attacker can inject Jinja2 syntax into the template, causing the server to execute arbitrary code. For example, an attacker might be able to inject expressions like {{ config }}, {{ self.class.mro[1].subclasses() }}, or more dangerous payloads that trigger execution of arbitrary Python code. The vulnerability can be reproduced by submitting crafted input to all the template fields handled by ckeditor, that are passed directly to a Jinja2 template. If the input is rendered without sufficient sanitization, it results in the execution of malicious Jinja2 code on the server.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2024-56363 since 12/20/2024. The exploitability is told to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available.
Applying the patch 9f6b6e4a56a9119eb12126a4909441e83b6d7c11 is able to eliminate this problem. The bugfix is ready for download at github.com.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
License
Website
- Product: https://github.com/APTRS/APTRS/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.8VulDB Meta Temp Score: 7.6
VulDB Base Score: 7.8
VulDB Temp Score: 7.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 7.8
CNA Vector (GitHub_M): 🔍
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: 🔍
Exploiting
Class: Neutralization of directiveCWE: CWE-97 / CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Patch: 9f6b6e4a56a9119eb12126a4909441e83b6d7c11
Timeline
12/20/2024 🔍12/23/2024 🔍
12/23/2024 🔍
12/23/2024 🔍
Sources
Product: github.comAdvisory: GHSA-h4w2-hvcg-938j
Status: Confirmed
CVE: CVE-2024-56363 (🔍)
GCVE (CVE): GCVE-0-2024-56363
GCVE (VulDB): GCVE-100-289197
Entry
Created: 12/23/2024 22:01Changes: 12/23/2024 22:01 (65)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.