Memory corruption in Mozilla Thunderbird
A buffer overflow can occur when the image renderer attempts to paint non-displayable SVG elements.
firefox security update
Released 2017-08-10 · Red Hat rating Critical · View on Red Hat →
A buffer overflow can occur when the image renderer attempts to paint non-displayable SVG elements.
A buffer overflow can occur when manipulating Accessible Rich Internet Applications (ARIA) attributes within the DOM.
A buffer overflow will occur when viewing a certificate in the certificate manager if the certificate has an extremely long object identifier (OID).
A use-after-free vulnerability can occur when reading an image observer during frame reconstruction after the observer has been freed.
A use-after-free vulnerability can occur when an editor DOM node is deleted prematurely during tree traversal while still bound to the document.
A use-after-free vulnerability can occur when manipulating the DOM during the resize event of an image element.
A use-after-free vulnerability can occur while re-computing layout for a "marquee" element during window resizing where the updated style object is freed while still in use.
A use-after-free vulnerability can occur in WebSockets when the object holding the connection is freed before the disconnection operation is finished.
Memory safety bugs were reported in Firefox 54, Firefox ESR 52.2, and Thunderbird 52.2.
An out-of-bounds read occurs when applying style rules to pseudo-elements, such as ::first-line, using cached style data.
The Developer Tools feature suffers from a XUL injection vulnerability due to improper sanitization of the web page source code.
A mechanism that uses AppCache to hijack a URL in a domain using fallback by serving the files from a sub-path on the domain.
When a page's content security policy (CSP) header contains a "sandbox" directive, other directives are ignored.
Same-origin policy protections can be bypassed on pages with embedded iframes during page reloads, allowing the iframes to access content on the top level page, leading to information disclosure.
On pages containing an iframe, the "data:" protocol can be used to create a modal alert that will render over arbitrary domains following page navigation, spoofing of the origin of the modal alert from the iframe content…