Incoming details.
CVE-2019-9810: IonMonkey MArraySlice has incorrect alias information Impact critical Description Incorrect alias information in IonMonkey JIT compiler for Array.prototype.slice method may lead to missing bounds check and a buffer overflow. CVE-2019-9813: Ionmonkey type confusion with __proto__ mutations Impact critical Description Incorrect handling of __proto__ mutations may lead to type confusion in IonMonkey JIT code and can be leveraged for arbitrary memory read and write.
CVE-2019-9790: Use-after-free when removing in-use DOM elements 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. CVE-2019-9791: Type inference is incorrect for constructors entered through on-stack replacement with IonMonkey 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. CVE-2019-9792: IonMonkey leaks JS_OPTIMIZED_OUT magic value to script 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. CVE-2019-9793: Improper bounds checks when Spectre mitigations are disabled 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 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. CVE-2019-9796: Use-after-free with SMIL animation controller Impact high Description A use-after-free vulnerability can occur when the SMIL animation controller incorrectly registers with the refresh driver twice when only a single registration is expected. When a registration is later freed with the removal of the animation controller element, the refresh driver incorrectly leaves a dangling pointer to the driver's observer array. CVE-2018-18506: Proxy Auto-Configuration file can define localhost access to be proxied Impact moderate Description When proxy auto-detection is enabled, if a web server serves a Proxy Auto-Configuration (PAC) file or if a PAC file is loaded locally, this PAC file can specify that requests to the localhost are to be sent through the proxy to another server. This behavior is disallowed by default when a proxy is manually configured, but when enabled could allow for attacks on services and tools that bind to the localhost for networked behavior if they are accessed through browsing. CVE-2019-9788: Memory safety bugs fixed in Firefox 66, Firefox ESR 60.6, and Thunderbird 60.6 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, Firefox ESR 60.5, and Thunderbird 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.
x86 stable
amd64 stable
@mozilla, please drop the vulnerable.
This issue was resolved and addressed in GLSA 201904-07 at https://security.gentoo.org/glsa/201904-07 by GLSA coordinator Aaron Bauman (b-man).
re-opened for cleanup
tree is clean
