Firefox, Squid, Chromium Updates for Arch Linux
Posted on: 07/17/2019 06:21 PM

The following security updates has been released for Arch Linux:

ASA-201907-4: firefox: multiple issues
ASA-201907-5: squid: arbitrary code execution
ASA-201907-6: chromium: multiple issues

ASA-201907-4: firefox: multiple issues

Arch Linux Security Advisory ASA-201907-4
=========================================

Severity: Critical
Date : 2019-07-17
CVE-ID : CVE-2019-9811 CVE-2019-11709 CVE-2019-11710 CVE-2019-11711
CVE-2019-11712 CVE-2019-11713 CVE-2019-11714 CVE-2019-11715
CVE-2019-11716 CVE-2019-11717 CVE-2019-11718 CVE-2019-11719
CVE-2019-11720 CVE-2019-11721 CVE-2019-11723 CVE-2019-11724
CVE-2019-11725 CVE-2019-11727 CVE-2019-11728 CVE-2019-11729
CVE-2019-11730
Package : firefox
Type : multiple issues
Remote : Yes
Link : https://security.archlinux.org/AVG-1002

Summary
=======

The package firefox before version 68.0-1 is vulnerable to multiple
issues including arbitrary code execution, access restriction bypass,
cross-site request forgery, sandbox escape, arbitrary filesystem
access, content spoofing, cross-site scripting, denial of service,
information disclosure, insufficient validation and silent downgrade.

Resolution
==========

Upgrade to 68.0-1.

# pacman -Syu "firefox>=68.0-1"

The problems have been fixed upstream in version 68.0.

Workaround
==========

None.

Description
===========

- CVE-2019-9811 (sandbox escape)

A sandbox escape has been found in Firefox before 68.0, by installing a
malicious language pack and then opening a browser feature that used
the compromised translation.

- CVE-2019-11709 (arbitrary code execution)

Several memory safety bugs have been found in Firefox before 68.0. Some
of these bugs showed evidence of memory corruption and Mozilla presumes
that with enough effort that some of these could be exploited to run
arbitrary code.

- CVE-2019-11710 (arbitrary code execution)

Several memory safety bugs have been found in Firefox before 68.0. Some
of these bugs showed evidence of memory corruption and Mozilla presumes
that with enough effort that some of these could be exploited to run
arbitrary code.

- CVE-2019-11711 (access restriction bypass)

In Firefox before 68.0, when an inner window is reused, it does not
consider the use of document.domain for cross-origin protections. If
pages on different subdomains ever cooperatively use document.domain,
then either page can abuse this to inject script into arbitrary pages
on the other subdomain, even those that did not use document.domain to
relax their origin security.

- CVE-2019-11712 (cross-site request forgery)

In Firefox before 68.0, POST requests made by NPAPI plugins, such as
Flash, that receive a status 308 redirect response can bypass CORS
requirements. This can allow an attacker to perform Cross-Site Request
Forgery (CSRF) attacks.

- CVE-2019-11713 (arbitrary code execution)

A use-after-free vulnerability can occur in the HTTP/2 component of
Firefox before 68.0, when a cached HTTP/2 stream is closed while still
in use, resulting in a potentially exploitable crash.

- CVE-2019-11714 (arbitrary code execution)

Necko can access a child on the wrong thread during UDP connections,
resulting in a potentially exploitable crash in some instances.

- CVE-2019-11715 (cross-site scripting)

In Firefox before 68.0, due to an error while parsing page content, it
is possible for properly sanitized user input to be misinterpreted and
lead to XSS hazards on web sites in certain circumstances.

- CVE-2019-11716 (access restriction bypass)

In Firefox before 68.0, until explicitly accessed by script,
window.globalThis is not enumerable and, as a result, is not visible to
code such as Object.getOwnPropertyNames(window). Sites that deploy a
sandboxing that depends on enumerating and freezing access to the
window object may miss this, allowing their sandboxes to be bypassed.

- CVE-2019-11717 (insufficient validation)

A vulnerability exists in Firebox before 68.0 where the caret ("^")
character is improperly escaped constructing some URIs due to it being
used as a separator, allowing for possible spoofing of origin
attributes.

- CVE-2019-11718 (insufficient validation)

In Firefox before 68.0, Activity Stream can display content from sent
from the Snippet Service website. This content is written to innerHTML
on the Activity Stream page without sanitization, allowing for a
potential access to other information available to the Activity Stream,
such as browsing history, if the Snipper Service were compromised.

- CVE-2019-11719 (information disclosure)

In Firefox before 68.0, when importing a curve25519 private key in
PKCS#8format with leading 0x00 bytes, it is possible to trigger an out-
of-bounds read in the Network Security Services (NSS) library.

