MozillaFirefox vulnerabilities (openSUSE)
3,079 vulnerabilities.
MozillaFirefoxopenSUSEPDF.js vulnerable to arbitrary JavaScript execution upon opening a malicious PDF8.8 HighMozillaFirefoxopenSUSEMemory safety bugs present in Firefox 124. Some of these bugs showed evidence of memory...8.1 HighMozillaFirefoxopenSUSEMemory safety bug present in Firefox 124, Firefox ESR 115.9, and Thunderbird 115.9. This bug...8.1 HighMozillaFirefoxopenSUSEThere was no limit to the number of HTTP/2 CONTINUATION frames that would be processed. A server...3.7 LowMozillaFirefoxopenSUSEThe executable file warning was not presented when downloading .xrm-ms files. *Note: This issue...9.8 CriticalMozillaFirefoxopenSUSEThe MarkStack assignment operator, part of the JavaScript engine, could access uninitialized...5.3 MediumMozillaFirefoxopenSUSEIf an AlignedBuffer were assigned to itself, the subsequent self-move could result in an...4.0 MediumMozillaFirefoxopenSUSEAn out-of-memory condition during object initialization could result in an empty shape list. If...6.2 MediumMozillaFirefoxopenSUSEOn 32-bit versions there were integer-overflows that led to an out-of-bounds-read that...5.9 MediumMozillaFirefoxopenSUSEIt was possible to mutate a JavaScript object so that the JIT could crash while tracing it. This...7.5 HighMozillaFirefoxopenSUSEThe JIT created incorrect code for arguments in certain cases. This led to potential use-after...7.8 HighMozillaFirefoxopenSUSEA use-after-free could occur during WASM execution if garbage collection ran during the creation...8.8 HighMozillaFirefoxopenSUSEIn certain cases the JIT incorrectly optimized MSubstr operations, which led to out-of-bounds...6.5 MediumMozillaFirefoxopenSUSEIn some code patterns the JIT incorrectly optimized switch statements and generated code with out...8.8 HighMozillaFirefoxopenSUSEA use-after-free could result if a JavaScript realm was in the process of being initialized when...7.5 HighMozillaFirefoxopenSUSEGetBoundName could return the wrong version of an object when JIT optimizations were applied....7.5 HighMozillaFirefoxopenSUSEAn attacker was able to inject an event handler into a privileged object that would allow...8.4 HighMozillaFirefoxopenSUSEAn attacker was able to perform an out-of-bounds read or write on a JavaScript object by fooling...9.8 CriticalMozillaFirefoxopenSUSETo harden ICU against exploitation, the behavior for out-of-memory conditions was changed to...2.7 LowMozillaFirefoxopenSUSEAn attacker could have leveraged the Windows Error Reporter to run arbitrary code on the system...5.9 MediumMozillaFirefoxopenSUSEMemory safety bugs present in Firefox 123. Some of these bugs showed evidence of memory...9.8 CriticalMozillaFirefoxopenSUSEMemory safety bugs present in Firefox 123, Firefox ESR 115.8, and Thunderbird 115.8. Some of...8.8 HighMozillaFirefoxopenSUSEData was not properly sanitized when decoding a QUIC ACK frame; this could have led to...7.5 HighMozillaFirefoxopenSUSEIf an attacker could find a way to trigger a particular code path in `SafeRefPtr`, it could have...8.1 HighMozillaFirefoxopenSUSEA missing delay on when pointer lock was used could have allowed a malicious page to trick a user...5.5 MediumMozillaFirefoxopenSUSEUsing a markup injection an attacker could have stolen nonce values. This could have been used to...6.1 MediumMozillaFirefoxopenSUSEThe permission prompt input delay could have expired while the window is not in focus, which made...6.1 MediumMozillaFirefoxopenSUSE`AppendEncodedAttributeValue(), ExtraSpaceNeededForAttrEncoding()` and `AppendEncodedCharacters()...8.4 HighMozillaFirefoxopenSUSEReturn registers were overwritten which could have allowed an attacker to execute arbitrary code....8.1 HighMozillaFirefoxopenSUSEPassing invalid data could have led to invalid wasm values being created, such as arbitrary...3.7 LowMozillaFirefoxopenSUSEMemory safety bugs present in Firefox 122. Some of these bugs showed evidence of memory...8.1 HighMozillaFirefoxopenSUSEThe incorrect object was checked for NULL in the built-in profiler, potentially leading to...6.5 MediumMozillaFirefoxopenSUSEWhen opening a website using the `firefox://` protocol handler, SameSite cookies were not...8.3 HighMozillaFirefoxopenSUSEThe `fetch()` API and navigation incorrectly shared the same cache, as the cache key did not...9.8 CriticalMozillaFirefoxopenSUSEMemory safety bugs present in Firefox 122, Firefox ESR 115.7, and Thunderbird 115.7. Some of...8.1 HighMozillaFirefoxopenSUSEIncorrect code generation could have led to unexpected numeric conversions and potential...7.5 HighMozillaFirefoxopenSUSESet-Cookie response headers were being incorrectly honored in multipart HTTP responses. If an...6.1 MediumMozillaFirefoxopenSUSEA malicious website could have used a combination of exiting fullscreen mode and ...6.1 MediumMozillaFirefoxopenSUSEIf a website set a large custom cursor, portions of the cursor could have overlapped with the...6.1 MediumMozillaFirefoxopenSUSEA website could have obscured the fullscreen notification by using a dropdown select input...4.3 MediumMozillaFirefoxopenSUSEThrough a series of API calls and redirects, an attacker-controlled alert dialog could have been...6.5 MediumMozillaFirefoxopenSUSEWhen storing and re-accessing data on a networking channel, the length of buffers may have been...7.5 HighMozillaFirefoxopenSUSESome WASM source files could have caused a crash when loaded in devtools. This vulnerability...6.5 MediumMozillaFirefoxopenSUSEA use-after-free crash could have occurred on macOS if a Firefox update were being applied on a...6.5 MediumMozillaFirefoxopenSUSEA compromised content process could have updated the document URI. This could have allowed an...4.3 MediumMozillaFirefoxopenSUSEThe WebAudio `OscillatorNode` object was susceptible to a stack buffer overflow. This could have...8.8 HighMozillaFirefoxopenSUSEIn some circumstances, JIT compiled code could have dereferenced a wild pointer value. This could...7.5 HighMozillaFirefoxopenSUSEAn unchecked return value in TLS handshake code could have caused a potentially exploitable crash...7.5 HighMozillaFirefoxopenSUSEMemory safety bugs present in Firefox 121, Firefox ESR 115.6, and Thunderbird 115.6. Some of...8.8 HighMozillaFirefoxopenSUSEIn specific HSTS configurations an attacker could have bypassed HSTS on a subdomain. This...6.5 Medium- Show moreLoading…