AI summary by TwinMind
Chrome Exposes Scary System Functions To All Google Domains
Theo - t3․gg
25m 58s
Initial Concern & Discovery
- Google Chrome gives all google.com sites full access to system and tab CPU usage, GPU usage, and memory usage
- Also provides access to detailed processor information and logging back channel
- API not exposed to other sites, only to google.com domains
- Clear violation of principle that browser vendors shouldn't give preference to their websites over others
Technical Investigation & Code Analysis
- Built-in Chrome extension that cannot be disabled, doesn't show in extensions panel
- Source code available, extension ID: specific identifier for hangout service
- Permissions include: desktop capture, Enterprise Hardware platform, processes, system CPU, web RTC functionality
- Uses giant if-else statements instead of switch statements for message processing
- Manually updates tab URLs to Google domains to brute force access through iframes
- 11-year-old code with TODO comments still present
Testing & Exploitation Attempts
- Attempted to access chrome.system API from google.com console - undefined in standard browser
- Used exploit snippet to test CPU info access on Google sites
- Successfully retrieved: arm64 architecture, M2 Max processor, 12 cores, individual core usage
- Enterprise features (get Hardware platform info, event logging) returned "not allowed" or "feature disabled"
- Chrome OS/Enterprise versions have additional restricted APIs
Scope & Purpose Analysis
- Primarily designed for Google Meet (formerly Hangouts)
- Domain pattern *.google.com because Google Meet changed URLs multiple times (Hangouts → Duo → Allo → Meet)
- Doesn't work on YouTube (youtube.com not google.com)
- Historical evidence shows Google changed extension from specific Hangouts URLs to all Google domains in 2006
Video Calling Technical Requirements
- CPU info essential for video encoding quality decisions
- Encoding 1080p video requires significantly more CPU than 360p
- Most video call performance issues are CPU-related, not bandwidth-related
- GPU acceleration helpful for video encoding
- Google Meet needs this info to determine optimal video quality settings
Browser Extension Replication
- Created test extension with same permissions (minus Enterprise features)
- Successfully replicated CPU info access functionality
- Any Chrome extension can theoretically access system CPU calls
- Upcoming Pressure Observer web API will provide similar (but less detailed) information
Competitive Impact & DMA Implications
- Gives Google Meet unfair advantage over competitors like Zoom
- Zoom pushes users to install native app, has security issues (backdoor after uninstall)
- May violate Digital Markets Act (DMA) requirements
- Other browsers (Edge, Brave) also include this extension to ensure Google Meet compatibility
Tracking & Usage Patterns
- Tampermonkey script created to track all window.chrome calls
- Google Meet shows cpu.getinfo calls during video sessions
- YouTube/Twitch show 200k+ chrome API calls for media capabilities detection
- No evidence of CPU info being accessed outside Google Meet context
Privacy & Security Assessment
- CPU info reveals: processor type, core count, architecture, current usage
- Not particularly sensitive data compared to other tracking methods
- Google has history of protecting user privacy (e.g., preventing JavaScript caching-based tracking)
- No evidence of user identification tracking when signed out
- Function only called during Google Meet sessions, not on other Google properties