- CVE-2019-11720 (insufficient validation)

In Firefox before 68.0, some unicode characters are incorrectly treated
as whitespace during the parsing of web content instead of triggering
parsing errors. This allows malicious code to then be processed,
evading cross-site scripting (XSS) filtering.

- CVE-2019-11721 (content spoofing)

The unicode latin 'kra' character can be used to spoof a standard 'k'
character in the addressbar in Firefox before 68.0. This allows for
domain spoofing attacks as do not display as punycode text, allowing
for user confusion.

- CVE-2019-11723 (information disclosure)

A vulnerability exists in Firefox 68.0 during the installation of add-
ons where the initial fetch ignored the origin attributes of the
browsing context. This could leak cookies in private browsing mode or
across different "containers" for people who use the Firefox Multi-
Account Containers Web Extension.

- CVE-2019-11724 (access restriction bypass)

Application permissions in Firefox before 68.0 give additional remote
troubleshooting permission to the site input.mozilla.org, which has
been retired and now redirects to another site. This additional
permission is unnecessary and is a potential vector for malicious
attacks.

- CVE-2019-11725 (access restriction bypass)

In Firefox before 68.0, when a user navigates to a site marked as
unsafe by the Safebrowsing API, warning messages are displayed and
navigation is interrupted but resources from the same site loaded
through websockets are not blocked, leading to the loading of unsafe
resources and bypassing safebrowsing protections.

- CVE-2019-11727 (silent downgrade)

A vulnerability exists in Firefox before 68.0 where it is possible to
force Network Security Services (NSS) to sign CertificateVerify with
PKCS#1 v1.5 signatures when those are the only ones advertised by
server in CertificateRequest in TLS 1.3. PKCS#1 v1.5 signatures should
not be used for TLS 1.3 messages.

- CVE-2019-11728 (information disclosure)

In firefox before 68.0, the HTTP Alternative Services header, Alt-Svc,
can be used by a malicious site to scan all TCP ports of any host that
the accessible to a user when web content is loaded.

- CVE-2019-11729 (denial of service)

Empty or malformed p256-ECDH public keys may trigger a segmentation
fault in Firefox before 68.0 due values being improperly sanitized
before being copied into memory and used.

- CVE-2019-11730 (arbitrary filesystem access)

A vulnerability exists in Firefox before 68.0 where if a user opens a
locally saved HTML file, this file can use file: URIs to access other
files in the same directory or sub-directories if the names are known
or guessed. The Fetch API can then be used to read the contents of any
files stored in these directories and they may uploaded to a server.
Luigi Gubello demonstrated that in combination with a popular Android
messaging app, if a malicious HTML attachment is sent to a user and
they opened that attachment in Firefox, due to that app's predictable
pattern for locally-saved file names, it is possible to read
attachments the victim received from other correspondents.

Impact
======

A remote attacker an access sensitive information, bypass security
measures and execute arbitrary code on the affected host.

References
==========

