firefox vulnerabilities (Rocky Linux)
848 vulnerabilities.
firefoxRocky LinuxMemory safety bugs present in Firefox 113, Firefox ESR 102.11, and Thunderbird 102.12. Some of...9.8 CriticalfirefoxRocky LinuxThe error page for sites with invalid TLS certificates was missing the activation-delay Firefox...3.1 LowfirefoxRocky LinuxMozilla developers and community members Gabriele Svelto, Andrew Osmond, Emily McDonough,...8.8 HighfirefoxRocky LinuxWhen reading a file, an uninitialized value could have been used as read limit. This...8.8 HighfirefoxRocky LinuxAn attacker could have positioned a <code>datalist</code> element to obscure the address bar....4.3 MediumfirefoxRocky LinuxA type checking bug would have led to invalid code being compiled. This vulnerability affects...6.5 MediumfirefoxRocky LinuxA missing delay in popup notifications could have made it possible for an attacker to trick a...8.8 HighfirefoxRocky LinuxAn out-of-bound read could have led to a crash in the RLBox Expat driver. This vulnerability...6.5 MediumfirefoxRocky LinuxIn multiple cases browser prompts could have been obscured by popups controlled by content. These...4.3 MediumfirefoxRocky LinuxMozilla developers Timothy Nikkel, Andrew McCreight, and the Mozilla Fuzzing Team reported memory...8.8 HighfirefoxRocky LinuxDragging a URL from a cross-origin iframe that was removed during the drag could have led to user...6.5 MediumfirefoxRocky LinuxWhile implementing AudioWorklets, some code may have casted one type to another, invalid, dynamic...8.8 HighfirefoxRocky LinuxWhen accessing throttled streams, the count of available bytes needed to be checked in the...6.5 MediumfirefoxRocky LinuxSometimes, when invalidating JIT code while following an iterator, the newly generated code could...6.5 MediumfirefoxRocky LinuxA lack of in app notification for entering fullscreen mode could have lead to a malicious website...7.5 HighfirefoxRocky LinuxMozilla developers Philipp and Gabriele Svelto reported memory safety bugs present in Firefox ESR...8.8 HighfirefoxRocky LinuxMozilla developers Kershaw Chang and the Mozilla Fuzzing Team reported memory safety bugs present...8.8 HighfirefoxRocky LinuxWhen importing a SPKI RSA public key as ECDSA P-256, the key would be handled incorrectly causing...6.5 MediumfirefoxRocky LinuxModule load requests that failed were not being checked as to whether or not they were cancelled...8.8 HighfirefoxRocky LinuxAn invalid downcast from <code>nsTextNode</code> to <code>SVGElement</code> could have lead to...8.8 HighfirefoxRocky LinuxCross-compartment wrappers wrapping a scripted proxy could have caused objects from other...8.8 HighfirefoxRocky LinuxWhen encoding data from an <code>inputStream</code> in <code>xpcom</code> the size of the input...8.8 HighfirefoxRocky LinuxA background script invoking <code>requestFullscreen</code> and then blocking the main thread...5.4 MediumfirefoxRocky LinuxPermission prompts for opening external schemes were only shown for <code>ContentPrincipals</code...8.8 HighfirefoxRocky LinuxThe <code>Content-Security-Policy-Report-Only</code> header could allow an attacker to leak a...6.5 MediumfirefoxRocky LinuxAn attacker could construct a PKCS 12 cert bundle in such a way that could allow for arbitrary...8.8 HighfirefoxRocky LinuxMemory safety bugs fixed in Firefox 109 and Firefox ESR 102.78.8 HighfirefoxRocky LinuxCalls to console.log allowed bypassing Content Security Policy via format directive6.5 MediumfirefoxRocky LinuxContent Security Policy wasn't being correctly applied to WebSockets in WebWorkers6.5 MediumfirefoxRocky LinuxURL being dragged from cross-origin iframe into same tab triggers navigation6.5 MediumfirefoxRocky LinuxMalicious command could be hidden in devtools output on Windows6.5 MediumfirefoxRocky LinuxArbitrary file read from GTK drag and drop on Linux6.5 MediumfirefoxRocky LinuxBy confusing the browser, the fullscreen notification could have been delayed or suppressed,...4.3 MediumfirefoxRocky LinuxAn out of date library (libusrsctp) contained vulnerabilities that could potentially be exploited...8.8 HighfirefoxRocky LinuxA use-after-free in WebGL extensions could have led to a potentially exploitable crash. This...9.8 CriticalfirefoxRocky LinuxAn optimization in WebGL was incorrect in some cases, and could have led to memory corruption and...8.8 HighfirefoxRocky LinuxA missing check related to tex units could have led to a use-after-free and potentially...6.5 MediumfirefoxRocky LinuxMozilla developers Randell Jesup, Valentin Gosu, Olli Pettay, and the Mozilla Fuzzing Team...8.8 HighfirefoxRocky LinuxA file with a long filename could have had its filename truncated to remove the valid extension,...8.8 HighfirefoxRocky LinuxAn attacker who compromised a content process could have partially escaped the sandbox to read...8.6 HighfirefoxRocky LinuxMozilla developers Andrew McCreight and Gabriele Svelto reported memory safety bugs present in...8.8 HighfirefoxRocky LinuxUse tables inside of an iframe, an attacker could have caused iframe contents to be rendered...6.5 MediumfirefoxRocky LinuxIf a custom mouse cursor is specified in CSS, under certain circumstances the cursor could have...6.1 MediumfirefoxRocky LinuxKeyboard events reference strings like "KeyA" that were at fixed, known, and widely-spread...6.5 MediumfirefoxRocky LinuxWhen resolving a symlink such as <code>file:///proc/self/fd/1</code>, an error message may be...8.8 HighfirefoxRocky LinuxCross-Site Tracing occurs when a server will echo a request back via the Trace method, allowing...6.1 MediumfirefoxRocky LinuxWhen a ServiceWorker intercepted a request with <code>FetchEvent</code>, the origin of the...6.5 MediumfirefoxRocky LinuxThe garbage collector could have been aborted in several states and zones and <code>GCRuntime:...8.8 HighfirefoxRocky LinuxThrough a series of popups that reuse windowName, an attacker can cause a window to go fullscreen...6.5 MediumfirefoxRocky LinuxIf an out-of-memory condition occurred when creating a JavaScript global, a JavaScript realm may...9.8 Critical- Show moreLoading…