StackStorm up to 3.5.x Jinja Interpreter sandbox

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.3$0-$5k0.00

Summaryinfo

A vulnerability classified as critical has been found in StackStorm up to 3.5.x. This issue affects some unknown processing of the component Jinja Interpreter. Performing a manipulation results in sandbox. This vulnerability was named CVE-2021-44657. There is no available exploit. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in StackStorm up to 3.5.x. It has been classified as critical. This affects some unknown processing of the component Jinja Interpreter. The manipulation with an unknown input leads to a sandbox vulnerability. CWE is classifying the issue as CWE-265. This is going to have an impact on confidentiality, integrity, and availability.

The weakness was presented 12/15/2021 as 549. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2021-44657 since 12/06/2021. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1611 for this issue.

Upgrading to version 3.6.0 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.3

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Sandbox
CWE: CWE-265 / CWE-264
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: StackStorm 3.6.0
Patch: github.com

Timelineinfo

12/06/2021 🔍
12/15/2021 +9 days 🔍
12/15/2021 +0 days 🔍
12/18/2021 +3 days 🔍

Sourcesinfo

Advisory: 549
Status: Confirmed

CVE: CVE-2021-44657 (🔍)
GCVE (CVE): GCVE-0-2021-44657
GCVE (VulDB): GCVE-100-188313

Entryinfo

Created: 12/15/2021 18:45
Updated: 12/18/2021 09:31
Changes: 12/15/2021 18:45 (40), 12/18/2021 09:31 (1)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!