Juniper ATP up to 5.0.2 Password Hashing Salt inadequate encryption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.9 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Juniper ATP up to 5.0.2 and classified as critical. Impacted is an unknown function of the component Password Hashing. Performing a manipulation results in inadequate encryption (Salt). This vulnerability was named CVE-2019-0030. The attack may be initiated remotely. There is no available exploit. The affected component should be upgraded.
Details
A vulnerability, which was classified as problematic, was found in Juniper ATP up to 5.0.2. This affects an unknown part of the component Password Hashing. The manipulation with an unknown input leads to a inadequate encryption vulnerability (Salt). CWE is classifying the issue as CWE-326. The product stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Juniper ATP uses DES and a hardcoded salt for password hashing, allowing for trivial de-hashing of the password file contents. This issue affects Juniper ATP 5.0 versions prior to 5.0.3.
The bug was discovered 01/09/2019. The weakness was presented 01/15/2019 (Website). It is possible to read the advisory at kb.juniper.net. This vulnerability is uniquely identified as CVE-2019-0030 since 10/11/2018. The exploitability is told to be difficult. It is possible to initiate the attack remotely. A authentication is necessary for exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1600 according to MITRE ATT&CK.
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 $5k-$25k.
Upgrading to version 5.0.3 eliminates this vulnerability.
See VDB-129760, VDB-129773, VDB-129774 and VDB-129775 for similar entries. Be aware that VulDB is the high quality source for vulnerability data.
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.0VulDB Meta Temp Score: 5.9
VulDB Base Score: 4.1
VulDB Temp Score: 3.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.2
NVD Vector: 🔍
CNA Base Score: 6.7
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: SaltClass: Inadequate encryption / Salt
CWE: CWE-326 / CWE-310
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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: 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-0030 (🔍)
GCVE (CVE): GCVE-0-2019-0030
GCVE (VulDB): GCVE-100-129783
See also: 🔍
Entry
Created: 01/16/2019 13:31Updated: 07/01/2023 09:44
Changes: 01/16/2019 13:31 (61), 05/01/2020 17:54 (2), 07/01/2023 09:44 (14)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.