The latest Chrome version, 142, released by Google on October 28th, includes patches to fix several documented vulnerabilities, some of which are high-severity. The update includes permission to block local network access from public/local websites. Chrome now blocks websites from sending requests to local network devices (like routers, printers, or software running on your machine) unless you explicitly grant permission. When a website tries to access your local network, it will ask you if it can “look for and connect to any device on your local network”. You can allow or deny. If you deny, the websites will not be able to connect to your local network.
Why do websites need access to local networks?
Smart home applications like Google Home require access to smart devices in your home, while streaming devices need to interact with smart TVs and speakers. Additionally, printing from websites necessitates communication with printers. However, granting access to your local network poses security risks, as malicious websites can potentially access, track, and exploit your devices.
1. What is Local Network Access?
Local Network Access (LNA) allows websites to communicate with devices on your home or office network (e.g., printers, smart TVs, routers). Chrome 142 now asks for permission before granting this access.
2. Why Does Chrome Ask for Permission?
- Security: Prevents malicious sites from probing your network or exploiting vulnerable devices.
- Privacy: Stops websites from fingerprinting your network setup.
3. When Should You Allow Access?
Allow only if:
- You trust the website (official vendor or service you use regularly).
- You understand why it needs access, such as:
- Smart home control (e.g., Philips Hue, Google Home).
- Media streaming (e.g., Plex, Spotify Connect).
- Enterprise tools (e.g., Box, Teams for printer integration).
- Local development/testing (e.g., Selenium, TestCafe).
4. When Should You Block Access?
Block if:
- The site is unknown or suspicious.
- You are not using any local device integration.
- The request seems unnecessary (e.g., a shopping site asking for local access).
5. How to Manage Permissions
- Check Current Settings:
- Go to chrome://settings/content/localNetworkAccess.
- Add Trusted Sites:
- Under Allowed, add domains you trust.
- Remove Sites:
- Delete any site you do not recognise.
6. Tips for Safe Usage
- Always use HTTPS when granting access.
- Avoid granting access on public Wi-Fi.
- Review permissions periodically.
To brief things , Chrome version 142, addresses over 20 security vulnerabilities, including 7 high-severity issues. Notably, Google awarded over $100,000 in bug bounties for two critical flaws in the V8 JavaScript engine.
To stay protected and reduce the risk of exploitation:
Update Chrome to the latest version immediately
Restart your browser after updating.
The Lazy Networker 
Leave a comment