BADLOCK – Are ‘Branded’ Exploits Going Too Far?

The New Acunetix V12 Engine


So there’s been hype about this big exploit coming, for over a month, before anything was released. It had a name, a website and a logo – and it was called Badlock.

And now it’s out, and it’s more like Sadlock – really a local network DoS against DCE/RPC services on Windows and Linux with some slight chance of pulling off a MiTM. No remote code exeuction, not even privilege escalation.

BADLOCK - Are 'Branded' Exploits Going Too Far?

Microsoft hasn’t even labelled it as critical, merely important.

Crucial? As it was marketed, hardly.

On April 12th, 2016 Badlock, a crucial security bug in Windows and Samba was disclosed.

Samba 4.4.2, 4.3.8 and 4.2.11 Security Releases are available.

Please update your systems. We are pretty sure that there will be exploits soon.

Engineers at Microsoft and the Samba Team worked together during the past months to get this problem fixed.

Source: http://badlock.org/

There is a whole list of CVE’s related, none of them are really critical.

Another questionable point is that the person who ‘discovered’ these bugs, is a member of Samba Core Team..and works on Samba.

So it’s like hey, here’s a bunch of vulnerabilities I found in my own software, let’s make a logo for them and give them a name (which doesn’t even really related to the vulns).

So yah there’s nothing really wrong with branding a vulnerability, to get awareness about something critical – get press coverage and get people fixing it. But this? This is a minor bug, with no real major production impact, only exploitable over a LAN which at words allows for a MiTM.

And well, if someone has access to your LAN, they have plenty of ways to run MiTM without exploiting obscure bugs in SAMBA (if you even run it).

Windows has patched then in the latest patch Tuesday, specifically MS16-047:

This security update resolves a vulnerability in Microsoft Windows. The vulnerability could allow elevation of privilege if an attacker launches a man-in-the-middle (MiTM) attack. An attacker could then force a downgrade of the authentication level of the SAM and LSAD channels and impersonate an authenticated user.

This security update is rated Important for all supported editions of Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8.1, Windows Server 2012, Windows Server 2012 R2, Windows RT 8.1, and Windows 10.

Definitely a candidate for the award Pwnie for Most Overhyped Bug. Shellshock won last year, which was also very overstated.

The reaction to Badlock however has been MUCH worse, due to a SAMBA vendor and core team member being involved.

It’s also not a particularly good look for SerNet, which appeared to be publicizing a Samba flaw as serious while touting, er, Samba enterprise support.

“I’m left wondering who at SerNet decided the Badlock marketing campaign was a good idea and why,” said Michael Gorelik, R&D veep at infosec biz Morphisec.

“Microsoft gave the vulnerability a security ranking of ‘important’ but not critical. In fact, it would be extremely difficult for cybercriminals to exploit the Badlock vulnerability. The attacker would need to be already inside the network and past any security mechanisms. He must be in a place in which he can sniff and intercept the traffic and would need administrative credentials to access resources required for network interception from inside the network.

Source: The Register

A saw a great quote on Twitter..it went something like:

LOL indeed.

Are these bugs important enough to patch? Oh yes, absolutely. Did they need a month of marketing, a logo and a name to raise awareness? Absolutely not. They could have slid into regular, automated patch updates along with all other ‘important’ patches.

It could have been a interesting story about a whole series of bugs in SAMBA, but it became a huge discussion about the Badlock clownshow. Sad.

Posted in: Exploits/Vulnerabilities, Hacking News


Latest Posts:


Malcom - Malware Communication Analyzer Malcom – Malware Communication Analyzer
Malcom is a Malware Communication Analyzer designed to analyze a system's network communication using graphical representations of network traffic.
WepAttack - WLAN 802.11 WEP Key Hacking Tool WepAttack – WLAN 802.11 WEP Key Hacking Tool
WepAttack is a WLAN open source Linux WEP key hacking tool for breaking 802.11 WEP keys using a wordlist based dictionary attack.
Eraser - Windows Secure Erase Hard Drive Wiper Eraser – Windows Secure Erase Hard Drive Wiper
Eraser is a hard drive wiper for Windows which allows you to run a secure erase and completely remove sensitive data from your hard drive by overwriting it several times with carefully selected patterns.
Insecure software versions are a problem Web Security Stats Show XSS & Outdated Software Are Major Problems
Netsparker just published some anonymized Web Security Stats about the security vulnerabilities their online solution identified on their users’ web applications and web services during the last 3 years.
CTFR - Abuse Certificate Transparency Logs For HTTPS Subdomains CTFR – Abuse Certificate Transparency Logs For HTTPS Subdomains
CTFR is a Python-based tool to Abuse Certificate Transparency Logs to get subdomains from a HTTPS website in a few seconds.
testssl.sh - Test SSL Security Including Ciphers, Protocols & Detect Flaws testssl.sh – Test SSL Security Including Ciphers, Protocols & Detect Flaws
testssl.sh is a free command line tool to test SSL security, it checks a server's service on any port for the support of TLS/SSL ciphers, protocols as well as recent cryptographic flaws and more.


One Response to BADLOCK – Are ‘Branded’ Exploits Going Too Far?

  1. Gary April 18, 2016 at 4:40 pm #

    Agree on the points made as regards Badlock, my first thoughts when reading the site set up for this exploit “brand” was that it was all hype and no trousers, but I don’t agree that Shellshock was overstated. Many more attack vectors which could leverage the Shellshock exploit exist, including some which require no MITM or user intervention: http://malwarewolf.blogspot.co.uk/2014/09/thoughts-on-dhclient-and-shellshock.html