Mozilla has released patches of Firefox 111, which remediates around dozen vulnerabilities, including potentially serious issues.
In total 13 CVEs got released, out of which seven have been assigned a ‘high’ severity rating. Three of them only impact Firefox for Android, that allows the threat actors to hide full screen notifications this can lead to user confusion or spoofing attacks and open third-party apps without a prompt.
Other high-severity flaws patched with the latest Firefox updates can lead to arbitrary code execution and information disclosure.
|CVE-2023- 28159||Fullscreen Notification could have been hidden by download popups on Android||High||The fullscreen notification could have been hidden on Firefox for Android by using download popups, resulting in potential user confusion or spoofing attacks.|
|CVE-2023-25748||Fullscreen Notification could have been hidden by window prompts on Android||High||By displaying a prompt with a long description, the fullscreen notification could have been hidden, resulting in potential user confusion or spoofing attacks.|
|CVE-2023-25749||Firefox for Android may have opened third-party apps without a prompt||High||Android applications with unpatched vulnerabilities can be launched from a browser using Intents, exposing users to these vulnerabilities. Firefox will now confirm with users that they want to launch an external application before doing so.|
|CVE-2023-25750||Potential Service Worker cache leak during private browsing mode||High||Under certain circumstances, a ServiceWorker’s offline cache may have leaked to the file system when using private browsing mode.|
|CVE-2023-25751||Incorrect code generation during JIT compilation||High||While invalidating JIT code while following an iterator, the newly generated code could be overwritten incorrectly. This could lead to a potentially exploitable crash.|
|CVE-2023-28176||Memory safety bugs fixed in Firefox 111 and Firefox ESR 102.9||High||A memory safety bugs present in Firefox 110 and Firefox ESR 102.8. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code.|
|CVE-2023-28177||Memory safety bugs fixed in Firefox 111||High||A memory safety bugs present in Firefox 110. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code.|
|CVE-2023-28160||Redirect to Web Extension files may have leaked local path||Moderate||While 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.|
|CVE-2023-28164||URL being dragged from a removed cross-origin iframe into the same tab triggered navigation||Moderate||Dragging a URL from a cross-origin iframe that was removed during the drag could have led to user confusion and website spoofing attacks.|
|CVE-2023-28161||ne-time permissions granted to a local file were extended to other local files loaded in the same tab||Moderate||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. This is potentially dangerous if the local files came from different sources, such as in a download directory.|
|CVE-2023-28162||Invalid downcast in Worklets||Moderate||While implementing AudioWorklets, some code may have casted one type to another, invalid, dynamic type. This could have led to a potentially exploitable crash.|
|CVE-2023-25752||Potential out-of-bounds when accessing throttled streams||Moderate||When accessing throttled streams, the count of available bytes needed to be checked in the calling function to be within bounds. This may have lead future code to be incorrect and vulnerable.|
|CVE-2023-28163||Windows Save As dialog resolved environment variables||Moderate||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.|