Out-of-bounds write in Mozilla Firefox
Memory safety bugs present in Firefox 110.
13 records
Memory safety bugs present in Firefox 110.
Memory safety bugs present in Firefox 110 and Firefox ESR 102.8.
Dragging a URL from a cross-origin iframe that was removed during the drag could have led to user confusion and website spoofing attacks.
When downloading files through the Save As dialog on Windows with suggested filenames containing environment variable names, Windows would have resolved those in the context of the current user.
While implementing AudioWorklets, some code may have casted one type to another, invalid, dynamic type.
If temporary "one-time" permissions, such as the ability to use the Camera, were granted to a document loaded using a file: URL, that permission persisted in that tab for all other documents loaded from a file: URL.
When following a redirect to a publicly accessible web extension file, the URL may have been translated to the actual local path, leaking potentially sensitive information.
The fullscreen notification could have been hidden on Firefox for Android by using download popups, resulting in potential user confusion or spoofing attacks.
When accessing throttled streams, the count of available bytes needed to be checked in the calling function to be within bounds.
Sometimes, when invalidating JIT code while following an iterator, the newly generated code could be overwritten incorrectly.
Under certain circumstances, a ServiceWorker's offline cache may have leaked to the file system when using private browsing mode.
Android applications with unpatched vulnerabilities can be launched from a browser using Intents, exposing users to these vulnerabilities.
By displaying a prompt with a long description, the fullscreen notification could have been hidden, resulting in potential user confusion or spoofing attacks.