Post reply

The message has the following error or errors that must be corrected before continuing:: Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.

Name
Email
Subject
Message icon

Other options

Return to this topic
Don't use smileys

Verification:

Please leave this box empty:

Shortcuts: ALT+S post or ALT+P preview

Topic summary

Posted by dvsdv

- August 11, 2024, 16:55:13

Quote from: indy on August 09, 2024, 21:17:59uBlock Origin natively protects against this flaw in Chrome

It will not be available in Chrome soon

Posted by A

- August 11, 2024, 15:43:15

Quote from: NikoB (B) on August 11, 2024, 14:07:12I urgently need a comment from red-eyed Linux geeks about its brilliant security...

What does this have to do with Linux? It's a browser issue, not a linux issue. unix based platforms use 0.0.0.0 as wilcard local. It isn't a bug or a security issue. Browsers should treat 0.0.0.0 as a local. And all web apps, even local ones should use CSRF

Posted by NikoB (B)

- August 11, 2024, 14:07:12

I urgently need a comment from red-eyed Linux geeks about its brilliant security...

Posted by indy

- August 09, 2024, 21:17:59

For what it's worth the extension uBlock Origin natively protects against this flaw in Chrome and Firefox.

Posted by Redaktion

- August 08, 2024, 21:28:23

The "0.0.0.0 Day" vulnerability, discovered 18 years ago, allows malicious websites to bypass security protocols in Google Chrome, Mozilla Firefox, and Apple Safari, primarily affecting Linux and macOS devices. This flaw lets attackers remotely alter settings, access protected information, and potentially execute code on affected systems. Despite its initial disclosure in 2008, the vulnerability remains unresolved, though browser developers are now taking steps to address it. Additional security measures are recommended for developers to protect their applications.

https://www.notebookcheck.net/0-0-0-0-Day-exploit-reveals-18-year-old-security-flaw-in-Chrome-Safari-and-Firefox.873472.0.html