What Just Happened? Part 2

The last two weeks of October were a wild ride in the world of Cybersecurity. We covered the week of the 19th last week, lets take a look at what happened in the last week of October

11/9/20264 min read

Tim asking the hard questions
Tim asking the hard questions

And we're back! The hits didn't stop coming! We're taking a look at what happened in the last week of October, Cybersecurity awareness month, and boy are we well aware of this now. For a quick recap of the week prior, we saw four major RCE vulnerabilities blow up and TLS certs protected with the number 4. Any of these on their own would have been a big deal, but all in one week was... something else.

With the Node2Shell changing into HTTP2Shell over the weekend, patching was in the works across the world for anything running the Brotili library as well as people continuing to patch PHP. Monday morning had extremely detailed reports of exploits in the wild for PHP2Shell hitting honeypots. So if people didn't already have a fire under their asses, they should have by now. Wednesday would see confirmation of HTTP2Shell being exploited in the wild as well.

Where the week before we saw things happen everyday, we're a bit more concentrated the week of the 26th. Would this have been the case if people weren't heads down working to mitigate and remediate the issues of the week before, not sure, but there was already such a tension going into the week that I think a few days of news was better than constant news. That being said, Tuesday saw major five vulnerabilities in the Tailscale platform. Tailscale is a VPN/Zero Trust company built off the Wireguard protocol. It's popular in the prosumer space with plenty of people I know using it. The worst was an SSH vulnerability that would allow a device in the network to get root RCE on a host. It is important to know that most of these vulnerabilities required network access already, so no one was breaking into your tailnet, but still dangerous. Check the BleepingComputer writeup here.

Tuesday also saw the release of a vuln in TianoCore EDK II, an open source codebase as Ars Technica describes it, that is UEFI creation. If you send a specially crafted ICMP packet during a system's PXE boot sequence, you can get code in under the TPM for execution. And this code is in most servers, sounds pretty scary right? I think this one is more of a great fear piece than an actual threat. If an attacker has the ability to send a ping to a device at the right moment during start-up, they're already pretty deep in your network. In my personal designs of subnets, you're not sending ICMP traffic across subnets or vlans aside from testing windows. And if someone knows the device is rebooting, or has made it reboot, they pretty much control your network. And you should be having monitoring software sending out alarms about devices rebooting without a scheduled window. So this one is really a threat if your network is already owned and your completely unaware of it.

Thursday rolls in and while it doesn't bring huge vulnerabilities, it does bring huge news. Polymarket suspends trading after attackers get in via a third-party service, distribute wallet draining software and make off with $2.5 million. No word on attribution yet, but Polymarket has said they will restore people's funds. Estimates are about 700 wallets were impacted by this. I wonder if they were taking odds on this happening? Check out the report from Hudson Rock on the whole thing.

Now is when Binance steps up and says "Hold my beer" and $6.3 billion slips out to North Korean actors in 20 minutes. This is why I waited a bit longer to write up, so we could get more details on what happened. The NK group known as TraderTraitor, which split out of the Lazarus Group. If you've been in the field for a while, you know Lazarus Group and that they're some of the most dangerous actors out there. The reporting has come out that a Binance employee fell for a fake job interview, used their Binance laptop for it and executed malicious code as part of a coding test. The belief is TraderTraitor had been in Binance's systems for months, conducting recon and establishing access throughout the network. Binance, like Polymarket, has said they will absorb the loss themselves and compensate everyone who lost funds. Here is the initial write-up from TRM Labs on the hack.

This is your reminder that cryptocurrency isn't real money, isn't protected like real money, and these companies could have just left people out high and dry. I am glad they didn't, but they're also not going to face any of the consequences that would face a bank if they had lost this much money. TraitorTrader has taken close to $8 billion in cryto in the last two years. Banks have not lost anywhere close to that amount of money. And honestly, this does nothing to fight my perception of crypto as enabling web crimes. Because the money NK has now is useless if people won't do business with them, but someone will tumble the crypto, take a cut, and help mixup the wallets so they're not associated with this hack any more and they can use it.

So that was the end of October. And what crazy ride it was. Things have slowed down, but not by much. More freezer systems in Europe were set to defrost and ruined millions of Euros of food. Sshole vuln came out for musl linux variants letting anyone login using a password greater than 256 characters. And this morning N-able took their N-central cloud offline after public disclosure of 33 vulns with PoC exploits. I don't have much advice to give to those of you out there other than keep an eye on the news, make sure you are monitoring your logs and not just gathering them, and buy your IT team that's patching all these issues a drink, and if possible with mitigations, time to fix it.