Vulnerability Note VU#174119

Solarwinds Network Performance Monitor 10.2.2 contains multiple vulnerabilities

Original Release date: 03 Aug 2012 | Last revised: 14 Aug 2014


Solarwinds Network Performance Monitor 10.2.2 and possibly earlier versions contain a cross-site scripting (XSS), and cross-site request forgery (CSRF) vulnerability.


Solarwinds Network Performance Monitor 10.2.2 can be attacked by modifying the snmpd.conf file with malicious JavaScript (XSS) (CWE-79) (CVE-2012-2577). The malicious JavaScript is stored in the application and then may be leveraged to mount an CSRF (CWE-352) (CVE-2012-2602) attack against a logged on administrator.


A remote unauthenticated attacker may obtain sensitive information, cause a denial of service condition or execute arbitrary code with the privileges of the application.


Apply an Update

Solarwinds has released Network Performance Monitor 10.3.1 to address these vulnerabilities. Customers may obtain the update from the Solarwinds Customer Portal.

Restrict access

As a general good security practice, only allow connections from trusted hosts and networks. Note that restricting access does not prevent XSS or CSRF attacks since the attack comes as an HTTP request from a legitimate user's host. Restricting access would prevent an attacker from accessing a web interface using stolen credentials from a blocked network location.

Vendor Information (Learn More)

VendorStatusDate NotifiedDate Updated
SOLARWINDSAffected25 Jun 201203 Aug 2012
If you are a vendor and your product is affected, let us know.

CVSS Metrics (Learn More)

Group Score Vector
Base 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P
Temporal 5.3 E:POC/RL:OF/RC:C
Environmental 1.3 CDP:ND/TD:L/CR:ND/IR:ND/AR:ND



Thanks to Offensive Security for reporting these vulnerabilities.

This document was written by Jared Allar.

Other Information

  • CVE IDs: CVE-2012-2602 CVE-2012-2577
  • Date Public: 20 Jul 2012
  • Date First Published: 03 Aug 2012
  • Date Last Updated: 14 Aug 2014
  • Document Revision: 17


If you have feedback, comments, or additional information about this vulnerability, please send us email.