Google CVEs
9,109 CVEs and advisories name Google as an affected vendor, 82 of them on CISA's Known Exploited Vulnerabilities catalog, newest first. Follow it as a feed.
- CVE-2023-5852Use after free in Printing in Google Chrome prior to 119.0.6045.105 allowed a remote attacker who convinced a user to engage in specific UI
- CVE-2023-5851Inappropriate implementation in Downloads in Google Chrome prior to 119.0.6045.105 allowed a remote attacker to obfuscate security UI via a
- CVE-2023-5850Incorrect security UI in Downloads in Google Chrome prior to 119.0.6045.105 allowed a remote attacker to perform domain spoofing via a craft
- CVE-2023-5849Integer overflow in USB in Google Chrome prior to 119.0.6045.105 allowed a remote attacker to potentially exploit heap corruption via a craf
- CVE-2023-5482Insufficient data validation in USB in Google Chrome prior to 119.0.6045.105 allowed a remote attacker to perform out of bounds memory acces
- CVE-2023-5480Inappropriate implementation in Payments in Google Chrome prior to 119.0.6045.105 allowed a remote attacker to bypass XSS preventions via a
- CVE-2023-45780In Print Service, there is a possible background activity launch due to a logic error in the code.
- CVE-2023-40101In collapse of canonicalize_md.c, there is a possible out of bounds read due to a missing bounds check.
- CVE-2023-21398In sdksandbox, there is a possible strandhogg style overlay attack due to a logic error in the code.
- CVE-2023-21397In Setup Wizard, there is a possible way to save a WiFi network due to an insecure default value.
- CVE-2023-21396In Activity Manager, there is a possible background activity launch due to a logic error in the code.
- CVE-2023-21395In Bluetooth, there is a possible out of bounds read due to a use after free.
- CVE-2023-21394In registerPhoneAccount of TelecomServiceImpl.java, there is a possible way to reveal images from another user due to a missing permission c
- CVE-2023-21393In Settings, there is a possible way for the user to change SIM due to a missing permission check.
- CVE-2023-21392In Bluetooth, there is a possible way to corrupt memory due to a use after free.
- CVE-2023-21391In Messaging, there is a possible way to disable the messaging application due to improper input validation.
- CVE-2023-21390In Sim, there is a possible way to evade mobile preference restrictions due to a permission bypass.
- CVE-2023-21389In Settings, there is a possible bypass of profile owner restrictions due to a missing permission check.
- CVE-2023-21388In Settings, there is a possible restriction bypass due to a missing permission check.
- CVE-2023-21387In User Backup Manager, there is a possible way to leak a token to bypass user confirmation for backup due to log information disclosure.
- CVE-2023-21385In Whitechapel, there is a possible out of bounds read due to memory corruption.
- CVE-2023-21384In Package Manager, there is a possible possible permissions bypass due to an unsafe PendingIntent.
- CVE-2023-21383In Settings, there is a possible way for the user to unintentionally send extra data due to an unclear prompt.
- CVE-2023-21382In Content Resolver, there is a possible method to access metadata about existing content providers on the device due to a missing permissio
- CVE-2023-21381In Media Resource Manager, there is a possible local arbitrary code execution due to use after free.
- CVE-2023-21380In Bluetooth, there is a possible out of bounds write due to a heap buffer overflow.
- CVE-2023-21379In Bluetooth, there is a possible out of bounds read due to a missing bounds check.
- CVE-2023-21378In Telecomm, there is a possible way to silence the ring for calls of secondary users due to a missing permission check.
- CVE-2023-21377In SELinux Policy, there is a possible restriction bypass due to a permissions bypass.
- CVE-2023-21376In Telephony, there is a possible way to retrieve the ICCID due to a logic error in the code.