rpm package
suse/MozillaFirefox&distro=SUSE Linux Enterprise High Performance Computing 15 SP1-LTSS
pkg:rpm/suse/MozillaFirefox&distro=SUSE%20Linux%20Enterprise%20High%20Performance%20Computing%2015%20SP1-LTSS
Vulnerabilities (316)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2021-23994 | Hig | 8.8 | < 78.10.0-3.139.1 | 78.10.0-3.139.1 | Jun 24, 2021 | A WebGL framebuffer was not initialized early enough, resulting in memory corruption and an out of bound write. This vulnerability affects Firefox ESR < 78.10, Thunderbird < 78.10, and Firefox < 88. | |
| CVE-2021-30547 | Hig | 8.8 | < 78.12.0-3.147.1 | 78.12.0-3.147.1 | Jun 15, 2021 | Out of bounds write in ANGLE in Google Chrome prior to 91.0.4472.101 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML page. | |
| CVE-2021-23987 | Hig | 8.8 | < 78.9.0-3.136.1 | 78.9.0-3.136.1 | Mar 31, 2021 | Mozilla developers and community members reported memory safety bugs present in Firefox 86 and Firefox ESR 78.8. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code. This vuln | |
| CVE-2021-23984 | Med | 6.5 | < 78.9.0-3.136.1 | 78.9.0-3.136.1 | Mar 31, 2021 | A malicious extension could have opened a popup window lacking an address bar. The title of the popup lacking an address bar should not be fully controllable, but in this situation was. This could have been used to spoof a website and attempt to trick the user into providing cred | |
| CVE-2021-23982 | Med | 6.5 | < 78.9.0-3.136.1 | 78.9.0-3.136.1 | Mar 31, 2021 | Using techniques that built on the slipstream research, a malicious webpage could have scanned both an internal network's hosts as well as services running on the user's local machine utilizing WebRTC connections. This vulnerability affects Firefox ESR < 78.9, Firefox < 87, and T | |
| CVE-2021-23981 | Hig | 8.1 | < 78.9.0-3.136.1 | 78.9.0-3.136.1 | Mar 31, 2021 | A texture upload of a Pixel Buffer Object could have confused the WebGL code to skip binding the buffer used to unpack it, resulting in memory corruption and a potentially exploitable information leak or crash. This vulnerability affects Firefox ESR < 78.9, Firefox < 87, and Thun | |
| CVE-2021-23978 | Hig | 8.8 | < 78.8.0-3.133.1 | 78.8.0-3.133.1 | Feb 26, 2021 | Mozilla developers reported memory safety bugs present in Firefox 85 and Firefox ESR 78.7. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code. This vulnerability affects Fire | |
| CVE-2021-23964 | Hig | 8.8 | < 78.7.0-3.128.2 | 78.7.0-3.128.2 | Feb 26, 2021 | Mozilla developers reported memory safety bugs present in Firefox 84 and Firefox ESR 78.6. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code. This vulnerability affects Fire | |
| CVE-2021-23961 | Hig | 7.4 | < 78.10.0-3.139.1 | 78.10.0-3.139.1 | Feb 26, 2021 | Further techniques that built on the slipstream research combined with a malicious webpage could have exposed both an internal network's hosts as well as services running on the user's local machine. This vulnerability affects Firefox < 85. | |
| CVE-2021-23960 | Hig | 8.8 | < 78.7.0-3.128.2 | 78.7.0-3.128.2 | Feb 26, 2021 | Performing garbage collection on re-declared JavaScript variables resulted in a user-after-poison, and a potentially exploitable crash. This vulnerability affects Firefox < 85, Thunderbird < 78.7, and Firefox ESR < 78.7. | |
| CVE-2021-23954 | Hig | 8.8 | < 78.7.0-3.128.2 | 78.7.0-3.128.2 | Feb 26, 2021 | Using the new logical assignment operators in a JavaScript switch statement could have caused a type confusion, leading to a memory corruption and a potentially exploitable crash. This vulnerability affects Firefox < 85, Thunderbird < 78.7, and Firefox ESR < 78.7. | |
| CVE-2021-23953 | Med | 4.3 | < 78.7.0-3.128.2 | 78.7.0-3.128.2 | Feb 26, 2021 | If a user clicked into a specifically crafted PDF, the PDF reader could be confused into leaking cross-origin information, when said information is served as chunked data. This vulnerability affects Firefox < 85, Thunderbird < 78.7, and Firefox ESR < 78.7. | |
| CVE-2021-23973 | Med | 6.5 | < 78.8.0-3.133.1 | 78.8.0-3.133.1 | Feb 26, 2021 | When trying to load a cross-origin resource in an audio/video context a decoding error may have resulted, and the content of that error may have revealed information about the resource. This vulnerability affects Firefox < 86, Thunderbird < 78.8, and Firefox ESR < 78.8. | |
| CVE-2021-23969 | Med | 4.3 | < 78.8.0-3.133.1 | 78.8.0-3.133.1 | Feb 26, 2021 | As specified in the W3C Content Security Policy draft, when creating a violation report, "User agents need to ensure that the source file is the URL requested by the page, pre-redirects. If that’s not possible, user agents need to strip the URL down to an origin to avoid unintent | |
| CVE-2021-23968 | Med | 4.3 | < 78.8.0-3.133.1 | 78.8.0-3.133.1 | Feb 26, 2021 | If Content Security Policy blocked frame navigation, the full destination of a redirect served in the frame was reported in the violation report; as opposed to the original frame URI. This could be used to leak sensitive information contained in such URIs. This vulnerability affe | |
| CVE-2020-26976 | Med | 6.5 | < 78.7.0-3.128.2 | 78.7.0-3.128.2 | Jan 7, 2021 | When a HTTPS pages was embedded in a HTTP page, and there was a service worker registered for the former, the service worker could have intercepted the request for the secure page despite the iframe not being a secure context due to the (insecure) framing. This vulnerability affe |
- affected < 78.10.0-3.139.1fixed 78.10.0-3.139.1
A WebGL framebuffer was not initialized early enough, resulting in memory corruption and an out of bound write. This vulnerability affects Firefox ESR < 78.10, Thunderbird < 78.10, and Firefox < 88.
- affected < 78.12.0-3.147.1fixed 78.12.0-3.147.1
Out of bounds write in ANGLE in Google Chrome prior to 91.0.4472.101 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML page.
- affected < 78.9.0-3.136.1fixed 78.9.0-3.136.1
Mozilla developers and community members reported memory safety bugs present in Firefox 86 and Firefox ESR 78.8. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code. This vuln
- affected < 78.9.0-3.136.1fixed 78.9.0-3.136.1
A malicious extension could have opened a popup window lacking an address bar. The title of the popup lacking an address bar should not be fully controllable, but in this situation was. This could have been used to spoof a website and attempt to trick the user into providing cred
- affected < 78.9.0-3.136.1fixed 78.9.0-3.136.1
Using techniques that built on the slipstream research, a malicious webpage could have scanned both an internal network's hosts as well as services running on the user's local machine utilizing WebRTC connections. This vulnerability affects Firefox ESR < 78.9, Firefox < 87, and T
- affected < 78.9.0-3.136.1fixed 78.9.0-3.136.1
A texture upload of a Pixel Buffer Object could have confused the WebGL code to skip binding the buffer used to unpack it, resulting in memory corruption and a potentially exploitable information leak or crash. This vulnerability affects Firefox ESR < 78.9, Firefox < 87, and Thun
- affected < 78.8.0-3.133.1fixed 78.8.0-3.133.1
Mozilla developers reported memory safety bugs present in Firefox 85 and Firefox ESR 78.7. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code. This vulnerability affects Fire
- affected < 78.7.0-3.128.2fixed 78.7.0-3.128.2
Mozilla developers reported memory safety bugs present in Firefox 84 and Firefox ESR 78.6. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code. This vulnerability affects Fire
- affected < 78.10.0-3.139.1fixed 78.10.0-3.139.1
Further techniques that built on the slipstream research combined with a malicious webpage could have exposed both an internal network's hosts as well as services running on the user's local machine. This vulnerability affects Firefox < 85.
- affected < 78.7.0-3.128.2fixed 78.7.0-3.128.2
Performing garbage collection on re-declared JavaScript variables resulted in a user-after-poison, and a potentially exploitable crash. This vulnerability affects Firefox < 85, Thunderbird < 78.7, and Firefox ESR < 78.7.
- affected < 78.7.0-3.128.2fixed 78.7.0-3.128.2
Using the new logical assignment operators in a JavaScript switch statement could have caused a type confusion, leading to a memory corruption and a potentially exploitable crash. This vulnerability affects Firefox < 85, Thunderbird < 78.7, and Firefox ESR < 78.7.
- affected < 78.7.0-3.128.2fixed 78.7.0-3.128.2
If a user clicked into a specifically crafted PDF, the PDF reader could be confused into leaking cross-origin information, when said information is served as chunked data. This vulnerability affects Firefox < 85, Thunderbird < 78.7, and Firefox ESR < 78.7.
- affected < 78.8.0-3.133.1fixed 78.8.0-3.133.1
When trying to load a cross-origin resource in an audio/video context a decoding error may have resulted, and the content of that error may have revealed information about the resource. This vulnerability affects Firefox < 86, Thunderbird < 78.8, and Firefox ESR < 78.8.
- affected < 78.8.0-3.133.1fixed 78.8.0-3.133.1
As specified in the W3C Content Security Policy draft, when creating a violation report, "User agents need to ensure that the source file is the URL requested by the page, pre-redirects. If that’s not possible, user agents need to strip the URL down to an origin to avoid unintent
- affected < 78.8.0-3.133.1fixed 78.8.0-3.133.1
If Content Security Policy blocked frame navigation, the full destination of a redirect served in the frame was reported in the violation report; as opposed to the original frame URI. This could be used to leak sensitive information contained in such URIs. This vulnerability affe
- affected < 78.7.0-3.128.2fixed 78.7.0-3.128.2
When a HTTPS pages was embedded in a HTTP page, and there was a service worker registered for the former, the service worker could have intercepted the request for the secure page despite the iframe not being a secure context due to the (insecure) framing. This vulnerability affe
Page 16 of 16