CVE-2017-5655
UnknownEPSS 2.06%
Last modified
CVE-2017-5655 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 2.06% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Apache | Ambari | 2.2.2 |
| Apache | Ambari | 2.4.0 |
| Apache | Ambari | 2.4.1 |
| Apache | Ambari | 2.4.2 |
| Apache | Ambari | 2.5.0 |
References
- https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Vulnerabilities#AmbariVulnerabilities-FixedinAmbari2.4.3Release Notes, Vendor Advisory
- https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Vulnerabilities#AmbariVulnerabilities-FixedinAmbari2.5.1Release Notes, Vendor Advisory
- https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Vulnerabilities#AmbariVulnerabilities-FixedinAmbari2.4.3Release Notes, Vendor Advisory
- https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Vulnerabilities#AmbariVulnerabilities-FixedinAmbari2.5.1Release Notes, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-5655?
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.
How severe is CVE-2017-5655?
Severity scoring for CVE-2017-5655 is pending analysis. The EPSS model estimates a 2.06% probability of exploitation in the next 30 days.
How do I fix CVE-2017-5655?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-5649Apache Geode before 1.1.1, when a cluster has enabled securi…
- CVE-2017-5650In Apache Tomcat 9.0.0.M1 to 9.0.0.M18 and 8.5.0 to 8.5.12, …
- CVE-2017-5651In Apache Tomcat 9.0.0.M1 to 9.0.0.M18 and 8.5.0 to 8.5.12, …
- CVE-2017-5652During a routine security analysis, it was found that one of…
- CVE-2017-5653JAX-RS XML Security streaming clients in Apache CXF before 3…
- CVE-2017-5654In Ambari 2.4.x (before 2.4.3) and Ambari 2.5.0, an authoriz…
- CVE-2017-5656Apache CXF's STSClient before 3.1.11 and 3.0.13 uses a flawe…
- CVE-2017-5657Several REST service endpoints of Apache Archiva are not pro…
- CVE-2017-5658The statistics generator in Apache Pony Mail 0.7 to 0.9 was …
- CVE-2017-5659Apache Traffic Server before 6.2.1 generates a coredump when…
- CVE-2017-5660There is a vulnerability in Apache Traffic Server (ATS) 6.2.…
- CVE-2017-5661In Apache FOP before 2.2, files lying on the filesystem of t…
Are you affected by CVE-2017-5655?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST