CVE-2023-0547
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 · uneditedOCSP revocation status of recipient certificates was not checked when sending S/Mime encrypted email, and revoked certificates would be accepted. Thunderbird versions from 68 to 102.9.1 were affected by this bug. This vulnerability affects Thunderbird < 102.10.
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 perform OCSP revocation checks on recipient certificates when sending S/MIME encrypted email, causing revoked certificates to be accepted. This allows encrypted messages to be sent to recipients whose certificates have been compromised or revoked.
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>= 68.0, < 102.10CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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.
-
Verify Thunderbird is installedCheck if Thunderbird exists on the system. On Windows: look for Thunderbird in Program Files or check the registry. On Linux: run 'which thunderbird' or check /usr/bin/thunderbird. On macOS: check /Applications/Thunderbird.appAffected if Thunderbird is not installed on the system
-
Determine installed Thunderbird versionLaunch Thunderbird and go to Help > About Thunderbird, or run 'thunderbird --version' from command lineAffected if The installed version is greater than or equal to 68.0 AND less than 102.10
-
Check if S/MIME encryption is configuredIn Thunderbird, go to Account Settings > End-to-End Encryption and verify if S/MIME is enabled for any accounts. Look for configured certificates under the Security tab of account settings.Affected if S/MIME encryption is enabled and configured for sending encrypted emails
A user is affected if Thunderbird version is between 68.0 and 102.10 (inclusive of 68.0, exclusive of 102.10) AND S/MIME encryption is used for sending encrypted messages.
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 · scoped102.10
Upgrade Thunderbird to version 102.10 or later to enable proper OCSP revocation checking for S/MIME encrypted communications.
Thunderbird 102.10 or later
- Check your current Thunderbird version by going to Help > About Thunderbird
- If the version is below 102.10, download Thunderbird 102.10 or later from the official Mozilla website (www.mozilla.org)
- Install the downloaded Thunderbird 102.10 or later version
- After installation, verify the version by checking Help > About Thunderbird to confirm you are running 102.10 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0547 — 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-2023-0547 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