Vulnerabilities

Memory safety bugs present in Firefox 132, Firefox ESR 128.4, and Thunderbird 128.4.

Missing thread synchronization primitives could have led to a data race on members of the PlaybackParams structure.

A null pointer dereference may have inadvertently occurred in `pk12util`, and specifically in the `SEC_ASN1DecodeItem_Util` function, when handling malformed or improperly formatted input files.

`NSC_DeriveKey` inadvertently assumed that the `phKey` parameter is always non-NULL.

A flaw in handling fullscreen transitions may have inadvertently caused the application to become stuck in fullscreen mode when a modal dialog was opened during the transition.

A double-free issue could have occurred in `sec_pkcs7_decoder_start_decrypt()` when handling an error path.

When handling keypress events, an attacker may have been able to trick a user into bypassing the "Open Executable File?" confirmation dialog.

The application failed to account for exceptions thrown by the `loadManifestFromFile` method during add-on signature verification.

A crafted URL containing Arabic script and whitespace characters could have hidden the true origin of the page, resulting in a potential spoofing attack.

Enhanced Tracking Protection's Strict mode may have inadvertently allowed a CSP `frame-src` bypass and DOM-based XSS through the Google SafeFrame shim in the Web Compatibility extension.

The executable file warning was not presented when downloading .library-ms files.

Copying sensitive information from Private Browsing tabs on Android, such as passwords, may have inadvertently stored data in the cloud-based clipboard history if enabled.

The incorrect domain may have been displayed in the address bar during an interrupted navigation attempt.

An attacker could cause a select dropdown to be shown over another tab; this could have led to user confusion and possible spoofing attacks.

Malicious websites may have been able to perform user intent confirmation through tapjacking.

Certain WebGL operations on Apple silicon M series devices could have lead to an out-of-bounds write and memory corruption due to a flaw in Apple's GPU driver.