openSUSE Security Update : Chromium (openSUSE-2016-682)

Chromium was updated to 51.0.2704.79 to fix the following vulnerabilities : - CVE-2016-1696: Cross-origin bypass in Extension bindings - CVE-2016-1697: Cross-origin bypass in Blink - CVE-2016-1698: Information leak in Extension bindings - CVE-2016-1699: Parameter sanitization failure in DevTools ...

CVE-2016-1684

numbers.c in libxslt before 1.1.29, as used in Google Chrome before 51.0.2704.63, mishandles the i format token for xsl:number data, which allows remote attackers to cause a denial of service integer overflow or resource consumption or possibly have unspecified other impact via a crafted document...

DEBIAN-CVE-2016-1684

numbers.c in libxslt before 1.1.29, as used in Google Chrome before 51.0.2704.63, mishandles the i format token for xsl:number data, which allows remote attackers to cause a denial of service integer overflow or resource consumption or possibly have unspecified other impact via a crafted document...

CVE-2016-1684

numbers.c in libxslt before 1.1.29, as used in Google Chrome before 51.0.2704.63, mishandles the i format token for xsl:number data, which allows remote attackers to cause a denial of service integer overflow or resource consumption or possibly have unspecified other impact via a crafted document...

DEBIAN-CVE-2016-1683

numbers.c in libxslt before 1.1.29, as used in Google Chrome before 51.0.2704.63, mishandles namespace nodes, which allows remote attackers to cause a denial of service out-of-bounds heap memory access or possibly have unspecified other impact via a crafted document...

CVE-2016-1683

numbers.c in libxslt before 1.1.29, as used in Google Chrome before 51.0.2704.63, mishandles namespace nodes, which allows remote attackers to cause a denial of service out-of-bounds heap memory access or possibly have unspecified other impact via a crafted document...

Integer overflow

numbers.c in libxslt before 1.1.29, as used in Google Chrome before 51.0.2704.63, mishandles the i format token for xsl:number data, which allows remote attackers to cause a denial of service integer overflow or resource consumption or possibly have unspecified other impact via a crafted document...

CVE-2016-1684

CVE-2016-1684 is a libxslt vulnerability listed in Apple advisories and related OS X/iOS updates. Connected documents indicate libxslt multiple memory corruption issues were addressed (no explicit root-cause or fix version provided in the sources). Affected products include libxslt in Apple platf...

CVE-2016-1683

numbers.c in libxslt before 1.1.29, as used in Google Chrome before 51.0.2704.63, mishandles namespace nodes, which allows remote attackers to cause a denial of service out-of-bounds heap memory access or possibly have unspecified other impact via a crafted document...

CVE-2016-1684

numbers.c in libxslt before 1.1.29, as used in Google Chrome before 51.0.2704.63, mishandles the i format token for xsl:number data, which allows remote attackers to cause a denial of service integer overflow or resource consumption or possibly have unspecified other impact via a crafted document...

CVE-2016-1683

CVE-2016-1683 affects libxslt prior to 1.1.29, as used in Google Chrome before 51.0.2704.63. The issue arises from numbers.c in libxslt, where namespace nodes are mishandled, enabling a remote attacker to trigger out-of-bounds heap memory access and cause a denial of service (with potential unspe...

CVE-2016-1683

numbers.c in libxslt before 1.1.29, as used in Google Chrome before 51.0.2704.63, mishandles namespace nodes, which allows remote attackers to cause a denial of service out-of-bounds heap memory access or possibly have unspecified other impact via a crafted document...

CVE-2016-1684

numbers.c in libxslt before 1.1.29, as used in Google Chrome before 51.0.2704.63, mishandles the i format token for xsl:number data, which allows remote attackers to cause a denial of service integer overflow or resource consumption or possibly have unspecified other impact via a crafted document...

Security update for Chromium (important)

Chromium was updated to 51.0.2704.79 to fix the following vulnerabilities: - CVE-2016-1696: Cross-origin bypass in Extension bindings - CVE-2016-1697: Cross-origin bypass in Blink - CVE-2016-1698: Information leak in Extension bindings - CVE-2016-1699: Parameter sanitization failure in DevTools -...

Google Chrome Libxslt Integer Overflow Vulnerability

Google Chrome is a popular web browser. An integer overflow vulnerability in Google Chrome Libxslt allows remote attackers to exploit the vulnerability to construct a malicious WEB page that can be tricked into parsing by users, which can crash the application or execute arbitrary code...

Google Chrome Libxslt Out-of-Bounds Access Vulnerability

Google Chrome is a popular web browser. An out-of-bounds access vulnerability in Google Chrome Libxslt allows remote attackers to exploit the vulnerability to build malicious WEB pages that can be tricked into parsing by users, which can crash the application or execute arbitrary code...

chromium-browser: integer overflow in libxslt

numbers.c in libxslt before 1.1.29, as used in Google Chrome before 51.0.2704.63, mishandles the i format token for xsl:number data, which allows remote attackers to cause a denial of service integer overflow or resource consumption or possibly have unspecified other impact via a crafted document...

chromium-browser: out-of-bounds access in libxslt

numbers.c in libxslt before 1.1.29, as used in Google Chrome before 51.0.2704.63, mishandles namespace nodes, which allows remote attackers to cause a denial of service out-of-bounds heap memory access or possibly have unspecified other impact via a crafted document...

openSUSE Security Update : libxslt (openSUSE-2016-661)

This update for libxslt fixes the following issues : - CVE-2015-7995: A type confusion in preprocessing attributes was fixed boo952474. %NASLMINLEVEL 70300 C Tenable Network Security, Inc. The descriptive text and package checks in this plugin were extracted from openSUSE Security Update...

CVE-2016-1684

numbers.c in libxslt before 1.1.29, as used in Google Chrome before 51.0.2704.63, mishandles the i format token for xsl:number data, which allows remote attackers to cause a denial of service integer overflow or resource consumption or possibly have unspecified other impact via a crafted document...