RSA Identity Governance up to 7.1.1 P02 JMX Agent missing authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.9 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in RSA Identity Governance, Lifecycle, RSA Via Lifecycle and Governance up to 7.1.1 P02. Affected by this issue is some unknown functionality of the component JMX Agent. Performing a manipulation results in missing authentication. This vulnerability is cataloged as CVE-2019-18572. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to install a patch to address this issue.
Details
A vulnerability was found in RSA Identity Governance, Lifecycle, RSA Via Lifecycle and Governance up to 7.1.1 P02. It has been classified as critical. This affects some unknown processing of the component JMX Agent. The manipulation with an unknown input leads to a missing authentication vulnerability. CWE is classifying the issue as CWE-306. The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
The RSA Identity Governance and Lifecycle and RSA Via Lifecycle and Governance products prior to 7.1.1 P03 contain an Improper Authentication vulnerability. A Java JMX agent running on the remote host is configured with plain text password authentication. An unauthenticated remote attacker can connect to the JMX agent and monitor and manage the Java application.
The weakness was shared 12/18/2019. This vulnerability is uniquely identified as CVE-2019-18572. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.
Applying the patch 7.1.1 P03 is able to eliminate this problem.
The entries VDB-147490 and VDB-147488 are related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 7.9
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.3
NVD Vector: 🔍
CNA Base Score: 8.3
CNA Vector (Dell): 🔍
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: Missing authenticationCWE: CWE-306 / CWE-287
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: 7.1.1 P03
Timeline
10/29/2019 🔍12/18/2019 🔍
12/20/2019 🔍
03/15/2024 🔍
Sources
Advisory: DSA-2019-164Status: Not defined
CVE: CVE-2019-18572 (🔍)
GCVE (CVE): GCVE-0-2019-18572
GCVE (VulDB): GCVE-100-147489
See also: 🔍
Entry
Created: 12/20/2019 06:40Updated: 03/15/2024 15:41
Changes: 12/20/2019 06:40 (38), 12/20/2019 06:45 (10), 03/15/2024 15:35 (4), 03/15/2024 15:41 (20)
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.