Vendor
9,109 known vulnerabilities.
Products
2,324 results · Clear filters · Feed
-
Medium 4.3
Inappropriate implementation in UI in Google Chrome prior to 124.0.6367.60 allowed a remote attacker who convinced a us…
-
Medium 6.1
Insufficient data validation in Omnibox in Google Chrome on Android prior to 129.0.6668.58 allowed a remote attacker wh…
-
Medium 4.3
Inappropriate implementation in UI in Google Chrome on iOS prior to 129.0.6668.58 allowed a remote attacker to perform …
-
Medium 4.3
Incorrect security UI in Downloads in Google Chrome prior to 129.0.6668.58 allowed a remote attacker who convinced a us…
-
Medium 4.3
Inappropriate implementation in Autofill in Google Chrome prior to 129.0.6668.58 allowed a remote attacker to perform U…
-
Medium 5.3
-
Medium 4.4
there is a possible arbitrary read due to an insecure default value. This could lead to local information disclosure wi…
-
Medium 5.5
In getRegistration of RemoteProvisioningService.java, there is a possible way to permanently disable the AndroidKeyStor…
-
Medium 5.5
In handleCreateConferenceComplete of ConnectionServiceWrapper.java, there is a possible way to reveal images across use…
-
Medium 4.8
AngularJS improper sanitization in '<source>' element
Improper sanitization of the value of the [srcset] attribute in <source> HTML elements in AngularJS allows attackers to bypass common image source restrictions, which can also lead to a form of Content Spoofing https://owasp.org/www-community/attacks/Content_…
-
Medium 4.8
AngularJS improper sanitization in 'srcset' attribute
Improper sanitization of the value of the 'srcset' attribute in AngularJS allows attackers to bypass common image source restrictions, which can also lead to a form of Content Spoofing https://owasp.org/www-community/attacks/Content_Spoofing . This issue affe…
-
Medium 4.3
Inappropriate implementation in Custom Tabs in Google Chrome on Android prior to 128.0.6613.84 allowed a remote attacke…
-
Medium 4.3
Inappropriate implementation in Extensions in Google Chrome on Windows prior to 128.0.6613.84 allowed a remote attacker…
-
Medium 4.3
Insufficient policy enforcement in Data Transfer in Google Chrome prior to 128.0.6613.84 allowed a remote attacker who …
-
Medium 4.3
Inappropriate implementation in Views in Google Chrome prior to 128.0.6613.84 allowed a remote attacker to perform UI s…
-
Medium 4.3
Inappropriate implementation in WebApp Installs in Google Chrome on Windows prior to 128.0.6613.84 allowed an attacker …
-
Medium 4.3
Inappropriate implementation in Permissions in Google Chrome prior to 128.0.6613.84 allowed a remote attacker to perfor…
-
Medium 4.3
Inappropriate implementation in FedCM in Google Chrome prior to 128.0.6613.84 allowed a remote attacker to perform UI s…
-
Medium 5.9
The libcurl CURLOPT_SSL_VERIFYPEER option was disabled on a subset of requests made by Nest production devices which en…
-
Medium 5.5
In shouldWrite of OwnersData.java, there is a possible edge case that prevents MDM policies from being persisted due to…
-
Medium 6.2
In setupVideoEncoder of StagefrightRecorder.cpp, there is a possible asynchronous playback when B-frame support is enab…
-
Medium 4.3
Insufficient validation of untrusted input in Safe Browsing in Google Chrome prior to 127.0.6533.72 allowed a remote at…
-
Medium 4.3
Inappropriate implementation in HTML in Google Chrome prior to 127.0.6533.72 allowed a remote attacker who convinced a …
-
Medium 4.3
Inappropriate implementation in FedCM in Google Chrome prior to 127.0.6533.72 allowed a remote attacker who convinced a…
-
Medium 4.3
Inappropriate implementation in FedCM in Google Chrome prior to 127.0.6533.72 allowed a remote attacker who convinced a…
-
Medium 6.3
HPACK table poisoning in gRPC C++, Python & Ruby
It's possible for a gRPC client communicating with a HTTP/2 proxy to poison the HPACK table between the proxy and the backend such that other clients see failed requests. It's also possible to use this vulnerability to leak other clients HTTP header keys, but…
-
Medium 6.5
Insufficient policy enforcement in Navigation in Google Chrome prior to 85.0.4183.83 allowed a remote attacker to leak …
-
Medium 5.3
Inappropriate implementation in iframe in Google Chrome prior to 77.0.3865.75 allowed a remote attacker to potentially …
-
Medium 6.5
Inappropriate implementation in Sign-In in Google Chrome prior to 1.3.36.351 allowed a remote attacker to bypass naviga…
-
Medium 5.4
Inappropriate implementation in Compositing in Google Chrome prior to 119.0.6045.105 allowed a remote attacker to poten…
-
Medium 6.3
Out of bounds read in V8 in Google Chrome prior to 121.0.6167.139 allowed a remote attacker to potentially perform out …
-
Medium 6.5
Inappropriate implementation in Picture in Picture in Google Chrome prior to 119.0.6045.105 allowed a remote attacker t…
-
Medium 5.3
In onTransact of ParcelableListBinder.java , there is a possible way to steal mAllowlistToken to launch an app from bac…
-
Medium 6.2
In ensureFileColumns of MediaProvider.java, there is a possible disclosure of files owned by another user due to improp…
-
Medium 6.7
In DevmemIntFreeDefBackingPage of devicemem_server.c, there is a possible arbitrary code execution due to a logic error…
-
Medium 5.3
In multiple functions of MessageQueueBase.h, there is a possible out of bounds write due to a race condition. This coul…
-
Medium 6.3
In updateServicesLocked of AccessibilityManagerService.java, there is a possible way for an app to be hidden from the S…
-
Medium 5.3
In multiple functions of ManagedServices.java, there is a possible way to hide an app with notification access in the D…
-
Medium 6.2
In multiple functions of ShortcutService.java, there is a possible persistent DOS due to resource exhaustion. This coul…
-
Medium 5.5
In multiple locations, there is a possible information leak due to a missing permission check. This could lead to local…