First published: Tue Apr 05 2022(Updated: )
When importing a revoked key that specified key compromise as the revocation reason, Thunderbird did not update the existing copy of the key that was not yet revoked, and the existing key was kept as non-revoked. Revocation statements that used another revocation reason, or that didn't specify a revocation reason, were unaffected.
Credit: security@mozilla.org
Affected Software | Affected Version | How to fix |
---|---|---|
Mozilla Thunderbird | <91.8 | 91.8 |
<91.8 | 91.8 | |
Mozilla Thunderbird | <91.8 | |
debian/thunderbird | 1:91.12.0-1~deb10u1 1:115.3.1-1~deb10u1 1:102.13.1-1~deb11u1 1:115.3.1-1~deb11u1 1:102.15.1-1~deb12u1 1:115.3.1-1~deb12u1 1:115.3.1-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Found alongside the following vulnerabilities)
CVE-2022-1197 is a vulnerability that allows Thunderbird to keep an existing key as non-revoked when importing a revoked key with a key compromise revocation reason.
CVE-2022-1197 has a severity of medium with a CVSS score of 5.4.
CVE-2022-1197 affects Thunderbird versions up to and exclusive of 91.8 by not updating an existing non-revoked key when importing a revoked key with a key compromise revocation reason.
To fix CVE-2022-1197 in Thunderbird, update to a version higher than 91.8.
You can find more information about CVE-2022-1197 on the Mozilla website, specifically in the security advisories MFSA2022-15 and MFSA2022-15/#CVE-2022-1197.