Out-of-bounds write in Mozilla Firefox
Memory safety bugs present in Firefox 114.
13 records
Memory safety bugs present in Firefox 114.
A website could prevent a user from exiting full-screen mode via alert and prompt calls.
A use-after-free condition existed in `NotifyOnHistoryReload` where a `LoadingSessionHistoryEntry` object was freed and a reference to that object remained.
Uploading files which contain symlinks may have allowed an attacker to trick a user into submitting sensitive data to a malicious website.
The use of RTL Arabic characters in the address bar may have allowed for URL spoofing.
A website could have obscured the fullscreen notification by using an option element by introducing lag via an expensive computational function.
Insufficient validation in the Drag and Drop API in conjunction with social engineering, may have allowed an attacker to trick end-users into creating a shortcut to local system files.
When Firefox is configured to block storage of all cookies, it was still possible to store data in localstorage by using an iframe with a source of 'about:blank'.
Memory safety bugs present in Firefox 114, Firefox ESR 102.12, and Thunderbird 102.12.
When opening Diagcab files, Firefox did not warn the user that these files may contain malicious code.
A website could have obscured the fullscreen notification by using a URL with a scheme handled by an external program, such as a mailto URL.
Cross-compartment wrappers wrapping a scripted proxy could have caused objects from other compartments to be stored in the main compartment resulting in a use-after-free.
An attacker could have triggered a use-after-free condition when creating a WebRTC connection over HTTPS.