Google Chrome 132.0.6834.83

CPE Details

Google Chrome 132.0.6834.83
132.0.6834.83
2025-02-27
13h56 +00:00
2025-02-27
13h56 +00:00
Alerte pour un CPE
Restez informé de toutes modifications pour un CPE spécifique.
Gestion des notifications

CPE Name: cpe:2.3:a:google:chrome:132.0.6834.83:*:*:*:*:*:*:*

Informations

Vendor

google

Product

chrome

Version

132.0.6834.83

Related CVE

Open and find in CVE List

CVE ID Publié Description Score Gravité
CVE-2025-2783 2025-03-26 16h07 +00:00 Incorrect handle provided in unspecified circumstances in Mojo in Google Chrome on Windows prior to 134.0.6998.177 allowed a remote attacker to perform a sandbox escape via a malicious file. (Chromium security severity: High)
8.3
Haute
CVE-2025-2476 2025-03-19 18h59 +00:00 Use after free in Lens in Google Chrome prior to 134.0.6998.117 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Critical)
8.8
Haute
CVE-2025-1923 2025-03-05 03h48 +00:00 Inappropriate implementation in Permission Prompts in Google Chrome prior to 134.0.6998.35 allowed an attacker who convinced a user to install a malicious extension to perform UI spoofing via a crafted Chrome Extension. (Chromium security severity: Low)
4.3
Moyen
CVE-2025-1922 2025-03-05 03h48 +00:00 Inappropriate implementation in Selection in Google Chrome on Android prior to 134.0.6998.35 allowed a remote attacker who convinced a user to engage in specific UI gestures to perform UI spoofing via a crafted HTML page. (Chromium security severity: Low)
4.3
Moyen
CVE-2025-1921 2025-03-05 03h48 +00:00 Inappropriate implementation in Media Stream in Google Chrome prior to 134.0.6998.35 allowed a remote attacker to obtain information about a peripheral via a crafted HTML page. (Chromium security severity: Medium)
6.5
Moyen
CVE-2025-1919 2025-03-05 03h48 +00:00 Out of bounds read in Media in Google Chrome prior to 134.0.6998.35 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML page. (Chromium security severity: Medium)
8.8
Haute
CVE-2025-1918 2025-03-05 03h48 +00:00 Out of bounds read in PDFium in Google Chrome prior to 134.0.6998.35 allowed a remote attacker to potentially perform out of bounds memory access via a crafted PDF file. (Chromium security severity: Medium)
8.8
Haute
CVE-2025-1917 2025-03-05 03h48 +00:00 Inappropriate implementation in Browser UI in Google Chrome on Android prior to 134.0.6998.35 allowed a remote attacker to perform UI spoofing via a crafted HTML page. (Chromium security severity: Medium)
4.3
Moyen
CVE-2025-1916 2025-03-05 03h48 +00:00 Use after free in Profiles in Google Chrome prior to 134.0.6998.35 allowed an attacker who convinced a user to install a malicious extension to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Medium)
8.8
Haute
CVE-2025-1915 2025-03-05 03h48 +00:00 Improper Limitation of a Pathname to a Restricted Directory in DevTools in Google Chrome on Windows prior to 134.0.6998.35 allowed an attacker who convinced a user to install a malicious extension to bypass file access restrictions via a crafted Chrome Extension. (Chromium security severity: Medium)
8.1
Haute
CVE-2025-1914 2025-03-05 03h48 +00:00 Out of bounds read in V8 in Google Chrome prior to 134.0.6998.35 allowed a remote attacker to perform out of bounds memory access via a crafted HTML page. (Chromium security severity: High)
8.8
Haute
CVE-2013-6662 2017-04-13 15h00 +00:00 Google Chrome caches TLS sessions before certificate validation occurs.
6.5
Moyen
CVE-2012-4929 2012-09-15 16h00 +00:00 The TLS protocol 1.2 and earlier, as used in Mozilla Firefox, Google Chrome, Qt, and other products, can encrypt compressed data without properly obfuscating the length of the unencrypted data, which allows man-in-the-middle attackers to obtain plaintext HTTP headers by observing length differences during a series of guesses in which a string in an HTTP request potentially matches an unknown string in an HTTP header, aka a "CRIME" attack.
2.6
CVE-2012-4930 2012-09-15 16h00 +00:00 The SPDY protocol 3 and earlier, as used in Mozilla Firefox, Google Chrome, and other products, can perform TLS encryption of compressed data without properly obfuscating the length of the unencrypted data, which allows man-in-the-middle attackers to obtain plaintext HTTP headers by observing length differences during a series of guesses in which a string in an HTTP request potentially matches an unknown string in an HTTP header, aka a "CRIME" attack.
2.6
CVE-2012-2647 2012-07-31 10h00 +00:00 Yahoo! Toolbar 1.0.0.5 and earlier for Chrome and Safari allows remote attackers to modify the configured search URL, and intercept search terms, via a crafted web page.
5.8