librewolf vulnerabilities (Alpine)
353 vulnerabilities.
librewolfAlpineAn attacker could have exploited a timing attack by sending a large number of allowCredential...6.5 MediumlibrewolfAlpineA crafted CMS message could have been processed incorrectly, leading to an invalid memory read,...8.8 HighlibrewolfAlpineOn arm64, WASM code could have resulted in incorrect assembly generation leading to a register...8.8 HighlibrewolfAlpineWhen exiting fullscreen mode, an iframe could have confused the browser about the current state...6.5 MediumlibrewolfAlpineA malicious webpage could have caused an out-of-bounds write in WebGL, leading to memory...9.8 CriticallibrewolfAlpineA malicious website could have learned the size of a cross-origin resource that supported Range...9.8 CriticallibrewolfAlpineUse after free in Codecs in Google Chrome prior to 101.0.4951.41 allowed a remote attacker to...8.8 HighlibrewolfAlpineIf an attacker was able to corrupt the methods of an Array object in JavaScript via prototype...8.8 HighlibrewolfAlpineAn attacker could have sent a message to the parent process where the contents were used to...8.8 HighlibrewolfAlpineMozilla developers Gabriele Svelto, Randell Jesup and the Mozilla Fuzzing Team reported memory...8.8 HighlibrewolfAlpineThe Performance API did not properly hide the fact whether a request cross-origin resource has...4.3 MediumlibrewolfAlpineMozilla developers Andrew McCreight, Gabriele Svelto, Tom Ritter and the Mozilla Fuzzing Team...9.8 CriticallibrewolfAlpineFirefox behaved slightly differently for already known resources when loading CSS resources...6.5 MediumlibrewolfAlpineWhen reusing existing popups Firefox would have allowed them to cover the fullscreen notification...6.5 MediumlibrewolfAlpineRequests initiated through reader mode did not properly omit cookies with a SameSite attribute....6.1 MediumlibrewolfAlpineAn improper implementation of the new iframe sandbox keyword <code>allow-top-navigation-by-user...6.1 MediumlibrewolfAlpineDocuments in deeply-nested cross-origin browsing contexts could have obtained permissions granted...8.8 HighlibrewolfAlpineMozilla developers and community members Randell Jesup, Sebastian Hengst, and the Mozilla Fuzzing...8.8 HighlibrewolfAlpineIn unusual circumstances, selecting text could cause text selection caching to behave incorrectly...6.5 MediumlibrewolfAlpineSVG's <code><use></code> element could have been used to load unexpected content that could...8.8 HighlibrewolfAlpineThe sourceMapURL feature in devtools was missing security checks that would have allowed a...6.5 MediumlibrewolfAlpineMozilla developers and community members Nika Layzell, Andrew McCreight, Gabriele Svelto, and the...8.8 HighlibrewolfAlpineDue to a layout change, iframe contents could have been rendered outside of its border. This...5.4 MediumlibrewolfAlpineWhen generating the assembly code for <code>MLoadTypedArrayElementHole</code>, an incorrect...6.5 MediumlibrewolfAlpineBy using a link with <code>rel="localization"</code> a use-after-free could have been triggered...6.5 MediumlibrewolfAlpineIf a compromised content process sent an unexpected number of WebAuthN Extensions in a Register...8.8 HighlibrewolfAlpine<code>NSSToken</code> objects were referenced via direct points, and could have been accessed in...6.5 MediumlibrewolfAlpineIn unusual circumstances, an individual thread may outlive the thread's manager during shutdown....6.5 MediumlibrewolfAlpineWhile the text displayed in Autofill tooltips cannot be directly read by JavaScript, the text was...4.3 MediumlibrewolfAlpineMozilla developers Kershaw Chang, Ryan VanderMeulen, and Randell Jesup reported memory safety...8.8 HighlibrewolfAlpineWhen installing an add-on, Firefox verified the signature before prompting the user; but while...7.5 HighlibrewolfAlpineIf an attacker could control the contents of an iframe sandboxed with <code>allow-popups</code>...9.6 CriticallibrewolfAlpineWhen resizing a popup after requesting fullscreen access, the popup would not display the...4.3 MediumlibrewolfAlpineAn attacker could have caused a use-after-free by forcing a text reflow in an SVG object leading...8.8 HighlibrewolfAlpineRegular expression denial of service in Rust's regex crate7.5 HighlibrewolfAlpineAn unexpected message in the WebGPU IPC framework could lead to a use-after-free and exploitable...9.6 CriticallibrewolfAlpineRemoving an XSLT parameter during processing could have lead to an exploitable use-after-free. We...8.8 HighlibrewolfAlpineA Time-of-Check Time-of-Use bug existed in the Maintenance (Updater) Service that could be abused...7.1 HighlibrewolfAlpineMozilla developers Paul Adenot and the Mozilla Fuzzing Team reported memory safety bugs present...8.8 HighlibrewolfAlpineWeb-accessible extension pages (pages with a moz-extension:// scheme) were not correctly...8.8 HighlibrewolfAlpineWhen importing resources using Web Workers, error messages would distinguish the difference...6.5 MediumlibrewolfAlpineIf a document created a sandboxed iframe without <code>allow-scripts</code>, and subsequently...9.6 CriticallibrewolfAlpineRemote Agent, used in WebDriver, did not validate the Host or Origin headers. This could have...6.5 MediumlibrewolfAlpineIf a user was convinced to drag and drop an image to their desktop or other folder, the resulting...8.8 HighlibrewolfAlpineBy using XSL Transforms, a malicious webserver could have served a user an XSL document that...8.8 HighlibrewolfAlpineIf a user installed an extension of a particular type, the extension could have auto-updated...6.5 MediumlibrewolfAlpineMozilla developers and community members Gabriele Svelto, Sebastian Hengst, Randell Jesup, Luan...8.8 HighlibrewolfAlpineA race condition could have allowed bypassing the fullscreen notification which could have lead...5.9 MediumlibrewolfAlpineThe constructed curl command from the "Copy as curl" feature in DevTools was not properly escaped...8.8 HighlibrewolfAlpineMozilla developers Christian Holler and Jason Kratzer reported memory safety bugs present in...8.8 High- Show moreLoading…