- Arch-security - lists.archlinux.org

[arch-security] [ASA-201710-7] libcurl-compat: multiple issues
by Levente Polyak 06 Oct '17

06 Oct '17

Arch Linux Security Advisory ASA-201710-7 ========================================= Severity: Medium Date : 2017-10-05 CVE-ID : CVE-2017-1000099 CVE-2017-1000100 CVE-2017-1000254 Package : libcurl-compat Type : multiple issues Remote : Yes Link : https://security.archlinux.org/AVG-389 Summary ======= The package libcurl-compat before version 7.56.0-1 is vulnerable to multiple issues including information disclosure and denial of service. Resolution ========== Upgrade to 7.56.0-1. # pacman -Syu "libcurl-compat>=7.56.0-1" The problems have been fixed upstream in version 7.56.0. Workaround ========== None. Description =========== - CVE-2017-1000099 (information disclosure) An information disclosure issue has been found in curl < 7.55.0. When asking to get a file from a file:// URL, libcurl provides a feature that outputs meta-data about the file using HTTP-like headers. The code doing this would send the wrong buffer to the user (stdout or the application's provide callback), which could lead to other private data from the heap to get inadvertently displayed. The wrong buffer was an uninitialized memory area allocated on the heap and if it turned out to not contain any zero byte, it would continue and display the data following that buffer in memory. - CVE-2017-1000100 (information disclosure) An information disclosure issue has been found in curl < 7.55.0. When doing a TFTP transfer and curl/libcurl is given a URL that contains a very long file name (longer than about 515 bytes), the file name is truncated to fit within the buffer boundaries, but the buffer size is still wrongly updated to use the untruncated length. This too large value is then used in the sendto() call, making curl attempt to send more data than what is actually put into the buffer. The sendto() function will then read beyond the end of the heap based buffer. A malicious HTTP(S) server could redirect a vulnerable libcurl-using client to a crafted TFTP URL (if the client hasn't restricted which protocols it allows redirects to) and trick it to send private memory contents to a remote server over UDP. - CVE-2017-1000254 (denial of service) When libcurl connects to an FTP server and successfully logs in (anonymous or not), it asks the server for the current directory with the `PWD` command. The server then responds with a 257 response containing the path, inside double quotes. The returned path name is then kept by libcurl for subsequent uses. Due to a flaw in the string parser for this directory name, a directory name passed like this but without a closing double quote would lead to libcurl not adding a trailing NUL byte to the buffer holding the name. When libcurl would then later access the string, it could read beyond the allocated heap buffer and crash or wrongly access data beyond the buffer, thinking it was part of the path. A malicious server could abuse this fact and effectively prevent libcurl-based clients to work with it - the PWD command is always issued on new FTP connections and the mistake has a high chance of causing a segfault. Impact ====== An attacker is able to read sensitive information by asking curl to retrieve a maliciously crafted URL. Furthermore a malicious server can cause libcurl to segfault when connecting via FTP leading to denial of service. References ========== https://curl.haxx.se/docs/adv_20170809C.html https://curl.haxx.se/CVE-2017-1000099.patch https://curl.haxx.se/docs/adv_20170809B.html https://curl.haxx.se/CVE-2017-1000100.patch https://curl.haxx.se/docs/adv_20171004.html https://curl.haxx.se/CVE-2017-1000254.patch https://github.com/curl/curl/commit/5ff2c5ff25750aba1a8f64fbcad8e5b891512584 https://security.archlinux.org/CVE-2017-1000099 https://security.archlinux.org/CVE-2017-1000100 https://security.archlinux.org/CVE-2017-1000254

1 0

[arch-security] [ASA-201710-6] lib32-libcurl-compat: multiple issues
by Levente Polyak 06 Oct '17

06 Oct '17

