firefox vulnerabilities (openEuler)
1,191 vulnerabilities.
firefoxopenEulerAn out-of-bounds read could have led to an exploitable crash when parsing HTML with DOMParser in...7.5 HighfirefoxopenEulerA bug in popup notifications delay calculation could have made it possible for an attacker to...8.8 HighfirefoxopenEulerIn some circumstances, a stale value could have been used for a global variable in WASM JIT...5.3 MediumfirefoxopenEulerOffscreen Canvas did not properly track cross-origin tainting, which could have been used to...5.3 MediumfirefoxopenEulerUse-after-free in workers8.8 HighfirefoxopenEulerMemory safety bugs present in Firefox 114. Some of these bugs showed evidence of memory...8.8 HighfirefoxopenEulerA website could prevent a user from exiting full-screen mode via alert and prompt calls. This...6.5 MediumfirefoxopenEulerA use-after-free condition existed in `NotifyOnHistoryReload` where a `LoadingSessionHistoryEntry...8.8 HighfirefoxopenEulerUploading files which contain symlinks may have allowed an attacker to trick a user into...6.5 MediumfirefoxopenEulerThe use of RTL Arabic characters in the address bar may have allowed for URL spoofing. This...6.5 MediumfirefoxopenEulerA website could have obscured the fullscreen notification by using an option element by...6.5 MediumfirefoxopenEulerInsufficient validation in the Drag and Drop API in conjunction with social engineering, may have...7.8 HighfirefoxopenEulerWhen Firefox is configured to block storage of all cookies, it was still possible to store data...6.5 MediumfirefoxopenEulerMemory safety bugs present in Firefox 114, Firefox ESR 102.12, and Thunderbird 102.12. Some of...8.8 HighfirefoxopenEulerWhen opening Diagcab files, Firefox did not warn the user that these files may contain malicious...7.8 HighfirefoxopenEulerA website could have obscured the fullscreen notification by using a URL with a scheme handled by...6.5 MediumfirefoxopenEulerCross-compartment wrappers wrapping a scripted proxy could have caused objects from other...8.8 HighfirefoxopenEulerAn attacker could have triggered a use-after-free condition when creating a WebRTC connection...8.8 HighfirefoxopenEulerMemory safety bugs present in Firefox 113. Some of these bugs showed evidence of memory...9.8 CriticalfirefoxopenEulerWhen choosing a site-isolated process for a document loaded from a data: URL that was the result...6.1 MediumfirefoxopenEulerMemory safety bugs present in Firefox 112. Some of these bugs showed evidence of memory...9.8 CriticalfirefoxopenEulerMozilla developers and community members Gabriele Svelto, Andrew Osmond, Emily McDonough,...8.8 HighfirefoxopenEulerWhen reading a file, an uninitialized value could have been used as read limit. This...8.8 HighfirefoxopenEulerAn attacker could have positioned a <code>datalist</code> element to obscure the address bar....4.3 MediumfirefoxopenEulerA type checking bug would have led to invalid code being compiled. This vulnerability affects...6.5 MediumfirefoxopenEulerDocuments were incorrectly assuming an ordering of principal objects when ensuring we were...6.5 MediumfirefoxopenEulerA maliciously crafted favicon could have led to an out of memory crash. This vulnerability...7.5 HighfirefoxopenEulerService workers could reveal script base URL due to dynamic `import()`. This vulnerability...5.3 MediumfirefoxopenEulerA missing delay in popup notifications could have made it possible for an attacker to trick a...8.8 HighfirefoxopenEulerAn out-of-bound read could have led to a crash in the RLBox Expat driver. This vulnerability...6.5 MediumfirefoxopenEulerIn multiple cases browser prompts could have been obscured by popups controlled by content. These...4.3 MediumfirefoxopenEulerMozilla developers Randell Jesup, Andrew McCreight, Gabriele Svelto, and the Mozilla Fuzzing Team...8.8 HighfirefoxopenEulerUnder certain circumstances, a call to the <code>bind</code> function may have resulted in the...6.5 MediumfirefoxopenEulerWhen a secure cookie existed in the Firefox cookie jar an insecure cookie for the same domain...6.5 MediumfirefoxopenEulerAn attacker could have caused memory corruption and a potentially exploitable use-after-free of a...8.8 HighfirefoxopenEulerUsing a redirect embedded into <code>sourceMappingUrls</code> could allow for navigation to...6.1 MediumfirefoxopenEulerUnder specific circumstances a WebExtension may have received a <code>jar:file:///</code> URI...4.3 MediumfirefoxopenEulerMultiple race conditions in the font initialization could have led to memory corruption and...7.5 HighfirefoxopenEulerUse after free in libwebp5.3 MediumfirefoxopenEulerMozilla developers Randell Jesup, Andrew Osmond, Sebastian Hengst, Andrew McCreight, and the...8.8 HighfirefoxopenEulerA wrong lowering instruction in the ARM64 Ion compiler resulted in a wrong optimization result....6.5 MediumfirefoxopenEulerFirefox did not properly handle downloads of files ending in <code>.desktop</code>, which can be...8.8 HighfirefoxopenEulerWhen handling the filename directive in the Content-Disposition header, the filename would be...8.8 HighfirefoxopenEulerAn attacker could cause the memory manager to incorrectly free a pointer that addresses attacker...8.8 HighfirefoxopenEulerFollowing a Garbage Collector compaction, weak maps may have been accessed before they were...6.5 MediumfirefoxopenEulerA website could have obscured the fullscreen notification by using a combination of <code>window...4.3 MediumfirefoxopenEulerUnexpected data returned from the Safe Browsing API could have led to memory corruption and a...6.5 MediumfirefoxopenEulerMozilla developers and community members Calixte Denizet, Gabriele Svelto, Andrew McCreight, and...8.8 HighfirefoxopenEulerMozilla developers Timothy Nikkel, Andrew McCreight, and the Mozilla Fuzzing Team reported memory...8.8 HighfirefoxopenEulerDragging a URL from a cross-origin iframe that was removed during the drag could have led to user...6.5 Medium- Show moreLoading…