| CVE-2024-0748 |
A compromised content process could have updated the document URI
|
4.3
Medium
|
Jan 23, 2024 |
| CVE-2024-0745 |
The WebAudio `OscillatorNode` object was susceptible to a stack buffer overflow
|
8.8
High
|
Jan 23, 2024 |
| CVE-2024-0743 |
An unchecked return value in TLS handshake code could have caused a potentially exploitable crash
|
7.5
High
|
Jan 23, 2024 |
| CVE-2024-0744 |
In some circumstances, JIT compiled code could have dereferenced a wild pointer value
|
7.5
High
|
Jan 23, 2024 |
| CVE-2024-0753 |
In specific HSTS configurations an attacker could have bypassed HSTS on a subdomain
|
6.5
Medium
|
Jan 23, 2024 |
| CVE-2024-0755 |
Memory safety bugs present in Firefox 121, Firefox ESR 115.6, and Thunderbird 115.6
|
8.8
High
|
Jan 23, 2024 |
| CVE-2024-0751 |
A malicious devtools extension could have been used to escalate privileges
|
8.8
High
|
Jan 23, 2024 |
| CVE-2024-0750 |
A bug in popup notifications delay calculation could have made it possible for an attacker to trick a user into granting…
|
8.8
High
|
Jan 23, 2024 |
| CVE-2024-0749 |
A phishing site could have repurposed an `about:` dialog to show phishing content with an incorrect origin in the…
|
4.3
Medium
|
Jan 23, 2024 |
| CVE-2024-0747 |
When a parent page loaded a child in an iframe with `unsafe-inline`, the parent Content Security Policy could have…
|
6.5
Medium
|
Jan 23, 2024 |
| CVE-2024-0746 |
A Linux user opening the print preview dialog could have caused the browser to crash
|
6.5
Medium
|
Jan 23, 2024 |
| CVE-2024-0742 |
It was possible for certain browser prompts and dialogs to be activated or dismissed unintentionally by the user due…
|
4.3
Medium
|
Jan 23, 2024 |
| CVE-2024-0741 |
An out of bounds write in ANGLE could have allowed an attacker to corrupt memory leading to a potentially exploitable…
|
6.5
Medium
|
Jan 23, 2024 |
| CVE-2023-6873 |
Memory safety bugs present in Firefox 120
|
Not rated
|
Dec 19, 2023 |
| CVE-2023-6872 |
Browser tab titles were being leaked by GNOME to system logs
|
Not rated
|
Dec 19, 2023 |
| CVE-2023-6871 |
Under certain conditions, Firefox did not display a warning when a user attempted to navigate to a new protocol handler
|
Not rated
|
Dec 19, 2023 |
| CVE-2023-6870 |
Applications which spawn a Toast notification in a background thread may have obscured fullscreen notifications…
|
Not rated
|
Dec 19, 2023 |
| CVE-2023-6869 |
A `<dialog>` element could have been manipulated to paint content outside of a sandboxed iframe
|
6.5
Medium
|
Dec 19, 2023 |
| CVE-2023-6868 |
In some instances, the user-agent would allow push requests which lacked a valid VAPID even though the push manager…
|
Not rated
|
Dec 19, 2023 |
| CVE-2023-6867 |
The timing of a button click causing a popup to disappear was approximately the same length as the anti-clickjacking…
|
Not rated
|
Dec 19, 2023 |
| CVE-2023-6866 |
TypedArrays can be fallible and lacked proper exception handling
|
8.8
High
|
Dec 19, 2023 |
| CVE-2023-6865 |
`EncryptingOutputStream` was susceptible to exposing uninitialized data
|
Not rated
|
Dec 19, 2023 |
| CVE-2023-6135 |
Multiple NSS NIST curves were susceptible to a side-channel attack known as "Minerva"
|
Not rated
|
Dec 19, 2023 |
| CVE-2023-6864 |
Memory safety bugs present in Firefox 120, Firefox ESR 115.5, and Thunderbird 115.5
|
Not rated
|
Dec 19, 2023 |
| CVE-2023-6863 |
The `ShutdownObserver()` was susceptible to potentially undefined behavior due to its reliance on a dynamic type that…
|
Not rated
|
Dec 19, 2023 |