Arch Linux Security Advisory ASA-201710-6 ========================================= Severity: Medium Date : 2017-10-05 CVE-ID : CVE-2017-1000099 CVE-2017-1000100 CVE-2017-1000254 Package : lib32-libcurl-compat Type : multiple issues Remote : Yes Link : https://security.archlinux.org/AVG-388 Summary ======= The package lib32-libcurl-compat before version 7.56.0-1 is vulnerable to multiple issues including information disclosure and denial of service. Resolution ========== Upgrade to 7.56.0-1. # pacman -Syu "lib32-libcurl-compat>=7.56.0-1" The problems have been fixed upstream in version 7.56.0. Workaround ========== None. Description =========== - CVE-2017-1000099 (information disclosure) An information disclosure issue has been found in curl < 7.55.0. When asking to get a file from a file:// URL, libcurl provides a feature that outputs meta-data about the file using HTTP-like headers. The code doing this would send the wrong buffer to the user (stdout or the application's provide callback), which could lead to other private data from the heap to get inadvertently displayed. The wrong buffer was an uninitialized memory area allocated on the heap and if it turned out to not contain any zero byte, it would continue and display the data following that buffer in memory. - CVE-2017-1000100 (information disclosure) An information disclosure issue has been found in curl < 7.55.0. When doing a TFTP transfer and curl/libcurl is given a URL that contains a very long file name (longer than about 515 bytes), the file name is truncated to fit within the buffer boundaries, but the buffer size is still wrongly updated to use the untruncated length. This too large value is then used in the sendto() call, making curl attempt to send more data than what is actually put into the buffer. The sendto() function will then read beyond the end of the heap based buffer. A malicious HTTP(S) server could redirect a vulnerable libcurl-using client to a crafted TFTP URL (if the client hasn't restricted which protocols it allows redirects to) and trick it to send private memory contents to a remote server over UDP. - CVE-2017-1000254 (denial of service) When libcurl connects to an FTP server and successfully logs in (anonymous or not), it asks the server for the current directory with the `PWD` command. The server then responds with a 257 response containing the path, inside double quotes. The returned path name is then kept by libcurl for subsequent uses. Due to a flaw in the string parser for this directory name, a directory name passed like this but without a closing double quote would lead to libcurl not adding a trailing NUL byte to the buffer holding the name. When libcurl would then later access the string, it could read beyond the allocated heap buffer and crash or wrongly access data beyond the buffer, thinking it was part of the path. A malicious server could abuse this fact and effectively prevent libcurl-based clients to work with it - the PWD command is always issued on new FTP connections and the mistake has a high chance of causing a segfault. Impact ====== An attacker is able to read sensitive information by asking curl to retrieve a maliciously crafted URL. Furthermore a malicious server can cause libcurl to segfault when connecting via FTP leading to denial of service. References ========== https://curl.haxx.se/docs/adv_20170809C.html https://curl.haxx.se/CVE-2017-1000099.patch https://curl.haxx.se/docs/adv_20170809B.html https://curl.haxx.se/CVE-2017-1000100.patch https://curl.haxx.se/docs/adv_20171004.html https://curl.haxx.se/CVE-2017-1000254.patch https://github.com/curl/curl/commit/5ff2c5ff25750aba1a8f64fbcad8e5b891512584 https://security.archlinux.org/CVE-2017-1000099 https://security.archlinux.org/CVE-2017-1000100 https://security.archlinux.org/CVE-2017-1000254

1 0

[arch-security] [ASA-201710-5] libcurl-gnutls: multiple issues
by Levente Polyak 06 Oct '17

06 Oct '17

