Epiqo Email 6.x-1.0/6.x-1.1/6.x-1.2/6.x-1.x Stored access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.6 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical was found in Epiqo Email 6.x-1.0/6.x-1.1/6.x-1.2/6.x-1.x. This affects an unknown part. The manipulation results in access control (Stored). This vulnerability is reported as CVE-2012-5588. No exploit exists. Upgrading the affected component is advised.
Details
A vulnerability classified as problematic has been found in Epiqo Email 6.x-1.0/6.x-1.1/6.x-1.2/6.x-1.x. Affected is an unknown function. The manipulation with an unknown input leads to a access control vulnerability (Stored). CWE is classifying the issue as CWE-264. This is going to have an impact on integrity. CVE summarizes:
The Email Field module 6.x-1.x before 6.x-1.3 for Drupal, when using a field permission module and the field contact field formatter is set to the full or teaser display mode, does not properly check permissions, which allows remote attackers to email the stored address via unspecified vectors.
The weakness was disclosed 12/26/2012 (Website). The advisory is shared for download at drupal.org. This vulnerability is traded as CVE-2012-5588 since 10/24/2012. The exploitability is told to be difficult. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1068.
Upgrading to version 6.x-1.x eliminates this vulnerability.
The entry VDB-63251 is pretty similar. Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.7VulDB Meta Temp Score: 3.6
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
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: 🔍
NVD Base Score: 🔍
Exploiting
Name: StoredClass: Access control / Stored
CWE: CWE-264
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: Email 6.x-1.x
Timeline
10/24/2012 🔍12/26/2012 🔍
12/26/2012 🔍
03/24/2015 🔍
02/24/2019 🔍
Sources
Advisory: drupal.orgStatus: Not defined
Confirmation: 🔍
CVE: CVE-2012-5588 (🔍)
GCVE (CVE): GCVE-0-2012-5588
GCVE (VulDB): GCVE-100-63252
See also: 🔍
Entry
Created: 03/24/2015 12:22Updated: 02/24/2019 10:08
Changes: 03/24/2015 12:22 (48), 02/24/2019 10:08 (2)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.