Ushahidi Platform up to 2.4.1 Libraries MY_Comments_Api_Object.php API information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Ushahidi Platform up to 2.4.1. Affected is the function API in the library application/libraries/api/MY_Comments_Api_Object.php of the component Libraries. This manipulation causes information disclosure.
This vulnerability is registered as CVE-2012-3474. No exploit is available.
It is suggested to upgrade the affected component.
Details
A vulnerability has been found in Ushahidi Platform up to 2.4.1 and classified as problematic. Affected by this vulnerability is the function API in the library application/libraries/api/MY_Comments_Api_Object.php of the component Libraries. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:
The comments API in application/libraries/api/MY_Comments_Api_Object.php in the Ushahidi Platform before 2.5 allows remote attackers to obtain sensitive information about the e-mail address, IP address, and other attributes of the author of a comment via an API function call.
The weakness was published 08/12/2012 (Website). It is possible to read the advisory at github.com. This vulnerability is known as CVE-2012-3474 since 06/14/2012. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
By approaching the search of inurl:application/libraries/api/MY_Comments_Api_Object.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 2.4.1 eliminates this vulnerability.
Similar entries are available at VDB-61557, VDB-61556, VDB-61554 and VDB-61553. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
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-3474 (🔍)
GCVE (CVE): GCVE-0-2012-3474
GCVE (VulDB): GCVE-100-61555
See also: 🔍
Entry
Created: 03/23/2015 16:50Updated: 12/07/2021 14:58
Changes: 03/23/2015 16:50 (50), 02/19/2019 15:21 (2), 12/07/2021 14:58 (3)
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.