SolarWinds Orion Data Breach

Hello everyone. As many of you know, SolarWinds just suffered a significant data breach. Our CEO, Mike Meline, spent quite a bit of this week researching the compromise and have gathered some details to aid you in your response. We, at Cyber Self-Defense, will continue to monitor and update you.

There is some information available on the breach, that shows that in March (or perhaps before), a nation state injected a trojanized DLL into the SolarWinds.Orion.Core.BusinessLayer.dll (with a file hash of [b91ce2fa41029f6955bff20079468448]) into the update CORE-2019.4.5220.20574-SolarWinds-Core-v2019.4.5220-Hotfix5.msp. After a dormant period (that seems to differ for each compromised system; but around two weeks), the trojan attempts to resolve a subdomain of avsvmcloud.com (I placed a generic link of google.com into the previously listed link, to prevent someone from accidentally clicking on it and going to the website). The ensuing DNS response returned, points the system that was compromised to a command and control network.

Good morning, As many of you know, SolarWinds suffered a significant data breach. Our CEO, Mike Meline, spent quite a bit of this week researching the compromise and have gathered some details to aid you in your response. We, at Cyber Self-Defense, will continue to monitor and update you.

There is some information available on the breach, that shows that in March (or perhaps before), a nation state injected a trojanized DLL into the SolarWinds.Orion.Core.BusinessLayer.dll (with a file hash of [b91ce2fa41029f6955bff20079468448]) into the update CORE-2019.4.5220.20574-SolarWinds-Core-v2019.4.5220-Hotfix5.msp. After a dormant period (that seems to differ for each compromised system; but around two weeks), the trojan attempts to resolve a subdomain of avsvmcloud.com (I placed a generic link of google.com into the previously listed link, to prevent someone from accidentally clicking on it and going to the website). The ensuing DNS response returned, points the system that was compromised to a command and control network.

a. Identification of vulnerability
i. This affects “SolarWinds® Orion® Platform software builds for versions 2019.4 HF 5 and 2020.2 with no hotfix or 2020.2 HF 1.”
1. Known affected products: Orion Platform versions 2019.4 HF 5 and 2020.2 with no hotfix or with 2020.2 HF 1, including:
a. Application Centric Monitor (ACM)
b. Database Performance Analyzer Integration Module (DPAIM)
c. Enterprise Operations Console (EOC)
d. High Availability (HA)
e. IP Address Manager (IPAM)
f. Log Analyzer (LA)
g. Network Automation Manager (NAM)
h. Network Configuration Manager (NCM)
i. Network Operations Manager (NOM)
j. Network Performance Monitor (NPM)
k. NetFlow Traffic Analyzer (NTA)
l. Server & Application Monitor (SAM)
m. Server Configuration Monitor (SCM)
n. Storage Resource Monitor (SCM)
o. User Device Tracker (UDT)
p. Virtualization Manager (VMAN)
q. VoIP & Network Quality Manager (VNQM)
r. Web Performance Monitor (WPM)
2. I recommend that you determine if you have SolarWinds.Orion.Core.BusinessLayer.dll
a. with a file hash of [b91ce2fa41029f6955bff20079468448];
b. [C:\WINDOWS\SysWOW64\netsetupsvc.dll] (unknown hash)
c. If you have Tenable Nessus installed, you can use plugin 62117 to detect SolarWinds Orion and 144198 To detect the specific version believed to have been affected.
b. Actions to take
i. There is an update that should be applied, which came out yesterday and one that will come out today. See https://www.solarwinds.com/securityadvisory
ii. It is recommended that if you have these products, that you;
1. Review logs, to ensure that there are no indicators of compromise.
iii. Forensically image system memory and/or host operating systems hosting all instances of SolarWinds Orion versions 2019.4 through 2020.2.1 HF1].
1. Analyze for new user or service accounts, privileged or otherwise. (from https://cyber.dhs.gov/ed/21-01/)
2. Analyze stored network traffic for indications of compromise, including new external DNS domains to which a small number of hosts (e.g., SolarWinds systems) have had connections. (from https://cyber.dhs.gov/ed/21-01/)
iv. Block all traffic to and from any devices that have SolarWinds installed
v. Monitor traffic
c. For more information;
i. please review the SolarWinds advisory at; https://www.solarwinds.com/securityadvisory
ii. see the guidance provided by DHS at; https://cyber.dhs.gov/ed/21-01/
d. Assistance
i. We do have Tenable Nessus and forensic tools and can run tests for you; please let us know if you need help or further guidance.

If you have any questions or would like to discuss this further, don’t hesitate to reach out to us. Stay safe!

Leave a Reply