61 points bearsyankees 56 minutes ago 15 comments

bearsyankees 56 minutes ago | parent

We were (and still are) considering them as an inference provider and did a quick check first... but kudos to their team for the fast patch

vatsachak 44 minutes ago | parent

We really are entering the AI economy.

Now if only we knew if the stonks would go up or down (due to global turmoil) before I throw my savings at the SPY

dgellow 41 minutes ago | parent

Right now Trump is the wild card you have to take in account. He’s influencing the SPY way more than the AI trade

swyx 43 minutes ago | parent

> Baseten handled this well. The timeline was:

> July 13, 11:10 PM: I reported the live basetenbot token, the public Harbor project, and the repository permissions.

> July 14, morning: Baseten made the Harbor project private. I flagged that the token itself still worked.

> July 14, 4:34 PM: Anton from Baseten Security confirmed the issue as critical and said they had made the Harbor project private and rotated the token. He also asked us to securely delete the images we'd pulled.

> July 14, 5:05 PM: We confirmed deletion and sent over two lower-severity findings from the same scan.

> July 17: Baseten closed out the remaining findings.

> September: We let Baseten know we planned to disclose the finding publicly and sent them a draft of this post.

They also sent us some T-shirts and sweatshirts as a thank-you for finding this critical bug.

well done all around. i think my only open question is what default security boundaries should all vibecoded internal agents follow as a learning we can take from this

mtlynch 9 minutes ago | parent

Good in terms of prompt communication and fix. Absurdly bad in terms of reward.

Earlier in the article, it mentions that Baseten is valued at $13B. They can't dig into their couch cushions to give a few thousand dollars to the researcher privately disclosing a bug that let an attacker escalate to admin in their GitHub org?

This sends the message that honest researchers should not waste their time looking for vulnerabilities in Baseten, but it's a good target for criminals who want to monetize these vulnerabilities.

ramon156 40 minutes ago | parent

i quite liked using strix. last time i tried it, deepseek was a mess and bloated the context with nonsense. that was ~5 months ago, i wonder how it performs now

bearsyankees 18 minutes ago | parent

We've made a lot of awesome changes recently, would love any feedback on the latest version :)

sandeepkd 38 minutes ago | parent

This sounds interesting and twisted in some sense

1. A start up is validating a service provider to ensure that they are secure enough so that they can trust them before signing up for their service

2. The service provider is already trusted by so many big name companies who handed over their data, the customers data to them

Should it not be other way around?

On a different note, the finding is not just one off absolute, rather its a symptom which points to certain experience and expertise level for security practices. To be fair its hard to blame the start up folks, they are running against time and cutting corners is somewhat critical for survival for their business

bearsyankees 27 minutes ago | parent

Yeah... interesting paradigm

aatd86 29 minutes ago | parent

That is great marketing for strix, pretty bad for baseten. I don't think someone can have a better story to advertise their own security product. Did not know about strix but I am going to look it up now. Might add it to my stack.

bearsyankees 25 minutes ago | parent

Let us know if you have any feedback!

brewmarche 23 minutes ago | parent

Yeah I have seen this issue a few times. If you use Docker build arguments that way add `--provenance=false` to get rid of all that build metadata. Build secrets are still better since they allow you to scope the secret inside of the Dockerfile. Also, the metadata can be useful to inspect images.

bearsyankees 22 minutes ago | parent

Yeah honestly I wasn't too familiar with this beforehand but now have a sense of the best practices going forward