firefox vulnerabilities (Ubuntu)
1,530 vulnerabilities.
firefoxUbuntuA cross-origin iframe referencing an XSLT document would inherit the parent domain's permissions ...8.8 HighfirefoxUbuntuAn attacker could have abused XSLT error handling to associate attacker-controlled content with...6.5 MediumfirefoxUbuntuMozilla developers and the Mozilla Fuzzing Team reported memory safety bugs present in Firefox...8.8 HighfirefoxUbuntuMozilla developers and the Mozilla Fuzzing Team reported memory safety bugs present in Firefox...9.8 CriticalfirefoxUbuntuWhen combining CSS properties for overflow and transform, the mouse cursor could interact with...7.5 HighfirefoxUbuntuWhen visiting directory listings for `chrome://` URLs as source text, some parameters were...5.3 MediumfirefoxUbuntuWhen using the Performance API, an attacker was able to notice subtle differences between...6.1 MediumfirefoxUbuntuWhen loading a script with Subresource Integrity, attackers with an injection capability could...4.3 MediumfirefoxUbuntuMozilla developers Bryce Seager van Dyk and the Mozilla Fuzzing Team reported potential...9.8 CriticalfirefoxUbuntuAn attacker who could have convinced a user to drag and drop an image to a filesystem could have...8.8 HighfirefoxUbuntuAn attacker who could have convinced a user to drag and drop an image to a filesystem could have...8.8 HighfirefoxUbuntuWithin the <code>lg_init()</code> function, if several allocations succeed but then one fails, an...8.8 HighfirefoxUbuntuThe MediaError message property should be consistent to avoid leaking information about cross...7.5 HighfirefoxUbuntuASN.1 parsing of an indefinite SEQUENCE inside an indefinite GROUP could have resulted in the...9.8 CriticalfirefoxUbuntuSVG <code><use></code> tags that referenced a same-origin document could have resulted in...6.1 MediumfirefoxUbuntuEven when an iframe was sandboxed with <code>allow-top-navigation-by-user-activation</code>, if...6.1 MediumfirefoxUbuntuThe HTML Sanitizer should have sanitized the <code>href</code> attribute of SVG <code><use>...6.1 MediumfirefoxUbuntuWhen downloading an update for an addon, the downloaded addon update's version was not verified...6.5 MediumfirefoxUbuntuThe Mozilla Fuzzing Team reported potential vulnerabilities present in Thunderbird 91.10. Some of...8.8 HighfirefoxUbuntuIn the <code>nsTArray_Impl::ReplaceElementsAt()</code> function, an integer overflow could have...8.8 HighfirefoxUbuntuA malicious website that could create a popup could have resized the popup to overlay the address...6.5 MediumfirefoxUbuntuIf there was a PAC URL set and the server that hosts the PAC was not reachable, OCSP requests...4.3 MediumfirefoxUbuntuSession history navigations may have led to a use-after-free and potentially exploitable crash....9.8 CriticalfirefoxUbuntuAn iframe that was not permitted to run scripts could do so if the user clicked on a <code...8.8 HighfirefoxUbuntuIf an object prototype was corrupted by an attacker, they would have been able to set undesired...8.8 HighfirefoxUbuntuMozilla developers Gabriele Svelto, Timothy Nikkel, Randell Jesup, Jon Coppeard, and the Mozilla...9.8 CriticalfirefoxUbuntuMozilla developers Andrew McCreight, Nicolas B. Pierron, and the Mozilla Fuzzing Team reported...9.8 CriticalfirefoxUbuntuIf array shift operations are not used, the Garbage Collector may have become confused about...4.3 MediumfirefoxUbuntuAn attacker could have injected CSS into stylesheets accessible via internal URIs, such as...6.5 MediumfirefoxUbuntuFirefox's HTML parser did not correctly interpret HTML comment tags, resulting in an incongruity...6.5 MediumfirefoxUbuntuAn attacker could have exploited a timing attack by sending a large number of allowCredential...6.5 MediumfirefoxUbuntuA crafted CMS message could have been processed incorrectly, leading to an invalid memory read,...8.8 HighfirefoxUbuntuOn arm64, WASM code could have resulted in incorrect assembly generation leading to a register...8.8 HighfirefoxUbuntuWhen exiting fullscreen mode, an iframe could have confused the browser about the current state...6.5 MediumfirefoxUbuntuA malicious webpage could have caused an out-of-bounds write in WebGL, leading to memory...9.8 CriticalfirefoxUbuntuA malicious website could have learned the size of a cross-origin resource that supported Range...9.8 CriticalfirefoxUbuntuUse after free in Codecs in Google Chrome prior to 101.0.4951.41 allowed a remote attacker to...8.8 HighfirefoxUbuntuIf an attacker was able to corrupt the methods of an Array object in JavaScript via prototype...8.8 HighfirefoxUbuntuAn attacker could have sent a message to the parent process where the contents were used to...8.8 HighfirefoxUbuntuMozilla developers Gabriele Svelto, Randell Jesup and the Mozilla Fuzzing Team reported memory...8.8 HighfirefoxUbuntuThe Performance API did not properly hide the fact whether a request cross-origin resource has...4.3 MediumfirefoxUbuntuMozilla developers Andrew McCreight, Gabriele Svelto, Tom Ritter and the Mozilla Fuzzing Team...9.8 CriticalfirefoxUbuntuFirefox behaved slightly differently for already known resources when loading CSS resources...6.5 MediumfirefoxUbuntuWhen reusing existing popups Firefox would have allowed them to cover the fullscreen notification...6.5 MediumfirefoxUbuntuRequests initiated through reader mode did not properly omit cookies with a SameSite attribute....6.1 MediumfirefoxUbuntuAn improper implementation of the new iframe sandbox keyword <code>allow-top-navigation-by-user...6.1 MediumfirefoxUbuntuDocuments in deeply-nested cross-origin browsing contexts could have obtained permissions granted...8.8 HighfirefoxUbuntuMozilla developers and community members Randell Jesup, Sebastian Hengst, and the Mozilla Fuzzing...8.8 HighfirefoxUbuntuIn unusual circumstances, selecting text could cause text selection caching to behave incorrectly...6.5 MediumfirefoxUbuntuSVG's <code><use></code> element could have been used to load unexpected content that could...8.8 High- Show moreLoading…