Submit a ticketCall us

WebinarUpcoming Webinar: How Help Desk and Remote Support Pays for Itself

Learn how help desk software can simplify ticketing management, allow you to track hardware and software assets, and accelerate the speed of IT support and service delivery. Gain insights on how remote support tools allow your IT team to maximize their efficiency and ticket resolution by expediting desktop troubleshooting, ultimately helping keep end-users happy and productive.

Register here.

Home > Success Center > Network Performance Monitor (NPM) > Sweet32 and SolarWinds Orion products - CVE-2016-2183 and CVE-2016-6329

Sweet32 and SolarWinds Orion products - CVE-2016-2183 and CVE-2016-6329

Updated Feburary 3, 2017


Sweet32 is a vulnerability in 3DES-CBC ciphers that attacks 64-bit block ciphers in TLS and OpenVPN.


  • Any Orion Platform product using 3DES ciphers on version 2016.1 and later


Disable 3DES cipher suites

  1. Log in to the Orion server as an administrator.
  2. Download and install IIS Crypto from Nartac. (© 2013 Nartack Software, available at, obtained on Feb 3, 2017.)
  3. Open the tool.
  4. Select Schannel, and clear the Triple DES 168 selection.
  5. Apply changes and restart the computer.

Configure the cipher suites used by RabbitMQ

  1. Log in to the Orion server as an administrator.
  2. Open the Orion Service Manager.
  3. Stop all Orion services.
  4. Navigate to ProgramData\Solarwinds\Orion\RabbitMQ.
  5. Replace the rabbitmq.config file with the one from this article.
  6. Start all Orion services.


Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.


Last modified