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

First public macOS kernel memory corruption exploit on Apple M5

blog.calif.io

Post reply on HN
Print view View original

101–110 of 140 posts

Re: First public macOS kernel memory corruption exploit on Apple M5

#101

Post by marysol5 »

runlevel1 wrote: post #47
dgellow wrote: post #20

The world is so not ready for the impact of LLMs on security issues. If true, congrats to the Calif team. It’s likely too technical for me to understand in details but looking forward to reading the 55 pages report

> The world is so not ready for the impact of LLMs on security issues. I agree, but it's the people I'm worried about. I'm hearing anecdotes from all over about devs pushing LLM-generated code changes into production without retaining any knowledge of what it is they're pushing. The changes compound, their understanding of the codebase diminishes, and so the actions become risker. What's worse is a lot of this behavi…

>I'm hearing anecdotes from all over about devs pushing LLM-generated code changes into production without retaining any knowledge of what it is they're pushing. The changes compound, their understanding of the codebase diminishes, and so the actions become risker.

No anecdotes needed, it's entirely happening.

But it's also devs, being devs.

Re: First public macOS kernel memory corruption exploit on Apple M5

#102

Post by marysol5 »

Veserv wrote: post #43
nvr219 wrote: post #25

Earlier quoted context omitted.

Most companies in the world do not have “blue teams”. They barely have any kind of security employee.

That is actually unfair. Most companys spend enormous amounts on security with vast armys of security employees. Not that it is effective, but it is not for lack of resources or trying. I mean we are literally in a thread about how the 4 trillion dollar company, literally the 3rd most valuable company in the world, with a core competency in software has, yet again, released a core product riddled with security defect…

Hey now, when Apple products get a serious Kernel level vulnerability that is able to be executed just by browsing a website. It's a "jailbreak" not an "exploit".

Exploits are BAD!

Re: First public macOS kernel memory corruption exploit on Apple M5

#103

Post by marysol5 »

aiisjustanif wrote: post #50
nvr219 wrote: post #25

Earlier quoted context omitted.

Most companies in the world do not have “blue teams”. They barely have any kind of security employee.

While maybe true, it is better to back that up with data and the data I know of and read yearly is mostly not great. Between Splunk and SANS surveys of 2025 maybe ~2000 companies have a SOC. [1] [2] Then you have the many companies in the UK, US, Canada, EU that have compliance and regulatory laws that require them to exist in some capacity in house. Though that is changing with MDR services, but someone still has to…

Does the report talk about how many are /actual/ "SOC"'s, rather than some outsourced SIEM service. Or one guy who gets a daily report...

Re: First public macOS kernel memory corruption exploit on Apple M5

#105

Post by cheevly »

lugu wrote: post #81
lowdude wrote: post #79

Earlier quoted context omitted.

I would rather claim that building a theoretically secure system is prohibitively expensive. At the end of the day, Mythos et al. are just better tools for finding vulnerabilities that will eventually be available to both offensive and defensive actors. If you imagine you had a vulnerability scanner as fast and convenient as a linter, it would be much cheaper to write secure code right away. Probably not perfectly se…

I would find it funny if one day we found it irresponsable to write hand generated production code. Just like it would be irresponsable to build a significan building without running numerical simulations.

This day is probably not long off. My prediction is before the end of 2028.

Re: First public macOS kernel memory corruption exploit on Apple M5

#106

Post by plewd »

alwillis wrote: post #73
runlevel1 wrote: post #47

Earlier quoted context omitted.

> The world is so not ready for the impact of LLMs on security issues. I agree, but it's the people I'm worried about. I'm hearing anecdotes from all over about devs pushing LLM-generated code changes into production without retaining any knowledge of what it is they're pushing. The changes compound, their understanding of the codebase diminishes, and so the actions become risker. What's worse is a lot of this behavi…

> I'm hearing anecdotes from all over about devs pushing LLM-generated code changes into production without retaining any knowledge of what it is they're pushing. The changes compound, their understanding of the codebase diminishes, and so the actions become riskier. I don’t think so. An LLM can produce higher-quality documentation than most humans. If it's not already happening, when a new developer joins a team, th…

It's not just about documentation.

If stuff really goes wrong, you need people who deeply understand the codebase so that they know where to look and how to diagnose the issue. It might be the case in the future that LLMs become so powerful they'll diagnose any issue (I doubt it), but until then, we need people in the loop.

Re: First public macOS kernel memory corruption exploit on Apple M5

#107

Post by nashadelic »

jp0001 wrote: post #56

LLMs are going to produce amazing Rube Goldberg style vulnerabilities for years to come. It's already starting, this instance isn't the case, but it's happening.

hyperbolic but it might be safe to assume any local data on a connected device is going to be accessible.

Re: First public macOS kernel memory corruption exploit on Apple M5

#108

Post by fsflover »

shpx wrote: post #75
jp0001 wrote: post #56

LLMs are going to produce amazing Rube Goldberg style vulnerabilities for years to come. It's already starting, this instance isn't the case, but it's happening.

Maybe it's physically impossible to build a theoretically secure system, just as it's (presumably) impossible to have a cell that isn't susceptible to any virus. Maybe this whole time we've been getting away with a type of security by obscurity, where the obscurity is just no one having the time and focus to actually analyze the code.

It's probably impossible to achieve security through correctness, but security through compartmentalization can work. See: https://qubes-os.org.

Re: First public macOS kernel memory corruption exploit on Apple M5

#109

Post by iknowSFR »

nashadelic wrote: post #107
jp0001 wrote: post #56

LLMs are going to produce amazing Rube Goldberg style vulnerabilities for years to come. It's already starting, this instance isn't the case, but it's happening.

hyperbolic but it might be safe to assume any local data on a connected device is going to be accessible.

Genuine question as I’m far less technical than the crowd here. Has this not always been the case?

Re: First public macOS kernel memory corruption exploit on Apple M5

#110

Post by dhosek »

gorbachev wrote: post #96
Veserv wrote: post #43

Earlier quoted context omitted.

That is actually unfair. Most companys spend enormous amounts on security with vast armys of security employees. Not that it is effective, but it is not for lack of resources or trying. I mean we are literally in a thread about how the 4 trillion dollar company, literally the 3rd most valuable company in the world, with a core competency in software has, yet again, released a core product riddled with security defect…

For every Apple, there are 100 mom-and-pop companies who have nothing. Even more so in the future when a software company can be launched by a farm of AI Agents with a founder at helm with no clue about computing or security. What's debateable is how many of those companies actually need irontight security, because they are never realistically going to be targets of criminals and/or they have nothing valuable to stea…

They have a website that can be used to host malware and/or seo link farms.

I still have nightmares about the contact form on my low-stakes personal website getting hijacked to use as a spam sender (because I used unsanitized input in mail headers).

Post reply on HN