Wasn't there some sort of shitstorm about Keeper Security a while back?
Conversation
Notices
-
Embed this notice
Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Wednesday, 12-Jun-2024 02:48:16 JST Ryan Castellucci :nonbinary_flag: -
Embed this notice
Dan Goodin (dangoodin@infosec.exchange)'s status on Wednesday, 12-Jun-2024 02:52:54 JST Dan Goodin -
Embed this notice
Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Wednesday, 12-Jun-2024 02:55:58 JST Ryan Castellucci :nonbinary_flag: @dangoodin yup, that was it, thanks.
-
Embed this notice
Sc00bz (sc00bz@infosec.exchange)'s status on Wednesday, 12-Jun-2024 04:37:51 JST Sc00bz @ryanc @dangoodin Don't forget this is a pattern. See "Vendor response" https://blog.fox-it.com/2013/04/05/security-advisory-unencrypted-storage-of-confidential-information-in-keeper-password-data-vault-v5-3-for-ios/. Also they don't like fixing things unless it's public. Timeline Jan 9-May 11 (they started getting SMTP 550 errors Feb 1) then went public May 15 https://seclists.org/fulldisclosure/2018/May/41 and "fixed" May 17 https://github.com/Keeper-Security/Commander/commit/ab0e928452bce6abaf12135814dbd5929b04ab0e
I just realized their name is "sosumi" "So sue me"... oh this is a thing https://en.wikipedia.org/wiki/Sosumi... now feel really stupid for wondering if Sosumi got sued.
-
Embed this notice