1,829 results · Feed
-
Unscored —
When trying to load a non-video in an audio/video context the exact status code (200, 302, 404, 500, 412, 403, etc.) wa…
-
Unscored —
When processing a MAR update file, after the signature has been validated, an invalid name length could result in a hea…
-
Unscored —
A lock was missing when accessing a data structure and importing certificate information into the trust database. This …
-
Unscored —
Mozilla developers reported memory safety bugs present in Firefox for Android 79. Some of these bugs showed evidence of…
-
Unscored —
Mozilla developers reported memory safety bugs present in Firefox 80 and Firefox ESR 78.2. Some of these bugs showed ev…
-
Unscored —
Mozilla developers reported memory safety bugs present in Firefox 80. Some of these bugs showed evidence of memory corr…
-
Unscored —
When processing surfaces, the lifetime may outlive a persistent buffer leading to memory corruption and a potentially e…
-
Unscored —
Firefox sometimes ran the onload handler for SVG elements that the DOM sanitizer decided to remove, resulting in JavaSc…
-
Unscored —
By exploiting an Open Redirect vulnerability on a website, an attacker could have spoofed the site displayed in the dow…
-
Unscored —
When recursing through graphical layers while scrolling, an iterator may have become invalid, resulting in a potential …
-
Unscored —
A redirected HTTP request which is observed or modified through a web extension could bypass existing CORS checks, lead…
-
Unscored —
Using object or embed tags, it was possible to frame other websites, even if they disallowed framing using the X-Frame-…
-
Unscored —
By observing the stack trace for JavaScript errors in web workers, it was possible to leak the result of a cross-origin…
-
Unscored —
An iframe sandbox element with the allow-popups flag could be bypassed when using noopener links. This could have led t…
-
Unscored —
When in an endless loop, a website specifying a custom cursor using CSS could make it look like the user is interacting…
-
Unscored —
The code for downloading files did not properly take care of special characters, which led to an attacker being able to…
-
Unscored —
JIT optimizations involving the Javascript arguments object could confuse later optimizations. This risk was already mi…
-
Unscored —
Mozilla developers and community members reported memory safety bugs present in Firefox 78 and Firefox ESR 78.0. Some o…
-
Unscored —
Mozilla Developer Nicolas Silva found that when using WebRender, Firefox would under certain conditions leak arbitrary …
-
Unscored —
When browsing a document hosted on an IP address, an attacker could insert certain characters to flip domain and path i…
-
Unscored —
Mozilla developers reported memory safety bugs present in Firefox 76. Some of these bugs showed evidence of memory corr…
-
Unscored —
When using certain blank characters in a URL, they where incorrectly rendered as spaces instead of an encoded URL. This…
-
Unscored —
Mozilla developers reported memory safety bugs present in Firefox 76 and Firefox ESR 68.8. Some of these bugs showed ev…
-
Unscored —
When browsing a malicious page, a race condition in our SharedWorkerService could occur and lead to a potentially explo…
-
Unscored —
Mozilla Developer Iain Ireland discovered a missing type check during unboxed objects removal, resulting in a crash. We…
-
Unscored —
A VideoStreamEncoder may have been freed in a race condition with VideoBroadcaster::AddOrUpdateSink, resulting in a use…
-
Unscored —
In non-standard configurations, a JPEG image created by JavaScript could have caused an internal variable to overflow, …
-
Unscored —
When trying to connect to a STUN server, a race condition could have caused a use-after-free of a pointer, leading to m…
-
Unscored —
Due to confusion about ValueTags on JavaScript Objects, an object may pass through the type barrier, resulting in memor…
-
Unscored —
Due to confusion processing a hyphen character in Date.parse(), a one-byte out of bounds read could have occurred, lead…
-
Unscored —
When performing add-on updates, certificate chains terminating in non-built-in-roots were rejected (even if they were l…
-
Unscored —
When processing callbacks that occurred during window flushing in the parent process, the associated window may die; ca…
-
Unscored —
When "%2F" was present in a manifest URL, Firefox's AppCache behavior may have become confused and allowed a manifest t…
-
Unscored —
Mozilla developers and community members reported memory safety bugs present in Firefox 77. Some of these bugs showed e…
-
Unscored —
Manipulating individual parts of a URL object could have caused an out-of-bounds read, leaking process memory to malici…
-
Unscored —
When constructing a permission prompt for WebRTC, a URI was supplied from the content process. This URI was untrusted, …
-
Unscored —
A buffer overflow could occur when parsing and validating SCTP chunks in WebRTC. This could have led to memory corrupti…
-
Unscored —
A race condition when running shutdown code for Web Worker led to a use-after-free vulnerability. This resulted in a po…
-
Unscored —
The Firefox content processes did not sufficiently lockdown access control which could result in a sandbox escape. *Not…
-
Unscored —
The Firefox content processes did not sufficiently lockdown access control which could result in a sandbox escape. *Not…