- Arch-security - lists.archlinux.org

[ASA-201904-3] apache: multiple issues
by Remi Gacogne 11 Apr '19

11 Apr '19

Arch Linux Security Advisory ASA-201904-3 ========================================= Severity: Critical Date : 2019-04-05 CVE-ID : CVE-2019-0196 CVE-2019-0197 CVE-2019-0211 CVE-2019-0215 CVE-2019-0217 CVE-2019-0220 Package : apache Type : multiple issues Remote : Yes Link : https://security.archlinux.org/AVG-946 Summary ======= The package apache before version 2.4.39-1 is vulnerable to multiple issues including privilege escalation, access restriction bypass and denial of service. Resolution ========== Upgrade to 2.4.39-1. # pacman -Syu "apache>=2.4.39-1" The problems have been fixed upstream in version 2.4.39. Workaround ========== None. Description =========== - CVE-2019-0196 (denial of service) A use-after-free issue has been found in the http/2 request handling code of Apache HTTPd <= 2.4.18 and <= 2.4.38. Using crafted network input, the http/2 request handling could be made to access freed memory in string comparison when determining the method of a request and thus process the request incorrectly. - CVE-2019-0197 (denial of service) An issue has been found in Apache HTTPd >= 2.4.34 and <= 2.4.38. When HTTP/2 was enabled for a http: host or H2Upgrade was enabled for h2 on a https: host, an Upgrade request from http/1.1 to http/2 that was not the first request on a connection could lead to a misconfiguration and crash. A server that never enabled the h2 protocol or that only enabled it for https: and did not configure the "H2Upgrade on" is unaffected by this. - CVE-2019-0211 (privilege escalation) In Apache HTTP Server 2.4 releases 2.4.17 to 2.4.38, with MPM event, worker or prefork, code executing in less-privileged child processes or threads (including scripts executed by an in-process scripting interpreter) could execute arbitrary code with the privileges of the parent process (usually root) by manipulating the scoreboard. - CVE-2019-0215 (access restriction bypass) In Apache HTTP Server 2.4 releases 2.4.37 and 2.4.38, a bug in mod_ssl when using per-location client certificate verification with TLSv1.3 allowed a client supporting Post-Handshake Authentication to bypass configured access control restrictions. - CVE-2019-0217 (access restriction bypass) In Apache HTTP Server 2.4 release 2.4.38 and prior, a race condition in mod_auth_digest when running in a threaded server could allow a user with valid credentials to authenticate using another username, bypassing configured access control restrictions. - CVE-2019-0220 (access restriction bypass) A security issue has been found in Apache HTTPd 2.4.x before 2.4.39. When the path component of a request URL contains multiple consecutive slashes ('/'), directives such as LocationMatch and RewriteRule must account for duplicates in regular expressions while other aspects of the servers processing will implicitly collapse them. Impact ====== A remote attacker can bypass access control restrictions, or crash a server via a crafted HTTP/2 query. A local attacker can elevate privileges to root by manipulating the scoreboard. References ========== https://httpd.apache.org/security/vulnerabilities_24.html https://security.archlinux.org/CVE-2019-0196 https://security.archlinux.org/CVE-2019-0197 https://security.archlinux.org/CVE-2019-0211 https://security.archlinux.org/CVE-2019-0215 https://security.archlinux.org/CVE-2019-0217 https://security.archlinux.org/CVE-2019-0220

1 0

[ASA-201904-2] gnutls: multiple issues
by Remi Gacogne 11 Apr '19

11 Apr '19

