upvote
AI is doing quite well at automating the escalation of small memory bugs (which can usually theoretically cause RCEs) into actual RCE exploits. This bug has a similar nature to php2shell.
reply
Yes, the actual post just implies possibility

> Exploiting this bug to mount an Remote Code Execution attack (RCE) can't be ruled out.

reply
Today's LLMs can often escalate to RCE, so it makes sense to assume the worst.
reply
it does not make sense to say RCE for something that does not have an open port on the system
reply
If someone opens an encrypted email that came from an attacker using GnuPG and code is executed on his machine as a result, that is still remote code execution.
reply
What is not "remote" code execution under this definition?
reply
Have you ever heard of IP over Avian Carrier? It might help expand your definition of “remote”.

In all seriousness, “remote” in this case means attacker controlled.

reply
Are you suggesting the existence of exploits outside of the definition of "attacker controlled"?

If not, and all exploits are attacker controlled, it sounds like all exploits are RCE.

EDIT I guess I have to weaken the last condition since we haven't proved all exploits are "code execution", but we have at least proved all exploits are "remote".

reply
It makes sense to assume the worst, then try to achieve it. And only if you achieve it so you tag it as such. You can't announce vulnerabilities to the world based on vibes of what it might do....

"Yeah this is a classic double free. We can't think of a way to transform it into a RCE or something like that, we've also failed at having LLMs do it so far. but in the current climate it could happen so we humbly ask the tag of most dangerous vulnerability please. Not just this disclaimer. We want 9.9 CVE that says RCE!!"

This is ridiculous.

reply
Sending somebody a signed message and trigger a double free is a prime example for RCE
reply
RCE might be possible, you still need to overlay something useful in the freed memory and bypass ASLR.
reply
The mail says "Exploiting this bug to mount an Remote Code Execution attack (RCE) can't be ruled out.". They didn't write this just for fun. gnupg usually downplays security issues.
reply
I'd say that is as accurate as they can be. Since it's a library and it's a heap bug they have no idea how a particular application will be affected.

It's still a critical bug, just would not call it a prime example of rce.

reply
I mean, the blame is moreso on the title of this HackerNews submission. "RCE can't be ruled out" is not equivalent to "RCE in Gnupg"
reply
it can't be ruled out that an RCE exists in other parts of this software either
reply
Or any software...
reply
"overlay something useful in the freed memory and bypass ASLR"

I thought we reached the point a few years ago where the assumed probability this can be done is 100% ?

reply
poc needed.
reply
IMHO, these days any kind of UB has to be considered exploitable by an LLM. The times of debating whether something is exploitable or not are over.
reply
It's interesting to see how polarizing this comment is, it's being upvoted and downvoted in waves.
reply
We are having this debate right now. So it's far from over. Without PoC it's unclear if it's RCE or just overhyped bullshit. See PHP or Nginx "RCE" which required specific crafted settings for it to even work. A video is not a "PoC".

If you believe an LLM can generate an exploit for this - feel free to post one.

reply
I agree PoC's should be a requirement for all this exploits.
reply
at the very least should be criteria for assigning "high", CVE spam is annoying enough as it is
reply
Na, for years I've been seeing crap like this "well there is no exploit" and then a year later one is found.

Quit writing memory free errors in software. Prove your software is safe, not prove that it's not exploitable.

reply
A year later you hopefully have updated the software, no loss there.
reply
It's more of a "made public" a year later, you have no idea if anyone exploited it in between.

At first I thought the whole Linux everything is a CVE was kind of annoying, but over time, especially with automated exploit finding it really has shown to be in front of what was about to happen.

reply
deleted
reply