Arch Linux Security Advisory ASA-201710-5 ========================================= Severity: Medium Date : 2017-10-05 CVE-ID : CVE-2017-1000099 CVE-2017-1000100 CVE-2017-1000254 Package : libcurl-gnutls Type : multiple issues Remote : Yes Link : https://security.archlinux.org/AVG-387 Summary ======= The package libcurl-gnutls before version 7.56.0-1 is vulnerable to multiple issues including information disclosure and denial of service. Resolution ========== Upgrade to 7.56.0-1. # pacman -Syu "libcurl-gnutls>=7.56.0-1" The problems have been fixed upstream in version 7.56.0. Workaround ========== None. Description =========== - CVE-2017-1000099 (information disclosure) An information disclosure issue has been found in curl < 7.55.0. When asking to get a file from a file:// URL, libcurl provides a feature that outputs meta-data about the file using HTTP-like headers. The code doing this would send the wrong buffer to the user (stdout or the application's provide callback), which could lead to other private data from the heap to get inadvertently displayed. The wrong buffer was an uninitialized memory area allocated on the heap and if it turned out to not contain any zero byte, it would continue and display the data following that buffer in memory. - CVE-2017-1000100 (information disclosure) An information disclosure issue has been found in curl < 7.55.0. When doing a TFTP transfer and curl/libcurl is given a URL that contains a very long file name (longer than about 515 bytes), the file name is truncated to fit within the buffer boundaries, but the buffer size is still wrongly updated to use the untruncated length. This too large value is then used in the sendto() call, making curl attempt to send more data than what is actually put into the buffer. The sendto() function will then read beyond the end of the heap based buffer. A malicious HTTP(S) server could redirect a vulnerable libcurl-using client to a crafted TFTP URL (if the client hasn't restricted which protocols it allows redirects to) and trick it to send private memory contents to a remote server over UDP. - CVE-2017-1000254 (denial of service) When libcurl connects to an FTP server and successfully logs in (anonymous or not), it asks the server for the current directory with the `PWD` command. The server then responds with a 257 response containing the path, inside double quotes. The returned path name is then kept by libcurl for subsequent uses. Due to a flaw in the string parser for this directory name, a directory name passed like this but without a closing double quote would lead to libcurl not adding a trailing NUL byte to the buffer holding the name. When libcurl would then later access the string, it could read beyond the allocated heap buffer and crash or wrongly access data beyond the buffer, thinking it was part of the path. A malicious server could abuse this fact and effectively prevent libcurl-based clients to work with it - the PWD command is always issued on new FTP connections and the mistake has a high chance of causing a segfault. Impact ====== An attacker is able to read sensitive information by asking curl to retrieve a maliciously crafted URL. Furthermore a malicious server can cause libcurl to segfault when connecting via FTP leading to denial of service. References ========== https://curl.haxx.se/docs/adv_20170809C.html https://curl.haxx.se/CVE-2017-1000099.patch https://curl.haxx.se/docs/adv_20170809B.html https://curl.haxx.se/CVE-2017-1000100.patch https://curl.haxx.se/docs/adv_20171004.html https://curl.haxx.se/CVE-2017-1000254.patch https://github.com/curl/curl/commit/5ff2c5ff25750aba1a8f64fbcad8e5b891512584 https://security.archlinux.org/CVE-2017-1000099 https://security.archlinux.org/CVE-2017-1000100 https://security.archlinux.org/CVE-2017-1000254

1 0

[arch-security] [ASA-201710-4] lib32-libcurl-gnutls: multiple issues
by Levente Polyak 06 Oct '17

06 Oct '17

