Pimcore Customer Data Framework prior 4.0.6 GDPR Extract access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Pimcore Customer Data Framework. This impacts an unknown function of the component GDPR Extract Handler. Performing a manipulation results in access control. This vulnerability is reported as CVE-2024-21667. The attack is possible to be carried out remotely. No exploit exists. It is recommended to upgrade the affected component.
Details
A vulnerability, which was classified as critical, was found in Pimcore Customer Data Framework. This affects some unknown processing of the component GDPR Extract Handler. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. This is going to have an impact on confidentiality.
The weakness was disclosed 01/10/2024. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2024-21667 since 12/29/2023. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.
Upgrading to version 4.0.6 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 6.5
CNA Vector (GitHub, Inc.): 🔍
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: Access controlCWE: CWE-284 / CWE-266
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 4.0.6
Patch: github.com
Timeline
12/29/2023 🔍01/10/2024 🔍
01/10/2024 🔍
01/30/2024 🔍
Sources
Advisory: 6c34515be2ba39dceee7da07a1abf246309ccd77Status: Confirmed
CVE: CVE-2024-21667 (🔍)
GCVE (CVE): GCVE-0-2024-21667
GCVE (VulDB): GCVE-100-250347
Entry
Created: 01/10/2024 23:00Updated: 01/30/2024 07:10
Changes: 01/10/2024 23:00 (38), 01/30/2024 07:05 (3), 01/30/2024 07:10 (12)
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.