firefox vulnerabilities (Red Hat)
2,057 vulnerabilities.
firefoxRed HatA lack of in app notification for entering fullscreen mode could have lead to a malicious website...7.5 HighfirefoxRed HatMozilla developers Philipp and Gabriele Svelto reported memory safety bugs present in Firefox ESR...8.8 HighfirefoxRed HatMozilla developers Kershaw Chang and the Mozilla Fuzzing Team reported memory safety bugs present...8.8 HighfirefoxRed HatWhen importing a SPKI RSA public key as ECDSA P-256, the key would be handled incorrectly causing...6.5 MediumfirefoxRed HatModule load requests that failed were not being checked as to whether or not they were cancelled...8.8 HighfirefoxRed HatAn invalid downcast from <code>nsTextNode</code> to <code>SVGElement</code> could have lead to...8.8 HighfirefoxRed HatCross-compartment wrappers wrapping a scripted proxy could have caused objects from other...8.8 HighfirefoxRed HatWhen encoding data from an <code>inputStream</code> in <code>xpcom</code> the size of the input...8.8 HighfirefoxRed HatA background script invoking <code>requestFullscreen</code> and then blocking the main thread...5.4 MediumfirefoxRed HatPermission prompts for opening external schemes were only shown for <code>ContentPrincipals</code...8.8 HighfirefoxRed HatThe <code>Content-Security-Policy-Report-Only</code> header could allow an attacker to leak a...6.5 MediumfirefoxRed HatAn attacker could construct a PKCS 12 cert bundle in such a way that could allow for arbitrary...8.8 HighfirefoxRed HatMemory safety bugs fixed in Firefox 109 and Firefox ESR 102.78.8 HighfirefoxRed HatCalls to console.log allowed bypassing Content Security Policy via format directive6.5 MediumfirefoxRed HatContent Security Policy wasn't being correctly applied to WebSockets in WebWorkers6.5 MediumfirefoxRed HatURL being dragged from cross-origin iframe into same tab triggers navigation6.5 MediumfirefoxRed HatMalicious command could be hidden in devtools output on Windows6.5 MediumfirefoxRed HatArbitrary file read from GTK drag and drop on Linux6.5 MediumfirefoxRed HatBy confusing the browser, the fullscreen notification could have been delayed or suppressed,...4.3 MediumfirefoxRed HatAn out of date library (libusrsctp) contained vulnerabilities that could potentially be exploited...8.8 HighfirefoxRed HatA use-after-free in WebGL extensions could have led to a potentially exploitable crash. This...9.8 CriticalfirefoxRed HatAn optimization in WebGL was incorrect in some cases, and could have led to memory corruption and...8.8 HighfirefoxRed HatA missing check related to tex units could have led to a use-after-free and potentially...6.5 MediumfirefoxRed HatMozilla developers Randell Jesup, Valentin Gosu, Olli Pettay, and the Mozilla Fuzzing Team...8.8 HighfirefoxRed HatA file with a long filename could have had its filename truncated to remove the valid extension,...8.8 HighfirefoxRed HatAn attacker who compromised a content process could have partially escaped the sandbox to read...8.6 HighfirefoxRed HatMozilla developers Andrew McCreight and Gabriele Svelto reported memory safety bugs present in...8.8 HighfirefoxRed HatUse tables inside of an iframe, an attacker could have caused iframe contents to be rendered...6.5 MediumfirefoxRed HatIf a custom mouse cursor is specified in CSS, under certain circumstances the cursor could have...6.1 MediumfirefoxRed HatKeyboard events reference strings like "KeyA" that were at fixed, known, and widely-spread...6.5 MediumfirefoxRed HatWhen resolving a symlink such as <code>file:///proc/self/fd/1</code>, an error message may be...8.8 HighfirefoxRed HatCross-Site Tracing occurs when a server will echo a request back via the Trace method, allowing...6.1 MediumfirefoxRed HatWhen a ServiceWorker intercepted a request with <code>FetchEvent</code>, the origin of the...6.5 MediumfirefoxRed HatThe garbage collector could have been aborted in several states and zones and <code>GCRuntime:...8.8 HighfirefoxRed HatThrough a series of popups that reuse windowName, an attacker can cause a window to go fullscreen...6.5 MediumfirefoxRed HatIf an out-of-memory condition occurred when creating a JavaScript global, a JavaScript realm may...9.8 CriticalfirefoxRed HatFreeing arbitrary <code>nsIInputStream</code>'s on a different thread than creation could have...6.5 MediumfirefoxRed HatThrough a series of popup and <code>window.print()</code> calls, an attacker can cause a window...6.5 MediumfirefoxRed HatService Workers should not be able to infer information about opaque cross-origin responses; but...6.5 MediumfirefoxRed HatIn libexpat through 2.4.9, there is a use-after free caused by overeager destruction of a shared...7.5 HighfirefoxRed HatMozilla developers Ashley Hale and the Mozilla Fuzzing Team reported memory safety bugs present...8.8 HighfirefoxRed HatIf a website called <code>window.print()</code> in a particular way, it could cause a denial of...6.5 MediumfirefoxRed HatCertain types of allocations were missing annotations that, if the Garbage Collector was in a...8.8 HighfirefoxRed HatA same-origin policy violation could have allowed the theft of cross-origin URL entries, leaking...8.1 HighfirefoxRed HatInconsistent data in instruction and data cache when creating wasm code could lead to a...6.5 MediumfirefoxRed HatAn out-of-bounds read can occur when decoding H264 video. This results in a potentially...5.5 MediumfirefoxRed HatMozilla developers Nika Layzell, Timothy Nikkel, Sebastian Hengst, Andreas Pehrson, and the...8.8 HighfirefoxRed HatConcurrent use of the URL parser with non-UTF-8 data was not thread-safe. This could lead to a...6.5 MediumfirefoxRed HatDuring iframe navigation, certain pages did not have their FeaturePolicy fully initialized...6.5 MediumfirefoxRed HatBy injecting a cookie with certain special characters, an attacker on a shared subdomain which is...6.5 Medium- Show moreLoading…