A password management issue exists where the Organization authentication username and password were stored in plaintext in log files. A locally authenticated attacker who is able to access these stored plaintext credentials can use them to login to the Organization. Affected products are: Juniper Networks Service Insight versions from 15.1R1, prior to 18.1R1. Service Now versions from 15.1R1, prior to 18.1R1.
Advisories
Source ID Title
EUVD EUVD EUVD-2019-0839 A password management issue exists where the Organization authentication username and password were stored in plaintext in log files. A locally authenticated attacker who is able to access these stored plaintext credentials can use them to login to the Organization. Affected products are: Juniper Networks Service Insight versions from 15.1R1, prior to 18.1R1. Service Now versions from 15.1R1, prior to 18.1R1.
Fixes

Solution

The following Junos Space Service Now and Service Insight releases have been updated to resolve this specific issue: 18.1R1, and all subsequent releases. These releases of Service Now and Service Insight require at least version 18.4R1 of Junos Space. No action is needed to resolve this issue other than upgrading. Existing log files will roll over as more actions are logged. To clear log files manually, login to the server as admin and issue the following commands: [root@space ~]# cd /var/log/jboss/servers/server1/ [root@space server1]# [root@space server1]# ls serviceNow.log* Should result in output similar to: serviceNow.log serviceNow.log.10 serviceNow.log.12 serviceNow.log.14 serviceNow.log.2 serviceNow.log.4 serviceNow.log.6 serviceNow.log.8 serviceNow.log.1 serviceNow.log.11 serviceNow.log.13 serviceNow.log.15 serviceNow.log.3 serviceNow.log.5 serviceNow.log.7 serviceNow.log.9 Next, [root@space server1]# >> serviceNow.log [root@space server1]# rm serviceNow.log.* If you wish to change the Organization password as a result of this advisory, you must contact JTAC for assistance to properly update the Organization.


Workaround

There are no workarounds for this issue. To reduce the risk of exploitation of this issue use access lists or firewall filters to limit access to the device(s) via all means to only trusted administrative networks, hosts and users.

History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: juniper

Published:

Updated: 2024-09-16T23:21:58.214Z

Reserved: 2018-10-11T00:00:00

Link: CVE-2019-0032

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2019-04-10T20:29:00.537

Modified: 2024-11-21T04:16:05.457

Link: CVE-2019-0032

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.