Medium severity · published Jan 15, 2019
CVE-2019-0004
Juniper ATP: API and device keys are logged in a world-readable permissions file
5.5
CVSS
0.3%
EPSS
No
On KEV
Description
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.
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Confidentiality
High
Integrity
None
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.3% · higher than 26% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
JA
Juniper ATP · Juniper Networks
5.0 before 5.0.3 · source: vendor
AT
Advanced Threat Prevention · Juniper
5.0.0 before 5.0.3 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2019-0004
CVE.org
https://www.cve.org/CVERecord?id=CVE-2019-0004
Vendor Advisory
https://kb.juniper.net/JSA10918
More from Juniper ATP
9.8
CVE-2019-0022
Juniper ATP: Two hard coded credentials sharing the same password give an attacker the ability to take control of any installation of the software.
9.8
CVE-2019-0020
Juniper ATP: Hard coded credentials used in Web Collector
7.8
CVE-2019-0029
Juniper ATP: Splunk credentials are in logged in clear text
7.2
CVE-2019-0030
Juniper ATP: Password hashing uses DES and a hardcoded salt
5.5
CVE-2019-0021
Juniper ATP: secret CLI inputs are logged to /var/log/syslog in clear text