AI summary by TwinMind
How "Crash Safari" Reboots Your Phone
Tom Scott
5m 18s
Web Page Crashing Fundamentals
- Crashing web pages easy: create infinite loop code
- People don't do it often: no point, can't share crashed content
- Browser evolution: smarter defenses against crashes
- Chrome: each tab separate process, isolates crashes
- Firefox: detects problems, asks to stop problematic scripts after few seconds
- Possible to bypass defenses if malicious, but results in site obscurity
CrashSafari.com Case Study
- Created by "mandatory" in April 2015
- Months of low traffic until posted to Hacker News week ago
- Went viral, picked up by tech news reporters seeking clicks
- None tracked back to original source
- One reporter called it "New Journalism"
- Also operates crashchrome.com and crashfirefox.com
Success Factors
- Clear, descriptive domain name (crashsafari.com)
- Easy to type in tweets, shareable
- iPhone-specific behavior: doesn't just crash browser, restarts entire phone
iPhone Safari Vulnerability Technical Details
- Safari has defenses: monitors memory usage, detects infinite loops
- Reloads/closes tabs when problems detected
- CrashSafari.com breaks out of browser sandbox
- Exploits area engineers didn't anticipate
Code Analysis
- Creates string variable "total" for text storage
- Loop runs 100,000 times with counter variable "i"
- Each iteration: adds current number to string as text
- String grows progressively larger each loop
- Each iteration pushes string into browser history
- History manipulation (pushState) is the exploit vector
Browser History Manipulation Background
- PushState: fairly new web page capability
- Security aspects not properly thought through
- Historical problem: single page apps (Gmail) broke back button
- Email opens on same page, back button would exit Gmail entirely
- PushState solution: tells browser "user switched within page, don't go back to previous site"
- Unlike regular web addresses: pushState entries can be unlimited length and quantity
Memory Exploitation Mechanics
- 100,000 entries sent to browser history
- Each entry progressively longer (up to ~0.5MB per entry)
- Total: approximately 25GB of history data
- iPhone RAM: only 1GB available
- System gives up instantly, recognizes critical problem, reboots to recover
Security Implications
- Should have checks for this exploit: yes
- Will next iOS version fix: maybe
- Worst case scenario: perfect conditions could allow arbitrary code execution
- Likelihood of code execution: unlikely
- Crashing phones: annoying but doesn't drive traffic to sites
- Does generate clicks for news articles/videos about exploit
