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

[R2] HP OpenView Performance Insight sendEmail.jsp bgcolor Parameter Reflected XSS



HP OpenView Performance Insight contains a flaw that allows for a reflected cross-site scripting (XSS) attack. This flaw exists because the sendEmail.jsp script does not validate input to the 'bgcolor' parameter before returning it to users. This may allow an attacker to create a specially crafted request that would execute arbitrary script code in a user's browser session within the trust relationship between their browser and the server.

Note, additional XSS issues were reported to HP at the same time, but the original report has been lost unfortunately. Yes, we're sad too.


HP has released a patch to address this issue.

Proof of Concept


Disclosure Timeline

2011-02-07: Initial report sent to [email protected]
2011-02-07: HP acknowledges report and assigns SSRT100338
2011-08-10: Asked HP if they've confirmed vulnerabilities exist
2011-08-10: HP acknowledges vulnerablities exist and says they're working on a fix
2011-08-11: HP says that a fix and an advisory were already published

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]