Arch Linux Security Advisory ASA-201904-2 ========================================= Severity: Critical Date : 2019-04-05 CVE-ID : CVE-2019-3829 CVE-2019-3836 Package : gnutls Type : multiple issues Remote : Yes Link : https://security.archlinux.org/AVG-945 Summary ======= The package gnutls before version 3.6.7-1 is vulnerable to multiple issues including arbitrary code execution and denial of service. Resolution ========== Upgrade to 3.6.7-1. # pacman -Syu "gnutls>=3.6.7-1" The problems have been fixed upstream in version 3.6.7. Workaround ========== None. Description =========== - CVE-2019-3829 (arbitrary code execution) A critical memory corruption vulnerability has been found in GnuTLS versions prior to 3.6.7, in any API backed by verify_crt(), including gnutls_x509_trust_list_verify_crt() and related routines. Any client or server that verifies X.509 certificates with GnuTLS is likely affected and can be compromised by a malicious server or active network attacker. - CVE-2019-3836 (denial of service) An invalid pointer access via malformed TLS1.3 async messages has been found in GnuTLS versions prior to 3.6.7. Impact ====== A remote attacker can execute arbitrary code on a client or server validating certificates. References ========== https://lists.gnupg.org/pipermail/gnutls-help/2019-March/004497.html https://gitlab.com/gnutls/gnutls/issues/694 https://gitlab.com/gnutls/gnutls/issues/704 https://security.archlinux.org/CVE-2019-3829 https://security.archlinux.org/CVE-2019-3836

1 0

[ASA-201904-1] evolution: content spoofing
by Remi Gacogne 11 Apr '19

11 Apr '19

Arch Linux Security Advisory ASA-201904-1 ========================================= Severity: High Date : 2019-04-02 CVE-ID : CVE-2018-15587 Package : evolution Type : content spoofing Remote : Yes Link : https://security.archlinux.org/AVG-889 Summary ======= The package evolution before version 3.32.0-1 is vulnerable to content spoofing. Resolution ========== Upgrade to 3.32.0-1. # pacman -Syu "evolution>=3.32.0-1" The problem has been fixed upstream in version 3.32.0. Workaround ========== None. Description =========== GNOME Evolution through 3.28.2 is prone to OpenPGP signatures being spoofed for arbitrary messages using a specially crafted email that contains a valid signature from the entity to be impersonated as an attachment. Impact ====== A remote attacker can spoof a valid signature for a specially crafted e-mail. References ========== https://bugzilla.gnome.org/show_bug.cgi?id=796424 https://gitlab.gnome.org/GNOME/evolution/issues/120 https://security.archlinux.org/CVE-2018-15587

1 0

[ASA-201903-16] dovecot: privilege escalation
by Remi Gacogne 28 Mar '19

28 Mar '19

Arch Linux Security Advisory ASA-201903-16 ========================================== Severity: High Date : 2019-03-28 CVE-ID : CVE-2019-7524 Package : dovecot Type : privilege escalation Remote : No Link : https://security.archlinux.org/AVG-944 Summary ======= The package dovecot before version 2.3.5.1-1 is vulnerable to privilege escalation. Resolution ========== Upgrade to 2.3.5.1-1. # pacman -Syu "dovecot>=2.3.5.1-1" The problem has been fixed upstream in version 2.3.5.1. Workaround ========== None. Description =========== A stack-based buffer overflow has been found in Dovecot versions prior to 2.3.5.1. When reading FTS or POP3-UIDL header from dovecot index, the input buffer size is not bound, and data is copied to target structure causing stack overflow. This can be used for local root privilege escalation or executing arbitrary code in dovecot process context. This requires ability to directly modify dovecot indexes. Impact ====== A local attacker with the ability to alter FTS or POP3-UIDL files can escalate privileges to root. References ========== https://seclists.org/oss-sec/2019/q1/197 https://dovecot.org/pipermail/dovecot/2019-March/115296.html https://github.com/dovecot/core/commit/79679674eb6d2c7d38f2537e613efc103058… https://github.com/dovecot/core/commit/d79845350e0754f5e25c41bd56591ddd5b0a… https://security.archlinux.org/CVE-2019-7524

1 0

[ASA-201903-15] imagemagick: arbitrary code execution
by Remi Gacogne 28 Mar '19

28 Mar '19