Arch Linux Security Advisory ASA-201710-4 ========================================= Severity: Medium Date : 2017-10-05 CVE-ID : CVE-2017-1000099 CVE-2017-1000100 CVE-2017-1000254 Package : lib32-libcurl-gnutls Type : multiple issues Remote : Yes Link : https://security.archlinux.org/AVG-386 Summary ======= The package lib32-libcurl-gnutls before version 7.56.0-1 is vulnerable to multiple issues including information disclosure and denial of service. Resolution ========== Upgrade to 7.56.0-1. # pacman -Syu "lib32-libcurl-gnutls>=7.56.0-1" The problems have been fixed upstream in version 7.56.0. Workaround ========== None. Description =========== - CVE-2017-1000099 (information disclosure) An information disclosure issue has been found in curl < 7.55.0. When asking to get a file from a file:// URL, libcurl provides a feature that outputs meta-data about the file using HTTP-like headers. The code doing this would send the wrong buffer to the user (stdout or the application's provide callback), which could lead to other private data from the heap to get inadvertently displayed. The wrong buffer was an uninitialized memory area allocated on the heap and if it turned out to not contain any zero byte, it would continue and display the data following that buffer in memory. - CVE-2017-1000100 (information disclosure) An information disclosure issue has been found in curl < 7.55.0. When doing a TFTP transfer and curl/libcurl is given a URL that contains a very long file name (longer than about 515 bytes), the file name is truncated to fit within the buffer boundaries, but the buffer size is still wrongly updated to use the untruncated length. This too large value is then used in the sendto() call, making curl attempt to send more data than what is actually put into the buffer. The sendto() function will then read beyond the end of the heap based buffer. A malicious HTTP(S) server could redirect a vulnerable libcurl-using client to a crafted TFTP URL (if the client hasn't restricted which protocols it allows redirects to) and trick it to send private memory contents to a remote server over UDP. - CVE-2017-1000254 (denial of service) When libcurl connects to an FTP server and successfully logs in (anonymous or not), it asks the server for the current directory with the `PWD` command. The server then responds with a 257 response containing the path, inside double quotes. The returned path name is then kept by libcurl for subsequent uses. Due to a flaw in the string parser for this directory name, a directory name passed like this but without a closing double quote would lead to libcurl not adding a trailing NUL byte to the buffer holding the name. When libcurl would then later access the string, it could read beyond the allocated heap buffer and crash or wrongly access data beyond the buffer, thinking it was part of the path. A malicious server could abuse this fact and effectively prevent libcurl-based clients to work with it - the PWD command is always issued on new FTP connections and the mistake has a high chance of causing a segfault. Impact ====== An attacker is able to read sensitive information by asking curl to retrieve a maliciously crafted URL. Furthermore a malicious server can cause libcurl to segfault when connecting via FTP leading to denial of service. References ========== https://curl.haxx.se/docs/adv_20170809C.html https://curl.haxx.se/CVE-2017-1000099.patch https://curl.haxx.se/docs/adv_20170809B.html https://curl.haxx.se/CVE-2017-1000100.patch https://curl.haxx.se/docs/adv_20171004.html https://curl.haxx.se/CVE-2017-1000254.patch https://github.com/curl/curl/commit/5ff2c5ff25750aba1a8f64fbcad8e5b891512584 https://security.archlinux.org/CVE-2017-1000099 https://security.archlinux.org/CVE-2017-1000100 https://security.archlinux.org/CVE-2017-1000254

1 0

[arch-security] [ASA-201710-3] lib32-curl: multiple issues
by Levente Polyak 06 Oct '17

06 Oct '17

Arch Linux Security Advisory ASA-201710-3 ========================================= Severity: Medium Date : 2017-10-05 CVE-ID : CVE-2017-1000099 CVE-2017-1000100 CVE-2017-1000254 Package : lib32-curl Type : multiple issues Remote : Yes Link : https://security.archlinux.org/AVG-371 Summary ======= The package lib32-curl before version 7.56.0-1 is vulnerable to multiple issues including information disclosure and denial of service. Resolution ========== Upgrade to 7.56.0-1. # pacman -Syu "lib32-curl>=7.56.0-1" The problems have been fixed upstream in version 7.56.0. Workaround ========== None. Description =========== - CVE-2017-1000099 (information disclosure) An information disclosure issue has been found in curl < 7.55.0. When asking to get a file from a file:// URL, libcurl provides a feature that outputs meta-data about the file using HTTP-like headers. The code doing this would send the wrong buffer to the user (stdout or the application's provide callback), which could lead to other private data from the heap to get inadvertently displayed. The wrong buffer was an uninitialized memory area allocated on the heap and if it turned out to not contain any zero byte, it would continue and display the data following that buffer in memory. - CVE-2017-1000100 (information disclosure) An information disclosure issue has been found in curl < 7.55.0. When doing a TFTP transfer and curl/libcurl is given a URL that contains a very long file name (longer than about 515 bytes), the file name is truncated to fit within the buffer boundaries, but the buffer size is still wrongly updated to use the untruncated length. This too large value is then used in the sendto() call, making curl attempt to send more data than what is actually put into the buffer. The sendto() function will then read beyond the end of the heap based buffer. A malicious HTTP(S) server could redirect a vulnerable libcurl-using client to a crafted TFTP URL (if the client hasn't restricted which protocols it allows redirects to) and trick it to send private memory contents to a remote server over UDP. - CVE-2017-1000254 (denial of service) When libcurl connects to an FTP server and successfully logs in (anonymous or not), it asks the server for the current directory with the `PWD` command. The server then responds with a 257 response containing the path, inside double quotes. The returned path name is then kept by libcurl for subsequent uses. Due to a flaw in the string parser for this directory name, a directory name passed like this but without a closing double quote would lead to libcurl not adding a trailing NUL byte to the buffer holding the name. When libcurl would then later access the string, it could read beyond the allocated heap buffer and crash or wrongly access data beyond the buffer, thinking it was part of the path. A malicious server could abuse this fact and effectively prevent libcurl-based clients to work with it - the PWD command is always issued on new FTP connections and the mistake has a high chance of causing a segfault. Impact ====== An attacker is able to read sensitive information by asking curl to retrieve a maliciously crafted URL. Furthermore a malicious server can cause libcurl to segfault when connecting via FTP leading to denial of service. References ========== https://curl.haxx.se/docs/adv_20170809C.html https://curl.haxx.se/CVE-2017-1000099.patch https://curl.haxx.se/docs/adv_20170809B.html https://curl.haxx.se/CVE-2017-1000100.patch https://curl.haxx.se/docs/adv_20171004.html https://curl.haxx.se/CVE-2017-1000254.patch https://github.com/curl/curl/commit/5ff2c5ff25750aba1a8f64fbcad8e5b891512584 https://security.archlinux.org/CVE-2017-1000099 https://security.archlinux.org/CVE-2017-1000100 https://security.archlinux.org/CVE-2017-1000254

