JetBrains Code With Me prior 2020.3 Session ID random values
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in JetBrains Code With Me. It has been classified as problematic. This vulnerability affects unknown code of the component Session ID Handler. The manipulation leads to random values. This vulnerability is traded as CVE-2021-25755. Access to the local network is required for this attack to succeed. There is no exploit available. Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as problematic, has been found in JetBrains Code With Me. This issue affects an unknown code block of the component Session ID Handler. The manipulation with an unknown input leads to a random values vulnerability. Using CWE to declare the problem leads to CWE-330. The product uses insufficiently random numbers or values in a security context that depends on unpredictable numbers. Impacted is confidentiality.
The weakness was shared 02/04/2021. It is possible to read the advisory at blog.jetbrains.com. The identification of this vulnerability is CVE-2021-25755. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1600.001 according to MITRE ATT&CK.
Upgrading to version 2020.3 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.1VulDB Meta Temp Score: 3.0
VulDB Base Score: 3.1
VulDB Temp Score: 3.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Random valuesCWE: CWE-330 / CWE-310
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Code With Me 2020.3
Timeline
01/21/2021 🔍02/04/2021 🔍
02/04/2021 🔍
02/23/2021 🔍
Sources
Advisory: blog.jetbrains.comStatus: Confirmed
CVE: CVE-2021-25755 (🔍)
GCVE (CVE): GCVE-0-2021-25755
GCVE (VulDB): GCVE-100-169139
Entry
Created: 02/04/2021 07:52Updated: 02/23/2021 10:27
Changes: 02/04/2021 07:52 (37), 02/23/2021 10:27 (5)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.