Bitwarden CLI Compromised in Ongoing Checkmarx Supply Chain Campaign

Re:Bitwarden CLI Compromised in Ongoing Checkmarx Supply Cha... by fragmede on Thursday April 23, 2026 @05:36PM (#47882394)

That simple prod example isn't where people struggle with CORS. It's during development and I've got assets on Cloudflare and AWS and GCP and localhost:3000 and localhost:8000, and localhost:3001 and then a VM in Hetner at API.example.com because why not, that shit gets complicated and people get confused and lost. I mean, yeah, don't do that, but CORS gets complicated once the project gets enough teams involved.

[ Parent | on HN ]

Re:Bitwarden CLI Compromised in Ongoing Checkmarx Supply Cha... by tcoff91 on Friday April 24, 2026 @02:55AM (#47886577)

I’ve found that the best way to deal with this is to add an entry to /etc/hosts for my local machine that fits the pattern for QA environment. Then I run a local reverse proxy with a self signed certificate.

So I do local dev on https://local.qa.yourappnamehere.com

[ Parent | on HN ]