CVE-2022-1197
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWhen 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. This vulnerability affects Thunderbird < 91.8.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThunderbird failed to properly mark existing GPG keys as revoked when importing a new key with 'key compromise' specified as the revocation reason, leaving the old key copy in a non-revoked state.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 91.8CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Thunderbird versionOpen Thunderbird, go to Help > About Thunderbird. Verify the installed version number.Affected if Version is below 91.8 (e.g., 91.7.x or earlier)
-
Confirm GPG/OpenPGP is enabledIn Thunderbird, go to Account Settings > End-to-End Encryption. Verify if OpenPGP is configured or enabled for any account.Affected if OpenPGP support is enabled and configured for at least one account
-
Inspect GPG keyring for imported keysUse command-line gpg --list-keys to list all imported GPG keys. Look for any keys that were imported after a revocation was issued, especially with 'key compromise' as the reason.Affected if Keys with revocation certificates for compromise were imported but old non-revoked copies still exist in the keyring
-
Verify key revocation statusRun gpg --list-sigs for each key to check signatures. Compare key fingerprints before and after importing a revocation. Look for keys showing inconsistent revocation status.Affected if A key shows multiple copies with different revocation statuses, where the older copy remains marked as valid despite a revocation being imported
User is affected if Thunderbird version is below 91.8, OpenPGP encryption is enabled, and GPG keys with key compromise revocation reasons have been imported, leaving old key copies in a non-revoked state.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped91.8
Upgrade Thunderbird to version 91.8 or later to receive the fix for proper key revocation handling.
Thunderbird 91.8
- Back up any important local data (email, address books, settings) before upgrading
- Open Thunderbird
- Go to Help > About Thunderbird (or on macOS Thunderbird > About Thunderbird)
- The About dialog will check for updates automatically
- If an update is available, download and install Thunderbird 91.8 or later
- Restart Thunderbird after the update completes
- Verify the version by checking Help > About Thunderbird shows version 91.8 or higher
- Alternatively, download Thunderbird 91.8 or later directly from the official Mozilla Thunderbird website
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1197 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-1197 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data