1 0

[arch-security] [ASA-201710-2] curl: denial of service
by Levente Polyak 06 Oct '17

06 Oct '17

Arch Linux Security Advisory ASA-201710-2 ========================================= Severity: Low Date : 2017-10-05 CVE-ID : CVE-2017-1000254 Package : curl Type : denial of service Remote : Yes Link : https://security.archlinux.org/AVG-422 Summary ======= The package curl before version 7.56.0-1 is vulnerable to denial of service. Resolution ========== Upgrade to 7.56.0-1. # pacman -Syu "curl>=7.56.0-1" The problem has been fixed upstream in version 7.56.0. Workaround ========== None. Description =========== When libcurl connects to an FTP server and successfully logs in (anonymous or not), it asks the server for the current directory with the `PWD` command. The server then responds with a 257 response containing the path, inside double quotes. The returned path name is then kept by libcurl for subsequent uses. Due to a flaw in the string parser for this directory name, a directory name passed like this but without a closing double quote would lead to libcurl not adding a trailing NUL byte to the buffer holding the name. When libcurl would then later access the string, it could read beyond the allocated heap buffer and crash or wrongly access data beyond the buffer, thinking it was part of the path. A malicious server could abuse this fact and effectively prevent libcurl-based clients to work with it - the PWD command is always issued on new FTP connections and the mistake has a high chance of causing a segfault. Impact ====== A malicious server can cause libcurl to segfault when connecting via FTP leading to denial of service. References ========== https://curl.haxx.se/docs/adv_20171004.html https://curl.haxx.se/CVE-2017-1000254.patch https://github.com/curl/curl/commit/5ff2c5ff25750aba1a8f64fbcad8e5b891512584 https://security.archlinux.org/CVE-2017-1000254

1 0

[arch-security] [ASA-201710-1] dnsmasq: multiple issues
by Levente Polyak 02 Oct '17

02 Oct '17

