THREATIST.IORead the docs firefox security update
Released 2019-09-04 · Red Hat rating Important · View on Red Hat →
When a master password is set, it is required to be entered again before stored passwords can be accessed in the 'Saved Logins' dialog.
Given a compromised sandboxed content process due to a separate vulnerability, it is possible to escape that sandbox by loading accounts.firefox.com in that process and forcing a log-in to a malicious Firefox Sync accoun…
It is possible to delete an IndexedDB key value and subsequently try to extract it during conversion.
A use-after-free vulnerability can occur while manipulating video elements if the body is freed while still in use.
Mozilla developers and community members reported memory safety bugs present in Firefox 68, Firefox ESR 68, and Firefox 60.8.
Mozilla developers and community members reported memory safety bugs present in Firefox 68 and Firefox ESR 68.
A same-origin policy violation occurs allowing the theft of cross-origin images through a combination of SVG filters and a <canvas> element due to an error in how same-origin policy is applied to cached image conte…
A type confusion vulnerability exists in Spidermonkey, which results in a non-exploitable crash.
WebRTC in Firefox will honor persisted permissions given to sites for access to microphone and camera resources even when in a third-party context.
The "Forget about this site" feature in the History pane is intended to remove all saved user data that indicates a user has visited a site.
If a Content Security Policy (CSP) directive is defined that uses a hash-based source that takes the empty string as input, execution of any javascript: URIs will be allowed.
Some HTML elements, such as <title> and <textarea>, can contain literal angle brackets without treating them as markup.
A vulnerability exists in WebRTC where malicious web content can use probing techniques on the getUserMedia API using constraints to reveal device properties of cameras on the system without triggering a user prompt or n…
Navigation events were not fully adhering to the W3C's "Navigation-Timing Level 2" draft specification in some instances for the unload event, which restricts access to detailed timing attributes to only be same-origin.