CVE-2019-0030: Juniper ATP: Password hashing uses DES and a hardcoded salt
First published: Tue Jan 15 2019(Updated: )
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.
Credit: sirt@juniper.net
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Juniper Advanced Threat Prevention Firmware | >=5.0.0<5.0.3 | |
| Juniper Atp400 | ||
| Juniper Atp700 |
Remedy
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.
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2019-0030?
CVE-2019-0030 is classified as a high severity vulnerability due to its potential to allow unauthorized access to user passwords.
How do I fix CVE-2019-0030?
To fix CVE-2019-0030, upgrade Juniper ATP to version 5.0.3 or later.
What types of systems are affected by CVE-2019-0030?
CVE-2019-0030 affects Juniper ATP 5.0 versions prior to 5.0.3.
What is the cause of CVE-2019-0030?
CVE-2019-0030 is caused by the use of DES and a hardcoded salt for password hashing.
Does CVE-2019-0030 affect Juniper ATP 400 and 700 models?
No, CVE-2019-0030 does not affect Juniper ATP 400 and 700 models.
- collector/nvd-index
- agent/type
- agent/softwarecombine
- agent/remedy
- agent/weakness
- agent/severity
- agent/title
- agent/author
- agent/references
- agent/description
- agent/tags
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/source
- vendor/juniper
- canonical/juniper advanced threat prevention firmware
- version/juniper advanced threat prevention firmware/5.0.0
- canonical/juniper atp400
- canonical/juniper atp700