DEF CON 19 - Artem Dinaburg - Bit-squatting: DNS Hijacking Without Exploitation
Channel:DEFCONConference · Length:45:14 · Published:2013-11-02 · Views:4004
Summary
Artem Dinaburg's DEF CON 19 talk on bit-squatting, where DRAM bit flips cause DNS requests to go to domains one bit off from the intended one. It shows how hardware faults can be exploited for hijacking without any software exploit.
Why HN recommends it
Recommended as a fun, practical talk on why bit flips matter for security, and cited in ECC memory discussions.
A really fun DefCon talk on bitsquatting. — HN, 2022
Networking & internet infrastructure · Security & hacking · Computer architecture & CPUs
Subtitles (excerpt)
uh my name is ardam dyerberg I work as a security researcher for rathon company and I'm here to talk to you about a vulnerability I discovered called bit squatting so in these slides I always like to start off with a problem and the problem is that you may be compromised even when you're following the very best web security practices so let's go into a little more detail let's pretend you're users somewhere around the world and you're browsing Facebook when you're browsing Facebook a lot of things get loaded in the background such as images JavaScript and CSS and sometimes they're not actually loaded from Facebook they're loaded from a domain that's one bit away from Facebook and Facebook isn't the only site that's vulnerable technically any site is vulnerable and the more popular a website is the more vulnerable it is but some of you may be out there thinking hey I'm running Windows 7 and you know latest Chrome so this problem isn't something I should be bothered by but you're probably wrong this slide has actual platforms that have requested resources from me instead of from the domain they originally were going to the problem is actually platform operating system and Hardware agnostic you may be
On Hacker News
A really fun DefCon talk on bitsquatting. Bitsquatting is the practice of registering domains that are one bit off from a popular one: [VIDEO] google.com vs ooogle.com >>> chr(int('0b1100111', 2)) 'g' >>> chr(int('0b1101111', 2)) 'o' If the 4th to last bit of 'g' were to flip before writing to disk, you could get persistent requests to ooogle.com Having done queries against very large datasets at… — hayst4ck, 2022-09
Regarding "some hardware errors": This might include operationg conditions you didn't consider; say: The divisor in your code went through a non-ECC DRAM module (maybe in a disk drive) that runs hotter than its specified operating temperature would allow and a random bit-flip changes your `1` into a `0`. On this topic, the talk on Bitsquatting from Artem Dinaburg during Defcon 19 is worth watchin… — btschaegg, 2018-08
Encryption and signing don't protect against memory corruption. For example, I download software from the internet then hash it. The hash matches. Before the bytes are written to disk locally, a bit flips in RAM. The corrupted data is written to disk and used. Likewise, dnssec doesn't protect you against DNS bitsquatting attacks[1] because the domain name can be changed before the DNS request is … — josephg, 2023-10
This reminds me of Bitsquatting, which is like typosquatting but uses domains one bit-flip away instead of one mistyped letter away.[0] In a small experiment, for some popular domains, the author reportedly got a lot of hits. In the associated DEFCON talk, the author notes that even if you use ECC memory, it's unlikely that the DRAM in your hard drives does too.[1] 0: [LINK] 1: [VIDEO] — jstrieb, 2021-04
The thing about ECC vs. non-ECC. If you don't have ECC, you don't know silent bit corruption is happening, and when it's finally (if it's ever) discovered, there's nothing that can be done. ECC (SECDED) keeps data safer than it would be otherwise. ECC is necessary for anything real or important based on the financial cost of losing data. For everything else, it can be optional. Plus, don't forget… — dfeojm-zlib, 2019-06
Related videos
- Scale By The Bay 2018: Bryan Cantrill, Rust and Other Interesting Things · FunctionalTV · 37:06
- 36C3 - BahnMining - Pünktlichkeit ist eine Zier - english translation · media.ccc.de · 1:01:50
- 34C3 - Dude, you broke the Future! · media.ccc.de · 57:58
- Principles for Dealing with the Changing World Order by Ray Dalio · Principles by Ray Dalio · 43:42
- Our democracy no longer represents the people. Here's how we fix it | Larry Lessig | TEDxMidAtlantic · TEDx Talks · 20:54
- Timothy Snyder: The Making of Modern Ukraine. Class 1: Ukrainian Questions Posed by Russian Invasion · YaleCourses · 46:05
- We the People, and the Republic we must reclaim | Lawrence Lessig · TED · 18:19
- LESSON 1: Do Not Obey In Advance · Timothy Snyder · 7:39
- Timothy Snyder Speaks, ep. 14: Politics of Eternity, Politics of Inevitability · Timothy Snyder · 11:25
- Fear the Boom and Bust: Keynes vs. Hayek - The Original Economics Rap Battle! · Radical Discourse · 6:18
- Fight of the Century: Keynes vs. Hayek - Economics Rap Battle Round Two · Radical Discourse · 8:42
- 8-bit computer update · Ben Eater · 6:53
- Light Years Ahead | The 1969 Apollo Guidance Computer · TNMoC · 1:21:22
- “Hello, world” from scratch on a 6502 — Part 1 · Ben Eater · 27:24
- Behind the Scenes of iOS Security · Black Hat · 51:31
- Why Electronic Voting Is Still A Bad Idea · Tom Scott · 12:00