News for hackers. Stuff that matters.
Re:Amazon identifies Oct 17 PHP2Shell exploitation prior to ... by hemlock4593 on Thursday October 22, 2026 @01:06PM (#50198166)
> The security added by this proxy is strictly additive, it can't make things worse

Except if this code contains bugs that lead to another RCE.

> Well, this is why you should point Claude at the repo and ask it if it has any backdoors.

When do people understand that LLMs are no oracles. Just because some LLMs tell you the code is safe or has no backdoor doesn't mean it is true.

Re:Amazon identifies Oct 17 PHP2Shell exploitation prior to ... by 8note on Thursday October 22, 2026 @01:29PM (#50198461)
> When do people understand that LLMs are no oracles. Just because some LLMs tell you the code is safe or has no backdoor doesn't mean it is true.

if it tells me there is a backdoor, and shows me how its used, i can be pretty sure that there is one though.

if claude cant find the backdoor, chances are that claude cant find a backdoor. its still not an oracle, but that is still useful feedback for updating priors

Re:Amazon identifies Oct 17 PHP2Shell exploitation prior to ... by EGreg on Thursday October 22, 2026 @01:16PM (#50198273)
Right. But it can’t, for several reasons:

1) The proxy is open source and much simpler than PHP runtime or a web application. Its code only takes input and generates output. It is basically a pipe. It has no other capabilities to exploit.

2) The operating system, such as BSD or Linux, supports running processes under a user and enforces limits on that user. So you just jail this proxy — since it has one purpose. Unlike your application, which may do many things and you can’t restrict it, it may become a confused deputy

What this has taught me is that we should decouple as much as possible into microservices, so that we can properly sandbox each service, and that way we have chokepoints.