- Arch-security - lists.archlinux.org

[arch-security] [ASA-201601-18] roundcubemail: remote code execution
by Remi Gacogne 17 Jan '16

17 Jan '16

Arch Linux Security Advisory ASA-201601-18 ========================================== Severity: High Date : 2016-01-17 CVE-ID : CVE-2015-8770 Package : roundcubemail Type : remote code execution Remote : Yes Link : https://wiki.archlinux.org/index.php/CVE Summary ======= The package roundcubemail before version 1.2beta-2 is vulnerable to remote code execution. Resolution ========== Upgrade to 1.2beta-2. # pacman -Syu "roundcubemail>=1.2beta-2" The problem has been fixed upstream in version 1.0.8 and 1.1.4. Workaround ========== None. Description =========== High-Tech Bridge Security Research Lab discovered a path traversal vulnerability in Roundcube. Vulnerability can be exploited to gain access to sensitive information and under certain circumstances to execute arbitrary code and totally compromise the vulnerable server. The vulnerability exists due to insufficient sanitization of "_skin" HTTP POST parameter in "/index.php" script when changing between different skins of the web application. A remote authenticated attacker can use path traversal sequences (e.g. "../../") to load a new skin from arbitrary location on the system, readable by the webserver. Exploitation of the vulnerability requires valid user credentials and ability to create files on vulnerable host. Impact ====== A remote authenticated attacker can access sensitive information and may be able to execute arbitrary code on the affected host. References ========== https://bugs.archlinux.org/task/47764 https://www.htbridge.com/advisory/HTB23283 https://access.redhat.com/security/cve/CVE-2015-8770 https://roundcube.net/news/2015/12/26/updates-1.1.4-and-1.0.8-released/ https://github.com/roundcube/roundcubemail/commit/10e5192a2b1bc90ec137f5e69…

1 0

[arch-security] [ASA-201601-17] ffmpeg: information leakage
by Remi Gacogne 17 Jan '16

17 Jan '16

Arch Linux Security Advisory ASA-201601-17 ========================================== Severity: Medium Date : 2016-01-17 CVE-ID : CVE-2016-1897 CVE-2016-1898 Package : ffmpeg Type : information leakage Remote : Yes Link : https://wiki.archlinux.org/index.php/CVE Summary ======= The package ffmpeg before version 1:2.8.4-3 is vulnerable to information leakage. Resolution ========== Upgrade to 1:2.8.4-3. # pacman -Syu "ffmpeg>=1:2.8.4-3" The problem has been fixed upstream in version 2.8.5. Workaround ========== None. Description =========== A vulnerability in the way FFmpeg handles the concat (CVE-2016-1897) and subfile (CVE-2016-1898) protocols in a HTTP Live Streaming (HLS) M3U8 file allows a remote attacker to conduct a cross-origin attacks, and to access arbitrary local files on the vulnerable host. The attack uses a crafted M3U8 file to make FFmpeg send a HTTP request to an external server, with the URL containing data from arbitrary local files. Impact ====== A remote attacker, by providing a crafted M3U8 file, can access the content of arbitrary local files on the affected host. References ========== https://bugs.archlinux.org/task/47738 http://seclists.org/oss-sec/2016/q1/85 https://security-tracker.debian.org/tracker/CVE-2016-1897 https://security-tracker.debian.org/tracker/CVE-2016-1898

1 0

[arch-security] [ASA-201601-16] syncthing: information leakage
by Levente Polyak 17 Jan '16

17 Jan '16

Arch Linux Security Advisory ASA-201601-16 ========================================== Severity: High Date : 2016-01-17 CVE-ID : CVE-2015-8618 Package : syncthing Type : information leakage Remote : Yes Link : https://wiki.archlinux.org/index.php/CVE Summary ======= The package syncthing before version 0.12.14-2 is vulnerable to information leakage. Resolution ========== Upgrade to 0.12.14-2. # pacman -Syu "syncthing>=0.12.14-2" The problem has been fixed upstream in go version 1.5.3. Workaround ========== None. Description =========== This issue can affect RSA computations in crypto/rsa, which is used by crypto/tls. TLS servers on 32-bit systems could plausibly leak their RSA private key due to this issue. Other protocol implementations that create many RSA signatures could also be impacted in the same way. Specifically, incorrect results in one part of the RSA Chinese Remainder computation can cause the result to be incorrect in such a way that it leaks one of the primes. While RSA blinding should prevent an attacker from crafting specific inputs that trigger the bug, on 32-bit systems the bug can be expected to occur at random around one in 2^26 times. Thus collecting around 64 million signatures (of known data) from an affected server should be enough to extract the private key used. On 64-bit systems, the frequency of the bug is so low (less than one in 2^50) that it would be very difficult to exploit. Nonetheless, everyone is strongly encouraged to upgrade. Impact ====== A remote unauthenticated attacker can extract a private RSA key by passively collecting signatures. References ========== https://access.redhat.com/security/cve/CVE-2015-8618 https://groups.google.com/forum/#!topic/golang-dev/MEATuOi_ei4 https://lists.archlinux.org/pipermail/arch-security/2016-January/000516.html

1 0

[arch-security] [ASA-201601-15] keybase: information leakage
by Levente Polyak 17 Jan '16

17 Jan '16

Arch Linux Security Advisory ASA-201601-15 ========================================== Severity: High Date : 2016-01-17 CVE-ID : CVE-2015-8618 Package : keybase Type : information leakage Remote : Yes Link : https://wiki.archlinux.org/index.php/CVE Summary ======= The package keybase before version 1.0.8.0-2 is vulnerable to information leakage. Resolution ========== Upgrade to 1.0.8.0-2. # pacman -Syu "keybase>=1.0.8.0-2" The problem has been fixed upstream in go version 1.5.3. Workaround ========== None. Description =========== This issue can affect RSA computations in crypto/rsa, which is used by crypto/tls. TLS servers on 32-bit systems could plausibly leak their RSA private key due to this issue. Other protocol implementations that create many RSA signatures could also be impacted in the same way. Specifically, incorrect results in one part of the RSA Chinese Remainder computation can cause the result to be incorrect in such a way that it leaks one of the primes. While RSA blinding should prevent an attacker from crafting specific inputs that trigger the bug, on 32-bit systems the bug can be expected to occur at random around one in 2^26 times. Thus collecting around 64 million signatures (of known data) from an affected server should be enough to extract the private key used. On 64-bit systems, the frequency of the bug is so low (less than one in 2^50) that it would be very difficult to exploit. Nonetheless, everyone is strongly encouraged to upgrade. Impact ====== A remote unauthenticated attacker can extract a private RSA key by passively collecting signatures. References ========== https://access.redhat.com/security/cve/CVE-2015-8618 https://groups.google.com/forum/#!topic/golang-dev/MEATuOi_ei4 https://lists.archlinux.org/pipermail/arch-security/2016-January/000516.html

1 0

[arch-security] [ASA-201601-14] hub: information leakage
by Levente Polyak 17 Jan '16

17 Jan '16

Arch Linux Security Advisory ASA-201601-14 ========================================== Severity: High Date : 2016-01-17 CVE-ID : CVE-2015-8618 Package : hub Type : information leakage Remote : Yes Link : https://wiki.archlinux.org/index.php/CVE Summary ======= The package hub before version 2.2.2-2 is vulnerable to information leakage. Resolution ========== Upgrade to 2.2.2-2. # pacman -Syu "hub>=2.2.2-2" The problem has been fixed upstream in go version 1.5.3. Workaround ========== None. Description =========== This issue can affect RSA computations in crypto/rsa, which is used by crypto/tls. TLS servers on 32-bit systems could plausibly leak their RSA private key due to this issue. Other protocol implementations that create many RSA signatures could also be impacted in the same way. Specifically, incorrect results in one part of the RSA Chinese Remainder computation can cause the result to be incorrect in such a way that it leaks one of the primes. While RSA blinding should prevent an attacker from crafting specific inputs that trigger the bug, on 32-bit systems the bug can be expected to occur at random around one in 2^26 times. Thus collecting around 64 million signatures (of known data) from an affected server should be enough to extract the private key used. On 64-bit systems, the frequency of the bug is so low (less than one in 2^50) that it would be very difficult to exploit. Nonetheless, everyone is strongly encouraged to upgrade. Impact ====== A remote unauthenticated attacker can extract a private RSA key by passively collecting signatures. References ========== https://access.redhat.com/security/cve/CVE-2015-8618 https://groups.google.com/forum/#!topic/golang-dev/MEATuOi_ei4 https://lists.archlinux.org/pipermail/arch-security/2016-January/000516.html

