| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in NICE Engage up to 6.5. It has been rated as critical. The affected element is an unknown function of the component JMX/RMI Interface. Performing a manipulation results in access control. This vulnerability is cataloged as CVE-2019-7727. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to use restrictive firewalling.
Details
A vulnerability, which was classified as critical, was found in NICE Engage up to 6.5. This affects an unknown function of the component JMX/RMI Interface. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-264. This is going to have an impact on confidentiality, integrity, and availability.
The bug was discovered 04/01/2019. The weakness was shared 04/01/2019 by Red Timmy Sec (SegFault) as CVE-2019-7727 - JMX/RMI Nice ENGAGE <= 6.5 Remote Command Execution as not defined mailinglist post (Bugtraq). It is possible to read the advisory at seclists.org. This vulnerability is uniquely identified as CVE-2019-7727 since 02/11/2019. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.
It is possible to mitigate the weakness by firewalling tcp/6338.
Further details are available at redtimmysec.wordpress.com. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.3
VulDB Base Score: 7.3
VulDB Temp Score: 6.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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
Class: Access controlCWE: CWE-264
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: FirewallStatus: 🔍
0-Day Time: 🔍
Firewalling: 🔍
Timeline
02/11/2019 🔍04/01/2019 🔍
04/01/2019 🔍
04/02/2019 🔍
08/21/2023 🔍
Sources
Advisory: CVE-2019-7727 - JMX/RMI Nice ENGAGE <= 6.5 Remote Command ExecutionResearcher: Red Timmy Sec (SegFault)
Status: Not defined
CVE: CVE-2019-7727 (🔍)
GCVE (CVE): GCVE-0-2019-7727
GCVE (VulDB): GCVE-100-132699
Misc.: 🔍
Entry
Created: 04/02/2019 15:39Updated: 08/21/2023 12:00
Changes: 04/02/2019 15:39 (59), 05/23/2020 16:49 (2), 08/21/2023 12:00 (4)
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.