Kony Enterprise Mobile Management up to 1.2 Messages getMessageBody requestId information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Kony Enterprise Mobile Management up to 1.2. This affects an unknown part of the file selfservice/managedevice/getMessageBody of the component Messages. The manipulation of the argument requestId leads to information disclosure. This vulnerability is referenced as CVE-2014-8487. Furthermore, an exploit is available.
Details
A vulnerability was found in Kony Enterprise Mobile Management up to 1.2. It has been rated as problematic. This issue affects an unknown functionality of the file selfservice/managedevice/getMessageBody of the component Messages. The manipulation of the argument requestId with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:
Kony Management (aka Enterprise Mobile Management or EMM) 1.2 and earlier allows remote authenticated users to read (1) arbitrary messages via the messageId parameter to selfservice/managedevice/getMessageBody or (2) requests via the requestId parameter to selfservice/devicemgmt/getDeviceInfoTab.htm.
The weakness was published 02/24/2015 (Website). The advisory is shared at securityfocus.com. The identification of this vulnerability is CVE-2014-8487 since 10/26/2014. The exploitation is known to be easy. The attack may be initiated remotely. The successful exploitation needs a simple authentication. Technical details as well as a public exploit are known. MITRE ATT&CK project uses the attack technique T1592 for this issue.
The exploit is available at packetstormsecurity.com. It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 72714†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.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: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
10/26/2014 🔍02/23/2015 🔍
02/24/2015 🔍
02/24/2015 🔍
03/30/2015 🔍
06/09/2024 🔍
Sources
Advisory: securityfocus.com⛔Status: Not defined
CVE: CVE-2014-8487 (🔍)
GCVE (CVE): GCVE-0-2014-8487
GCVE (VulDB): GCVE-100-74285
SecurityFocus: 72714
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/30/2015 12:20Updated: 06/09/2024 19:12
Changes: 03/30/2015 12:20 (45), 04/13/2018 11:46 (6), 06/09/2024 19:12 (24)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.