firefox vulnerabilities (Ubuntu)
1,530 vulnerabilities.
firefoxUbuntuA use-after-free vulnerability was found via testing, and traced to an out-of-date Cairo library....8.8 HighfirefoxUbuntuMozilla developers reported memory safety bugs present in code shared between Firefox and...8.8 HighfirefoxUbuntuA malicious webpage could have triggered a use-after-free, memory corruption, and a potentially...8.8 HighfirefoxUbuntuOut of bounds write in ANGLE in Google Chrome prior to 91.0.4472.101 allowed a remote attacker to...8.8 HighfirefoxUbuntuMozilla developers reported memory safety bugs present in Firefox 88 and Firefox ESR 78.11. Some...8.8 HighfirefoxUbuntuMozilla developers reported memory safety bugs present in Firefox 88. Some of these bugs showed...8.8 HighfirefoxUbuntuWhen styling and rendering an oversized `<select>` element, Firefox did not apply correct...4.3 MediumfirefoxUbuntuFirefox used to cache the last filename used for printing a file. When generating a filename for...4.3 MediumfirefoxUbuntuWhen a user has already allowed a website to access microphone and camera, disabling camera...4.3 MediumfirefoxUbuntuWhen Web Render components were destructed, a race condition could have caused undefined behavior...7.5 HighfirefoxUbuntuMozilla developers and community members reported memory safety bugs present in Firefox 87. Some...8.8 HighfirefoxUbuntuPorts that were written as an integer overflow above the bounds of a 16-bit integer could have...8.8 HighfirefoxUbuntuThe WebAssembly JIT could miscalculate the size of a return type, which could lead to a null read...6.5 MediumfirefoxUbuntuWhen a user clicked on an FTP URL containing encoded newline characters (%0A and %0D), the...8.8 HighfirefoxUbuntuA compromised content process could have performed session history manipulations it should not...4.3 MediumfirefoxUbuntuA race condition with requestPointerLock() and setTimeout() could have resulted in a user...3.1 LowfirefoxUbuntuIf a Blob URL was loaded through some unusual user interaction, it could have been loaded by the...8.8 HighfirefoxUbuntuThrough complicated navigations with new windows, an HTTP page could have inherited a secure lock...6.5 MediumfirefoxUbuntuDue to unexpected data type conversions, a use-after-free could have occurred when interacting...8.8 HighfirefoxUbuntuBy utilizing 3D CSS in conjunction with Javascript, content could have been rendered outside the...6.5 MediumfirefoxUbuntuWhen Responsive Design Mode was enabled, it used references to objects that were previously freed...8.8 HighfirefoxUbuntuA WebGL framebuffer was not initialized early enough, resulting in memory corruption and an out...8.8 HighfirefoxUbuntuMozilla developers reported memory safety bugs present in Firefox 86. Some of these bugs showed...8.8 HighfirefoxUbuntuA malicious extension with the 'search' permission could have installed a new search engine whose...6.5 MediumfirefoxUbuntuIf an attacker is able to alter specific about:config values (for example malware running on the...6.5 MediumfirefoxUbuntuA transient execution vulnerability, named Floating Point Value Injection (FPVI) allowed an...5.3 MediumfirefoxUbuntuMozilla developers and community members reported memory safety bugs present in Firefox 86 and...8.8 HighfirefoxUbuntuA malicious extension could have opened a popup window lacking an address bar. The title of the...6.5 MediumfirefoxUbuntuBy causing a transition on a parent node by removing a CSS rule, an invalid property for a marker...6.5 MediumfirefoxUbuntuUsing techniques that built on the slipstream research, a malicious webpage could have scanned...6.5 MediumfirefoxUbuntuA texture upload of a Pixel Buffer Object could have confused the WebGL code to skip binding the...8.1 HighfirefoxUbuntuMozilla developers reported memory safety bugs present in Firefox 85. Some of these bugs showed...8.8 HighfirefoxUbuntuContext-specific code was included in a shared jump table; resulting in assertions being...6.5 MediumfirefoxUbuntuWhen processing a redirect with a conflicting Referrer-Policy, Firefox would have adopted the...6.5 MediumfirefoxUbuntuOne phishing tactic on the web is to provide a link with HTTP Auth. For example 'https://www...8.8 HighfirefoxUbuntuThe DOMParser API did not properly process '<noscript>' elements for escaping. This could be used...6.1 MediumfirefoxUbuntuThe developer page about:memory has a Measure function for exploring what object types the...6.5 MediumfirefoxUbuntuMozilla developers reported memory safety bugs present in Firefox 85 and Firefox ESR 78.7. Some...8.8 HighfirefoxUbuntuWhen trying to load a cross-origin resource in an audio/video context a decoding error may have...6.5 MediumfirefoxUbuntuAs specified in the W3C Content Security Policy draft, when creating a violation report, "User...4.3 MediumfirefoxUbuntuIf Content Security Policy blocked frame navigation, the full destination of a redirect served in...4.3 MediumfirefoxUbuntufirefox regressionNo scorefirefoxUbuntuMozilla developers reported memory safety bugs present in Firefox 84. Some of these bugs showed...8.8 HighfirefoxUbuntuMozilla developers reported memory safety bugs present in Firefox 84 and Firefox ESR 78.6. Some...8.8 HighfirefoxUbuntuWhen sharing geolocation during an active WebRTC share, Firefox could have reset the webRTC...4.3 MediumfirefoxUbuntuIncorrect use of the '<RowCountChanged>' method could have led to a user-after-poison and a...8.8 HighfirefoxUbuntuFurther techniques that built on the slipstream research combined with a malicious webpage could...7.4 HighfirefoxUbuntuPerforming garbage collection on re-declared JavaScript variables resulted in a user-after-poison...8.8 HighfirefoxUbuntuThe browser could have been confused into transferring a screen sharing state into another tab,...6.5 MediumfirefoxUbuntuAn ambiguous file picker design could have confused users who intended to select and upload a...6.5 Medium- Show moreLoading…