3 ms·
That report: https://cure53.de/pentest-report_remembear.pdf https://cure53.de/pentest-report_remembear.pdf > It can be observed that since the algorithm is rem
by JetSpiegel 9y ago
That report: https://cure53.de/pentest-report_remembear.pdf https://cure53.de/pentest-report_remembear.pdf
> It can be observed that since the algorithm is removing up to two top level domains, it actually treats victim.co.uk, victim.com, victim.de and even test.victim.co.at as if they were identical
> it has been noticeable that the development
process of the RememBear suite was affected by tight deadlines. Evidencing this was
the fact that builds were generally provided only one or two days before actual testing
started, leaving little room for in-depth reconnaissance
TunnelBear's pull-quote @ https://www.remembear.com/blog/remembear-security-audit/ https://www.remembear.com/blog/remembear-security-audit/:
> we’re proud to share that no critical security issues were discovered
I'd consider putting credentials on an incorrect domain a showstopper for a password manager, but whatever.
- tptacek 9y agoIt's got to at least be in the top 3 problem-domain-specific vulnerabilities you can have in a password manager, that's at least for sure.