From: glsamaker@gentoo.org
To: gentoo-announce@lists.gentoo.org
Subject: [gentoo-announce] [ GLSA 202208-14 ] Mozilla Thunderbird: Multiple Vulnerabilities
Date: Wed, 10 Aug 2022 04:08:59 -0000 [thread overview]
Message-ID: <166010453994.7.12828344774604420937@fa4d926cc35c> (raw)
[-- Attachment #1: Type: text/plain, Size: 10130 bytes --]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory GLSA 202208-14
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Severity: High
Title: Mozilla Thunderbird: Multiple Vulnerabilities
Date: August 10, 2022
Bugs: #794085, #802759, #807943, #811912, #813501, #822294, #828539, #831040, #833520, #834805, #845057, #846596, #849047, #857048, #864577
ID: 202208-14
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Synopsis
========
Multiple vulnerabilities have been found in Mozilla Thunderbird, the
worst of which could result in the arbitrary execution of code.
Background
==========
Mozilla Thunderbird is a popular open-source email client from the
Mozilla project.
Affected packages
=================
-------------------------------------------------------------------
Package / Vulnerable / Unaffected
-------------------------------------------------------------------
1 mail-client/thunderbird < 91.12.0 >= 91.12.0
2 mail-client/thunderbird-bin< 91.12.0 >= 91.12.0
Description
===========
Multiple vulnerabilities have been discovered in Mozilla Thunderbird.
Please review the CVE identifiers referenced below for details.
Impact
======
Please review the referenced CVE identifiers for details.
Workaround
==========
There is no known workaround at this time.
Resolution
==========
All Mozilla Thunderbird users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=mail-client/thunderbird-91.12.0"
All Mozilla Thunderbird binary users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=mail-client/thunderbird-bin-91.12.0"
References
==========
[ 1 ] CVE-2021-4129
https://nvd.nist.gov/vuln/detail/CVE-2021-4129
[ 2 ] CVE-2021-4140
https://nvd.nist.gov/vuln/detail/CVE-2021-4140
[ 3 ] CVE-2021-29967
https://nvd.nist.gov/vuln/detail/CVE-2021-29967
[ 4 ] CVE-2021-29969
https://nvd.nist.gov/vuln/detail/CVE-2021-29969
[ 5 ] CVE-2021-29970
https://nvd.nist.gov/vuln/detail/CVE-2021-29970
[ 6 ] CVE-2021-29976
https://nvd.nist.gov/vuln/detail/CVE-2021-29976
[ 7 ] CVE-2021-29980
https://nvd.nist.gov/vuln/detail/CVE-2021-29980
[ 8 ] CVE-2021-29984
https://nvd.nist.gov/vuln/detail/CVE-2021-29984
[ 9 ] CVE-2021-29985
https://nvd.nist.gov/vuln/detail/CVE-2021-29985
[ 10 ] CVE-2021-29986
https://nvd.nist.gov/vuln/detail/CVE-2021-29986
[ 11 ] CVE-2021-29988
https://nvd.nist.gov/vuln/detail/CVE-2021-29988
[ 12 ] CVE-2021-29989
https://nvd.nist.gov/vuln/detail/CVE-2021-29989
[ 13 ] CVE-2021-30547
https://nvd.nist.gov/vuln/detail/CVE-2021-30547
[ 14 ] CVE-2021-38492
https://nvd.nist.gov/vuln/detail/CVE-2021-38492
[ 15 ] CVE-2021-38493
https://nvd.nist.gov/vuln/detail/CVE-2021-38493
[ 16 ] CVE-2021-38495
https://nvd.nist.gov/vuln/detail/CVE-2021-38495
[ 17 ] CVE-2021-38503
https://nvd.nist.gov/vuln/detail/CVE-2021-38503
[ 18 ] CVE-2021-38504
https://nvd.nist.gov/vuln/detail/CVE-2021-38504
[ 19 ] CVE-2021-38506
https://nvd.nist.gov/vuln/detail/CVE-2021-38506
[ 20 ] CVE-2021-38507
https://nvd.nist.gov/vuln/detail/CVE-2021-38507
[ 21 ] CVE-2021-38508
https://nvd.nist.gov/vuln/detail/CVE-2021-38508
[ 22 ] CVE-2021-38509
https://nvd.nist.gov/vuln/detail/CVE-2021-38509
[ 23 ] CVE-2021-40529
https://nvd.nist.gov/vuln/detail/CVE-2021-40529
[ 24 ] CVE-2021-43528
https://nvd.nist.gov/vuln/detail/CVE-2021-43528
[ 25 ] CVE-2021-43529
https://nvd.nist.gov/vuln/detail/CVE-2021-43529
[ 26 ] CVE-2021-43536
https://nvd.nist.gov/vuln/detail/CVE-2021-43536
[ 27 ] CVE-2021-43537
https://nvd.nist.gov/vuln/detail/CVE-2021-43537
[ 28 ] CVE-2021-43538
https://nvd.nist.gov/vuln/detail/CVE-2021-43538
[ 29 ] CVE-2021-43539
https://nvd.nist.gov/vuln/detail/CVE-2021-43539
[ 30 ] CVE-2021-43541
https://nvd.nist.gov/vuln/detail/CVE-2021-43541
[ 31 ] CVE-2021-43542
https://nvd.nist.gov/vuln/detail/CVE-2021-43542
[ 32 ] CVE-2021-43543
https://nvd.nist.gov/vuln/detail/CVE-2021-43543
[ 33 ] CVE-2021-43545
https://nvd.nist.gov/vuln/detail/CVE-2021-43545
[ 34 ] CVE-2021-43546
https://nvd.nist.gov/vuln/detail/CVE-2021-43546
[ 35 ] CVE-2022-0566
https://nvd.nist.gov/vuln/detail/CVE-2022-0566
[ 36 ] CVE-2022-1196
https://nvd.nist.gov/vuln/detail/CVE-2022-1196
[ 37 ] CVE-2022-1197
https://nvd.nist.gov/vuln/detail/CVE-2022-1197
[ 38 ] CVE-2022-1520
https://nvd.nist.gov/vuln/detail/CVE-2022-1520
[ 39 ] CVE-2022-1529
https://nvd.nist.gov/vuln/detail/CVE-2022-1529
[ 40 ] CVE-2022-1802
https://nvd.nist.gov/vuln/detail/CVE-2022-1802
[ 41 ] CVE-2022-1834
https://nvd.nist.gov/vuln/detail/CVE-2022-1834
[ 42 ] CVE-2022-2200
https://nvd.nist.gov/vuln/detail/CVE-2022-2200
[ 43 ] CVE-2022-2226
https://nvd.nist.gov/vuln/detail/CVE-2022-2226
[ 44 ] CVE-2022-22737
https://nvd.nist.gov/vuln/detail/CVE-2022-22737
[ 45 ] CVE-2022-22738
https://nvd.nist.gov/vuln/detail/CVE-2022-22738
[ 46 ] CVE-2022-22739
https://nvd.nist.gov/vuln/detail/CVE-2022-22739
[ 47 ] CVE-2022-22740
https://nvd.nist.gov/vuln/detail/CVE-2022-22740
[ 48 ] CVE-2022-22741
https://nvd.nist.gov/vuln/detail/CVE-2022-22741
[ 49 ] CVE-2022-22742
https://nvd.nist.gov/vuln/detail/CVE-2022-22742
[ 50 ] CVE-2022-22743
https://nvd.nist.gov/vuln/detail/CVE-2022-22743
[ 51 ] CVE-2022-22745
https://nvd.nist.gov/vuln/detail/CVE-2022-22745
[ 52 ] CVE-2022-22747
https://nvd.nist.gov/vuln/detail/CVE-2022-22747
[ 53 ] CVE-2022-22748
https://nvd.nist.gov/vuln/detail/CVE-2022-22748
[ 54 ] CVE-2022-22751
https://nvd.nist.gov/vuln/detail/CVE-2022-22751
[ 55 ] CVE-2022-22754
https://nvd.nist.gov/vuln/detail/CVE-2022-22754
[ 56 ] CVE-2022-22756
https://nvd.nist.gov/vuln/detail/CVE-2022-22756
[ 57 ] CVE-2022-22759
https://nvd.nist.gov/vuln/detail/CVE-2022-22759
[ 58 ] CVE-2022-22760
https://nvd.nist.gov/vuln/detail/CVE-2022-22760
[ 59 ] CVE-2022-22761
https://nvd.nist.gov/vuln/detail/CVE-2022-22761
[ 60 ] CVE-2022-22763
https://nvd.nist.gov/vuln/detail/CVE-2022-22763
[ 61 ] CVE-2022-22764
https://nvd.nist.gov/vuln/detail/CVE-2022-22764
[ 62 ] CVE-2022-24713
https://nvd.nist.gov/vuln/detail/CVE-2022-24713
[ 63 ] CVE-2022-26381
https://nvd.nist.gov/vuln/detail/CVE-2022-26381
[ 64 ] CVE-2022-26383
https://nvd.nist.gov/vuln/detail/CVE-2022-26383
[ 65 ] CVE-2022-26384
https://nvd.nist.gov/vuln/detail/CVE-2022-26384
[ 66 ] CVE-2022-26386
https://nvd.nist.gov/vuln/detail/CVE-2022-26386
[ 67 ] CVE-2022-26387
https://nvd.nist.gov/vuln/detail/CVE-2022-26387
[ 68 ] CVE-2022-26485
https://nvd.nist.gov/vuln/detail/CVE-2022-26485
[ 69 ] CVE-2022-26486
https://nvd.nist.gov/vuln/detail/CVE-2022-26486
[ 70 ] CVE-2022-28281
https://nvd.nist.gov/vuln/detail/CVE-2022-28281
[ 71 ] CVE-2022-28282
https://nvd.nist.gov/vuln/detail/CVE-2022-28282
[ 72 ] CVE-2022-28285
https://nvd.nist.gov/vuln/detail/CVE-2022-28285
[ 73 ] CVE-2022-28286
https://nvd.nist.gov/vuln/detail/CVE-2022-28286
[ 74 ] CVE-2022-28289
https://nvd.nist.gov/vuln/detail/CVE-2022-28289
[ 75 ] CVE-2022-29909
https://nvd.nist.gov/vuln/detail/CVE-2022-29909
[ 76 ] CVE-2022-29911
https://nvd.nist.gov/vuln/detail/CVE-2022-29911
[ 77 ] CVE-2022-29912
https://nvd.nist.gov/vuln/detail/CVE-2022-29912
[ 78 ] CVE-2022-29913
https://nvd.nist.gov/vuln/detail/CVE-2022-29913
[ 79 ] CVE-2022-29914
https://nvd.nist.gov/vuln/detail/CVE-2022-29914
[ 80 ] CVE-2022-29916
https://nvd.nist.gov/vuln/detail/CVE-2022-29916
[ 81 ] CVE-2022-29917
https://nvd.nist.gov/vuln/detail/CVE-2022-29917
[ 82 ] CVE-2022-31736
https://nvd.nist.gov/vuln/detail/CVE-2022-31736
[ 83 ] CVE-2022-31737
https://nvd.nist.gov/vuln/detail/CVE-2022-31737
[ 84 ] CVE-2022-31738
https://nvd.nist.gov/vuln/detail/CVE-2022-31738
[ 85 ] CVE-2022-31740
https://nvd.nist.gov/vuln/detail/CVE-2022-31740
[ 86 ] CVE-2022-31741
https://nvd.nist.gov/vuln/detail/CVE-2022-31741
[ 87 ] CVE-2022-31742
https://nvd.nist.gov/vuln/detail/CVE-2022-31742
[ 88 ] CVE-2022-31747
https://nvd.nist.gov/vuln/detail/CVE-2022-31747
[ 89 ] CVE-2022-34468
https://nvd.nist.gov/vuln/detail/CVE-2022-34468
[ 90 ] CVE-2022-34470
https://nvd.nist.gov/vuln/detail/CVE-2022-34470
[ 91 ] CVE-2022-34472
https://nvd.nist.gov/vuln/detail/CVE-2022-34472
[ 92 ] CVE-2022-34478
https://nvd.nist.gov/vuln/detail/CVE-2022-34478
[ 93 ] CVE-2022-34479
https://nvd.nist.gov/vuln/detail/CVE-2022-34479
[ 94 ] CVE-2022-34481
https://nvd.nist.gov/vuln/detail/CVE-2022-34481
[ 95 ] CVE-2022-34484
https://nvd.nist.gov/vuln/detail/CVE-2022-34484
[ 96 ] CVE-2022-36318
https://nvd.nist.gov/vuln/detail/CVE-2022-36318
[ 97 ] CVE-2022-36319
https://nvd.nist.gov/vuln/detail/CVE-2022-36319
[ 98 ] MOZ-2021-0007
[ 99 ] MOZ-2021-0008
Availability
============
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/202208-14
Concerns?
=========
Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users' machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
https://bugs.gentoo.org.
License
=======
Copyright 2022 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).
The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.
https://creativecommons.org/licenses/by-sa/2.5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2022-08-10 4:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=166010453994.7.12828344774604420937@fa4d926cc35c \
--to=glsamaker@gentoo.org \
--cc=gentoo-announce@lists.gentoo.org \
--cc=security@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox