firefox vulnerabilities (Ubuntu)
1,530 vulnerabilities.
firefoxUbuntufirefox regressionsNo scorefirefoxUbuntuAn attacker was able to inject an event handler into a privileged object that would allow...8.4 HighfirefoxUbuntuAn attacker was able to perform an out-of-bounds read or write on a JavaScript object by fooling...9.8 CriticalfirefoxUbuntuMemory safety bugs present in Firefox 123. Some of these bugs showed evidence of memory...9.8 CriticalfirefoxUbuntuMemory safety bugs present in Firefox 123, Firefox ESR 115.8, and Thunderbird 115.8. Some of...8.8 HighfirefoxUbuntuData was not properly sanitized when decoding a QUIC ACK frame; this could have led to...7.5 HighfirefoxUbuntuIf an attacker could find a way to trigger a particular code path in `SafeRefPtr`, it could have...8.1 HighfirefoxUbuntuA missing delay on when pointer lock was used could have allowed a malicious page to trick a user...5.5 MediumfirefoxUbuntuUsing a markup injection an attacker could have stolen nonce values. This could have been used to...6.1 MediumfirefoxUbuntuThe permission prompt input delay could have expired while the window is not in focus, which made...6.1 MediumfirefoxUbuntu`AppendEncodedAttributeValue(), ExtraSpaceNeededForAttrEncoding()` and `AppendEncodedCharacters()...8.4 HighfirefoxUbuntuReturn registers were overwritten which could have allowed an attacker to execute arbitrary code....8.1 HighfirefoxUbuntuPassing invalid data could have led to invalid wasm values being created, such as arbitrary...3.7 LowfirefoxUbuntufirefox regressionsNo scorefirefoxUbuntuMemory safety bugs present in Firefox 122. Some of these bugs showed evidence of memory...8.1 HighfirefoxUbuntuThe incorrect object was checked for NULL in the built-in profiler, potentially leading to...6.5 MediumfirefoxUbuntuWhen opening a website using the `firefox://` protocol handler, SameSite cookies were not...8.3 HighfirefoxUbuntuThe `fetch()` API and navigation incorrectly shared the same cache, as the cache key did not...9.8 CriticalfirefoxUbuntuMemory safety bugs present in Firefox 122, Firefox ESR 115.7, and Thunderbird 115.7. Some of...8.1 HighfirefoxUbuntuIncorrect code generation could have led to unexpected numeric conversions and potential...7.5 HighfirefoxUbuntuSet-Cookie response headers were being incorrectly honored in multipart HTTP responses. If an...6.1 MediumfirefoxUbuntuA malicious website could have used a combination of exiting fullscreen mode and ...6.1 MediumfirefoxUbuntuIf a website set a large custom cursor, portions of the cursor could have overlapped with the...6.1 MediumfirefoxUbuntuA website could have obscured the fullscreen notification by using a dropdown select input...4.3 MediumfirefoxUbuntuThrough a series of API calls and redirects, an attacker-controlled alert dialog could have been...6.5 MediumfirefoxUbuntuWhen storing and re-accessing data on a networking channel, the length of buffers may have been...7.5 HighfirefoxUbuntufirefox regressionsNo scorefirefoxUbuntuSome WASM source files could have caused a crash when loaded in devtools. This vulnerability...6.5 MediumfirefoxUbuntuA compromised content process could have updated the document URI. This could have allowed an...4.3 MediumfirefoxUbuntuThe WebAudio `OscillatorNode` object was susceptible to a stack buffer overflow. This could have...8.8 HighfirefoxUbuntuIn some circumstances, JIT compiled code could have dereferenced a wild pointer value. This could...7.5 HighfirefoxUbuntuAn unchecked return value in TLS handshake code could have caused a potentially exploitable crash...7.5 HighfirefoxUbuntuMemory safety bugs present in Firefox 121, Firefox ESR 115.6, and Thunderbird 115.6. Some of...8.8 HighfirefoxUbuntuIn specific HSTS configurations an attacker could have bypassed HSTS on a subdomain. This...6.5 MediumfirefoxUbuntuA malicious devtools extension could have been used to escalate privileges. This vulnerability...8.8 HighfirefoxUbuntuA bug in popup notifications delay calculation could have made it possible for an attacker to...8.8 HighfirefoxUbuntuA phishing site could have repurposed an `about:` dialog to show phishing content with an...4.3 MediumfirefoxUbuntuWhen a parent page loaded a child in an iframe with `unsafe-inline`, the parent Content Security...6.5 MediumfirefoxUbuntuA Linux user opening the print preview dialog could have caused the browser to crash. This...6.5 MediumfirefoxUbuntuIt was possible for certain browser prompts and dialogs to be activated or dismissed...4.3 MediumfirefoxUbuntuAn out of bounds write in ANGLE could have allowed an attacker to corrupt memory leading to a...6.5 MediumfirefoxUbuntufirefox regressionsNo scorefirefoxUbuntuMemory safety bugs present in Firefox 120. Some of these bugs showed evidence of memory...8.8 HighfirefoxUbuntuBrowser tab titles were being leaked by GNOME to system logs. This could potentially expose the...6.5 MediumfirefoxUbuntuUnder certain conditions, Firefox did not display a warning when a user attempted to navigate to...4.3 MediumfirefoxUbuntuA `` element could have been manipulated to paint content outside of a sandboxed iframe. This...6.5 MediumfirefoxUbuntuThe timing of a button click causing a popup to disappear was approximately the same length as...6.1 MediumfirefoxUbuntuTypedArrays can be fallible and lacked proper exception handling. This could lead to abuse in...8.8 HighfirefoxUbuntu`EncryptingOutputStream` was susceptible to exposing uninitialized data. This issue could only...6.5 MediumfirefoxUbuntuMultiple NSS NIST curves were susceptible to a side-channel attack known as "Minerva". This...4.3 Medium- Show moreLoading…