Arch Linux Security Advisory ASA-201903-15 ========================================== Severity: Critical Date : 2019-03-28 CVE-ID : CVE-2019-9956 Package : imagemagick Type : arbitrary code execution Remote : Yes Link : https://security.archlinux.org/AVG-931 Summary ======= The package imagemagick before version 7.0.8.35-1 is vulnerable to arbitrary code execution. Resolution ========== Upgrade to 7.0.8.35-1. # pacman -Syu "imagemagick>=7.0.8.35-1" The problem has been fixed upstream in version 7.0.8.35. Workaround ========== None. Description =========== A stack-based buffer overflow has been found in ImageMagick before 7.0.8-35, in the WritePSImage() function. Impact ====== An attacker can execute arbitrary code via a crafted file. References ========== https://github.com/ImageMagick/ImageMagick/issues/1523 https://github.com/ImageMagick/ImageMagick/commit/34a6a5a45e83a4af852090b4e… https://security.archlinux.org/CVE-2019-9956

1 0

[ASA-201903-14] firefox: arbitrary code execution
by Remi Gacogne 24 Mar '19

24 Mar '19

Arch Linux Security Advisory ASA-201903-14 ========================================== Severity: Critical Date : 2019-03-23 CVE-ID : CVE-2019-9810 CVE-2019-9813 Package : firefox Type : arbitrary code execution Remote : Yes Link : https://security.archlinux.org/AVG-930 Summary ======= The package firefox before version 66.0.1-1 is vulnerable to arbitrary code execution. Resolution ========== Upgrade to 66.0.1-1. # pacman -Syu "firefox>=66.0.1-1" The problems have been fixed upstream in version 66.0.1. Workaround ========== None. Description =========== - CVE-2019-9810 (arbitrary code execution) An incorrect alias information in the IonMonkey JIT compiler of Firefox before 66.0.1 for the Array.prototype.slice method may lead to missing bounds check and a buffer overflow. - CVE-2019-9813 (arbitrary code execution) An incorrect handling of __proto__ mutations may lead to type confusion in the IonMonkey JIT code of Firefox before 66.0.1 and can be leveraged for arbitrary memory read and write. Impact ====== A remote attacker can execute arbitrary code on the affected host. References ========== https://www.mozilla.org/en-US/security/advisories/mfsa2019-09/ https://www.mozilla.org/en-US/security/advisories/mfsa2019-09/#CVE-2019-9810 https://bugzilla.mozilla.org/show_bug.cgi?id=1537924 https://www.mozilla.org/en-US/security/advisories/mfsa2019-09/#CVE-2019-9813 https://bugzilla.mozilla.org/show_bug.cgi?id=1538006 https://security.archlinux.org/CVE-2019-9810 https://security.archlinux.org/CVE-2019-9813

1 0

[ASA-201903-13] powerdns: insufficient validation
by Remi Gacogne 22 Mar '19

22 Mar '19

Arch Linux Security Advisory ASA-201903-13 ========================================== Severity: High Date : 2019-03-22 CVE-ID : CVE-2019-3871 Package : powerdns Type : insufficient validation Remote : Yes Link : https://security.archlinux.org/AVG-927 Summary ======= The package powerdns before version 4.1.7-1 is vulnerable to insufficient validation. Resolution ========== Upgrade to 4.1.7-1. # pacman -Syu "powerdns>=4.1.7-1" The problem has been fixed upstream in version 4.1.7. Workaround ========== None. Description =========== An issue has been found in PowerDNS Authoritative Server before 4.1.7, when the HTTP remote backend is used in RESTful mode (without post=1 set), allowing a remote user to cause the HTTP backend to connect to an attacker-specified host instead of the configured one, via a crafted DNS query. This can be used to cause a denial of service by preventing the remote backend from getting a response, content spoofing if the attacker can time its own query so that subsequent queries will use an attacker-controlled HTTP server instead of the configured one, and possibly information disclosure if the Authoritative Server has access to internal servers. Impact ====== A remote user can cause a denial of service by preventing the remote backend from getting a response, content spoofing if the attacker can time its own query so that subsequent queries will use an attacker- controlled HTTP server instead of the configured one, and possibly information disclosure if the Authoritative Server has access to internal servers. References ========== https://seclists.org/oss-sec/2019/q1/185 https://docs.powerdns.com/authoritative/security-advisories/powerdns-adviso… https://github.com/PowerDNS/pdns/issues/7573 https://github.com/PowerDNS/pdns/pull/7577 https://security.archlinux.org/CVE-2019-3871