Arch Linux Security Advisory ASA-201710-1 ========================================= Severity: Critical Date : 2017-10-02 CVE-ID : CVE-2017-14491 CVE-2017-14492 CVE-2017-14493 CVE-2017-14494 CVE-2017-14495 CVE-2017-14496 Package : dnsmasq Type : multiple issues Remote : Yes Link : https://security.archlinux.org/AVG-421 Summary ======= The package dnsmasq before version 2.78-1 is vulnerable to multiple issues including arbitrary code execution, denial of service and information disclosure. Resolution ========== Upgrade to 2.78-1. # pacman -Syu "dnsmasq>=2.78-1" The problems have been fixed upstream in version 2.78. Workaround ========== None. Description =========== - CVE-2017-14491 (arbitrary code execution) A heap buffer overflow was found in dnsmasq in the code responsible for building DNS replies. An attacker could send crafted DNS packets to dnsmasq which would cause it to crash or, potentially, execute arbitrary code. - CVE-2017-14492 (arbitrary code execution) A heap buffer overflow was discovered in dnsmasq in the IPv6 router advertisement (RA) handling code. An attacker on the local network segment could send crafted RAs to dnsmasq which would cause it to crash or, potentially, execute arbitrary code. This issue only affected configurations using one of these options: enable-ra, ra-only, slaac, ra-names, ra-advrouter, or ra-stateless. - CVE-2017-14493 (arbitrary code execution) A stack buffer overflow was found in dnsmasq in the DHCPv6 code. An attacker on the local network could send a crafted DHCPv6 request to dnsmasq which would cause it to a crash or, potentially, execute arbitrary code. - CVE-2017-14494 (information disclosure) An information leak was found in dnsmasq in the DHCPv6 relay code. An attacker on the local network could send crafted DHCPv6 packets to dnsmasq causing it to forward the contents of process memory, potentially leaking sensitive data. - CVE-2017-14495 (denial of service) A memory exhaustion flaw was found in dnsmasq in the EDNS0 code. An attacker could send crafted DNS packets which would trigger memory allocations which would never be freed, leading to unbounded memory consumption and eventually a crash. This issue only affected configurations using one of the options: add-mac, add-cpe-id, or add- subnet. - CVE-2017-14496 (denial of service) An integer underflow flaw leading to a buffer over-read was found in dnsmasq in the EDNS0 code. An attacker could send crafted DNS packets to dnsmasq which would cause it to crash. This issue only affected configurations using one of the options: add-mac, add-cpe-id, or add- subnet. Impact ====== A remote attacker is able to execute arbitrary code, disclose sensitive information or crash the application by sending specially crafted packets. References ========== https://security.googleblog.com/2017/10/behind-masq-yet-more-dns-and-dhcp.h… https://github.com/google/security-research-pocs/tree/master/vulnerabilitie… http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=0549c73b7ea6b… http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=62cb936cb7ad5… http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=24036ea507862… http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=3d4ff1ba84195… http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=33e3f1029c9ec… http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=51eadb692a512… http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=897c113fda088… https://security.archlinux.org/CVE-2017-14491 https://security.archlinux.org/CVE-2017-14492 https://security.archlinux.org/CVE-2017-14493 https://security.archlinux.org/CVE-2017-14494 https://security.archlinux.org/CVE-2017-14495 https://security.archlinux.org/CVE-2017-14496

1 0

[arch-security] [ASA-201709-23] ffmpeg2.8: denial of service
by Levente Polyak 28 Sep '17

28 Sep '17

