|
======================================================================
Secunia Research 07/01/2009
- HP OpenView Network Node Manager Multiple Vulnerabilities -
======================================================================
Table of Contents
Affected Software....................................................1
Severity.............................................................2
Vendor's Description of Software.....................................3
Description of Vulnerability.........................................4
Solution.............................................................5
Time Table...........................................................6
Credits..............................................................7
References...........................................................8
About Secunia........................................................9
Verification........................................................10
======================================================================
1) Affected Software
* HP OpenView Network Node Manager 7.51 with NNM_01168.
NOTE: Other versions may also be affected.
======================================================================
2) Severity
Rating: Moderately critical
Impact: System Access
Where: Local network
======================================================================
3) Vendor's Description of Software
"This software provides a vast amount of automation, including event
correlation and automated monitoring of your network to improve the
efficiency and productivity of your IT staff."
Product Link:
http://www.openview.hp.com/products/nnm/
======================================================================
4) Description of Vulnerability
Secunia Research has discovered vulnerabilities in HP OpenView Network
Node Manager, which can be exploited by malicious people to compromise
a vulnerable system.
1) Various boundary errors in the OpenView5.exe CGI application when
processing parameters can be exploited to cause stack-based buffer
overflows via HTTP requests to the CGI application with overly long
parameter strings.
2) A boundary error in ov.dll can be exploited to cause a stack-based
buffer overflow by e.g. sending a HTTP request to the OpenView5.exe
CGI application with an overly long parameter string.
3) A boundary error in the getcvdata.exe CGI application can be
exploited to cause a stack-based buffer overflow by sending a HTTP
request to the CGI application with an overly long parameter string.
4) A boundary error in the ovlaunch.exe CGI application can be
exploited to cause a stack-based buffer overflow by sending a HTTP
request to the CGI application with an overly long parameter string.
5) A boundary error in the Toolbar.exe CGI application can be
exploited to cause a stack-based buffer overflow by sending a HTTP
request to the CGI application with an overly long parameter string.
6) A boundary error in the Toolbar.exe CGI application can be
exploited to cause a stack-based buffer overflow by sending a HTTP
request to the CGI application with an overly long parameter string.
Successful exploitation of the vulnerabilities allows execution of
arbitrary code.
======================================================================
5) Solution
Restrict access to the affected CGI applications.
The vendor is reportedly working on fixes.
======================================================================
6) Time Table
07/01/2008 - Vendor notified.
07/01/2008 - Vendor response.
24/01/2008 - Status update requested.
24/01/2008 - Vendor response (division has been asked for an update).
20/02/2008 - Status update requested.
20/02/2008 - Vendor response (division has been asked for an update
and claims that the product is unaffected by some of the
reported vulnerabilities).
20/02/2008 - Vendor informed that latest version (7.51 with NNM_01168)
is confirmed to be vulnerable.
20/02/2008 - Vendor response (additional information has been passed
along to the division).
27/02/2008 - Vendor provides status update and acknowledges the
reported vulnerabilities.
28/02/2008 - Additional information about two vulnerabilities provided
to the vendor.
27/05/2008 - Status update requested.
27/05/2008 - Vendor response (division has been asked for an update).
07/11/2008 - Status update requested.
07/11/2008 - Vendor response (original SSRT has been split into three
SSRTs and division has been asked for an update).
07/01/2009 - Public disclosure.
======================================================================
7) Credits
Discovered by JJ Reyes, Secunia Research.
======================================================================
8) References
The Common Vulnerabilities and Exposures (CVE) project has assigned
CVE-2008-0067 for the vulnerabilities.
======================================================================
9) About Secunia
Secunia offers vulnerability management solutions to corporate
customers with verified and reliable vulnerability intelligence
relevant to their specific system configuration:
http://secunia.com/advisories/business_solutions/
Secunia also provides a publicly accessible and comprehensive advisory
database as a service to the security community and private
individuals, who are interested in or concerned about IT-security.
http://secunia.com/advisories/
Secunia believes that it is important to support the community and to
do active vulnerability research in order to aid improving the
security and reliability of software in general:
http://secunia.com/secunia_research/
Secunia regularly hires new skilled team members. Check the URL below
to see currently vacant positions:
http://secunia.com/corporate/jobs/
Secunia offers a FREE mailing list called Secunia Security Advisories:
http://secunia.com/advisories/mailing_lists/
======================================================================
10) Verification
Please verify this advisory by visiting the Secunia website:
http://secunia.com/secunia_research/2008-13/
Complete list of vulnerability reports published by Secunia Research:
http://secunia.com/secunia_research/
=====================================================================