First published: Tue Jan 15 2019(Updated: )
On Juniper ATP, the API key and the device key are logged in a file readable by authenticated local users. These keys are used for performing critical operations on the WebUI interface. 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 | >=5.0.0<5.0.3 | |
Juniper Atp400 | ||
Juniper Atp700 |
The following software release have been updated to resolve this specific issue: 5.0.3 and all subsequent releases. It is also recommended to change the device key after the upgrade.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-0004 has a medium severity rating due to the exposure of sensitive API and device keys.
To fix CVE-2019-0004, upgrade to Juniper ATP version 5.0.3 or later.
CVE-2019-0004 affects Juniper Advanced Threat Prevention versions prior to 5.0.3.
The implications of CVE-2019-0004 include unauthorized access to critical operations on the WebUI by authenticated local users.
No, Juniper ATP 5.0.3 is not vulnerable to CVE-2019-0004.