Juniper ATP: Password hashing uses DES and a hardcoded salt
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Juniper Networks | Juniper ATP | affected |
|
Configuration 1 [-]
| AND |
|
No data.
No data available yet.
Vendor Solution
The following software release have been updated to resolve this specific issue: 5.0.3 and all subsequent releases. It is suggested to change any credentials after the upgrade to the fixed version.
Vendor Workaround
There are no known workarounds for this issue, however limit the access to only trusted administrators from trusted administrative networks or hosts would minimize the risk.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2019-0837 | 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. |
No CVSS v4.0
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.534% probability within 30 days)
Key SSVC decision points have not yet been added.
| Link | Providers |
|---|---|
| https://kb.juniper.net/JSA10918 |
|
No history.