First published: Mon May 15 2017(Updated: )
In Ambari 2.2.2 through 2.4.2 and Ambari 2.5.0, sensitive data may be stored on disk in temporary files on the Ambari Server host. The temporary files are readable by any user authenticated on the host.
Credit: security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
Apache Ambari | =2.2.2 | |
Apache Ambari | =2.2.2-rc0 | |
Apache Ambari | =2.2.2-rc1 | |
Apache Ambari | =2.4.0 | |
Apache Ambari | =2.4.0-rc0 | |
Apache Ambari | =2.4.1 | |
Apache Ambari | =2.4.1-rc0 | |
Apache Ambari | =2.4.1-rc1 | |
Apache Ambari | =2.4.2 | |
Apache Ambari | =2.4.2-rc0 | |
Apache Ambari | =2.4.2-rc1 | |
Apache Ambari | =2.5.0 | |
Apache Ambari | =2.5.0-rc0 | |
Apache Ambari | =2.5.0-rc1 | |
Apache Ambari | =2.5.0-rc2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-5655 has a medium severity due to sensitive data being stored in temporary files that can be read by any authenticated user on the host.
To fix CVE-2017-5655, upgrade to Ambari version 2.4.3 or later.
CVE-2017-5655 affects Ambari versions 2.2.2 through 2.5.0, excluding later releases.
CVE-2017-5655 may expose sensitive data stored in temporary files on the Ambari Server host.
No, only users authenticated on the host can access the sensitive data exposed by CVE-2017-5655.