Juniper ATP up to 5.0.2 Splunk Credentials credentials management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in Juniper ATP up to 5.0.2. This issue affects some unknown processing of the component Splunk Handler. Such manipulation leads to credentials management (Credentials). This vulnerability is uniquely identified as CVE-2019-0029. Local access is required to approach this attack. No exploit exists. You should upgrade the affected component. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Details
A vulnerability, which was classified as problematic, has been found in Juniper ATP up to 5.0.2. Affected by this issue is some unknown functionality of the component Splunk Handler. The manipulation with an unknown input leads to a credentials management vulnerability (Credentials). Using CWE to declare the problem leads to CWE-255. Impacted is confidentiality. CVE summarizes:
Juniper ATP Series Splunk credentials are logged in a file readable by authenticated local users. Using these credentials an attacker can access the Splunk server. This issue affects Juniper ATP 5.0 versions prior to 5.0.3.
The bug was discovered 01/09/2019. The weakness was disclosed 01/15/2019 (Website). The advisory is available at kb.juniper.net. This vulnerability is handled as CVE-2019-0029 since 10/11/2018. Local access is required to approach this attack. A simple authentication is required for exploitation. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1552 by the MITRE ATT&CK project.
The vulnerability was handled as a non-public zero-day exploit for at least 6 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 5.0.3 eliminates this vulnerability.
The entries VDB-129760, VDB-129773, VDB-129774 and VDB-129775 are pretty similar. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.juniper.net/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.6VulDB Meta Temp Score: 6.6
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
CNA Base Score: 8.8
CNA Vector (Juniper Networks, Inc.): 🔍
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: CredentialsClass: Credentials management / Credentials
CWE: CWE-255
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: ATP 5.0.3
Timeline
10/11/2018 🔍01/09/2019 🔍
01/15/2019 🔍
01/15/2019 🔍
01/16/2019 🔍
07/01/2023 🔍
Sources
Vendor: juniper.netAdvisory: kb.juniper.net
Status: Not defined
Confirmation: 🔍
CVE: CVE-2019-0029 (🔍)
GCVE (CVE): GCVE-0-2019-0029
GCVE (VulDB): GCVE-100-129782
See also: 🔍
Entry
Created: 01/16/2019 01:31 PMUpdated: 07/01/2023 09:40 AM
Changes: 01/16/2019 01:31 PM (61), 05/01/2020 05:50 PM (2), 07/01/2023 09:40 AM (14)
Complete: 🔍
Cache ID: 244:005:40
No comments yet. Languages: en.
Please log in to comment.