1 0

[arch-security] [ASA-201601-13] go-ipfs: information leakage
by Levente Polyak 17 Jan '16

17 Jan '16

Arch Linux Security Advisory ASA-201601-13 ========================================== Severity: High Date : 2016-01-17 CVE-ID : CVE-2015-8618 Package : go-ipfs Type : information leakage Remote : Yes Link : https://wiki.archlinux.org/index.php/CVE Summary ======= The package go-ipfs before version 0.3.11-2 is vulnerable to information leakage. Resolution ========== Upgrade to 0.3.11-2. # pacman -Syu "go-ipfs>=0.3.11-2" The problem has been fixed upstream in go version 1.5.3. Workaround ========== None. Description =========== This issue can affect RSA computations in crypto/rsa, which is used by crypto/tls. TLS servers on 32-bit systems could plausibly leak their RSA private key due to this issue. Other protocol implementations that create many RSA signatures could also be impacted in the same way. Specifically, incorrect results in one part of the RSA Chinese Remainder computation can cause the result to be incorrect in such a way that it leaks one of the primes. While RSA blinding should prevent an attacker from crafting specific inputs that trigger the bug, on 32-bit systems the bug can be expected to occur at random around one in 2^26 times. Thus collecting around 64 million signatures (of known data) from an affected server should be enough to extract the private key used. On 64-bit systems, the frequency of the bug is so low (less than one in 2^50) that it would be very difficult to exploit. Nonetheless, everyone is strongly encouraged to upgrade. Impact ====== A remote unauthenticated attacker can extract a private RSA key by passively collecting signatures. References ========== https://access.redhat.com/security/cve/CVE-2015-8618 https://groups.google.com/forum/#!topic/golang-dev/MEATuOi_ei4 https://lists.archlinux.org/pipermail/arch-security/2016-January/000516.html

1 0

[arch-security] [ASA-201601-12] docker: information leakage
by Levente Polyak 17 Jan '16

17 Jan '16

Arch Linux Security Advisory ASA-201601-12 ========================================== Severity: High Date : 2016-01-17 CVE-ID : CVE-2015-8618 Package : docker Type : information leakage Remote : Yes Link : https://wiki.archlinux.org/index.php/CVE Summary ======= The package docker before version 1:1.9.1-2 is vulnerable to information leakage. Resolution ========== Upgrade to 1:1.9.1-2. # pacman -Syu "docker>=1:1.9.1-2" The problem has been fixed upstream in go version 1.5.3. Workaround ========== None. Description =========== This issue can affect RSA computations in crypto/rsa, which is used by crypto/tls. TLS servers on 32-bit systems could plausibly leak their RSA private key due to this issue. Other protocol implementations that create many RSA signatures could also be impacted in the same way. Specifically, incorrect results in one part of the RSA Chinese Remainder computation can cause the result to be incorrect in such a way that it leaks one of the primes. While RSA blinding should prevent an attacker from crafting specific inputs that trigger the bug, on 32-bit systems the bug can be expected to occur at random around one in 2^26 times. Thus collecting around 64 million signatures (of known data) from an affected server should be enough to extract the private key used. On 64-bit systems, the frequency of the bug is so low (less than one in 2^50) that it would be very difficult to exploit. Nonetheless, everyone is strongly encouraged to upgrade. Impact ====== A remote unauthenticated attacker can extract a private RSA key by passively collecting signatures. References ========== https://access.redhat.com/security/cve/CVE-2015-8618 https://groups.google.com/forum/#!topic/golang-dev/MEATuOi_ei4 https://lists.archlinux.org/pipermail/arch-security/2016-January/000516.html

