Memory corruption in Mozilla Firefox
Memory safety bugs present in Firefox 130.
13 records
Memory safety bugs present in Firefox 130.
A specially crafted filename containing a large number of spaces could obscure the file's extension when displayed in the download dialog.
A user who enables full-screen mode on a specially crafted web page could potentially be prevented from exiting full screen mode.
Memory safety bugs present in Firefox 130, Firefox ESR 128.2, and Thunderbird 128.2.
Memory safety bugs present in Firefox 130, Firefox ESR 115.15, Firefox ESR 128.2, and Thunderbird 128.2.
A potential memory corruption vulnerability could be triggered if an attacker had the ability to trigger an OOM at a specific moment during JIT compilation.
A website configured to initiate a specially crafted WebTransport session could crash the Firefox process leading to a denial of service condition.
By checking the result of calls to `window.open` with specifically set protocol handlers, an attacker could determine if the application which implements that protocol handler is installed.
A missing delay in directory upload UI could have made it possible for an attacker to trick a user into granting permission via clickjacking.
It is currently unknown if this issue is exploitable but a condition may arise where the structured clone of certain objects could lead to memory corruption.
An attacker could, via a specially crafted multipart response, execute arbitrary JavaScript under the `resource://devtools` origin.
An attacker could, via a specially crafted multipart response, execute arbitrary JavaScript under the `resource://pdf.js` origin.
A compromised content process could have allowed for the arbitrary loading of cross-origin pages.