1,441 results · Feed
-
High 8.1
Memory safety bugs present in Firefox 122. Some of these bugs showed evidence of memory corruption and we presume that …
-
Critical 9.8
The `fetch()` API and navigation incorrectly shared the same cache, as the cache key did not include the optional heade…
-
High 8.3
When opening a website using the `firefox://` protocol handler, SameSite cookies were not properly respected. This vuln…
-
High 8.1
Memory safety bugs present in Firefox 122, Firefox ESR 115.7, and Thunderbird 115.7. Some of these bugs showed evidence…
-
High 7.5
Incorrect code generation could have led to unexpected numeric conversions and potential undefined behavior.*Note:* Thi…
-
Medium 6.1
Set-Cookie response headers were being incorrectly honored in multipart HTTP responses. If an attacker could control th…
-
Medium 6.1
If a website set a large custom cursor, portions of the cursor could have overlapped with the permission dialog, potent…
-
Medium 6.1
A malicious website could have used a combination of exiting fullscreen mode and `requestPointerLock` to cause the user…
-
Medium 6.5
Through a series of API calls and redirects, an attacker-controlled alert dialog could have been displayed on another w…
-
Medium 4.3
A website could have obscured the fullscreen notification by using a dropdown select input element. This could have led…
-
High 7.5
When storing and re-accessing data on a networking channel, the length of buffers may have been confused, resulting in …
-
Medium 6.5
Some WASM source files could have caused a crash when loaded in devtools. This vulnerability affects Firefox < 122.
-
High 8.8
The WebAudio `OscillatorNode` object was susceptible to a stack buffer overflow. This could have led to a potentially e…
-
Medium 4.3
A compromised content process could have updated the document URI. This could have allowed an attacker to set an arbitr…
-
High 7.5
An unchecked return value in TLS handshake code could have caused a potentially exploitable crash. This vulnerability a…
-
High 7.5
In some circumstances, JIT compiled code could have dereferenced a wild pointer value. This could have led to an exploi…
-
High 8.8
Memory safety bugs present in Firefox 121, Firefox ESR 115.6, and Thunderbird 115.6. Some of these bugs showed evidence…
-
Medium 6.5
In specific HSTS configurations an attacker could have bypassed HSTS on a subdomain. This vulnerability affects Firefox…
-
High 8.8
A malicious devtools extension could have been used to escalate privileges. This vulnerability affects Firefox < 122, F…
-
High 8.8
A bug in popup notifications delay calculation could have made it possible for an attacker to trick a user into grantin…
-
Medium 4.3
A phishing site could have repurposed an `about:` dialog to show phishing content with an incorrect origin in the addre…
-
Medium 6.5
When a parent page loaded a child in an iframe with `unsafe-inline`, the parent Content Security Policy could have over…
-
Medium 6.5
A Linux user opening the print preview dialog could have caused the browser to crash. This vulnerability affects Firefo…
-
Medium 6.5CVE-2024-0741 Public exploit
An out of bounds write in ANGLE could have allowed an attacker to corrupt memory leading to a potentially exploitable c…
-
Medium 4.3
It was possible for certain browser prompts and dialogs to be activated or dismissed unintentionally by the user due to…
-
Unscored —
Memory safety bugs present in Firefox 120. Some of these bugs showed evidence of memory corruption and we presume that …
-
Unscored —
Browser tab titles were being leaked by GNOME to system logs. This could potentially expose the browsing habits of user…
-
Unscored —
Under certain conditions, Firefox did not display a warning when a user attempted to navigate to a new protocol handler…
-
Medium 6.5
A `<dialog>` element could have been manipulated to paint content outside of a sandboxed iframe. This could allow un…
-
Unscored —
The timing of a button click causing a popup to disappear was approximately the same length as the anti-clickjacking de…
-
High 8.8
TypedArrays can be fallible and lacked proper exception handling. This could lead to abuse in other APIs which expect T…
-
Unscored —
`EncryptingOutputStream` was susceptible to exposing uninitialized data. This issue could only be abused in order to wr…
-
Unscored —
Multiple NSS NIST curves were susceptible to a side-channel attack known as "Minerva". This attack could potentially al…
-
Unscored —
Memory safety bugs present in Firefox 120, Firefox ESR 115.5, and Thunderbird 115.5. Some of these bugs showed evidence…
-
Unscored —
The `ShutdownObserver()` was susceptible to potentially undefined behavior due to its reliance on a dynamic type that l…
-
Unscored —
The `nsWindow::PickerOpen(void)` method was susceptible to a heap buffer overflow when running in headless mode. This v…
-
Unscored —
The `VideoBridge` allowed any content process to use textures produced by remote decoders. This could be abused to esca…
-
Unscored —
A use-after-free condition affected TLS socket creation when under memory pressure. This vulnerability affects Firefox …
-
High 8.8
Firefox was susceptible to a heap buffer overflow in `nsTextFragment` due to insufficient OOM handling. This vulnerabil…
-
Unscored —
When resolving a symlink, a race may occur where the buffer passed to `readlink` may actually be smaller than necessary…