CVE-2017-7847

Crafted CSS in an RSS feed can leak and reveal local path strings, which may contain user name. This vulnerability affects Thunderbird < 52.5.2.

Multiple vulnerabilities have been fixed in thunderbird.

• JavaScript Execution via RSS in mailbox:// origin (CVE-2017-7846).
• Local path string can be leaked from RSS feed (CVE-2017-7847).
• RSS Feed vulnerable to new line Injection (CVE-2017-7848).
• Mailsploit From address with encoded null character is cut off in message header display (CVE-2017-7829).

Multiple vulnerabilities have been fixed in the bundled enigmail package.

• An issue was discovered that allows remote attackers to trigger use of an intended public key for encryption, because incorrect regular expressions are used for extraction of an e-mail address from a comma-separated list (CVE-2017-17843).
• A remote attacker can obtain cleartext content by sending an encrypted data block to a victim, and relying on the victim to automatically decrypt that block and then send it back to the attacker as quoted text (CVE-2017-17844).
• An issue was discovered where Improper Random Secret Generation occurs because Math.Random() is used by pretty Easy privacy (pEp) (CVE-2017-17845).
• An issue was discovered where regular expressions are exploitable for Denial of Service, because of attempts to match arbitrarily long strings (CVE-2017-17846).
• An issue was discovered that signature spoofing is possible because the UI does not properly distinguish between an attachment signature, and a signature that applies to the entire containing message (CVE-2017-17847).
• In a variant of CVE-2017-17847, signature spoofing is possible for multipart/related messages because a signed message part can be referenced with a cid: URI but not actually displayed (CVE-2017-17848)

This update for Mozilla Thunderbird to version 52.5.2 fixes the following vulnerabilities:

• CVE-2017-7846: JavaScript Execution via RSS in mailbox:// origin (bsc#1074043)
• CVE-2017-7847: Local path string can be leaked from RSS feed (bsc#1074044)
• CVE-2017-7848: RSS Feed vulnerable to new line Injection (bsc#1074045)
• CVE-2017-7829: From address with encoded null character is cut off in message header display (bsc#1074046)

This update for Mozilla Thunderbird to version 52.5.2 fixes the following vulnerabilities:

• CVE-2017-7846: JavaScript Execution via RSS in mailbox:// origin (bsc#1074043)
• CVE-2017-7847: Local path string can be leaked from RSS feed (bsc#1074044)
• CVE-2017-7848: RSS Feed vulnerable to new line Injection (bsc#1074045)
• CVE-2017-7829: From address with encoded null character is cut off in message header display (bsc#1074046)

These are all security issues fixed in the MozillaThunderbird-91.1.1-1.1 package on the GA media of openSUSE Tumbleweed.

It was discovered that a From address encoded with a null character is cut off in the message header display. An attacker could potentially exploit this to spoof the sender address. (CVE-2017-7829)

It was discovered that it is possible to execute JavaScript in RSS feeds in some circumstances. If a user were tricked in to opening a specially crafted RSS feed, an attacker could potentially exploit this in combination with another vulnerability, in order to cause unspecified problems. (CVE-2017-7846)

It was discovered that the RSS feed can leak local path names. If a user were tricked in to opening a specially crafted RSS feed, an attacker could potentially exploit this to obtain sensitive information. (CVE-2017-7847)

It was discovered that RSS feeds are vulnerable to new line injection. If a user were tricked in to opening a specially crafted RSS feed, an attacker could potentially exploit this to cause unspecified problems. (CVE-2017-7848)

Multiple security issues were discovered in Thunderbird. If a user were tricked in to opening a specially crafted website in a browsing context, an attacker could potentially exploit these to cause a denial of service, execute arbitrary code, or cause other unspecified effects. (CVE-2018-5089, CVE-2018-5095, CVE-2018-5096, CVE-2018-5097, CVE-2018-5098, CVE-2018-5099, CVE-2018-5102, CVE-2018-5103, CVE-2018-5104, CVE-2018-5117)