ManageEngine ServiceDesk Plus 9.3 Login Page /mc User information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in ManageEngine ServiceDesk Plus 9.3. This issue affects some unknown processing of the file /mc of the component Login Page. This manipulation causes information disclosure (User). This vulnerability is tracked as CVE-2019-10273. The attack is possible to be carried out remotely. Moreover, an exploit is present.
Details
A vulnerability was found in ManageEngine ServiceDesk Plus 9.3. It has been declared as problematic. Affected by this vulnerability is some unknown processing of the file /mc of the component Login Page. The manipulation with an unknown input leads to a information disclosure vulnerability (User). 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:
Information leakage vulnerability in the /mc login page in ManageEngine ServiceDesk Plus 9.3 software allows authenticated users to enumerate active users. Due to a flaw within the way the authentication is handled, an attacker is able to login and verify any active account.
The bug was discovered 04/08/2019. The weakness was disclosed 04/04/2019 (Website). It is possible to read the advisory at exploit-db.com. This vulnerability is known as CVE-2019-10273 since 03/29/2019. The exploitation appears to be easy. The attack can be launched remotely. Required for exploitation is a single authentication. Technical details and also a public exploit are known. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
It is possible to download the exploit at exploit-db.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.
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: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 3.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.3
NVD Vector: 🔍
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: UserClass: Information disclosure / User
CWE: 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 |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
03/29/2019 🔍04/04/2019 🔍
04/05/2019 🔍
04/08/2019 🔍
12/03/2024 🔍
Sources
Advisory: 152439Status: Not defined
CVE: CVE-2019-10273 (🔍)
GCVE (CVE): GCVE-0-2019-10273
GCVE (VulDB): GCVE-100-133027
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 04/05/2019 08:53Updated: 12/03/2024 21:30
Changes: 04/05/2019 08:53 (55), 05/25/2020 17:11 (2), 08/25/2023 14:49 (4), 12/03/2024 21:30 (24)
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.