1 0

[ASA-201903-12] libssh2: multiple issues
by Remi Gacogne 22 Mar '19

22 Mar '19

Arch Linux Security Advisory ASA-201903-12 ========================================== Severity: Critical Date : 2019-03-22 CVE-ID : CVE-2019-3855 CVE-2019-3856 CVE-2019-3857 CVE-2019-3858 CVE-2019-3859 CVE-2019-3860 CVE-2019-3861 CVE-2019-3862 CVE-2019-3863 Package : libssh2 Type : multiple issues Remote : Yes Link : https://security.archlinux.org/AVG-926 Summary ======= The package libssh2 before version 1.8.1-1 is vulnerable to multiple issues including arbitrary code execution and information disclosure. Resolution ========== Upgrade to 1.8.1-1. # pacman -Syu "libssh2>=1.8.1-1" The problems have been fixed upstream in version 1.8.1. Workaround ========== None. Description =========== - CVE-2019-3855 (arbitrary code execution) A out-of-bounds write has been found in libssh2 before 1.8.1, where a malicious server could send a specially crafted packet which could result in an unchecked integer overflow. The value would then be used to allocate memory causing a possible memory write out of bounds error. - CVE-2019-3856 (arbitrary code execution) An issue has been found in libssh2 before 1.8.1 where a server could send a value approaching unsigned int max number of keyboard prompt requests which could result in an unchecked integer overflow. The value would then be used to allocate memory causing a possible memory write out of bounds error. - CVE-2019-3857 (arbitrary code execution) An issue has been found in libssh2 before 1.8.1 where a server could send a SSH_MSG_CHANNEL_REQUEST packet with an exit signal message with a length of max unsigned integer value. The length would then have a value of 1 added to it and used to allocate memory causing a possible memory write out of bounds error or zero byte allocation. - CVE-2019-3858 (information disclosure) An issue has been found in libssh2 before 1.8.1 where a server could send a specially crafted partial SFTP packet with a zero value for the payload length. This zero value would be used to then allocate memory resulting in a zero byte allocation and possible out of bounds read. - CVE-2019-3859 (information disclosure) An issue has been found in libssh2 before 1.8.1 where a server could send a specially crafted partial packet in response to various commands such as: sha1 and sha226 key exchange, user auth list, user auth password response, public key auth response, channel startup/open/forward/ setenv/request pty/x11 and session start up. The result would be a memory out of bounds read. - CVE-2019-3860 (information disclosure) An issue has been found in libssh2 before 1.8.1 where a server could send a specially crafted partial SFTP packet with a empty payload in response to various SFTP commands such as read directory, file status, status vfs and symlink. The result would be a memory out of bounds read. - CVE-2019-3861 (information disclosure) An issue has been found in libssh2 before 1.8.1 where a server could send a specially crafted SSH packet with a padding length value greater than the packet length. This would result in a buffer read out of bounds when decompressing the packet or result in a corrupted packet value. - CVE-2019-3862 (information disclosure) An issue has been found in libssh2 before 1.8.1 where a server could send a specially crafted SSH_MSG_CHANNEL_REQUEST packet with an exit status message and no payload. This would result in an out of bounds memory comparison. - CVE-2019-3863 (arbitrary code execution) An issue has been found in libssh2 before 1.8.1 where a server could send a multiple keyboard interactive response messages whose total length are greater than unsigned char max characters. This value is used as an index to copy memory causing in an out of bounds memory write error. Impact ====== A malicious server could access sensitive information or execute arbitrary code on a vulnerable client. References ========== https://www.libssh2.org/mail/libssh2-devel-archive-2019-03/0009.shtml https://www.libssh2.org/CVE-2019-3855.html https://libssh2.org/1.8.0-CVE/CVE-2019-3855.patch https://www.libssh2.org/CVE-2019-3856.html https://libssh2.org/1.8.0-CVE/CVE-2019-3856.patch https://www.libssh2.org/CVE-2019-3857.html https://libssh2.org/1.8.0-CVE/CVE-2019-3857.patch https://www.libssh2.org/CVE-2019-3858.html https://libssh2.org/1.8.0-CVE/CVE-2019-3858.patch https://www.libssh2.org/CVE-2019-3859.html https://libssh2.org/1.8.0-CVE/CVE-2019-3859.patch https://www.libssh2.org/CVE-2019-3860.html https://libssh2.org/1.8.0-CVE/CVE-2019-3860.patch https://www.libssh2.org/CVE-2019-3861.html https://libssh2.org/1.8.0-CVE/CVE-2019-3861.patch https://www.libssh2.org/CVE-2019-3862.html https://libssh2.org/1.8.0-CVE/CVE-2019-3862.patch https://www.libssh2.org/CVE-2019-3863.html https://libssh2.org/1.8.0-CVE/CVE-2019-3863.patch https://security.archlinux.org/CVE-2019-3855 https://security.archlinux.org/CVE-2019-3856 https://security.archlinux.org/CVE-2019-3857 https://security.archlinux.org/CVE-2019-3858 https://security.archlinux.org/CVE-2019-3859 https://security.archlinux.org/CVE-2019-3860 https://security.archlinux.org/CVE-2019-3861 https://security.archlinux.org/CVE-2019-3862 https://security.archlinux.org/CVE-2019-3863

