Security Market Segment LS
Thursday, 14 January 2021 11:26

Microsoft source code access: assume the worst, says Israeli firm Featured

Microsoft source code access: assume the worst, says Israeli firm Pixabay

The lack of timing and detail in Microsoft's announcement about its source code being accessed by the attackers who used SolarWinds' Orion network management software in a supply chain attack can only mean that this is bad news, the Israel-based source code control, detection, and response solution start-up Cycode, claims.

The company's vice-president of marketing, Andrew Fife, said while the lack of detail was not a big deal on its own, Microsoft had such a massive range of software that the difference between an attacker gaining access to the first-generation Zune source code and the source for Windows Server 2019 or GitHub, was massive.

"It's reasonable to guess that, if the breached codebase was inconsequential, it would have been mentioned to demonstrate the breach was immaterial," Fife argued.

"Furthermore, holidays are widely known in the PR community to be days to announce bad news. Both timing and lack of detail suggest Microsoft probably viewed this as bad news, which means we probably should too."

Microsoft announced that the attackers had accessed its source code on 31 December. The attack on SolarWinds came to light the same month, soon after American cyber security firm FireEye disclosed on 9 December AEDT that it had been compromised and had its Red Team tools stolen.

Five days later, FireEye published details about attacks using malware which it called SUNBURST; it said this malware had been used to hit both private and public entities, by corrupting the Orion network management software.

On Wednesday AEDT, the alleged attackers put out a notice offering source code from Microsoft, Cisco, the FireEye Red Team tools and multiple SolarWinds products for sale.

At the time of its announcement, Microsoft said: "At Microsoft, we have an inner source approach — the use of open source software development best practices and an open source-like culture — to making source code viewable within Microsoft." Fife dismissed this statement as disingenuous.

Attackers could still benefit from viewing source code, he said, pointing out three ways by which they could gain.

The first, he said, was by finding hard-coded secrets. "Whether usernames/passwords, API Keys, or tokens, modern applications are built as a mesh network of microservices, libraries, APIs, and SDKs that often require authentication to deliver the core service. It's common for developers to write these secrets directly into the source code on the assumption that only insiders can view them."

And, he added, "While Microsoft claims their 'threat models assume that attackers have knowledge of source code', it would be far more reassuring if they directly addressed whether or not the breached code contained secrets."

Fife said viewing source code could also be useful for those looking to reverse engineer products. "In much the same way that the source code is a software company's IP, it is also the blueprint on how to reverse engineer and exploit an application.

"If I can see your source code, I can trace the routes of inputs to determine which routes have security transforms for appropriate sanitisation (validation, redaction, encryption, etc.) before they hit their intended sink/database. Hence, by viewing Microsoft's source code the attackers now may have an easier time crafting zero-day exploits to compromise Microsoft directly and/or its customers, depending on which codebase was exposed."

Finally, Fife pointed out, the SolarWinds attackers had ensured they would stay unnoticed for more than a year by observing and learning how the company's employees wrote their code and following similar practices.

"Hence, if SolarWinds' developers looked at the malicious code they would most likely assume this code came from another SolarWinds developer and give it far less scrutiny," he said.

"External auditors had even less chance of identifying the attacker's malicious code. The attackers even appear to have tested their malicious code with a benign implant via an empty class that was delivered six months before the real backdoor was distributed to SolarWinds customers."

Fife said his company was rooting for Microsoft. "Not only is it the right thing to do, but what other choice do any of us really have? The consequences of a widespread Microsoft supply chain attack could necessitate an Internet 'shelter in place order'. We hope this is the final chapter of Microsoft's breach, but we fear it may have been reconnaissance for the next bigger operation."

Read 4519 times

Please join our community here and become a VIP.

Subscribe to ITWIRE UPDATE Newsletter here
JOIN our iTWireTV our YouTube Community here


If you're looking at enabling Microsoft Teams for your contact centre, you should bookmark this webinar.

Marketing budgets are now focused on Webinars combined with Lead Generation.

Our panellists from Whangarei District Council (NZ) and Maurice Blackburn Lawyers (Aus) were closely involved in recent projects to enable Microsoft Teams for their own contact centres.

They have kindly agreed to join Enghouse and Microsoft to talk about some of the things they would recommend as most critical for IT and CX professionals planning a Teams Contact Centre migration.

Date: 11 May 2022
Time: 12pm AEST | 2pm NZST | 10am SGT

We look forward to having you join us. Please click the button below to register.



The past year has seen a meteoric rise in ransomware incidents worldwide.

Over the past 12 months, SonicWall Capture Labs threat researchers have diligently tracked the meteoric rise in cyberattacks, as well as trends and activity across all threat vectors, including:

Encrypted threats
IoT malware
Zero-day attacks and more

These exclusive findings are now available via the 2022 SonicWall Cyber Threat Report, which ensures SMBs, government agencies, enterprises and other organizations have the actionable threat intelligence needed to combat the rising tide of cybercrime.

Click the button below to get the report.



It's all about Webinars.

Marketing budgets are now focused on Webinars combined with Lead Generation.

If you wish to promote a Webinar we recommend at least a 3 to 4 week campaign prior to your event.

The iTWire campaign will include extensive adverts on our News Site and prominent Newsletter promotion and Promotional News & Editorial. Plus a video interview of the key speaker on iTWire TV which will be used in Promotional Posts on the iTWire Home Page.

Now we are coming out of Lockdown iTWire will be focussed to assisting with your webinars and campaigns and assistance via part payments and extended terms, a Webinar Business Booster Pack and other supportive programs. We can also create your adverts and written content plus coordinate your video interview.

We look forward to discussing your campaign goals with you. Please click the button below.


Sam Varghese

Sam Varghese has been writing for iTWire since 2006, a year after the site came into existence. For nearly a decade thereafter, he wrote mostly about free and open source software, based on his own use of this genre of software. Since May 2016, he has been writing across many areas of technology. He has been a journalist for nearly 40 years in India (Indian Express and Deccan Herald), the UAE (Khaleej Times) and Australia (Daily Commercial News (now defunct) and The Age). His personal blog is titled Irregular Expression.

Share News tips for the iTWire Journalists? Your tip will be anonymous




Guest Opinion

Guest Interviews

Guest Reviews

Guest Research

Guest Research & Case Studies

Channel News