Page 336 of 3367 results (0.019 seconds)

CVSS: 9.3EPSS: 0%CPEs: 24EXPL: 1

23 Jun 2009 — Buffer overflow in the browser kernel in Google Chrome before 2.0.172.33 allows remote HTTP servers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted response. Desbordamiento de búfer en el núcleo del navegador en Google Chrome en versiones anteriores a la v2.0.172.33 permite a los servidores HTTP remotos causar una denegación de servicio (mediante caida de la aplicación) o posiblemente ejecutar código arbitrario a través de una respuesta HTTP modificada. • http://code.google.com/p/chromium/issues/detail?id=14508 • CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer •

CVSS: 6.8EPSS: 0%CPEs: 16EXPL: 0

15 Jun 2009 — Google Chrome before 1.0.154.53 displays a cached certificate for a (1) 4xx or (2) 5xx CONNECT response page returned by a proxy server, which allows man-in-the-middle attackers to spoof an arbitrary https site by letting a browser obtain a valid certificate from this site during one request, and then sending the browser a crafted 502 response page upon a subsequent request. Google Chrome anteriores a v1.0.154.53 muestra un certificado cacheado para una página de respuesta de CONEXIÓN (1) 4xx o (2) 5xx a tr... • http://code.google.com/p/chromium/issues/detail?id=7338 • CWE-287: Improper Authentication •

CVSS: 7.4EPSS: 0%CPEs: 16EXPL: 0

15 Jun 2009 — src/net/http/http_transaction_winhttp.cc in Google Chrome before 1.0.154.53 uses the HTTP Host header to determine the context of a document provided in a (1) 4xx or (2) 5xx CONNECT response from a proxy server, which allows man-in-the-middle attackers to execute arbitrary web script by modifying this CONNECT response, aka an "SSL tampering" attack. src/net/http/http_transaction_winhttp.cc en Google Chrome anteriores a v1.0.154.53 utiliza una cabecera Host HTTP para determinar el contexto de un documento pr... • http://code.google.com/p/chromium/issues/detail?id=7338 • CWE-287: Improper Authentication •

CVSS: 9.3EPSS: 6%CPEs: 76EXPL: 1

10 Jun 2009 — Use-after-free vulnerability in WebKit, as used in Apple Safari before 4.0, iPhone OS 1.0 through 2.2.1, iPhone OS for iPod touch 1.1 through 2.2.1, Google Chrome 1.0.154.53, and possibly other products, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) by setting an unspecified property of an HTML tag that causes child elements to be freed and later accessed when an HTML error occurs, related to "recursion in certain DOM event handlers.... • http://labs.idefense.com/intelligence/vulnerabilities/display.php?id=803 • CWE-399: Resource Management Errors •

CVSS: 8.8EPSS: 2%CPEs: 22EXPL: 1

07 May 2009 — Multiple integer overflows in Skia, as used in Google Chrome 1.x before 1.0.154.64 and 2.x, and possibly Android, might allow remote attackers to execute arbitrary code in the renderer process via a crafted (1) image or (2) canvas. Múltiples desbodamientos de enteros en Skia, utilizado en Google Chrome v1.x anteriores a v1.0.154.64 y v2.x, y posiblemente Android, debería permitir a los atacantes remotos ejecutar arbitrariamente código en el proceso de renderizado a través de (1) imagenes o (2) canvas manipu... • http://code.google.com/p/chromium/issues/detail?id=10736 • CWE-189: Numeric Errors •

CVSS: 9.3EPSS: 0%CPEs: 17EXPL: 1

07 May 2009 — Heap-based buffer overflow in the ParamTraits::Read function in Google Chrome before 1.0.154.64 allows attackers to leverage renderer access to cause a denial of service (application crash) or possibly execute arbitrary code via vectors related to a large bitmap that arrives over the IPC channel. Un desbordamiento de búfer en la región heap de la memoria en la función ParamTraits(SkBitmap)::Read en Chrome de Google anterior a versión 1.0.154.64, permite a los atacantes aprovechar el acceso al rend... • http://code.google.com/p/chromium/issues/detail?id=10869 • CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer •

CVSS: 6.5EPSS: 7%CPEs: 1EXPL: 2

04 May 2009 — Google Chrome 1.0.154.53 allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a throw statement with a long exception value. Google Chrome v1.0.154.53 permite a atacantes remotos provocar una denegación de servicio desreferenciación de puntero nulo y caída de aplicación) a través de una declaración con un valor de excepción largo. • https://www.exploit-db.com/exploits/8573 • CWE-399: Resource Management Errors •

CVSS: 7.8EPSS: 0%CPEs: 17EXPL: 2

24 Apr 2009 — Argument injection vulnerability in the chromehtml: protocol handler in Google Chrome before 1.0.154.59, when invoked by Internet Explorer, allows remote attackers to determine the existence of files, and open tabs for URLs that do not satisfy the IsWebSafeScheme restriction, via a web page that sets document.location to a chromehtml: value, as demonstrated by use of a (1) javascript: or (2) data: URL. NOTE: this can be leveraged for Universal XSS by exploiting certain behavior involving persistence across ... • http://chromium.googlecode.com/issues/attachment?aid=5579180911289877192&name=Google+Chrome+Advisory.doc • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •

CVSS: 6.1EPSS: 0%CPEs: 5EXPL: 0

24 Apr 2009 — Google Chrome 2.0.x lets modifications to the global object persist across a page transition, which makes it easier for attackers to conduct Universal XSS attacks via unspecified vectors. Google Chrome 2.0.x permite que las modificaciones en el objeto global persistan a través de una página de transición, lo que facilita a los atacantes a la hora de llevar a cabo ataques XSS universales a través de vectores no especificados. • http://code.google.com/p/chromium/issues/detail?id=9860 • CWE-264: Permissions, Privileges, and Access Controls •

CVSS: 6.1EPSS: 0%CPEs: 7EXPL: 0

24 Apr 2009 — Google Chrome 1.0.x does not cancel timeouts upon a page transition, which makes it easier for attackers to conduct Universal XSS attacks by calling setTimeout to trigger future execution of JavaScript code, and then modifying document.location to arrange for JavaScript execution in the context of an arbitrary web site. NOTE: this can be leveraged for a remote attack by exploiting a chromehtml: argument-injection vulnerability. Google Crome 1.0.x no cancela los timeouts sobre una pagina de transición, lo qu... • http://chromium.googlecode.com/issues/attachment?aid=5579180911289877192&name=Google+Chrome+Advisory.doc • CWE-264: Permissions, Privileges, and Access Controls •