CVE-2022-3033: XSS
If a Thunderbird user replied to a crafted HTML email containing a meta tag, with the meta tag having the http-equiv="refresh" attribute, and the content attribute specifying an URL, then Thunderbird started a network request to that URL, regardless of the configuration to block remote content. In combination with certain other HTML elements and attributes in the email, it was possible to execute JavaScript code included in the message in the context of the message compose document. The JavaScript code was able to perform actions including, but probably not limited to, read and modify the contents of the message compose document, including the quoted original message, which could potentially contain the decrypted plaintext of encrypted data in the crafted email. The contents could then be transmitted to the network, either to the URL specified in the META refresh tag, or to a different URL, as the JavaScript code could modify the URL specified in the document. This bug doesn't affect users who have changed the default Message Body display setting to 'simple html' or 'plain text'.
External References: https://www.mozilla.org/en-US/security/advisories/mfsa2022-38/#CVE-2022-3033 https://www.mozilla.org/en-US/security/advisories/mfsa2022-39/#CVE-2022-3033
Other sources
If a Thunderbird user replied to a crafted HTML email containing a <code>meta</code> tag, with the <code>meta</code> tag having the <code>http-equiv="refresh"</code> attribute, and the content attribute specifying an URL, then Thunderbird started a network request to that URL, regardless of the configuration to block remote content. In combination with certain other HTML elements and attributes in the email, it was possible to execute JavaScript code included in the message in the context of the message compose document. The JavaScript code was able to perform actions including, but probably not limited to, read and modify the contents of the message compose document, including the quoted original message, which could potentially contain the decrypted plaintext of encrypted data in the crafted email. The contents could then be transmitted to the network, either to the URL specified in the META refresh tag, or to a different URL, as the JavaScript code could modify the URL specified in the document. This bug doesn't affect users who have changed the default Message Body display setting to 'simple html' or 'plain text'. This vulnerability affects Thunderbird < 102.2.1 and Thunderbird < 91.13.1.
If a Thunderbird user replied to a crafted HTML email containing a meta tag, with the meta tag having the http-equiv="refresh" attribute, and the content attribute specifying an URL, then Thunderbird started a network request to that URL, regardless of the configuration to block remote content. In combination with certain other HTML elements and attributes in the email, it was possible to execute JavaScript code included in the message in the context of the message compose document. The JavaScript code was able to perform actions including, but probably not limited to, read and modify the contents of the message compose document, including the quoted original message, which could potentially contain the decrypted plaintext of encrypted data in the crafted email. The contents could then be transmitted to the network, either to the URL specified in the META refresh tag, or to a different URL, as the JavaScript code could modify the URL specified in the document. This bug doesn't affect users who have changed the default Message Body display setting to 'simple html' or 'plain text'.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Thunderbirdto a version that resolves this vulnerability.Fixed in 91.13.1 - Upgrade
Upgrade
debian/thunderbirdto a version that resolves this vulnerability.Fixed in 1:140.12.0esr-1~deb12u1Fixed in 1:153.6.0esr-1~deb12u2Fixed in 1:140.12.0esr-1~deb13u1Fixed in 1:153.6.0esr-1~deb13u1Fixed in 1:153.5.0esr-1Fixed in 1:153.6.0esr-1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 102.2.1 - Upgrade
Upgrade
debian/thunderbirdto a version that resolves this vulnerability.Fixed in 1:102.2.1-1 - Upgrade
Upgrade
redhat/thunderbirdto a version that resolves this vulnerability.Fixed in 91.13.1 - Upgrade
Upgrade
redhat/thunderbirdto a version that resolves this vulnerability.Fixed in 102.2.1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 91.13.1 - Upgrade
Upgrade
Thunderbirdto a version that resolves this vulnerability.Fixed in 102.2.1 - Configuration
Change the default Message Body display setting to 'simple html' or 'plain text'.
Thunderbird Message Body display = simple html or plain text
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is the vulnerability ID for this Thunderbird vulnerability?
The vulnerability ID for this Thunderbird vulnerability is CVE-2022-3033.
What is the severity rating of CVE-2022-3033?
The severity rating of CVE-2022-3033 is high (8.1).
What software is affected by CVE-2022-3033?
The software affected by CVE-2022-3033 is Mozilla Thunderbird versions 91.13.1 up to exclusive 91.13.1 and versions up to exclusive 102.2.1.
How can I fix CVE-2022-3033?
To fix CVE-2022-3033, update to Mozilla Thunderbird version 91.13.1 or version 102.2.1 or newer.
Where can I find more information about CVE-2022-3033?
You can find more information about CVE-2022-3033 in the following references: [Bugzilla](https://bugzilla.mozilla.org/show_bug.cgi?id=1784838), [Mozilla Security Advisory mfsa2022-39](https://www.mozilla.org/en-US/security/advisories/mfsa2022-39/), [Mozilla Security Advisory mfsa2022-38](https://www.mozilla.org/en-US/security/advisories/mfsa2022-38/).