Today, TeamViewer, a large remote access and control software provider, has confirmed a data breach by the notorious hacker group Midnight Blizzard. The company’s statement confirmed the breach is tied to an employee’s credentials within its Corporate IT environment. Bleeping Computer has more details:
While TeamViewer states there is no evidence that its product environment or customer data has been breached, its massive use in both consumer and corporate environments makes any breach a significant concern as it would provide full access to internal networks.
In 2019, TeamViewer confirmed a 2016 breach linked to Chinese threat actors due to their use of the Winnti backdoor. The company said they did not disclose the breach at the time as data was not stolen in the attack.
Glenn Chisolm, Co-Founder, Obsidian had this to say:
“Identity compromise, which has been a driver in the TeamViewer incident, is a critical component of most breaches we see in customer environments, accounting for over 80% of SaaS breaches. We see TeamViewer deployed by 1-in-3 organizations – so ensuring that the breach is contained is the first big step for the company.
Our advice to customers to minimize identity compromises is to follow 3 crucial steps – a) centralize identity access behind an IdP — often many apps also have local users, and ensuring the right levels of security is much harder in a distributed setting, b) federated access supported with the right levels of MFA to elevate the security, and c) monitor and protect employee accounts, especially administrative accounts, against abnormal behavior — such as can result from spear phishing attacks, AiTM phishing, and more.”
TeamViewer is something that I have been strongly recommending against since their 2016 hack that they only admitted to three years later. This reinforces the fact that if you use TeamViewer, you should strongly consider using another product. Because TeamViewer clearly cannot be trusted.



Dump Your D-Link DIR-859 Router In The Trash Because Hackers Are Exploiting It To Pwn You
Posted in Commentary with tags D-Link on June 30, 2024 by itnerdSo let me start with the exploit behind the title in this story. D-Link has released a security advisory which is tied to CVE-2024-0769 that goes like this:
** UNSUPPORTED WHEN ASSIGNED ** A vulnerability was found in D-Link DIR-859 1.06B01. It has been rated as critical. Affected by this issue is some unknown functionality of the file /hedwig.cgi of the component HTTP POST Request Handler. The manipulation of the argument service with the input ../../../../htdocs/webinc/getcfg/DHCPS6.BRIDGE-1.xml leads to path traversal. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. VDB-251666 is the identifier assigned to this vulnerability. NOTE: This vulnerability only affects products that are no longer supported by the maintainer. NOTE: Vendor was contacted early and confirmed immediately that the product is end-of-life. It should be retired and replaced.
So let’s unpack this. In English, what this is saying is that an attack that can be launched remotely exists that allows attackers to leak session data, achieve privilege escalation, and gain full control via the admin panel. In short, they can take over the router. And presumably use that access to launch secondary attacks. Like theft of data for example via reconfiguring the router to let them have full access to your network. On top of that you’ll note this part:
NOTE: This vulnerability only affects products that are no longer supported by the maintainer. NOTE: Vendor was contacted early and confirmed immediately that the product is end-of-life. It should be retired and replaced.
So this isn’t going to get fixed. Which means that if you have one of these routers, your best course of action is to throw it in the trash (or responsibly recycle it) and get something else. I say that because the word on the street is that threat actors are actively using this exploit to pwn people. Thus you don’t want to be the person on the other end of that.
Leave a comment »