News for hackers. Stuff that matters.
Re:Closing a 30 pixel gap between native and web by jwcacces on Tuesday September 27, 2022 @03:51PM (#33000273)
Looks like the perfect place to fake some browser chrome and trick people...

https://www.theregister.com/2017/01/19/browser_line_of_death...

Re:Closing a 30 pixel gap between native and web by nicoburns on Tuesday September 27, 2022 @04:04PM (#33000420)
I think you'll only get access to this API if the user has explicitly installed your app as a PWA, not just when visiting it as a webpage.
Re:Closing a 30 pixel gap between native and web by gildas on Tuesday September 27, 2022 @04:12PM (#33000528)
And then a shady company offers to buy the owner's website...
Re:Closing a 30 pixel gap between native and web by tshaddox on Tuesday September 27, 2022 @04:20PM (#33000610)
That’s a real problem, of course, but it seems fairly equivalent to any native app you install that can update itself or otherwise make a network request to obtain instructions.
Re:Closing a 30 pixel gap between native and web by sneak on Wednesday September 28, 2022 @06:09AM (#33006304)
Native apps that autoselfupdate have RCE vulnerabilities by definition and should be considered remote access malware already, before the developer release keys are compromised.

I am the reason Signal desktop now has a preference to opt out of autoupdate.

Re:Closing a 30 pixel gap between native and web by hulitu on Friday September 30, 2022 @05:55AM (#33032922)
"It won't happen to me."
Re:Closing a 30 pixel gap between native and web by gildas on Tuesday September 27, 2022 @04:27PM (#33000690)
I agree with you. On the other hand, in the case of a native application, we can hope that the antivirus removes it. I hope that Microsoft has planned to update Defender accordingly.
Re:Closing a 30 pixel gap between native and web by postalrat on Tuesday September 27, 2022 @05:13PM (#33001196)
Unlike the native app you probably won't have to worry about web page encrypted your files and asking a ransom.
Re:Closing a 30 pixel gap between native and web by bentcorner on Wednesday September 28, 2022 @11:44AM (#33009311)
For now
Re:Closing a 30 pixel gap between native and web by int_19h on Tuesday September 27, 2022 @05:07PM (#33001132)
JavaScript malware has been a thing for a while now, and antiviruses have been targeting it accordingly.
Re:Closing a 30 pixel gap between native and web by gildas on Tuesday September 27, 2022 @05:36PM (#33001435)
It's not necessarily a JavaScript malware. A pure HTML page with a <form> tag could suffice to steal credentials.
Re:Closing a 30 pixel gap between native and web by jb_s on Tuesday September 27, 2022 @06:49PM (#33002136)
XSS will mean that attackers control browser UI, that's kind of bad
Re:Closing a 30 pixel gap between native and web by hulitu on Friday September 30, 2022 @05:58AM (#33032937)
Bad ? I thought that was a feature. "Want to change your browser behaviour ? Just put this CSS in user.js".
Re:Closing a 30 pixel gap between native and web by drewzero1 on Tuesday September 27, 2022 @04:12PM (#33000529)
That was my first thought as well, but I couldn't remember the name for that boundary. I hope there is a well-designed per-site control/setting/user consent system to keep tech support scam sites (or worse!) from adding one more tool to their arsenal.
Re:Closing a 30 pixel gap between native and web by fiddlerwoaroof on Tuesday September 27, 2022 @05:50PM (#33001569)
I’ve seen it called “The Line of Death”

https://textslashplain.com/2017/01/14/the-line-of-death/