gsd-2022-3033
Vulnerability from gsd
Modified
2023-12-13 01:19
Details
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.
Aliases
Aliases
{
"GSD": {
"alias": "CVE-2022-3033",
"id": "GSD-2022-3033",
"references": [
"https://access.redhat.com/errata/RHSA-2022:6708",
"https://access.redhat.com/errata/RHSA-2022:6710",
"https://access.redhat.com/errata/RHSA-2022:6713",
"https://access.redhat.com/errata/RHSA-2022:6715",
"https://access.redhat.com/errata/RHSA-2022:6716",
"https://access.redhat.com/errata/RHSA-2022:6717",
"https://ubuntu.com/security/CVE-2022-3033"
]
},
"gsd": {
"affected": [
{
"package": {
"ecosystem": "Mozilla",
"name": "Thunderbird"
},
"ranges": [
{
"events": [
{
"fixed": "91.13.1"
},
{
"introduced": "0"
},
{
"fixed": "102.2.1"
},
{
"introduced": "0"
}
],
"type": "SEMVER"
}
],
"version": []
}
],
"alias": [
"CVE-2022-3033"
],
"database_specific": {
"GSD": {
"alias": "CVE-2022-3033",
"id": "GSD-2022-3033",
"references": [
"https://www.suse.com/security/cve/CVE-2022-3033.html"
]
}
},
"details": "If a Thunderbird user replied to a crafted HTML email containing a \u003ccode\u003emeta\u003c/code\u003e tag, with the \u003ccode\u003emeta\u003c/code\u003e tag\nhaving the \u003ccode\u003ehttp-equiv=\"refresh\"\u003c/code\u003e attribute, and the content attribute specifying an URL, then\nThunderbird started a network request to that URL, regardless of the configuration to block\nremote content. In combination with certain other HTML elements and attributes in the email,\nit was possible to execute JavaScript code included in the message in the context of the\nmessage compose document. \nThe JavaScript code was able to perform actions including, but probably not limited\nto, read and modify the contents of the message compose document, including the quoted\noriginal message, which could potentially contain the decrypted plaintext of encrypted data \nin the crafted email.\nThe contents could then be transmitted to the network, either to the URL specified in the META refresh tag,\nor to a different URL, as the JavaScript code could modify the URL specified in the document.\nThis bug doesn\u0027t affect users who have changed the default Message Body display setting to\n\u0027simple html\u0027 or \u0027plain text\u0027. This vulnerability affects Thunderbird \u003c 91.13.1 and Thunderbird \u003c 102.2.1.",
"id": "GSD-2022-3033",
"metadata": {
"exploitCode": "unknown",
"remediation": "unknown",
"reportConfidence": "confirmed",
"type": "vulnerability"
},
"modified": "2022-09-27T16:35:18.123266Z",
"osvSchema": {
"aliases": [
"CVE-2022-3033"
],
"details": "If a Thunderbird user replied to a crafted HTML email containing a \u003ccode\u003emeta\u003c/code\u003e tag, with the \u003ccode\u003emeta\u003c/code\u003e tag having the \u003ccode\u003ehttp-equiv=\"refresh\"\u003c/code\u003e 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\u0027t affect users who have changed the default Message Body display setting to \u0027simple html\u0027 or \u0027plain text\u0027. This vulnerability affects Thunderbird \u003c 102.2.1 and Thunderbird \u003c 91.13.1.",
"id": "GSD-2022-3033",
"modified": "2023-12-13T01:19:40.424962Z",
"schema_version": "1.4.0"
},
"references": [
{
"type": "ADVISORY",
"url": "https://www.mozilla.org/security/advisories/mfsa2022-39/"
},
{
"type": "ADVISORY",
"url": "https://www.mozilla.org/security/advisories/mfsa2022-38/"
},
{
"type": "ADVISORY",
"url": "https://bugzilla.mozilla.org/show_bug.cgi?id=1784838"
},
{
"type": "ADVISORY",
"url": "https://www.suse.com/security/cve/CVE-2022-3033.html"
}
],
"schema_version": "1.3.0",
"summary": "If a Thunderbird user replied to a crafted HTML email containing a \u003ccode\u003emeta\u003c/code\u003e tag, with the \u003ccode\u003emeta\u003c/code\u003e tag\nhaving the \u003ccode\u003ehttp-equiv=\"refresh\"\u003c/code\u003e attribute, and the content attribute specifying an URL, then\nThunderbird started a network request to that URL, regardless of the configuration to block\nremote content. In combination with certain other HTML elements and attributes in the email,\nit was possible to execute JavaScript code included in the message in the context of the\nmessage compose document. \nThe JavaScript code was able to perform actions including, but probably not limited\nto, read and modify the contents of the message compose document, including the quoted\noriginal message, which could potentially contain the decrypted plaintext of encrypted data \nin the crafted email.\nThe contents could then be transmitted to the network, either to the URL specified in the META refresh tag,\nor to a different URL, as the JavaScript code could modify the URL specified in the document.\nThis bug doesn\u0027t affect users who have changed the default Message Body display setting to\n\u0027simple html\u0027 or \u0027plain text\u0027. This vulnerability affects Thunderbird \u003c 91.13.1 and Thunderbird \u003c 102.2.1."
},
"namespaces": {
"cve.org": {
"CVE_data_meta": {
"ASSIGNER": "security@mozilla.org",
"ID": "CVE-2022-3033",
"STATE": "PUBLIC"
},
"affects": {
"vendor": {
"vendor_data": [
{
"product": {
"product_data": [
{
"product_name": "Thunderbird",
"version": {
"version_data": [
{
"version_affected": "\u003c",
"version_value": "102.2.1"
},
{
"version_affected": "\u003c",
"version_value": "91.13.1"
}
]
}
}
]
},
"vendor_name": "Mozilla"
}
]
}
},
"data_format": "MITRE",
"data_type": "CVE",
"data_version": "4.0",
"description": {
"description_data": [
{
"lang": "eng",
"value": "If a Thunderbird user replied to a crafted HTML email containing a \u003ccode\u003emeta\u003c/code\u003e tag, with the \u003ccode\u003emeta\u003c/code\u003e tag having the \u003ccode\u003ehttp-equiv=\"refresh\"\u003c/code\u003e 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\u0027t affect users who have changed the default Message Body display setting to \u0027simple html\u0027 or \u0027plain text\u0027. This vulnerability affects Thunderbird \u003c 102.2.1 and Thunderbird \u003c 91.13.1."
}
]
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"lang": "eng",
"value": "Leaking of sensitive information when composing a response to an HTML email with a META refresh tag"
}
]
}
]
},
"references": {
"reference_data": [
{
"name": "https://www.mozilla.org/security/advisories/mfsa2022-38/",
"refsource": "MISC",
"url": "https://www.mozilla.org/security/advisories/mfsa2022-38/"
},
{
"name": "https://www.mozilla.org/security/advisories/mfsa2022-39/",
"refsource": "MISC",
"url": "https://www.mozilla.org/security/advisories/mfsa2022-39/"
},
{
"name": "https://bugzilla.mozilla.org/show_bug.cgi?id=1784838",
"refsource": "MISC",
"url": "https://bugzilla.mozilla.org/show_bug.cgi?id=1784838"
}
]
}
},
"mozilla.org": {
"CVE_data_meta": {
"ASSIGNER": "security@mozilla.org",
"ID": "CVE-2022-3033"
},
"affects": {
"vendor": {
"vendor_data": [
{
"product": {
"product_data": [
{
"product_name": "Thunderbird",
"version": {
"version_data": [
{
"version_affected": "\u003c",
"version_value": "91.13.1"
},
{
"version_affected": "\u003c",
"version_value": "102.2.1"
}
]
}
}
]
},
"vendor_name": "Mozilla"
}
]
}
},
"data_format": "MITRE",
"data_type": "CVE",
"data_version": "4.0",
"description": {
"description_data": [
{
"lang": "eng",
"value": "If a Thunderbird user replied to a crafted HTML email containing a \u003ccode\u003emeta\u003c/code\u003e tag, with the \u003ccode\u003emeta\u003c/code\u003e tag\nhaving the \u003ccode\u003ehttp-equiv=\"refresh\"\u003c/code\u003e attribute, and the content attribute specifying an URL, then\nThunderbird started a network request to that URL, regardless of the configuration to block\nremote content. In combination with certain other HTML elements and attributes in the email,\nit was possible to execute JavaScript code included in the message in the context of the\nmessage compose document. \nThe JavaScript code was able to perform actions including, but probably not limited\nto, read and modify the contents of the message compose document, including the quoted\noriginal message, which could potentially contain the decrypted plaintext of encrypted data \nin the crafted email.\nThe contents could then be transmitted to the network, either to the URL specified in the META refresh tag,\nor to a different URL, as the JavaScript code could modify the URL specified in the document.\nThis bug doesn\u0027t affect users who have changed the default Message Body display setting to\n\u0027simple html\u0027 or \u0027plain text\u0027. This vulnerability affects Thunderbird \u003c 91.13.1 and Thunderbird \u003c 102.2.1."
}
]
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"lang": "eng",
"value": "Leaking of sensitive information when composing a response to an HTML email with a META refresh tag"
}
]
}
]
},
"references": {
"reference_data": [
{
"url": "https://www.mozilla.org/security/advisories/mfsa2022-39/"
},
{
"url": "https://www.mozilla.org/security/advisories/mfsa2022-38/"
},
{
"url": "https://bugzilla.mozilla.org/show_bug.cgi?id=1784838"
}
]
}
},
"nvd.nist.gov": {
"configurations": {
"CVE_data_version": "4.0",
"nodes": [
{
"children": [],
"cpe_match": [
{
"cpe23Uri": "cpe:2.3:a:mozilla:thunderbird:*:*:*:*:*:*:*:*",
"cpe_name": [],
"versionEndExcluding": "102.2.1",
"versionStartIncluding": "102.0",
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:mozilla:thunderbird:*:*:*:*:*:*:*:*",
"cpe_name": [],
"versionEndExcluding": "91.13.1",
"vulnerable": true
}
],
"operator": "OR"
}
]
},
"cve": {
"CVE_data_meta": {
"ASSIGNER": "security@mozilla.org",
"ID": "CVE-2022-3033"
},
"data_format": "MITRE",
"data_type": "CVE",
"data_version": "4.0",
"description": {
"description_data": [
{
"lang": "en",
"value": "If a Thunderbird user replied to a crafted HTML email containing a \u003ccode\u003emeta\u003c/code\u003e tag, with the \u003ccode\u003emeta\u003c/code\u003e tag having the \u003ccode\u003ehttp-equiv=\"refresh\"\u003c/code\u003e 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\u0027t affect users who have changed the default Message Body display setting to \u0027simple html\u0027 or \u0027plain text\u0027. This vulnerability affects Thunderbird \u003c 102.2.1 and Thunderbird \u003c 91.13.1."
}
]
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"lang": "en",
"value": "CWE-94"
}
]
}
]
},
"references": {
"reference_data": [
{
"name": "https://www.mozilla.org/security/advisories/mfsa2022-39/",
"refsource": "MISC",
"tags": [
"Vendor Advisory"
],
"url": "https://www.mozilla.org/security/advisories/mfsa2022-39/"
},
{
"name": "https://www.mozilla.org/security/advisories/mfsa2022-38/",
"refsource": "MISC",
"tags": [
"Vendor Advisory"
],
"url": "https://www.mozilla.org/security/advisories/mfsa2022-38/"
},
{
"name": "https://bugzilla.mozilla.org/show_bug.cgi?id=1784838",
"refsource": "MISC",
"tags": [
"Issue Tracking",
"Permissions Required",
"Vendor Advisory"
],
"url": "https://bugzilla.mozilla.org/show_bug.cgi?id=1784838"
}
]
}
},
"impact": {
"baseMetricV3": {
"cvssV3": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 8.1,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 5.2
}
},
"lastModifiedDate": "2023-01-03T20:22Z",
"publishedDate": "2022-12-22T20:15Z"
}
}
}
Loading...
Loading...
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.