1 0

[ASA-201903-11] firefox: multiple issues
by Remi Gacogne 22 Mar '19

22 Mar '19

Arch Linux Security Advisory ASA-201903-11 ========================================== Severity: Critical Date : 2019-03-22 CVE-ID : CVE-2019-9788 CVE-2019-9789 CVE-2019-9790 CVE-2019-9791 CVE-2019-9792 CVE-2019-9793 CVE-2019-9795 CVE-2019-9796 CVE-2019-9797 CVE-2019-9799 CVE-2019-9802 CVE-2019-9803 CVE-2019-9805 CVE-2019-9806 CVE-2019-9807 CVE-2019-9808 CVE-2019-9809 Package : firefox Type : multiple issues Remote : Yes Link : https://security.archlinux.org/AVG-925 Summary ======= The package firefox before version 66.0-1 is vulnerable to multiple issues including arbitrary code execution, information disclosure, same-origin policy bypass, access restriction bypass, content spoofing and denial of service. Resolution ========== Upgrade to 66.0-1. # pacman -Syu "firefox>=66.0-1" The problems have been fixed upstream in version 66.0. Workaround ========== None. Description =========== - CVE-2019-9788 (arbitrary code execution) Several memory safety bugs have been found in Firefox before 66.0. Some of these bugs showed evidence of memory corruption and Mozilla presumes that with enough effort some of these could be exploited to run arbitrary code. - CVE-2019-9789 (arbitrary code execution) Several memory safety bugs have been found in Firefox before 66.0. Some of these bugs showed evidence of memory corruption and Mozilla presumes that with enough effort some of these could be exploited to run arbitrary code. - CVE-2019-9790 (arbitrary code execution) A use-after-free vulnerability can occur in Firefox before 66.0 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 (arbitrary code execution) The type inference system in Firefox before 66.0 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 (arbitrary code execution) The IonMonkey just-in-time (JIT) compiler in Firefox before 66.0 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 (arbitrary code execution) A mechanism was discovered in Firefox before 66.0 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 that Spectre mitigations are currently enabled for all users by default settings. - CVE-2019-9795 (arbitrary code execution) A vulnerability has been found in Firefox before 66.0; 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 (arbitrary code execution) A use-after-free vulnerability can occur in Firefox before 66.0 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-2019-9797 (same-origin policy bypass) Cross-origin images can be read in violation of the same-origin policy, in Firefox before 66.0, by exporting an image after using createImageBitmap to read the image and then rendering the resulting bitmap image within a canvas element. - CVE-2019-9799 (information disclosure) Insufficient bounds checking of data during inter-process communication in Firefox before 66.0 might allow a compromised content process to be able to read memory from the parent process under certain conditions. - CVE-2019-9802 (information disclosure) If a Sandbox content process is compromised in Firefox before 66.0, it can initiate an FTP download which will then use a child process to render the downloaded data. The downloaded data can then be passed to the Chrome process with an arbitrary file length supplied by an attacker, bypassing sandbox protections and allow for a potential memory read of adjacent data from the privileged Chrome process, which may include sensitive data. - CVE-2019-9803 (access restriction bypass) The Upgrade-Insecure-Requests (UIR) specification states that if UIR is enabled through Content Security Policy (CSP), navigation to a same- origin URL must be upgraded to HTTPS. Firefox before 66.0 will incorrectly navigate to an HTTP URL rather than perform the security upgrade requested by the CSP in some circumstances, allowing for potential man-in-the-middle attacks on the linked resources. - CVE-2019-9805 (information disclosure) A latent vulnerability exists in the Prio library in Firefox before 66.0 where data may be read from uninitialized memory for some functions, leading to potential memory corruption. - CVE-2019-9806 (denial of service) A vulnerability exists in Firefox before 66.0 during authorization prompting for FTP transaction where successive modal prompts are displayed and cannot be immediately dismissed. This allows for a denial of service (DOS) attack. - CVE-2019-9807 (content spoofing) When arbitrary text is sent over an FTP connection and a page reload is initiated in Firefox before 66.0, it is possible to create a modal alert message with this text as the content. This could potentially be used for social engineering attacks. - CVE-2019-9808 (content spoofing) If WebRTC permission is requested from documents with data: or blob: URLs in Firefox before 66.0, the permission notifications do not properly display the originating domain. The notification states "Unknown origin" as the requestee, leading to user confusion about which site is asking for this permission. - CVE-2019-9809 (denial of service) If the source for resources on a page is through an FTP connection in Firefox before 66.0, it is possible to trigger a series of modal alert messages for these resources through invalid credentials or locations. These messages cannot be immediately dismissed, allowing for a denial of service (DOS) attack. Impact ====== A remote attacker might be able to spoof origin of a permission request, bypass security measures, access sensitive information, crash the browser or execute arbitrary code. References ========== https://www.mozilla.org/en-US/security/advisories/mfsa2019-07/ https://www.mozilla.org/en-US/security/advisories/mfsa2019-07/#CVE-2019-9788 https://bugzilla.mozilla.org/buglist.cgi?bug_id=1518001%2C1521304%2C1521214… https://www.mozilla.org/en-US/security/advisories/mfsa2019-07/#CVE-2019-9789 https://bugzilla.mozilla.org/buglist.cgi?bug_id=1520483%2C1522987%2C1528199… https://www.mozilla.org/en-US/security/advisories/mfsa2019-07/#CVE-2019-9790 https://bugzilla.mozilla.org/show_bug.cgi?id=1525145 https://www.mozilla.org/en-US/security/advisories/mfsa2019-07/#CVE-2019-9791 https://bugzilla.mozilla.org/show_bug.cgi?id=1530958 https://www.mozilla.org/en-US/security/advisories/mfsa2019-07/#CVE-2019-9792 https://bugzilla.mozilla.org/show_bug.cgi?id=1532599 https://www.mozilla.org/en-US/security/advisories/mfsa2019-07/#CVE-2019-9793 https://bugzilla.mozilla.org/show_bug.cgi?id=1528829 https://www.mozilla.org/en-US/security/advisories/mfsa2019-07/#CVE-2019-9795 https://bugzilla.mozilla.org/show_bug.cgi?id=1514682 https://www.mozilla.org/en-US/security/advisories/mfsa2019-07/#CVE-2019-9796 https://bugzilla.mozilla.org/show_bug.cgi?id=1531277 https://www.mozilla.org/en-US/security/advisories/mfsa2019-07/#CVE-2019-9797 https://bugzilla.mozilla.org/show_bug.cgi?id=1528909 https://www.mozilla.org/en-US/security/advisories/mfsa2019-07/#CVE-2019-9799 https://bugzilla.mozilla.org/show_bug.cgi?id=1505678 https://www.mozilla.org/en-US/security/advisories/mfsa2019-07/#CVE-2019-9802 https://bugzilla.mozilla.org/show_bug.cgi?id=1415508 https://www.mozilla.org/en-US/security/advisories/mfsa2019-07/#CVE-2019-9803 https://bugzilla.mozilla.org/show_bug.cgi?id=1515863 https://bugzilla.mozilla.org/show_bug.cgi?id=1437009 https://w3c.github.io/webappsec-upgrade-insecure-requests/ https://www.mozilla.org/en-US/security/advisories/mfsa2019-07/#CVE-2019-9805 https://bugzilla.mozilla.org/show_bug.cgi?id=1521360 https://www.mozilla.org/en-US/security/advisories/mfsa2019-07/#CVE-2019-9806 https://bugzilla.mozilla.org/show_bug.cgi?id=1525267 https://www.mozilla.org/en-US/security/advisories/mfsa2019-07/#CVE-2019-9807 https://bugzilla.mozilla.org/show_bug.cgi?id=1362050 https://www.mozilla.org/en-US/security/advisories/mfsa2019-07/#CVE-2019-9808 https://bugzilla.mozilla.org/show_bug.cgi?id=1434634 https://www.mozilla.org/en-US/security/advisories/mfsa2019-07/#CVE-2019-9809 https://bugzilla.mozilla.org/show_bug.cgi?id=1282430 https://bugzilla.mozilla.org/show_bug.cgi?id=1523249 https://security.archlinux.org/CVE-2019-9788 https://security.archlinux.org/CVE-2019-9789 https://security.archlinux.org/CVE-2019-9790 https://security.archlinux.org/CVE-2019-9791 https://security.archlinux.org/CVE-2019-9792 https://security.archlinux.org/CVE-2019-9793 https://security.archlinux.org/CVE-2019-9795 https://security.archlinux.org/CVE-2019-9796 https://security.archlinux.org/CVE-2019-9797 https://security.archlinux.org/CVE-2019-9799 https://security.archlinux.org/CVE-2019-9802 https://security.archlinux.org/CVE-2019-9803 https://security.archlinux.org/CVE-2019-9805 https://security.archlinux.org/CVE-2019-9806 https://security.archlinux.org/CVE-2019-9807 https://security.archlinux.org/CVE-2019-9808 https://security.archlinux.org/CVE-2019-9809

1 0

[ASA-201903-10] wordpress: directory traversal
by Santiago Torres-Arias 20 Mar '19

20 Mar '19

Arch Linux Security Advisory ASA-201903-10 ========================================== Severity: High Date : 2019-03-18 CVE-ID : CVE-2019-8943 Package : wordpress Type : directory traversal Remote : Yes Link : https://security.archlinux.org/AVG-909 Summary ======= The package wordpress before version 5.1-1 is vulnerable to directory traversal. Resolution ========== Upgrade to 5.1-1. # pacman -Syu "wordpress>=5.1-1" The problem has been fixed upstream in version 5.1. Workaround ========== None. Description =========== WordPress through 5.0.3 allows Path Traversal in wp_crop_image(). An attacker (who has privileges to crop an image) can write the output image to an arbitrary directory via a filename containing two image extensions and ../ sequences, such as a filename ending with the .jpg?/../../file.jpg substring. Impact ====== A remote attacker with image-cropping privileges can write files to an arbitrary directory References ========== https://blog.ripstech.com/2019/wordpress-image-remote-code-execution/ https://security.archlinux.org/CVE-2019-8943

1 0