News for hackers. Stuff that matters.
Re:LastPass: Notice of Recent Security Incident by dotty- on Thursday December 22, 2022 @06:38PM (#34100468)
LastPass storing the URLs unencrypted is so mind boggling. What could possibly be the justification for that? Also -- LastPass is being intentionally unclear when they write

>stored in a proprietary binary format that contains both unencrypted data, *such as* website URLs,

What do you mean such as?? What else is unencrypted? Now is not the time for tip-toeing around this kind of stuff.

Re:LastPass: Notice of Recent Security Incident by intelVISA on Thursday December 22, 2022 @07:12PM (#34100743)
> "proprietary binary format"

weird term for std::vector<std::string>

Re:LastPass: Notice of Recent Security Incident by papito on Thursday December 22, 2022 @08:55PM (#34101483)
Savage!
Re:LastPass: Notice of Recent Security Incident by leoh on Friday December 23, 2022 @01:47AM (#34102941)
Top-tier HN comment
Re:LastPass: Notice of Recent Security Incident by nycdotnet on Thursday December 22, 2022 @09:26PM (#34101681)
This repo claims to document the vault format.

https://github.com/cfbao/lastpass-vault-parser/wiki/LastPass...

Re:LastPass: Notice of Recent Security Incident by midas on Friday December 23, 2022 @02:14AM (#34103102)
Notes field appears to be encrypted!
Re:LastPass: Notice of Recent Security Incident by r0uv3n on Friday December 23, 2022 @07:19AM (#34104993)
I created a temporary account to check whether anything of this has changed since 2018, but no, the format is still entirely the same. The fields have slightly different names, but that might be because of the way I got the vault file (looked at network responses during login). There are also four fields not listed in the above link ("Form Fields", "?", "??", and "???"), but those might be an artifact of the process of reading the file.

In particular all timestamps (creation, last modification, last access) are unencrypted, as are information about whether you want to auto-logon or auto-fill, whether the password was auto-generated and whether the password has been breached.

Re:LastPass: Notice of Recent Security Incident by bb101 on Friday December 23, 2022 @08:44AM (#34105686)
Field 6 "sharedfromaid": "aid of the sharer's Site/Secure Note" is unencrypted. The hackers will be able to infer relationships between Lastpass users.

Field 10: "genpw": "Is an auto-saved generated password". Good for deciding whether to brute force or not.

Yikes. I can't imagine why anyone would trust Lastpass after this.

Re:LastPass: Notice of Recent Security Incident by wlonkly on Friday December 23, 2022 @09:03PM (#34113084)
Last password change date is a good way to figure out if a password is in a known breach dump, too.
Re:LastPass: Notice of Recent Security Incident by Beltalowda on Thursday December 22, 2022 @10:08PM (#34101940)
> LastPass storing the URLs unencrypted is so mind boggling. What could possibly be the justification for that?

I've never used LastPass, but if the URLs would be encrypted then checking "is there a password for news.ycombinator.com?" would require unlocking the vault, right?

So then you'd at least have to enter your password once on (browser) startup so it can load the list and keep that in memory, and you won't be able to automatically sync things either.

Re:LastPass: Notice of Recent Security Incident by eks391 on Friday December 23, 2022 @03:39AM (#34103597)
> So then you'd at least have to enter your password once on (browser) startup so it can load the list and keep that in memory, and you won't be able to automatically sync things either.

Correct. However this is how it ought to be. If someone acquires my laptop, I dont want logging into my accounts to be as easy as opening the browser

Re:LastPass: Notice of Recent Security Incident by worksonmine on Friday December 23, 2022 @08:16AM (#34105429)
That's true when it's on the users device, but archived on their servers there's no need for any of the data to be unencrypted. Best case scenario it will never have to be accessed. Even encrypted with their keys would've been a better solution.

I use pass and this attack vector is why I don't sync even in a private git repo like many suggest. I do sync but only encrypted tar files, and even then some sensitve sites are aliases instead of URLs.

Sure it makes life a little more difficult but for some things convenience should be the last priority.

Re:LastPass: Notice of Recent Security Incident by slenk on Sunday December 25, 2022 @07:52PM (#34133326)
This is the default with Bitwarden