Firefox 65 was another low

amd6502

Senior member
Apr 21, 2017
971
360
136
This is a pretty big rap sheet; just listing the top few here is what was found and fixed:

https://www.mozilla.org/en-US/security/advisories/mfsa2019-07/

#CVE-2019-9789: Memory safety bugs fixed in Firefox 66
Reporter Mozilla developers and community Impact critical Description

Mozilla developers and community members Dragana Damjanovic, Emilio Cobos Álvarez, Henri Sivonen, Narcis Beleuzu, Julian Seward, Marcia Knous, Gary Kwong, Tyson Smith, Yaron Tausky, Ronald Crane, and André Bargull reported memory safety bugs present in Firefox 65. Some of these bugs showed evidence of memory corruption and we presume that with enough effort that some of these could be exploited to run arbitrary code.

References

#CVE-2019-9788: Memory safety bugs fixed in Firefox 66 and Firefox ESR 60.6
Reporter Mozilla developers and community Impact critical Description

Mozilla developers and community members Bob Clary, Chun-Min Chang, Aral Yaman, Andreea Pavel, Jonathan Kew, Gary Kwong, Alex Gaynor, Masayuki Nakano, and Anne van Kesteren reported memory safety bugs present in Firefox 65 and Firefox ESR 60.5. Some of these bugs showed evidence of memory corruption and we presume that with enough effort that some of these could be exploited to run arbitrary code.


#CVE-2019-9790: Use-after-free when removing in-use DOM elements
Reporter Brandon Wieser Impact critical Description

A use-after-free vulnerability can occur when a raw pointer to a DOM element on a page is obtained using JavaScript and the element is then removed while still in use. This results in a potentially exploitable crash.

References

#CVE-2019-9791: Type inference is incorrect for constructors entered through on-stack replacement with IonMonkey
Reporter Samuel Groß of Google Project Zero Impact critical Description

The type inference system allows the compilation of functions that can cause type confusions between arbitrary objects when compiled through the IonMonkey just-in-time (JIT) compiler and when the constructor function is entered through on-stack replacement (OSR). This allows for possible arbitrary reading and writing of objects during an exploitable crash.

References

#CVE-2019-9792: IonMonkey leaks JS_OPTIMIZED_OUT magic value to script
Reporter Samuel Groß of Google Project Zero Impact critical Description

The IonMonkey just-in-time (JIT) compiler can leak an internal JS_OPTIMIZED_OUT magic value to the running script during a bailout. This magic value can then be used by JavaScript to achieve memory corruption, which results in a potentially exploitable crash.

References

#CVE-2019-9793: Improper bounds checks when Spectre mitigations are disabled
Reporter Bruno Keith & Niklas Baumstark from the phoenhex team Impact high Description

A mechanism was discovered that removes some bounds checking for string, array, or typed array accesses if Spectre mitigations have been disabled. This vulnerability could allow an attacker to create an arbitrary value in compiled JavaScript, for which the range analysis will infer a fully controlled, incorrect range in circumstances where users have explicitly disabled Spectre mitigations.
Note: Spectre mitigations are currently enabled for all users by default settings.

#CVE-2019-9795: Type-confusion in IonMonkey JIT compiler
Reporter Nils Impact high Description

A vulnerability where type-confusion in the IonMonkey just-in-time (JIT) compiler could potentially be used by malicious JavaScript to trigger a potentially exploitable crash.