News for hackers. Stuff that matters.
Re:Zerotier – multiple vulnerabilities lead to private netwo... by tiernano on Monday September 20, 2021 @03:31AM (#28591143)
> Zerotier promptly addressed the root server identity verification issues. This attack is still possible (as of 20/09/2021); however, an attacker is required to invest significant compute time (many many years with a single RTX2070) to generate a valid identity that collides with an intended target. Zerotier client’s still accept any identity learned via WHOIS packet as implicitly valid.

It also says below that the main vuln is fixed... Can't now figure out if I should be worried or not...

Re:Zerotier – multiple vulnerabilities lead to private netwo... by mistaken on Monday September 20, 2021 @03:50AM (#28591250)
What worries me is that 2 months have passed since the vulnerability was fixed and yet there is no new version released which contains the patch... So you're exposed unless you build ZT from source.
Re:Zerotier – multiple vulnerabilities lead to private netwo... by api on Monday September 20, 2021 @09:45AM (#28593723)
The patch was on the roots and was applied within 6 hours of learning of the vulnerability. A new release wasn't needed since the issue was not in there.
Re:Zerotier – multiple vulnerabilities lead to private netwo... by m4lvin on Monday September 20, 2021 @07:28AM (#28592581)
If the problem is in the ZT root servers, then the clients do not need to be patched, I guess?
Re:Zerotier – multiple vulnerabilities lead to private netwo... by mistaken on Monday September 27, 2021 @08:09AM (#28669667)
A new packaged version is now available.

zerotier-one (1.6.6) unstable; urgency=medium

  * Backport endpoint mitigation against address collision attack.

 -- Adam Ierymenko <[email protected]>  Tue, 21 Sep 2021 01:00:00 -0700
Re:Zerotier – multiple vulnerabilities lead to private netwo... by andag on Monday September 20, 2021 @03:48AM (#28591237)
> This attack is still possible (as of 20/09/2021); however, an attacker is required to invest significant compute time (many many years with a single RTX2070) to generate a valid identity

So it's entirely feasible if you have access to any cloud vendor then.

Re:Zerotier – multiple vulnerabilities lead to private netwo... by Uberphallus on Monday September 20, 2021 @04:06AM (#28591356)
> So it's entirely feasible if you have access to any cloud vendor then.

At around $0.50 per hour, and assuming "many many years" means 10 years, then the attack needs to be worth those $43800.

Re:Zerotier – multiple vulnerabilities lead to private netwo... by fragmede on Monday September 20, 2021 @12:36PM (#28595678)
That's... less than I expected? Certainly more expensive that a normal person could afford, but with the levels of income disparity in the US, that's frighteningly affordable for a large corporation and within reach for highly motivated rich individual. If you own a cloud (aka Amazon wants to break into your VPN), they get major discounts on time on their fleet. If, instead, it costs $0.01/hr due to using unused capacity during quiet times of day, that's works out to be like $1000 to crack it.

As to what makes it worth it. $50k is too expensive to attack all users of this particular VPN software, but there's way more than $50k worth of information companies want to keep secret (call it competitive intelligence) being protected by VPN software the world over.

Re:Zerotier – multiple vulnerabilities lead to private netwo... by m_eiman on Monday September 20, 2021 @05:59AM (#28592001)
Many many means 512 in the article. But that's with lots of room for optimizations.
Re:Zerotier – multiple vulnerabilities lead to private netwo... by m_eiman on Monday September 20, 2021 @05:59AM (#28591996)
In addition to the compute power, you also need som other things:

"An attacker would need to hijack the address for a peer that has been offline for 30 days or communicate only with other peers that do not have a cached identity for the hijacked address."

Re:Zerotier – multiple vulnerabilities lead to private netwo... by _hyn3 on Monday September 20, 2021 @10:43AM (#28594323)
If you have access to the victim's ZeroTier dashboard (or API calls), that's trivial to get. Even if there are currently no disclosed vulns in the dashboard, that doesn't mean that none exist.
Re:Zerotier – multiple vulnerabilities lead to private netwo... by _kbh_ on Monday September 20, 2021 @04:49AM (#28591565)
unless the number of years that compute time is measured in has a lot of digits (like 3 or more) I wouldn't be comfortable. a RTX2070 isn't even the fastest card available now, let alone in the next generation or two. Compute performance for video cards is still rapidly scaling and that means that if the "many many years" isn't large enough it may not even be years soon enough.
Re:Zerotier – multiple vulnerabilities lead to private netwo... by downrightmike on Monday September 20, 2021 @11:15AM (#28594696)
I kind of wish that the metric would be X hours on MSFT or Google's largest available cluster.
Re:Zerotier – multiple vulnerabilities lead to private netwo... by Griffinsauce on Monday September 20, 2021 @04:04AM (#28591342)
> many many years with a single RTX2070

Unless they're lucky.

Re:Zerotier – multiple vulnerabilities lead to private netwo... by midasuni on Monday September 20, 2021 @08:42AM (#28593176)
If you’re lucky you can break any encryption in under a second by pulling the key from /dev/urandom. It’s a meaningless statement without defining how lucky.
Re:Zerotier – multiple vulnerabilities lead to private netwo... by fragmede on Monday September 20, 2021 @12:52PM (#28595893)
If it takes 2 years to exhaustively search the entire keyspace, you'd expect to be 50% lucky a year in, assuming the keys are evenly distributed (which is a huge assumption). If you have a lot of keys to crack and it's a feasibly short time, mean time to brute-force key recovery becomes far more interesting to you than the worst case scenario.
Re:Zerotier – multiple vulnerabilities lead to private netwo... by midasuni on Wednesday September 22, 2021 @04:06AM (#28614072)
Which is why saying “if your lucky” isn’t helpful, but quoting time to exhaust keyspace (knowing that half the time you’ll get it in half the time) is more useful