Live data from Hacker News

Bitwarden CLI compromised in ongoing Checkmarx supply chain campaign

socket.dev

61–70 of 458 posts

Re: Bitwarden CLI compromised in ongoing Checkmarx supply chain campaign

#61
post #15

Never used the CLI, but I do use their browser plugin. Would be quite a mess if that got compromised. What can I do to prevent it? Run old --tried and tested-- versions? Quite bizarre to think much much of my well-being depends on those secrets staying secret.

Use the desktop or web vault directly, don't use the browser plugin.

Re: Bitwarden CLI compromised in ongoing Checkmarx supply chain campaign

#62
post #20

KeePass users continue to live the stress free live. I've managed to avoid several security breaches in last 5 years alone by using KeePass locally on my own infra.

> KeePass users continue to live the stress free live. https://cyberpress.org/hackers-exploit-keepass-password-mana...

Happy 1password user for more than a decade.

It's only a matter of time until _they_ are also popped :(.

Re: Bitwarden CLI compromised in ongoing Checkmarx supply chain campaign

#63

Earlier quoted context omitted.

> A password manager does not need a CLI tool. Why not? Even macos keychain supports cli.

The above comment is just a bunch of generalizations not meant to address seriously that's why.

So the comparison here is that you would rather trust a password manager with a CLI that imports hundreds of third-party dependencies over a first party password manager with a CLI that comes with the OS?

I don't think macOS Keychain uses NPM and it isn't in TypeScript or Javascript and, yes it does not need a CLI either.

The NPM and Java/Typescript ecosystem is part of the problem that encourages developers to import hundreds of third-party libraries, due to its weak standard library which it takes at least ONE transitive dependency to be compromised and it is game over.

Re: Bitwarden CLI compromised in ongoing Checkmarx supply chain campaign

#64
post #43

Earlier quoted context omitted.

Integration points increase the risk of compromise. For that reason, I never use the desktop browser extensions for my password manager. When password managers were starting to become popular there was one that had security issues with the browser integration so I decided to just avoid those entirely. On iOS, I'm more comfortable with the integration so I use it, but I'm wary of it.

The problem is that the UX with a browser extension is so much better.

I also find it far easier to resist accidentally entering credentials in a phishing site... I'm pretty good about checking, but it's something I tend to point out to family and friends to triple check if it doesn't auto suggest the right site.

Re: Bitwarden CLI compromised in ongoing Checkmarx supply chain campaign

#65
post #15

Never used the CLI, but I do use their browser plugin. Would be quite a mess if that got compromised. What can I do to prevent it? Run old --tried and tested-- versions? Quite bizarre to think much much of my well-being depends on those secrets staying secret.

You should use hunter2 as your password on all services.

That password cannot be cracked because it will always display as ** for anyone else.

My password is *****. See? It shows as asterisks so it's totally safe to share. Try it!

... Scnr •́ ‿ , •̀

Re: Bitwarden CLI compromised in ongoing Checkmarx supply chain campaign

#66
post #51

https://github.com/doy/rbw is a Rust alternative to the Bitwarden CLI. Although the Rust ecosystem is moving in NPM's direction (very large and very deep dependency trees), you still need to trust far fewer authors in your dependency tree than what is common for Javascript.

This + vaultwarden is an awesome self-hostable rust version of bitwarden. We might as well close the loop!

Re: Bitwarden CLI compromised in ongoing Checkmarx supply chain campaign

#67

Earlier quoted context omitted.

The problem is that the UX with a browser extension is so much better.

I also find it far easier to resist accidentally entering credentials in a phishing site... I'm pretty good about checking, but it's something I tend to point out to family and friends to triple check if it doesn't auto suggest the right site.

Exactly. Same principle of passkeys, Yubikeys and FIDO2. Much harder to phish because the domains have to match.

Re: Bitwarden CLI compromised in ongoing Checkmarx supply chain campaign

#68
post #43

Earlier quoted context omitted.

Integration points increase the risk of compromise. For that reason, I never use the desktop browser extensions for my password manager. When password managers were starting to become popular there was one that had security issues with the browser integration so I decided to just avoid those entirely. On iOS, I'm more comfortable with the integration so I use it, but I'm wary of it.

The problem is that the UX with a browser extension is so much better.

The 1Password mobile and desktop apps have such a nice UX that I’m happy copy pasting from and into it instead of having any of the browser extensions enabled.

I have 1Password configured to require password to unlock once per 24 hours. Rest of the time I have it running in the background or unlock it with TouchID (on the MacBook Pro) or FaceID (on the iPhone).

It also helps that I don’t really sign into a ton of services all the time. Mostly I log into HN, and GitHub, and a couple of others. A lot of my usage of 1Password is also centered around other kinds of passwords, like passwords that I use to protect some SSH keys, and passwords for the disk encryption of external hard drives, etc.

Re: Bitwarden CLI compromised in ongoing Checkmarx supply chain campaign

#69
post #16

Once again, it is in the NPM ecosystem. OneCLI [0] does not save you either. Happens less with languages that have better standard libraries such as Go. If you see any package that has hundreds of libraries , that increases the risk of a supply chain attack. A password manager does not need a CLI tool. [0] https://news.ycombinator.com/item?id=47585838

> A password manager does not need a CLI tool.

That's a wild statement. The CLI is just another UI.

The problem in this case is JS and the NPM ecosystem. Go would be an improvement, but complexity is the enemy of security. Something like (pass)age is my preference for storing sensitive data.

Re: Bitwarden CLI compromised in ongoing Checkmarx supply chain campaign

#70
post #41

Earlier quoted context omitted.

Which is great for Hacker News users that can maintain their own infra. But if we're talking "stress free", that's not an answer for the average user...

The average user is reusing their password everywhere, and rotation means changing the numeral 6 at the end of the password to 7.

We should be encouraging those users to switch to a password manager.
Post reply on HN