CVE-2022-29913
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 · uneditedThe parent process would not properly check whether the Speech Synthesis feature is enabled, when receiving instructions from a child process. This vulnerability affects Thunderbird < 91.9.
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 confidenceIn Thunderbird versions prior to 91.9, the parent process fails to validate whether the Speech Synthesis feature is enabled when processing instructions from child processes. This allows a potentially malicious child process to bypass the user-configured Speech Synthesis setting and trigger speech output through the parent process, constituting a privilege escalation or authorization bypass vulnerability.
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.9CVSS 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.
-
Check Thunderbird versionOpen Thunderbird, go to Help > About Thunderbird (or on macOS Thunderbird > About Thunderbird) to see the installed version numberAffected if Version is below 91.9 (for example 91.8, 91.7, etc.)
-
Identify installed add-ons and extensionsGo to Tools > Add-ons and Themes (or Menu > Add-ons) and review all installed extensionsAffected if Any untrusted, unknown, or suspiciously named extensions are installed that could execute as child processes
-
Review extension permissionsClick on each extension in the Add-ons Manager and check what permissions or capabilities they have been grantedAffected if Extensions have broad permissions that could allow them to make inter-process requests to the parent process
You are affected if Thunderbird version is below 91.9 and you have installed extensions from untrusted sources that could act as malicious child processes exploiting the Speech Synthesis validation bypass.
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.9
Upgrade Thunderbird to version 91.9 or later. As a temporary workaround, ensure only trusted extensions and add-ons are installed, as they may run as child processes.
Thunderbird 91.9 or later
- 1. Open Thunderbird and go to Help > About Thunderbird to check the current version
- 2. If the version is below 91.9, download Thunderbird version 91.9 or later from the official Mozilla website (www.thunderbird.net)
- 3. Close Thunderbird completely before installing the update
- 4. Run the installer for the new version and follow the installation prompts
- 5. After installation, restart Thunderbird and verify the version in Help > About Thunderbird shows 91.9 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29913 — 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-29913 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