firefox vulnerabilities (openEuler)
1,191 vulnerabilities.
firefoxopenEulernextScaffoldPart in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.8.8 HighfirefoxopenEulerstoreAtts in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.8.8 HighfirefoxopenEulerIn doProlog in xmlparse.c in Expat (aka libexpat) before 2.4.3, an integer overflow exists for...8.1 HighfirefoxopenEulerIn Expat (aka libexpat) before 2.4.3, a left shift by 29 (or more) places in the storeAtts...8.8 HighfirefoxopenEulerIt was possible to construct specific XSLT markup that would be able to bypass an iframe sandbox....10.0 CriticalfirefoxopenEulerWhen a user loaded a Web Extensions context menu, the Web Extension could access the post...4.3 MediumfirefoxopenEulerThe 'Copy Image Link' context menu action would copy the final image URL after redirects. By...6.1 MediumfirefoxopenEulerWhen parsing internationalized domain names, high bits of the characters in the URLs were...4.3 MediumfirefoxopenEulerIt was possible to recreate previous cursor spoofing attacks against users with a zoomed native...4.3 MediumfirefoxopenEulerUsing the Location API in a loop could have caused severe application hangs and crashes. This...6.5 MediumfirefoxopenEulerDocuments loaded with the CSP sandbox directive could have escaped the sandbox's script...6.1 MediumfirefoxopenEulerUsing XMLHttpRequest, an attacker could have identified installed applications by probing error...6.5 MediumfirefoxopenEulerWhen invoking protocol handlers for external protocols, a supplied parameter URL containing...6.5 MediumfirefoxopenEulerWebExtensions with the correct permissions were able to create and install ServiceWorkers for...6.5 MediumfirefoxopenEulerFailure to correctly record the location of live pointers across wasm instance calls resulted in...8.8 HighfirefoxopenEulerBy misusing a race in our notification code, an attacker could have forcefully hidden the...4.3 MediumfirefoxopenEulerAn incorrect type conversion of sizes from 64bit to 32bit integers allowed an attacker to corrupt...8.8 HighfirefoxopenEulerUnder certain circumstances, asynchronous functions could have caused a navigation to fail but...6.5 MediumfirefoxopenEulerThe executable file warning was not presented when downloading .inetloc files, which, due to a...8.8 HighfirefoxopenEulerA use-after-free could have occured when an HTTP2 session object was released on a different...8.8 HighfirefoxopenEulerMozilla developers and community members reported memory safety bugs present in Firefox 93 and...8.8 HighfirefoxopenEulerDue to an unusual sequence of attacker-controlled events, a Javascript alert() dialog with...4.3 MediumfirefoxopenEulerBy displaying a form validity message in the correct location at the same time as a permission...4.3 MediumfirefoxopenEulerThe Opportunistic Encryption feature of HTTP2 (RFC 8164) allows a connection to be transparently...6.5 MediumfirefoxopenEulerThrough a series of navigations, Firefox could have entered fullscreen mode without notification...4.3 MediumfirefoxopenEulerWhen interacting with an HTML input element's file picker dialog with webkitdirectory set, a use...8.8 HighfirefoxopenEulerThe iframe sandbox rules were not correctly applied to XSLT stylesheets, allowing an iframe to...10.0 CriticalfirefoxopenEulerMozilla developers reported memory safety bugs present in Firefox 92 and Firefox ESR 91.1. Some...8.8 HighfirefoxopenEulerMozilla developers reported memory safety bugs present in Firefox 92. Some of these bugs showed...8.8 HighfirefoxopenEulerDuring process shutdown, a document could have caused a use-after-free of a languages service...7.5 HighfirefoxopenEulerThrough use of reportValidity() and window.open(), a plain-text validation message could have...6.5 MediumfirefoxopenEulerMozilla developers reported memory safety bugs present in Firefox 92 and Firefox ESR 91.1. Some...8.8 HighfirefoxopenEulerDuring operations on MessageTasks, a task may have been removed while it was still scheduled,...8.8 HighfirefoxopenEulerMozilla developers reported memory safety bugs present in Firefox 91. Some of these bugs showed...8.8 HighfirefoxopenEulerMixed-content checks were unable to analyze opaque origins which led to some mixed content being...6.5 MediumfirefoxopenEulerMozilla developers reported memory safety bugs present in Firefox 91 and Firefox ESR 78.13. Some...8.8 HighfirefoxopenEulerFirefox incorrectly accepted a newline in a HTTP/3 header, interpretting it as two separate...8.1 HighfirefoxopenEulerMozilla developers and community members reported memory safety bugs present in Firefox 90. Some...8.8 HighfirefoxopenEulerMozilla developers reported memory safety bugs present in Firefox 90 and Firefox ESR 78.12. Some...8.8 HighfirefoxopenEulerFirefox incorrectly treated an inline list-item element as a block element, resulting in an out...8.8 HighfirefoxopenEulerAfter requesting multiple permissions, and closing the first permission panel, subsequent...6.5 MediumfirefoxopenEulerA suspected race condition when calling getaddrinfo led to memory corruption and a potentially...8.1 HighfirefoxopenEulerA use-after-free vulnerability in media channels could have led to memory corruption and a...8.8 HighfirefoxopenEulerInstruction reordering resulted in a sequence of instructions that would cause an object to be...8.8 HighfirefoxopenEulerDue to incorrect JIT optimization, we incorrectly interpreted data from the wrong type of object,...6.5 MediumfirefoxopenEulerAn issue present in lowering/register allocation could have led to obscure but deterministic...8.8 HighfirefoxopenEulerUninitialized memory in a canvas object could have caused an incorrect free() leading to memory...8.8 HighfirefoxopenEulerData race in crossbeam-deque9.8 CriticalfirefoxopenEulerMozilla developers reported memory safety bugs present in Firefox 89. Some of these bugs showed...8.8 HighfirefoxopenEulerThrough a series of DOM manipulations, a message, over which the attacker had control of the text...6.5 Medium- Show moreLoading…