Your message dated Sat, 20 Aug 2022 08:50:20 +0000
with message-id <e1opkbq-0061pz...@fasolo.debian.org>
and subject line Bug#1017707: Removed package(s) from unstable
has caused the Debian Bug report #1004548,
regarding Security Vulnerability /_data_/…/storage/cfg/…/…/accounts
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1004548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004548
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rainloop
Version: 1.16.0+dfsg-1
Hello,
According to https://github.com/RainLoop/rainloop-webmail/issues/2134 there is
a security issue in the package:
---------
Expected behavior:
File can't be decrypted on (backup) server.
actual behavior:
File can be decrypted on (backup) server.
Steps to reproduce the problem:
When calling \RainLoop\Actions->SetAccounts()
It will store an array of values from \RainLoop\Model\Account->GetAuthToken()
Which in turn calls \RainLoop\Utils::EncodeKeyValues()
And that calls \RainLoop\Utils::EncryptString(@\serialize($aValues),
\md5(APP_SALT))
When someone/something has access to the SALT.php file,
it can decode the encrypted accounts and gain all passwords.
These days with server breaches, ransomware, other attacks and the increase of
backup behavior, the chance of being listed on "have i been pwned" has
increased and the above mentioned issue becomes a bigger vulnerability.
Solutions:
Encrypting the file based on user cookie is very unreliable and has a high
fail rate.
Encrypting with a server stored key (like the SALT.php) opens this issue
Encrypting using the main account password (the login) fails when password
is changed or when using OAUTHBEARER/XOAuth2
Only encrypting the account passwords with (3) keeps the accounts, but only
login will fail.
With (4) you could store an HMAC of the encrypted password to check if the
account login works.
Same issue applies to the 'contacts_sync' file
---------
This was reported in november 2021 and left with no public reply.
This problem is reportedly fixed in rainloop fork named Snappymail
https://snappymail.eu/
There is also another pending security issue, not yet published,
https://github.com/RainLoop/rainloop-webmail/issues/2142 also left with no
public reply.
Regards
--- End Message ---
--- Begin Message ---
Version: 1.16.0+dfsg-1+rm
Dear submitter,
as the package rainloop has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1017707
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)
--- End Message ---
