Connect with our team of offensive security, AI security and pen testing experts at Black Hat Europe 2023. Learn More

Connect with our team of offensive security, AI security and pen testing experts at Black Hat Europe 2023. Learn More

Managed Detection & Response

Eradicate cyberthreats with world-class intel and expertise

Managed Security Services

Expand your team’s capabilities and strengthen your security posture

Consulting & Professional Services

Tap into our global team of tenured cybersecurity specialists

Penetration Testing

Subscription- or project-based testing, delivered by global experts

Database Security

Get ahead of database risk, protect data and exceed compliance requirements

Email Security & Management

Catch email threats others miss with layered security & maximum control

Co-Managed SOC (SIEM)

Eliminate alert fatigue, focus your SecOps team, stop threats fast, and reduce cyber risk

Microsoft Exchange Server Attacks
Stay protected against emerging threats
Rapidly Secure New Environments
Security for rapid response situations
Securing the Cloud
Safely navigate and stay protected
Securing the IoT Landscape
Test, monitor and secure network objects
Why Trustwave
The Trustwave Approach
Awards and Accolades
Trustwave SpiderLabs Team
Trustwave Fusion Platform
SpiderLabs Fusion Center
Security Operations Centers
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Trustwave PartnerOne Program
Join forces with Trustwave to protect against the most advance cybersecurity threats
SpiderLabs Blog

Rogue Certificates Set on Flame

It was only a matter of time before we felt Flame's aftershock. Yesterday morning it finally happened. Microsoft published an emergency Security Advisory 2718704 and an associated patch that revokes trust from three intermediate CA certificates:

  • Microsoft Enforced Licensing Intermediate PCA (2 certificates)
  • Microsoft Enforced Licensing Registration Authority CA (SHA1)

As predicted in our Threat Predictions 2012 paper, the use of rogue certificates for targeted attacks is still "trendy". According to Microsoft there are "active attacks using unauthorized digital certificates derived from a Microsoft Certificate Authority". Later on, Microsoft stated in a post that some components of the Flame malware "were signed with a certificate that chained up to the Microsoft Enforced Licensing Intermediate PCA certificate authority, and ultimately, to the Microsoft Root Authority."

So how did the "bad" guys manage to "steal" those intermediate certificates?
Apparently, certificates that are generated by Microsoft's "Terminal Services licensing certification authority" that are only intended to be used for license server verification, can also be used for signing code – as if this code was delivered by Microsoft. It seems that this flaw was used for signing Flame's components.

As we at the SpiderLabs posted before, we keep monitoring and researching Flame's case to provide the best protection to our customers. Today we have released a Security Update for all versions of Trustwave Secure Web Gateway that revokes the trust in those intermediate CAs. That means that even if the attackers sign or signed more binaries with these rogue certificates, SWG will block them all.

We'll continue to monitor the situation and post more updates as necessary.

Latest SpiderLabs Blogs

The 2023 Retail Services Sector Threat Landscape: A Trustwave Threat Intelligence Briefing

The annual holiday shopping season is poised for a surge in spending, a fact well-known to retailers, consumers, and cybercriminals alike. The latter group, however, is poised to exploit any...

Read More

Pwning Electroencephalogram (EEG) Medical Devices by Default

Overall Analysis of Vulnerability Identification – Default Credentials Leading to Remote Code Execution During internal network testing, a document was discovered titled the “XL Security Site...

Read More

Hidden Data Exfiltration Using Time, Literally

I was looking at my watch last week and my attention was moved towards the seconds over at the right of the watch face, incrementing nicely along as you’d expect. Now, I don’t know if I’d just spent...

Read More