Arch Linux Security Advisory ASA-201709-23 ========================================== Severity: Medium Date : 2017-09-28 CVE-ID : CVE-2017-14055 CVE-2017-14056 CVE-2017-14057 CVE-2017-14058 CVE-2017-14059 CVE-2017-14169 CVE-2017-14170 CVE-2017-14171 CVE-2017-14225 Package : ffmpeg2.8 Type : denial of service Remote : Yes Link : https://security.archlinux.org/AVG-405 Summary ======= The package ffmpeg2.8 before version 2.8.13-1 is vulnerable to denial of service. Resolution ========== Upgrade to 2.8.13-1. # pacman -Syu "ffmpeg2.8>=2.8.13-1" The problems have been fixed upstream in version 2.8.13. Workaround ========== None. Description =========== - CVE-2017-14055 (denial of service) In libavformat/mvdec.c in FFmpeg 3.3.3, a DoS in mv_read_header() due to lack of an EOF (End of File) check might cause huge CPU and memory consumption. When a crafted MV file, which claims a large "nb_frames" field in the header but does not contain sufficient backing data, is provided, the loop over the frames would consume huge CPU and memory resources, since there is no EOF check inside the loop. - CVE-2017-14056 (denial of service) In libavformat/rl2.c in FFmpeg 3.3.3, a DoS in rl2_read_header() due to lack of an EOF (End of File) check might cause huge CPU and memory consumption. When a crafted RL2 file, which claims a large "frame_count" field in the header but does not contain sufficient backing data, is provided, the loops (for offset and size tables) would consume huge CPU and memory resources, since there is no EOF check inside these loops. - CVE-2017-14057 (denial of service) In FFmpeg 3.3.3, a DoS in asf_read_marker() due to lack of an EOF (End of File) check might cause huge CPU and memory consumption. When a crafted ASF file, which claims a large "name_len" or "count" field in the header but does not contain sufficient backing data, is provided, the loops over the name and markers would consume huge CPU and memory resources, since there is no EOF check inside these loops. - CVE-2017-14058 (denial of service) In FFmpeg 3.3.3, the read_data function in libavformat/hls.c does not restrict reload attempts for an insufficient list, which allows remote attackers to cause a denial of service (infinite loop). - CVE-2017-14059 (denial of service) In FFmpeg 3.3.3, a DoS in cine_read_header() due to lack of an EOF check might cause huge CPU and memory consumption. When a crafted CINE file, which claims a large "duration" field in the header but does not contain sufficient backing data, is provided, the image-offset parsing loop would consume huge CPU and memory resources, since there is no EOF check inside the loop. - CVE-2017-14169 (denial of service) In the mxf_read_primer_pack function in libavformat/mxfdec.c in FFmpeg 3.3.3, an integer signedness error might occur when a crafted file, which claims a large "item_num" field such as 0xffffffff, is provided. As a result, the variable "item_num" turns negative, bypassing the check for a large value. - CVE-2017-14170 (denial of service) In libavformat/mxfdec.c in FFmpeg 3.3.3, a DoS in mxf_read_index_entry_array() due to lack of an EOF (End of File) check might cause huge CPU consumption. When a crafted MXF file, which claims a large "nb_index_entries" field in the header but does not contain sufficient backing data, is provided, the loop would consume huge CPU resources, since there is no EOF check inside the loop. Moreover, this big loop can be invoked multiple times if there is more than one applicable data segment in the crafted MXF file. - CVE-2017-14171 (denial of service) In libavformat/nsvdec.c in FFmpeg 3.3.3, a DoS in nsv_parse_NSVf_header() due to lack of an EOF (End of File) check might cause huge CPU consumption. When a crafted NSV file, which claims a large "table_entries_used" field in the header but does not contain sufficient backing data, is provided, the loop over 'table_entries_used' would consume huge CPU resources, since there is no EOF check inside the loop. - CVE-2017-14225 (denial of service) The av_color_primaries_name function in libavutil/pixdesc.c in FFmpeg 3.3.3 may return a NULL pointer depending on a value contained in a file, but callers do not anticipate this, as demonstrated by the avcodec_string function in libavcodec/utils.c, leading to a NULL pointer dereference. Impact ====== A remote attacker is able to crash the application while watching a HLS stream. Furthermore an attacker is able to crash the application by tricking the user into opening a specially crafted video file. References ========== https://github.com/FFmpeg/FFmpeg/commit/4f05e2e2dc1a89f38cd9f0960a6561083d7… https://github.com/FFmpeg/FFmpeg/commit/96f24d1bee7fe7bac08e2b7c74db1a046c9… https://github.com/FFmpeg/FFmpeg/commit/7f9ec5593e04827249e7aeb466da06a98a0… https://github.com/FFmpeg/FFmpeg/commit/7ec414892ddcad88313848494b6fc5f437c… https://github.com/FFmpeg/FFmpeg/commit/7e80b63ecd259d69d383623e75b318bf2bd… https://github.com/FFmpeg/FFmpeg/commit/9d00fb9d70ee8c0cc7002b89318c5be00f1… https://github.com/FFmpeg/FFmpeg/commit/900f39692ca0337a98a7cf047e4e2611071… https://github.com/FFmpeg/FFmpeg/commit/c24bcb553650b91e9eff15ef6e54ca73de2… https://github.com/FFmpeg/FFmpeg/commit/837cb4325b712ff1aab531bf41668933f61… https://security.archlinux.org/CVE-2017-14055 https://security.archlinux.org/CVE-2017-14056 https://security.archlinux.org/CVE-2017-14057 https://security.archlinux.org/CVE-2017-14058 https://security.archlinux.org/CVE-2017-14059 https://security.archlinux.org/CVE-2017-14169 https://security.archlinux.org/CVE-2017-14170 https://security.archlinux.org/CVE-2017-14171 https://security.archlinux.org/CVE-2017-14225

