6 ms·
Security researcher found Wi-Fi vulnerabilities that existed since the beginning
- sdfhbdf 6y agoThis is the website with the actual vulnerabilities: https://www.fragattacks.com https://www.fragattacks.com
- dspillett 6y ago> the design flaws are hard to abuse because… This is good. > in practice the biggest concern are the programming mistakes in Wi-Fi products since several of them are trivial to exploit. Any indication which devices are known to be affected? None of the pages I've read so far give that information. Though it could be that this information is subject to "responsible disclosure" and won't be released until manufacturers have had a reasonable amount of time to release patches.
- walterbell 6y agoAll devices are affected, that's why there was a 9-month embargo for Linux. Some vendor devices were silently patched during that period.
- dspillett 6y agoAll devices are affected by the base flaw as that is part of the protocol as set out from the start. But if you read the article and others, particularly around the bit I quoted, it essentially states that there are extra, avoidable, flaws in specific devices (or families of devices).
- Dinux 6y agoThis particular attack seems difficult in practice. Reassembled fragments still need to yield a checksum-valid frame. With TLS becoming the norm most laptop/mobile/server communication channels will not be affected. As mentioned in the paper, the problem is indeed that MCUs have become so cheap that every $7 light bulb is equipped with WiFi. The firmware on these devices is almost never updated after production. And even on devices that are being updated, like philips hue, it's often found that WiFi chipsets run their own firmware.
- bruce343434 6y agoWhat is an MCU?
- Dinux 6y agohttps://en.m.wikipedia.org/wiki/Microcontroller https://en.m.wikipedia.org/wiki/Microcontroller
- AnotherGoodName 6y ago>Reassembled fragments still need to yield a checksum-valid frame. For a 32bit checksum changing data will give you a 1 in 4,294,967,296 chance of being correct. So just keep bit twiddling some unimportant portion of the frame until you obtain a valid checksum. 4,294,967,296 is not a large number for a modern computer. These frame checksums are only intended for accidental bit flips. They aren't protection against someone creating fake frames with valid checksums.
- est31 6y agoDupe: https://news.ycombinator.com/item?id=27121918 https://news.ycombinator.com/item?id=27121918
- dmix 6y ago95% of the internet traffic is now TLS according to Google: https://transparencyreport.google.com/https/overview?hl=en https://transparencyreport.google.com/https/overview?hl=en Most of the most severe attacks require HTTP and physical proximity. So we’re fortunate of the huge drive towards HTTPS since Snowden’s 2013 releases when it was around ~55% (I’ve seen the rise in numbers correlated before). But it also recommends upgrading your router. I wonder how many routers and IoT device companies are actually releasing firmware updates. And quality ones at that…
- BeefWellington 6y agoTLS is useful and should be the default for everything; However, it is not the protection everyone seems to assume it is for several reasons: 1. Users generally still click "Accept & Continue" when they see certificate warnings. 2. A given app can easily disable certificate validation and blindly trust the other end. For web browsers, great they do it well. Other applications often disable certificate validation altogether. Plenty of mobile apps I've seen fail to do proper certificate validation, though thankfully it is becoming less common thanks to vendor platforms removing the option to be horribly insecure. 3. An attacker can still see which domain names and/or hostnames you're accessing. The simplest useful thing I could think of with this might be is finding a given WiFi network's IP on the Internet, in those circumstances where the hardware permits you to create your own frames.
- tialaramex 6y ago> 1. Users generally still click "Accept & Continue" when they see certificate warnings. In Firefox HSTS blocks this entirely. There is no "Accept" option at all. In Chrome HSTS means the only way to "accept and continue" is to type whatever the current magic bypass phrase is, the ordinary "accept and continue" option isn't there.
- grishka 6y agoAnd even without HSTS, most web browsers bury the option to continue deep enough that for most users it could as well not exist. In Chrome you have to click "details" and there will be a tiny link to "continue anyway".
- kordlessagain 6y agoIs this caused by me building my own auth system?