Arch Linux Security Advisory ASA-201703-3 ========================================= Severity: Critical Date : 2017-03-10 CVE-ID : CVE-2017-5398 CVE-2017-5399 CVE-2017-5400 CVE-2017-5401 CVE-2017-5402 CVE-2017-5403 CVE-2017-5404 CVE-2017-5405 CVE-2017-5406 CVE-2017-5407 CVE-2017-5408 CVE-2017-5410 CVE-2017-5412 CVE-2017-5413 CVE-2017-5414 CVE-2017-5415 CVE-2017-5416 CVE-2017-5417 CVE-2017-5418 CVE-2017-5419 CVE-2017-5420 CVE-2017-5421 CVE-2017-5422 CVE-2017-5426 CVE-2017-5427 Package : firefox Type : multiple issues Remote : Yes Link : https://security.archlinux.org/AVG-194 Summary ======= The package firefox before version 52.0-1 is vulnerable to multiple issues including arbitrary code execution, access restriction bypass, denial of service, information disclosure and content spoofing. Resolution ========== Upgrade to 52.0-1. # pacman -Syu "firefox>=52.0-1" The problems have been fixed upstream in version 52.0. Workaround ========== None. Description =========== - CVE-2017-5398 (arbitrary code execution) Several memory safety bugs, some of them leading to memory corruption issues have been found in Firefox < 52 and Thunderbird < 45.8. - CVE-2017-5399 (arbitrary code execution) Several memory safety bugs, some of them leading to memory corruption issues have been found in Firefox < 52. - CVE-2017-5400 (arbitrary code execution) JIT-spray targeting asm.js combined with a heap spray allows for a bypass of ASLR and DEP protections leading to potential memory corruption attacks. - CVE-2017-5401 (arbitrary code execution) A crash triggerable by web content in which an ErrorResult references unassigned memory due to a logic error. - CVE-2017-5402 (arbitrary code execution) A use-after-free can occur when events are fired for a FontFace object after the object has been already been destroyed while working with fonts. - CVE-2017-5403 (arbitrary code execution) When adding a range to an object in the DOM, it is possible to use addRange to add the range to an incorrect root object. This triggers a use-after-free, resulting in a potentially exploitable crash. - CVE-2017-5404 (arbitrary code execution) A use-after-free error can occur when manipulating ranges in selections with one node inside a native anonymous tree and one node outside of it. This results in a potentially exploitable crash. - CVE-2017-5405 (content spoofing) Certain response codes in FTP connections can result in the use of uninitialized values for ports in FTP operations. - CVE-2017-5406 (denial of service) A segmentation fault can occur in the Skia graphics library during some canvas operations due to issues with mask/clip intersection and empty masks. - CVE-2017-5407 (information disclosure) Using SVG filters that don't use the fixed point math implementation on a target iframe, a malicious page can extract pixel values from a targeted user. This can be used to extract history information and read text values across domains. This violates same-origin policy and leads to information disclosure. - CVE-2017-5408 (information disclosure) Video files loaded video captions cross-origin without checking for the presence of CORS headers permitting such cross-origin use, leading to potential information disclosure for video captions. - CVE-2017-5410 (arbitrary code execution) Memory corruption resulting in a potentially exploitable crash during garbage collection of JavaScript due errors in how incremental sweeping is managed for memory cleanup. - CVE-2017-5412 (information disclosure) A buffer overflow read during SVG filter color value operations, resulting in data exposure. - CVE-2017-5413 (denial of service) A segmentation fault can occur during some bidirectional layout operations. - CVE-2017-5414 (information disclosure) The file picker dialog can choose and display the wrong local default directory when instantiated. On some operating systems, this can lead to information disclosure, such as the operating system or the local account name. - CVE-2017-5415 (content spoofing) An attack can use a blob URL and script to spoof an arbitrary address bar URL prefaced by blob: as the protocol, leading to user confusion and further spoofing attacks. - CVE-2017-5416 (denial of service) In certain circumstances a networking event listener can be prematurely released. This appears to result in a null dereference in practice. - CVE-2017-5417 (content spoofing) When dragging content from the primary browser pane to the address bar on a malicious site, it is possible to change the address bar so that the displayed location following navigation does not match the URL of the newly loaded page. This allows for spoofing attacks. - CVE-2017-5418 (information disclosure) An out of bounds read error occurs when parsing some HTTP digest authorization responses, resulting in information leakage through the reading of random memory containing matches to specifically set patterns. - CVE-2017-5419 (denial of service) If a malicious site repeatedly triggers a modal authentication prompt, eventually the browser UI will become non-responsive, requiring shutdown through the operating system. This is a denial of service (DOS) attack. - CVE-2017-5420 (content spoofing) A javascript: url loaded by a malicious page can obfuscate its location by blanking the URL displayed in the address bar, allowing for an attacker to spoof an existing page without the malicious page's address being displayed correctly. - CVE-2017-5421 (content spoofing) A malicious site could spoof the contents of the print preview window if popup windows are enabled, resulting in user confusion of what site is currently loaded. - CVE-2017-5422 (denial of service) If a malicious site uses the view-source: protocol in a series within a single hyperlink, it can trigger a non-exploitable browser crash when the hyperlink is selected. This was fixed by no longer making view- source: linkable. - CVE-2017-5426 (access restriction bypass) On Linux, if the secure computing mode BPF (seccomp-bpf) filter is running when the Gecko Media Plugin sandbox is started, the sandbox fails to be applied and items that would run within the sandbox are run protected only by the running filter which is typically weak compared to the sandbox. - CVE-2017-5427 (arbitrary code execution) A non-existent chrome.manifest file will attempt to be loaded during startup from the primary installation directory. If a malicious user with local access puts chrome.manifest and other referenced files in this directory, they will be loaded and activated during startup. This could result in malicious software being added without consent or modification of referenced installed files. Impact ====== A remote attacker can bypass access restrictions, spoof content, access sensitive information, cause a denial of service or execute arbitrary code on the affected host. References ========== https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/ https://www.mozilla.org/en-US/security/advisories/mfsa2017-07/#CVE-2017-5398 https://bugzilla.mozilla.org/buglist.cgi?bug_id=1332550%2C1332597%2C1338383%... https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5399 https://bugzilla.mozilla.org/buglist.cgi?bug_id=1332569%2C1315248%2C1261335%... https://www.mozilla.org/en-US/security/advisories/mfsa2017-07/#CVE-2017-5400 https://bugzilla.mozilla.org/show_bug.cgi?id=1334933 https://www.mozilla.org/en-US/security/advisories/mfsa2017-07/#CVE-2017-5401 https://bugzilla.mozilla.org/show_bug.cgi?id=1328861 https://www.mozilla.org/en-US/security/advisories/mfsa2017-07/#CVE-2017-5402 https://bugzilla.mozilla.org/show_bug.cgi?id=1334876 https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5403 https://bugzilla.mozilla.org/show_bug.cgi?id=1340186 https://www.mozilla.org/en-US/security/advisories/mfsa2017-07/#CVE-2017-5404 https://bugzilla.mozilla.org/show_bug.cgi?id=1340138 https://www.mozilla.org/en-US/security/advisories/mfsa2017-07/#CVE-2017-5405 https://bugzilla.mozilla.org/show_bug.cgi?id=1336699 https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5406 https://bugzilla.mozilla.org/show_bug.cgi?id=1306890 https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5407 https://bugzilla.mozilla.org/show_bug.cgi?id=1336622 https://www.mozilla.org/en-US/security/advisories/mfsa2017-07/#CVE-2017-5408 https://bugzilla.mozilla.org/show_bug.cgi?id=1313711 https://www.mozilla.org/en-US/security/advisories/mfsa2017-07/#CVE-2017-5410 https://bugzilla.mozilla.org/show_bug.cgi?id=1330687 https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5412 https://bugzilla.mozilla.org/show_bug.cgi?id=1328323 https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5413 https://bugzilla.mozilla.org/show_bug.cgi?id=1337504 https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5414 https://bugzilla.mozilla.org/show_bug.cgi?id=1319370 https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5415 https://bugzilla.mozilla.org/show_bug.cgi?id=1321719 https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5416 https://bugzilla.mozilla.org/show_bug.cgi?id=1328121 https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5417 https://bugzilla.mozilla.org/show_bug.cgi?id=791597 https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5418 https://bugzilla.mozilla.org/show_bug.cgi?id=1338876 https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5419 https://bugzilla.mozilla.org/show_bug.cgi?id=1312243 https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5420 https://bugzilla.mozilla.org/show_bug.cgi?id=1284395 https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5421 https://bugzilla.mozilla.org/show_bug.cgi?id=1301876 https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5422 https://bugzilla.mozilla.org/show_bug.cgi?id=1295002 https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5426 https://bugzilla.mozilla.org/show_bug.cgi?id=1257361 https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5427 https://bugzilla.mozilla.org/show_bug.cgi?id=1295542 https://security.archlinux.org/CVE-2017-5398 https://security.archlinux.org/CVE-2017-5399 https://security.archlinux.org/CVE-2017-5400 https://security.archlinux.org/CVE-2017-5401 https://security.archlinux.org/CVE-2017-5402 https://security.archlinux.org/CVE-2017-5403 https://security.archlinux.org/CVE-2017-5404 https://security.archlinux.org/CVE-2017-5405 https://security.archlinux.org/CVE-2017-5406 https://security.archlinux.org/CVE-2017-5407 https://security.archlinux.org/CVE-2017-5408 https://security.archlinux.org/CVE-2017-5410 https://security.archlinux.org/CVE-2017-5412 https://security.archlinux.org/CVE-2017-5413 https://security.archlinux.org/CVE-2017-5414 https://security.archlinux.org/CVE-2017-5415 https://security.archlinux.org/CVE-2017-5416 https://security.archlinux.org/CVE-2017-5417 https://security.archlinux.org/CVE-2017-5418 https://security.archlinux.org/CVE-2017-5419 https://security.archlinux.org/CVE-2017-5420 https://security.archlinux.org/CVE-2017-5421 https://security.archlinux.org/CVE-2017-5422 https://security.archlinux.org/CVE-2017-5426 https://security.archlinux.org/CVE-2017-5427