1 0

[arch-security] [ASA-201709-22] nvidia: multiple issues
by Levente Polyak 28 Sep '17

28 Sep '17

Arch Linux Security Advisory ASA-201709-22 ========================================== Severity: High Date : 2017-09-28 CVE-ID : CVE-2017-6266 CVE-2017-6267 CVE-2017-6272 Package : nvidia Type : multiple issues Remote : Yes Link : https://security.archlinux.org/AVG-418 Summary ======= The package nvidia before version 384.90-1 is vulnerable to multiple issues including privilege escalation and denial of service. Resolution ========== Upgrade to 384.90-1. # pacman -Syu "nvidia>=384.90-1" The problems have been fixed upstream in version 384.90. Workaround ========== None. Description =========== - CVE-2017-6266 (denial of service) NVIDIA GPU Display Driver contains a vulnerability in the kernel mode layer handler where improper access controls could allow unprivileged users to cause a denial of service. - CVE-2017-6267 (denial of service) NVIDIA GPU Display Driver contains a vulnerability in the kernel mode layer handler where an incorrect initialization of internal objects can cause an infinite loop, which may lead to a denial of service. - CVE-2017-6272 (privilege escalation) NVIDIA GPU Display Driver contains a vulnerability in the kernel mode layer handler where a value passed from a user to the driver is not correctly validated and used as the index to an array, which may lead to a denial of service or possible escalation of privileges. Impact ====== A remote attacker who is able to invoke certain graphics API calls may be able to escalate privileges or crash the system on the affected host. References ========== https://nvidia.custhelp.com/app/answers/detail/a_id/4544 https://security.archlinux.org/CVE-2017-6266 https://security.archlinux.org/CVE-2017-6267 https://security.archlinux.org/CVE-2017-6272

1 0

[arch-security] [ASA-201709-21] openvpn: arbitrary code execution
by Levente Polyak 28 Sep '17

28 Sep '17

Arch Linux Security Advisory ASA-201709-21 ========================================== Severity: Medium Date : 2017-09-28 CVE-ID : CVE-2017-12166 Package : openvpn Type : arbitrary code execution Remote : Yes Link : https://security.archlinux.org/AVG-420 Summary ======= The package openvpn before version 2.4.4-1 is vulnerable to arbitrary code execution. Resolution ========== Upgrade to 2.4.4-1. # pacman -Syu "openvpn>=2.4.4-1" The problem has been fixed upstream in version 2.4.4. Workaround ========== Ensure 'key-method 2' is used (default value). Description =========== The bounds check in the read_key() function in OpenVPN before 2.4.4 and 2.3.18 was performed after using the value, instead of before. If 'key-method 1' is used, this allowed an attacker to send a malformed packet to trigger a stack buffer overflow. Note that 'key-method 1' has been replaced by 'key method 2' as the default in OpenVPN 2.0 (released on 2005-04-17), and explicitly deprecated in 2.4 and marked for removal in 2.5. This should limit the amount of users impacted by this issue. Impact ====== A remote attacker is able to execute arbitrary code on the affected host when an old key-method is configured. References ========== https://community.openvpn.net/openvpn/wiki/CVE-2017-12166 https://github.com/OpenVPN/openvpn/commit/3b1a61e9fb27213c46f76312f4065816b… https://security.archlinux.org/CVE-2017-12166

1 0