The bug has been referenced in the following commit(s):
Author: Thomas Deutschmann <firstname.lastname@example.org>
AuthorDate: 2020-02-21 16:51:14 +0000
Commit: Thomas Deutschmann <email@example.com>
CommitDate: 2020-02-21 16:55:20 +0000
mail-client/thunderbird: amd64 & x86 stable
Package-Manager: Portage-2.3.89, Repoman-2.3.20
Signed-off-by: Thomas Deutschmann <firstname.lastname@example.org>
mail-client/thunderbird/thunderbird-68.5.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Repository is clean.
Arches and Maintainer(s), Thank you for your work.
CVE-2020-6792: Message ID calculcation was based on uninitialized data
When deriving an identifier for an email message, uninitialized memory was used in addition to the message contents.
CVE-2020-6793: Out-of-bounds read when processing certain email messages
When processing an email message with an ill-formed envelope, Thunderbird could read data from a random memory location.
CVE-2020-6794: Setting a master password post-Thunderbird 52 does not delete unencrypted previously stored passwords
If a user saved passwords before Thunderbird 60 and then later set a master password, an unencrypted copy of these passwords is still accessible. This is because the older stored password file was not deleted when the data was copied to a new format starting in Thunderbird 60. The new master password is added only on the new file. This could allow the exposure of stored password data outside of user expectations.
CVE-2020-6795: Crash processing S/MIME messages with multiple signatures
When processing a message that contains multiple S/MIME signatures, a bug in the MIME processing code caused a null pointer dereference, leading to an unexploitable crash.
In general, this flaw cannot be exploited through email in the Thunderbird product because scripting is disabled when reading mail, but is potentially a risk in browser or browser-like contexts.
CVE-2020-6800: Memory safety bugs fixed in Thunderbird 68.5
Mozilla developers and community members Raul Gurzau, Tyson Smith, Bob Clary, Liz Henry, and Christian Holler reported memory safety bugs present in Firefox 72 and Firefox ESR 68.4. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code.
In general, these flaws cannot be exploited through email in the Thunderbird product because scripting is disabled when reading mail, but are potentially risks in browser or browser-like contexts.
This issue was resolved and addressed in
GLSA 202003-10 at https://security.gentoo.org/glsa/202003-10
by GLSA coordinator Thomas Deutschmann (whissi).