Let's Encrypt certificate used in malversiting

Posted by   Virus Bulletin on   Jan 8, 2016

We'd better get used to a world where malicious traffic is encrypted too.

According to some people, myself included, Let's Encrypt was one of the best things that happened to the Internet in 2015. Now that, as of December, the service is in public beta, anyone can register certificates for domains they own, in a process that is both easy and free.

Cybercriminals have noticed this too, and rather unsurprisingly, Trend Micro reports that a certificate issued by Let's Encrypt was used in an Angler exploit kit-powered malvertising campaign, to make the malicious advertisements harder to detect.

  The malvertising taking place. Source: Trend Micro.

What makes this case particularly interesting is the fact that the domain for which the certificate was issued was the subdomain of a legitimate site, whose DNS was compromised. As domain-based reputation isn't usually granular enough to distinguish between subdomains, this could have helped them avoid detection even further.

Let's Encrypt only issues Domain Validation certificates, which don't do more than validate the domain; hence it doesn't believe it needs to police the content of the domains for which it issues certificates, although as a possibly temporary compromise, the domains are checked against Google's Safe Browsing API before a certificate is issued.

I agree with Let's Encrypt here. I think our goal should be to encrypt all Internet traffic, and if bad traffic gets encrypted too, then that is a feature of the system, not a bug. Given how easy it is to register certificates, more policing would simply lead to a cat-and-mouse game. And there is also the danger of a slippery slope, where governments and interest groups start to pressure Let's Encrypt to revoke the certificates of sites they perceive as bad.

We'll just have to accept that more and more traffic is encrypted and find ways to block malicious activity in an environment where all traffic is encrypted.

Of course, this particular case is a little different: the exploit kit users in this case didn't "own" the subdomain; they were merely able to point it to their own server. It might be worth Let's Encrypt considering an automatic way in which domain owners can revoke certificates issued to subdomains. But that may well complicate the whole process and make little impact in practice. After all, for a successful malware campaign, domains only need to be active for a very short period of time.

If you've been telling people that the mere presence of a 'lock icon' in the address bar is a sign that a site is harmless, now is really the time to stop doing that.

Posted on 08 January 2016 by Martijn Grooten


Latest posts:

WannaCry shows we need to understand why organizations don't patch

Perhaps the question we should be asking about WannaCry is not "why do so many organizations allow unpatched machines to exist on their networks?" but "why doesn't patching work reasonably well most of the time?"

Modern security software is not necessarily powerless against threats like WannaCry

The WannaCry ransomware has affected many organisations around the world, making it probably the worst and most damaging of its kind. But modern security is not necessarily powerless against such threats.

Throwback Thursday: CARO: A personal view

This week sees the 11th International CARO Workshop taking place in Krakow, Poland – a prestigious annual meeting of anti-malware and security experts. As a founding member of CARO, Fridrik Skulason was well placed, in August 1994, to shed some light…

VB2016 paper: Uncovering the secrets of malvertising

Malicious advertising, a.k.a. malvertising, has evolved tremendously over the past few years to take a central place in some of today’s largest web-based attacks. It is by far the tool of choice for attackers to reach the masses but also to target…

Throwback Thursday: Tools of the DDoS Trade

As DDoS attacks become costlier to fix and continue to increase in both number and diversity, we turn back the clock to 2000, when Aleksander Czarnowski took a look at the DDoS tools of the day.