https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/
https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-9811
https://bugzilla.mozilla.org/show_bug.cgi?id=1538007
https://bugzilla.mozilla.org/show_bug.cgi?id=1539598
https://bugzilla.mozilla.org/show_bug.cgi?id=1539759
https://bugzilla.mozilla.org/show_bug.cgi?id=1523741
https://bugzilla.mozilla.org/show_bug.cgi?id=1563327
https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-11709
https://bugzilla.mozilla.org/buglist.cgi?bug_id=1547266%2C1540759%2C1548822%2C1550498%2C1515052%2C1539219%2C1547757%2C1550498%2C1533522
https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-11710
https://bugzilla.mozilla.org/buglist.cgi?bug_id=1549768%2C1548611%2C1533842%2C1537692%2C1540590%2C1551907%2C1510345%2C1535482%2C1535848%2C1547472%2C1547760%2C1507696%2C1544180
https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-11711
https://bugzilla.mozilla.org/show_bug.cgi?id=1552541
https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-11712
https://bugzilla.mozilla.org/show_bug.cgi?id=1543804
https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-11713
https://bugzilla.mozilla.org/show_bug.cgi?id=1528481
https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-11714
https://bugzilla.mozilla.org/show_bug.cgi?id=1542593
https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-11715
https://bugzilla.mozilla.org/show_bug.cgi?id=1555523
https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-11716
https://bugzilla.mozilla.org/show_bug.cgi?id=1552632
https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-11717
https://bugzilla.mozilla.org/show_bug.cgi?id=1548306
https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-11718
https://bugzilla.mozilla.org/show_bug.cgi?id=1408349
https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-11719
https://bugzilla.mozilla.org/show_bug.cgi?id=1540541
https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-11720
https://bugzilla.mozilla.org/show_bug.cgi?id=1556230
https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-11721
https://bugzilla.mozilla.org/show_bug.cgi?id=1256009
https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-11723
https://bugzilla.mozilla.org/show_bug.cgi?id=1528335
https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-11724
https://bugzilla.mozilla.org/show_bug.cgi?id=1512511
https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-11725
https://bugzilla.mozilla.org/show_bug.cgi?id=1483510
https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-11727
https://bugzilla.mozilla.org/show_bug.cgi?id=1552208
https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-11728
https://bugzilla.mozilla.org/show_bug.cgi?id=1552993
https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-11729
https://bugzilla.mozilla.org/show_bug.cgi?id=1515342
https://www.mozilla.org/en-US/security/advisories/mfsa2019-21/#CVE-2019-11730
https://bugzilla.mozilla.org/show_bug.cgi?id=1558299
https://security.archlinux.org/CVE-2019-9811
https://security.archlinux.org/CVE-2019-11709
https://security.archlinux.org/CVE-2019-11710
https://security.archlinux.org/CVE-2019-11711
https://security.archlinux.org/CVE-2019-11712
https://security.archlinux.org/CVE-2019-11713
https://security.archlinux.org/CVE-2019-11714
https://security.archlinux.org/CVE-2019-11715
https://security.archlinux.org/CVE-2019-11716
https://security.archlinux.org/CVE-2019-11717
https://security.archlinux.org/CVE-2019-11718
https://security.archlinux.org/CVE-2019-11719
https://security.archlinux.org/CVE-2019-11720
https://security.archlinux.org/CVE-2019-11721
https://security.archlinux.org/CVE-2019-11723
https://security.archlinux.org/CVE-2019-11724
https://security.archlinux.org/CVE-2019-11725
https://security.archlinux.org/CVE-2019-11727
https://security.archlinux.org/CVE-2019-11728
https://security.archlinux.org/CVE-2019-11729
https://security.archlinux.org/CVE-2019-11730



ASA-201907-5: squid: arbitrary code execution

Arch Linux Security Advisory ASA-201907-5
=========================================

Severity: Critical
Date : 2019-07-17
CVE-ID : CVE-2019-12527
Package : squid
Type : arbitrary code execution
Remote : Yes
Link : https://security.archlinux.org/AVG-1004

Summary
=======

The package squid before version 4.8-1 is vulnerable to arbitrary code
execution.

Resolution
==========

Upgrade to 4.8-1.

# pacman -Syu "squid>=4.8-1"

The problem has been fixed upstream in version 4.8.

Workaround
==========

None.

Description
===========

Due to incorrect buffer management Squid versions prior to 4.8 are
vulnerable to a heap overflow and possible remote code execution attack
when processing HTTP Authentication credentials.

Impact
======

A remote attacker can execute arbitrary code via crafted HTTP requests.

References
==========

http://www.squid-cache.org/Advisories/SQUID-2019_5.txt
http://www.squid-cache.org/Versions/v4/changesets/squid-4-7f73e9c5d17664b882ed32590e6af310c247f320.patch
https://security.archlinux.org/CVE-2019-12527


ASA-201907-6: chromium: multiple issues

Arch Linux Security Advisory ASA-201907-6
=========================================

Severity: High
Date : 2019-07-17
CVE-ID : CVE-2019-5847 CVE-2019-5848
Package : chromium
Type : multiple issues
Remote : Yes
Link : https://security.archlinux.org/AVG-1005

Summary
=======

The package chromium before version 75.0.3770.142-1 is vulnerable to
multiple issues including arbitrary code execution and information
disclosure.

Resolution
==========

Upgrade to 75.0.3770.142-1.

# pacman -Syu "chromium>=75.0.3770.142-1"

The problems have been fixed upstream in version 75.0.3770.142.

Workaround
==========

None.

Description
===========

- CVE-2019-5847 (arbitrary code execution)

A security issue has been found in chromium before 75.0.3770.142, where
V8 sealed/frozen elements can cause a crash.

- CVE-2019-5848 (information disclosure)

A security issue has been found in chromium before 75.0.3770.142, where
font sizes may expose sensitive information.

Impact
======

A remote attacker can access sensitive information and possibly execute
arbitrary code.

References
==========

https://chromereleases.googleblog.com/2019/07/stable-channel-update-for-desktop.html
https://crbug.com/972921
https://crbug.com/951487
https://security.archlinux.org/CVE-2019-5847
https://security.archlinux.org/CVE-2019-5848





Printed from Linux Compatible (https://www.linuxcompatible.org/news/story/firefoxsquidchromium_updates_for_arch_linux.html)