Facebook Google Plus Twitter LinkedIn YouTube RSS Menu Search Resource - BlogResource - WebinarResource - ReportResource - Eventicons_066 icons_067icons_068icons_069icons_070

[R1] HPE Intelligent Management Center SOM Module Remote File Disclosure



While Tenable was analyzing CVE-2017-5797 we realized that HPE did not completely fix the issue. Their attempted patch:

  1. Updated the application to require authentication to access the fileDownload endpoint.
  2. Added logic to restrict some files from being downloaded.

However, there is nothing in the patch that prevents path traversal. An authenticated user can download arbitrary files from the remote target. Here is an example of a URL that would download win.ini as somefile from a vulnerable host:


Oddly, HPE's advisory scores this vulnerability as a CVSSv2 9.4. We believe they erroneously indicate authentication is not required and that the remote attacker can modify files. Our own scoring flags this as a 6.8.


Upgrade to iMC SOM Software Module 7.3 E0501P01

Disclosure Timeline

2017-04-11 - Issue discovered
2017-04-13 - Issue reported to HPE
2017-04-13 - Vendor replies, assigns PSRT110420, will escalate with engineering
2017-10-03 - HPE publishes advisory

All information within TRA advisories is provided “as is”, without warranty of any kind, including the implied warranties of merchantability and fitness for a particular purpose, and with no guarantee of completeness, accuracy, or timeliness. Individuals and organizations are responsible for assessing the impact of any actual or potential security vulnerability.

Tenable takes product security very seriously. If you believe you have found a vulnerability in one of our products, we ask that you please work with us to quickly resolve it in order to protect customers. Tenable believes in responding quickly to such reports, maintaining communication with researchers, and providing a solution in short order.

For more details on submitting vulnerability information, please see our Vulnerability Reporting Guidelines page.

If you have questions or corrections about this advisory, please email [email protected]