Bentley View 10.15.0.75 JT File Parser memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Bentley View 10.15.0.75. The impacted element is an unknown function of the component JT File Parser. Performing a manipulation results in memory corruption. This vulnerability is known as CVE-2021-34934. Remote exploitation of the attack is possible. No exploit is available. You should upgrade the affected component.
Details
A vulnerability classified as critical has been found in Bentley View 10.15.0.75. This affects some unknown functionality of the component JT File Parser. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was published 01/14/2022. It is possible to read the advisory at zerodayinitiative.com. This vulnerability is uniquely identified as CVE-2021-34934 since 06/17/2021. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available.
Upgrading eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.2
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
CNA Base Score: 7.8
CNA Vector (Zero Day Initiative): 🔍
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: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
06/17/2021 🔍01/14/2022 🔍
01/14/2022 🔍
01/17/2022 🔍
Sources
Advisory: zerodayinitiative.comStatus: Confirmed
CVE: CVE-2021-34934 (🔍)
GCVE (CVE): GCVE-0-2021-34934
GCVE (VulDB): GCVE-100-190395
Entry
Created: 01/14/2022 13:34Updated: 01/17/2022 12:36
Changes: 01/14/2022 13:34 (48), 01/17/2022 12:27 (1), 01/17/2022 12:36 (18)
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.