mozjs52 vulnerabilities (Ubuntu)
1,829 vulnerabilities.
mozjs52UbuntuWhen network partitioning was enabled, e.g. as a result of Enhanced Tracking Protection settings,...4.3 Mediummozjs52UbuntuA use-after-free vulnerability was found via testing, and traced to an out-of-date Cairo library....8.8 Highmozjs52UbuntuMozilla developers reported memory safety bugs present in code shared between Firefox and...8.8 Highmozjs52UbuntuA malicious webpage could have triggered a use-after-free, memory corruption, and a potentially...8.8 Highmozjs52UbuntuFirefox for Android would become unstable and hard-to-recover when a website opened too many...4.3 Mediummozjs52UbuntuAddress bar search suggestions in private browsing mode were re-using session data from normal...4.3 Mediummozjs52UbuntuA malicious website that causes an HTTP Authentication dialog to be spawned could trick the built...5.3 Mediummozjs52UbuntuA locally-installed hostile program could send `WM_COPYDATA` messages that Firefox would process...7.1 Highmozjs52UbuntuMozilla developers reported memory safety bugs present in Firefox 88 and Firefox ESR 78.11. Some...8.8 Highmozjs52UbuntuMozilla developers reported memory safety bugs present in Firefox 88. Some of these bugs showed...8.8 Highmozjs52UbuntuWhen styling and rendering an oversized `<select>` element, Firefox did not apply correct...4.3 Mediummozjs52UbuntuFirefox used to cache the last filename used for printing a file. When generating a filename for...4.3 Mediummozjs52UbuntuWhen a user has already allowed a website to access microphone and camera, disabling camera...4.3 Mediummozjs52UbuntuWhen Web Render components were destructed, a race condition could have caused undefined behavior...7.5 Highmozjs52UbuntuMozilla developers and community members reported memory safety bugs present in Firefox 87. Some...8.8 Highmozjs52UbuntuPorts that were written as an integer overflow above the bounds of a 16-bit integer could have...8.8 Highmozjs52UbuntuThe WebAssembly JIT could miscalculate the size of a return type, which could lead to a null read...6.5 Mediummozjs52UbuntuWhen a user clicked on an FTP URL containing encoded newline characters (%0A and %0D), the...8.8 Highmozjs52UbuntuA compromised content process could have performed session history manipulations it should not...4.3 Mediummozjs52UbuntuA race condition with requestPointerLock() and setTimeout() could have resulted in a user...3.1 Lowmozjs52UbuntuIf a Blob URL was loaded through some unusual user interaction, it could have been loaded by the...8.8 Highmozjs52UbuntuThrough complicated navigations with new windows, an HTTP page could have inherited a secure lock...6.5 Mediummozjs52UbuntuDue to unexpected data type conversions, a use-after-free could have occurred when interacting...8.8 Highmozjs52UbuntuBy utilizing 3D CSS in conjunction with Javascript, content could have been rendered outside the...6.5 Mediummozjs52UbuntuWhen Responsive Design Mode was enabled, it used references to objects that were previously freed...8.8 Highmozjs52UbuntuA WebGL framebuffer was not initialized early enough, resulting in memory corruption and an out...8.8 Highmozjs52UbuntuMozilla developers reported memory safety bugs present in Firefox 86. Some of these bugs showed...8.8 Highmozjs52UbuntuA malicious extension with the 'search' permission could have installed a new search engine whose...6.5 Mediummozjs52UbuntuIf an attacker is able to alter specific about:config values (for example malware running on the...6.5 Mediummozjs52UbuntuA transient execution vulnerability, named Floating Point Value Injection (FPVI) allowed an...5.3 Mediummozjs52UbuntuMozilla developers and community members reported memory safety bugs present in Firefox 86 and...8.8 Highmozjs52UbuntuA malicious extension could have opened a popup window lacking an address bar. The title of the...6.5 Mediummozjs52UbuntuBy causing a transition on a parent node by removing a CSS rule, an invalid property for a marker...6.5 Mediummozjs52UbuntuUsing techniques that built on the slipstream research, a malicious webpage could have scanned...6.5 Mediummozjs52UbuntuA texture upload of a Pixel Buffer Object could have confused the WebGL code to skip binding the...8.1 Highmozjs52UbuntuMozilla developers reported memory safety bugs present in Firefox 85. Some of these bugs showed...8.8 Highmozjs52UbuntuFirefox for Android suffered from a time-of-check-time-of-use vulnerability that allowed a...5.3 Mediummozjs52UbuntuContext-specific code was included in a shared jump table; resulting in assertions being...6.5 Mediummozjs52UbuntuWhen processing a redirect with a conflicting Referrer-Policy, Firefox would have adopted the...6.5 Mediummozjs52UbuntuOne phishing tactic on the web is to provide a link with HTTP Auth. For example 'https://www...8.8 Highmozjs52UbuntuThe DOMParser API did not properly process '<noscript>' elements for escaping. This could be used...6.1 Mediummozjs52UbuntuThe developer page about:memory has a Measure function for exploring what object types the...6.5 Mediummozjs52UbuntuWhen accepting a malicious intent from other installed apps, Firefox for Android accepted...8.1 Highmozjs52UbuntuMozilla developers reported memory safety bugs present in Firefox 85 and Firefox ESR 78.7. Some...8.8 Highmozjs52UbuntuWhen trying to load a cross-origin resource in an audio/video context a decoding error may have...6.5 Mediummozjs52UbuntuAs specified in the W3C Content Security Policy draft, when creating a violation report, "User...4.3 Mediummozjs52UbuntuIf Content Security Policy blocked frame navigation, the full destination of a redirect served in...4.3 Mediummozjs52UbuntuMozilla developers reported memory safety bugs present in Firefox 84. Some of these bugs showed...8.8 Highmozjs52UbuntuMozilla developers reported memory safety bugs present in Firefox 84 and Firefox ESR 78.6. Some...8.8 Highmozjs52UbuntuWhen sharing geolocation during an active WebRTC share, Firefox could have reset the webRTC...4.3 Medium- Show moreLoading…