Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

I hacked macOS

asahilina.net

Post reply on HN
Print view View original

81–90 of 140 posts

Re: I hacked macOS

#81

Post by [deleted] »

tyingq wrote: post #4

The CVE description for some context (I re-ordered the sentences) "An app may be able to execute arbitrary code with kernel privileges. The issue was addressed with improved memory handling. This issue is fixed in iOS 16.1 and iPadOS 16, macOS Ventura 13, watchOS 9.1."

[deleted]

Re: I hacked macOS

#84

Post by mmis1000 »

zamalek wrote: post #76
dagmx wrote: post #68

Earlier quoted context omitted.

You’re pretty much correct. GPUs are a very interesting attack vector. Especially as more computation is being pushed to GPUs, and they’re not always well isolated.

I'm genuinely concerned about the WebGPU attack vector. The possibilities are exciting, but we (everyone) has virtually no experience with securing them (compared to decades of securing x86 - which we still can't pull off). My biggest concern is fingerprinting.

Fingerprinting is probably inevitable if it is enabled by default. Given game code themselves relies on exact device model to workaround gpu implementation bugs. Gpu compatibility is always a shit show history that relies on all sort of device specific workarounds. You may spoof it. But don't assume it would work perfectly for any moderate to big sized programs.

Re: I hacked macOS

#85

Post by dagmx »

zamalek wrote: post #76
dagmx wrote: post #68

Earlier quoted context omitted.

You’re pretty much correct. GPUs are a very interesting attack vector. Especially as more computation is being pushed to GPUs, and they’re not always well isolated.

I'm genuinely concerned about the WebGPU attack vector. The possibilities are exciting, but we (everyone) has virtually no experience with securing them (compared to decades of securing x86 - which we still can't pull off). My biggest concern is fingerprinting.

I feel like fingerprinting is inevitable with any hardware access, including WebGL or WebGPU. It’s one of my big concerns about Chrome exposing more and more of the hardware it runs on in the goal of being a Web based OS.

That said, fingerprinting is not as big a risk as what I was thinking of, which is one process being able to peer into another’s on the GPU. There are various takes on isolation on the GPU but they tend to have strong caveats attached.

Re: I hacked macOS

#86

Post by zamadatix »

thfuran wrote: post #75
rs_rs_rs_rs_rs wrote: post #71

Earlier quoted context omitted.

>Sounds extremely low for this kind of vulnerability How do you know that?

I’m not sure I follow. You’re asking them how they know their own impression of something?

That would be a fair question, we generally don't come to our impressions by random choice alone. My guess is the value of the vulnerability on the black market would be significantly higher and Apple could afford to compete with that better if they wanted. Only the GP could tell us the reasoning for their impression though.

Re: I hacked macOS

#88

Post by phreack »

codetrotter wrote: post #44
cassianoleal wrote: post #11

Earlier quoted context omitted.

Press space.

RIP mobile users :'(

Yeah, I dislike comments on format but on mobile the site was just unusable for me. I couldn't figure out which slide was the "correct one" to move forward, and even the zooming gesture would move me to another slide. I think the video presentation would be a better link than the slides.

Re: I hacked macOS

#89

Post by jonhohle »

zamalek wrote: post #76
dagmx wrote: post #68

Earlier quoted context omitted.

You’re pretty much correct. GPUs are a very interesting attack vector. Especially as more computation is being pushed to GPUs, and they’re not always well isolated.

I'm genuinely concerned about the WebGPU attack vector. The possibilities are exciting, but we (everyone) has virtually no experience with securing them (compared to decades of securing x86 - which we still can't pull off). My biggest concern is fingerprinting.

Somehow I can’t resign myself to this brave new world of web apps with low level hardware access. I do not want web apps doing GPGPU work on my machine. If the browser engine implements high level functionality that way, fine, but I don’t want arbitrary websites using low level hardware directly.

They were so preoccupied with whether they could, the never stopped to consider whether they should.

Post reply on HN