Ushahidi Platform up to 2.4.1 MY_Email_Api_Object.php improper authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Ushahidi Platform up to 2.4.1. This affects an unknown function in the library application/libraries/api/MY_Email_Api_Object.php. The manipulation leads to improper authentication. This vulnerability is listed as CVE-2012-3472. There is no available exploit. You should upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in Ushahidi Platform up to 2.4.1. This issue affects some unknown functionality in the library application/libraries/api/MY_Email_Api_Object.php. The manipulation with an unknown input leads to a improper authentication vulnerability. Using CWE to declare the problem leads to CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. Impacted is integrity, and availability. The summary by CVE is:
The email API in application/libraries/api/MY_Email_Api_Object.php in the Ushahidi Platform before 2.5 does not require authentication, which allows remote attackers to list, delete, or organize messages via a GET request.
The weakness was presented 08/12/2012 (Website). The advisory is shared at github.com. The identification of this vulnerability is CVE-2012-3472 since 06/14/2012. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.
By approaching the search of inurl:application/libraries/api/MY_Email_Api_Object.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 2.4.1 eliminates this vulnerability.
See VDB-61557, VDB-61556, VDB-61555 and VDB-61554 for similar entries. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.2
VulDB Base Score: 6.5
VulDB Temp Score: 6.2
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
Class: Improper authenticationCWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
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: Platform 2.4.1
Patch: github.com
Timeline
06/14/2012 🔍08/12/2012 🔍
08/12/2012 🔍
03/23/2015 🔍
12/07/2021 🔍
Sources
Advisory: github.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2012-3472 (🔍)
GCVE (CVE): GCVE-0-2012-3472
GCVE (VulDB): GCVE-100-61553
See also: 🔍
Entry
Created: 03/23/2015 16:50Updated: 12/07/2021 14:50
Changes: 03/23/2015 16:50 (48), 02/19/2019 15:17 (2), 12/07/2021 14:50 (3)
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.