pimcore customer-data-framework up to 3.3.9 password recoverable
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in pimcore customer-data-framework up to 3.3.9. This affects an unknown function. Executing a manipulation can lead to password recoverable. This vulnerability is registered as CVE-2023-2881. It is possible to launch the attack remotely. No exploit is available. It is advisable to upgrade the affected component.
Details
A vulnerability was found in pimcore customer-data-framework up to 3.3.9. It has been declared as problematic. This vulnerability affects an unknown functionality. The manipulation with an unknown input leads to a password recoverable vulnerability. The CWE definition for the vulnerability is CWE-257. The storage of passwords in a recoverable format makes them subject to password reuse attacks by malicious users. In fact, it should be noted that recoverable encrypted passwords provide no significant benefit over plaintext passwords since they are subject not only to reuse by malicious attackers but also by malicious insiders. If a system administrator can recover a password directly, or use a brute force search on the available information, the administrator can use the password on other accounts. As an impact it is known to affect confidentiality. CVE summarizes:
Storing Passwords in a Recoverable Format in GitHub repository pimcore/customer-data-framework prior to 3.3.10.
The weakness was published 05/25/2023. The advisory is available at huntr.dev. This vulnerability was named CVE-2023-2881 since 05/25/2023. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1552 by the MITRE ATT&CK project.
Upgrading to version 3.3.10 eliminates this vulnerability. Applying the patch d1d58c10313f080737dc1e71fab3beb12488a1e6 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.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.8VulDB Meta Temp Score: 4.7
VulDB Base Score: 2.7
VulDB Temp Score: 2.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.9
NVD Vector: 🔍
CNA Base Score: 6.7
CNA Vector (huntr.dev): 🔍
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: Password recoverableCWE: CWE-257 / CWE-255
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
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: 🔍
Upgrade: customer-data-framework 3.3.10
Patch: d1d58c10313f080737dc1e71fab3beb12488a1e6
Timeline
05/25/2023 🔍05/25/2023 🔍
05/25/2023 🔍
06/17/2023 🔍
Sources
Product: github.comAdvisory: d1d58c10313f080737dc1e71fab3beb12488a1e6
Status: Confirmed
CVE: CVE-2023-2881 (🔍)
GCVE (CVE): GCVE-0-2023-2881
GCVE (VulDB): GCVE-100-229930
Entry
Created: 05/25/2023 14:28Updated: 06/17/2023 16:22
Changes: 05/25/2023 14:28 (50), 06/17/2023 16:15 (1), 06/17/2023 16:22 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.