librewolf vulnerabilities (Alpine)
353 vulnerabilities.
librewolfAlpineInstruction reordering resulted in a sequence of instructions that would cause an object to be...8.8 HighlibrewolfAlpineDue to incorrect JIT optimization, we incorrectly interpreted data from the wrong type of object,...6.5 MediumlibrewolfAlpineAn issue present in lowering/register allocation could have led to obscure but deterministic...8.8 HighlibrewolfAlpineUninitialized memory in a canvas object could have caused an incorrect free() leading to memory...8.8 HighlibrewolfAlpineData race in crossbeam-deque9.8 CriticallibrewolfAlpineMozilla developers reported memory safety bugs present in Firefox 89. Some of these bugs showed...8.8 HighlibrewolfAlpineThrough a series of DOM manipulations, a message, over which the attacker had control of the text...6.5 MediumlibrewolfAlpineWhen network partitioning was enabled, e.g. as a result of Enhanced Tracking Protection settings,...4.3 MediumlibrewolfAlpineA use-after-free vulnerability was found via testing, and traced to an out-of-date Cairo library....8.8 HighlibrewolfAlpineMozilla developers reported memory safety bugs present in code shared between Firefox and...8.8 HighlibrewolfAlpineA malicious webpage could have triggered a use-after-free, memory corruption, and a potentially...8.8 HighlibrewolfAlpineLack of escaping allowed HTML injection when a webpage was viewed in Reader View. While a Content...6.1 MediumlibrewolfAlpineFirefox for Android would become unstable and hard-to-recover when a website opened too many...4.3 MediumlibrewolfAlpineAddress bar search suggestions in private browsing mode were re-using session data from normal...4.3 MediumlibrewolfAlpineA malicious website that causes an HTTP Authentication dialog to be spawned could trick the built...5.3 MediumlibrewolfAlpineOut of bounds write in ANGLE in Google Chrome prior to 91.0.4472.101 allowed a remote attacker to...8.8 HighlibrewolfAlpineMozilla developers reported memory safety bugs present in Firefox 88 and Firefox ESR 78.11. Some...8.8 HighlibrewolfAlpineMozilla developers reported memory safety bugs present in Firefox 88. Some of these bugs showed...8.8 HighlibrewolfAlpineWhen styling and rendering an oversized `<select>` element, Firefox did not apply correct...4.3 MediumlibrewolfAlpineFirefox used to cache the last filename used for printing a file. When generating a filename for...4.3 MediumlibrewolfAlpineWhen a user has already allowed a website to access microphone and camera, disabling camera...4.3 MediumlibrewolfAlpineWhen Web Render components were destructed, a race condition could have caused undefined behavior...7.5 HighlibrewolfAlpineMozilla developers and community members reported memory safety bugs present in Firefox 87. Some...8.8 HighlibrewolfAlpinePorts that were written as an integer overflow above the bounds of a 16-bit integer could have...8.8 HighlibrewolfAlpineThe WebAssembly JIT could miscalculate the size of a return type, which could lead to a null read...6.5 MediumlibrewolfAlpineWhen a user clicked on an FTP URL containing encoded newline characters (%0A and %0D), the...8.8 HighlibrewolfAlpineA compromised content process could have performed session history manipulations it should not...4.3 MediumlibrewolfAlpineA race condition with requestPointerLock() and setTimeout() could have resulted in a user...3.1 LowlibrewolfAlpineIf a Blob URL was loaded through some unusual user interaction, it could have been loaded by the...8.8 HighlibrewolfAlpineThrough complicated navigations with new windows, an HTTP page could have inherited a secure lock...6.5 MediumlibrewolfAlpineDue to unexpected data type conversions, a use-after-free could have occurred when interacting...8.8 HighlibrewolfAlpineBy utilizing 3D CSS in conjunction with Javascript, content could have been rendered outside the...6.5 MediumlibrewolfAlpineWhen Responsive Design Mode was enabled, it used references to objects that were previously freed...8.8 HighlibrewolfAlpineA WebGL framebuffer was not initialized early enough, resulting in memory corruption and an out...8.8 HighlibrewolfAlpineMozilla developers reported memory safety bugs present in Firefox 86. Some of these bugs showed...8.8 HighlibrewolfAlpineA malicious extension with the 'search' permission could have installed a new search engine whose...6.5 MediumlibrewolfAlpineIf an attacker is able to alter specific about:config values (for example malware running on the...6.5 MediumlibrewolfAlpineMozilla developers and community members reported memory safety bugs present in Firefox 86 and...8.8 HighlibrewolfAlpineA malicious extension could have opened a popup window lacking an address bar. The title of the...6.5 MediumlibrewolfAlpineBy causing a transition on a parent node by removing a CSS rule, an invalid property for a marker...6.5 MediumlibrewolfAlpineUsing techniques that built on the slipstream research, a malicious webpage could have scanned...6.5 MediumlibrewolfAlpineA texture upload of a Pixel Buffer Object could have confused the WebGL code to skip binding the...8.1 HighlibrewolfAlpineMozilla developers reported memory safety bugs present in Firefox 85. Some of these bugs showed...8.8 HighlibrewolfAlpineFirefox for Android suffered from a time-of-check-time-of-use vulnerability that allowed a...5.3 MediumlibrewolfAlpineNavigations through the Android-specific `intent` URL scheme could have been misused to escape...7.4 HighlibrewolfAlpineAn XSS bug in internal error pages could have led to various spoofing attacks, including other...6.1 MediumlibrewolfAlpineContext-specific code was included in a shared jump table; resulting in assertions being...6.5 MediumlibrewolfAlpineWhen processing a redirect with a conflicting Referrer-Policy, Firefox would have adopted the...6.5 MediumlibrewolfAlpineOne phishing tactic on the web is to provide a link with HTTP Auth. For example 'https://www...8.8 HighlibrewolfAlpineThe DOMParser API did not properly process '<noscript>' elements for escaping. This could be used...6.1 Medium- Show moreLoading…