New Media Smarty up to 9.9 data.mdb inadequate encryption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in New Media Smarty up to 9.9. It has been classified as problematic. This impacts an unknown function of the file data.mdb. This manipulation causes inadequate encryption. This vulnerability is handled as CVE-2020-10375. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is recommended.
Details
A vulnerability has been found in New Media Smarty up to 9.9 (Customer Relationship Management System) and classified as problematic. Affected by this vulnerability is an unknown code block of the file data.mdb. The manipulation with an unknown input leads to a inadequate encryption vulnerability. The CWE definition for the vulnerability is CWE-326. The product stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required. As an impact it is known to affect confidentiality.
The weakness was released 02/06/2021. This vulnerability is known as CVE-2020-10375. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1600 for this issue.
By approaching the search of inurl:data.mdb it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 9.10 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.9VulDB Meta Temp Score: 4.8
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
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: Inadequate encryptionCWE: CWE-326 / CWE-310
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
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: Smarty 9.10
Timeline
03/10/2020 🔍02/06/2021 🔍
02/06/2021 🔍
02/24/2021 🔍
Sources
Status: ConfirmedCVE: CVE-2020-10375 (🔍)
GCVE (CVE): GCVE-0-2020-10375
GCVE (VulDB): GCVE-100-169321
Entry
Created: 02/06/2021 10:09Updated: 02/24/2021 23:17
Changes: 02/06/2021 10:09 (38), 02/24/2021 23:11 (5), 02/24/2021 23:17 (18)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.