upvote

points

by ctolsen16 hours ago |
comments
upvoteby no-name-here16 hours ago|
[-]
>>>> a sandbox that a half skilled human operator could have broken out of easily

>>> Are "half skilled human operators" "easily" able to find zero-day vulnerabilities in a sandbox

>> Calling it zero day makes it sound elusive ... like 40 CVEs this year alone.

> [The CVEs] came from openai or anthropic research? In fact, every CVE in the last 2 years came from the last few months

I still don't understand how you can specifically point to zero CVEs being discovered by humans for year(s), then ~40 being discovered once OpenAI/Anthropic start looking at it, as the only(?) piece of data you provided to support the claim "a half skilled human" could have "easily" found/done this?

reply
upvoteby RadiozRadioz16 hours ago|
parent|
next
[-]
Well, yes. You don't find something if you don't look. The LLMs did the looking before the humans did, so they found the vulnerabilities.

It's definitely worthwhile to point out that LLMs have changed the economics of looking; we can now look in far more places far more quickly than we could before. But the above points were that the vulnerability itself happened to be an easy one that didn't intrinsically require an LLM.

reply
upvoteby aswegs816 hours ago|
parent|
[-]
Isn't the issue here that they used something like Artifactory for this purpose in the first place? It is not intended as a robust and secure packet manager for sandboxes. Why would any human look for vulnerabilities in Artifactory at all? So the scenario never arose where a human was incentivizied to scrutinize Artifactory, something that was never needed because it was never intended for the purpose of being a packet manager in a secure sandbox.

Means the problem lies elsewhere: deciding to use it at all. That points again towards the lack of basic SysAdmin skills.

reply
upvoteby ctolsen15 hours ago|
parent|
next
[-]
Right, that’s basically what I’m saying. There’s not zero use for an attack like this, but it’s not a likely situation.

Said another way: if Artifactory was somehow a common gatekeeper between grounded techy teenagers and their access to internet porn, this would have been found ages ago.

reply
upvoteby no-name-here15 hours ago|
parent|
prev|
[-]
> the lack of basic SysAdmin skills

If we exclude those who lack "basic" level skills, what solution would most typically be used by someone who has "basic" level skills for this use case? And what solution for someone with "expert" (or medium) level skills?

reply
upvoteby ctolsen15 hours ago|
parent|
next
[-]
Don’t let software inside the sandbox access the internet on request. Have a package repository with approved software the agents might want, and push to it over a channel that is ingress only. I can imagine ways of breaking out of this, and come up with a lot more to mitigate, but this would be fairly basic stuff that’d be vastly superior.
reply
upvoteby no-name-here15 hours ago|
parent|
[-]
> ingress only

The issue we're discussing happened while running ExploitGym. Doesn't the ExploitGym arXiv test explicitly have external "outbound" network requests as allowed for package installation and supporting toolchain installation?

reply
upvoteby ctolsen15 hours ago|
parent|
[-]
Part of the toolchain had full internet access. Agents had access to Artifactory, Artifactory could do whatever it wanted. So even locking that down to certain external sites would have stopped this particular attack.
reply
upvoteby imtringued15 hours ago|
parent|
prev|
[-]
Well the most obvious thing would be to gate access to artifactory behind tools. E.g. apt get install is a tool and only the tool gets access to artifactory.
reply
upvoteby vmg122 hours ago|
parent|
prev|
next
[-]
Nobody sane was relying on artifactory for this kind of adversarial workload
reply
upvoteby ctolsen16 hours ago|
parent|
prev|
next
[-]
Why would it be getting attention? There’s an enormous amount of garbage software out there, and not an endless supply of researchers. Especially tooling like this, used internally where it’s assumed that security is the job of something else. It’s far from the first time serious but simple vulnerabilities have gone unnoticed for a long time. And the use case of having this be your way to the internet is probably rare, so nobody has tried very hard (or tried but never told anyone).

I’ve looked at the CVEs a bit more and it’s just very clearly a pattern of systemic issues with validation, be it URLs or tokens.

It just shouldn’t be that hard to believe that OpenAI just didn’t care very much and thus did a crap job. The whole model of the sandbox is terrible, so why would they bother thinking about the implementation much?

reply
upvoteby Groxx5 hours ago|
parent|
[-]
The amount of garbage has also dramatically increased lately, spending a lot of that attention in places other than a normally-not-attacked-at-all entirely internal system.

It really isn't a high profile target, lots of fairly obvious issues is to be expected. Which is not at all a good thing, but very obviously the status quo for large software.

reply
upvoteby scotty7911 hours ago|
parent|
prev|
next
[-]
The key is motivation. It's a lame package proxy. No human was motivated to use it to access the Internet.
reply
upvoteby 16 hours ago|
parent|
prev|
next
[-]
deleted
reply
upvoteby imtringued15 hours ago|
parent|
prev|
[-]
What's the point in hacking the internal corporate artifactory instance? You'll get fired if you mess around with it.

Not to mention the only thing the artifactory instance got you was indirect internet access which is irrelevant if the artifactory instance is publicly exposed.

Also it might not be obvious but artifactory is proprietary software that used to be open source, so nobody is looking at the code anymore.

reply