1 0

[arch-security] [ASA-201601-11] go: information leakage
by Remi Gacogne 16 Jan '16

16 Jan '16

Arch Linux Security Advisory ASA-201601-11 ========================================== Severity: High Date : 2016-01-16 CVE-ID : CVE-2015-8618 Package : go Type : information leakage Remote : Yes Link : https://wiki.archlinux.org/index.php/CVE Summary ======= The package go before version 2:1.5.3-1 is vulnerable to information leakage. Please note that Go programs doing RSA computations must be recompiled with Go 1.5.3 in order to receive the fix. We are currently rebuilding several Arch packages concerned by this issue. Resolution ========== Upgrade to 2:1.5.3-1. # pacman -Syu "go>=2:1.5.3-1" The problem has been fixed upstream in version 1.5.3. Workaround ========== None. Description =========== This issue can affect RSA computations in crypto/rsa, which is used by crypto/tls. TLS servers on 32-bit systems could plausibly leak their RSA private key due to this issue. Other protocol implementations that create many RSA signatures could also be impacted in the same way. Specifically, incorrect results in one part of the RSA Chinese Remainder computation can cause the result to be incorrect in such a way that it leaks one of the primes. While RSA blinding should prevent an attacker from crafting specific inputs that trigger the bug, on 32-bit systems the bug can be expected to occur at random around one in 2^26 times. Thus collecting around 64 million signatures (of known data) from an affected server should be enough to extract the private key used. On 64-bit systems, the frequency of the bug is so low (less than one in 2^50) that it would be very difficult to exploit. Nonetheless, everyone is strongly encouraged to upgrade. Impact ====== A remote unauthenticated attacker can extract a private RSA key by passively collecting signatures. References ========== https://access.redhat.com/security/cve/CVE-2015-8618 https://groups.google.com/forum/#!topic/golang-dev/MEATuOi_ei4

1 0

[arch-security] [ASA-201601-10] php: multiple issues
by Levente Polyak 14 Jan '16

14 Jan '16

Arch Linux Security Advisory ASA-201601-10 ========================================== Severity: Medium Date : 2016-01-14 CVE-ID : CVE-2016-1903 CVE-2016-1904 Package : php Type : multiple issues Remote : Yes Link : https://wiki.archlinux.org/index.php/CVE Summary ======= The package php before version 7.0.2-1 is vulnerable to multiple issues including information disclosure and heap buffer overflow that is leading to denial of service or possibly arbitrary code execution. Resolution ========== Upgrade to 7.0.2-1. # pacman -Syu "php>=7.0.2-1" The problems have been fixed upstream in version 7.0.2. Workaround ========== None. Description =========== - CVE-2016-1903 (information disclosure) An out-of-bounds vulnerability has been discovered in ext/gd/libgd/gd_interpolation.c in the gdImageRotateInterpolated function. The background color of an image is passed in as an integer that represents an index to the color palette. As there is a lack of validation of that parameter, one can pass in a large number that exceeds the color palette array. This reads memory beyond the color palette. Information of the memory leak can then be obtained via the background color after the image has been rotated. - CVE-2016-1904 (arbitrary code execution) A not further specified integer overflow vulnerability has been discovered in ext/standard/exec.c (in the php_escape_shell_cmd function and the php_escape_shell_arg function). This issue results in a heap buffer overflow that is leading to a denial of service or possibly arbitrary code execution. Impact ====== A remote attacker is able to disclose information via a memory leak, perform a denial of service attack or possibly execute arbitrary code. References ========== http://seclists.org/oss-sec/2016/q1/100 https://secure.php.net/ChangeLog-7.php#7.0.2 https://bugs.php.net/bug.php?id=70976 https://github.com/php/php-src/commit/2871c70efaaaa0f

1 0

[arch-security] Suddenly being unsubscribed from all Archlinux mailing list
by Saren Arterius 14 Jan '16

14 Jan '16

Did that happen to all of us, or I just have been trolled? - Saren

3 2