Archive
17 September 2020
Vulnerabilities first published on this day (UTC), newest first.
138 results · Feed
-
Unscored —
In libstagefright, there is a possible out of bounds write due to an integer overflow. This could lead to remote code e…
-
Unscored —
In SyncManager, there is a possible permission bypass due to an unsafe PendingIntent. This could lead to local informat…
-
Unscored —
There is a possible way to view notifications even when the "Lockdown" feature is on. This could lead to local informat…
-
Unscored —
In libavb, there is a possible out of bounds read due to a missing bounds check. This could lead to local information d…
-
Unscored —
In apexd, there is a possible out of bounds read due to a missing bounds check. This could lead to local information di…
-
Unscored —
In libavb, there is a possible out of bounds write due to an integer overflow. This could lead to local escalation of p…
-
Unscored —
In ActivityManager, there is a possible access to protected data due to a missing permission check. This could lead to …
-
Unscored —
In MediaProvider, there is a possible permissions bypass due to SQL injection. This could lead to local information dis…
-
Unscored —
In NetworkStatsService, there is a possible access to protected data due to a missing permission check. This could lead…
-
Unscored —
In UsageStatsManager, there is a possible access to protected data due to a missing permission check. This could lead t…
-
Unscored —
In Battery Saver, there is a possible permission bypass due to an unsafe PendingIntent. This could lead to local inform…
-
Unscored —
In Window Manager, there is a possible permission bypass due to an unsafe PendingIntent. This could lead to local infor…
-
Unscored —
In devicepolicy service, there is a possible permission bypass due to an unsafe PendingIntent. This could lead to local…
-
Unscored —
In ADB server and USB server, there is a possible permission bypass due to an unsafe PendingIntent. This could lead to …
-
Unscored —
In Java network APIs, there is possible access to sensitive network state due to a missing permission check. This could…
-
Unscored —
In PackageManager, there is a missing permission check. This could lead to local information disclosure across users wi…
-
Unscored —
In PackageManager, there is a missing permission check. This could lead to local information disclosure across users wi…
-
Unscored —
In PackageManager, there is a missing permission check. This could lead to local information disclosure across user bou…
-
Unscored —
In PackageInstaller, there is a possible permissions bypass due to a tapjacking vulnerability. This could lead to local…
-
Unscored —
In DocumentsUI, there is a possible permission bypass due to a confused deputy. This could lead to local escalation of …
-
Unscored —
In DisplayManager, there is a possible permission bypass due to a missing permission check. This could lead to local es…
-
Unscored —
In NetworkPolicyManagerService, there is a possible permissions bypass due to a missing permission check. This could le…
-
Unscored —
In screencap, there is a possible command injection due to improper input validation. This could lead to local escalati…
-
Unscored —
In UrlQuerySanitizer, there is a possible improper input validation. This could lead to remote code execution with no a…
-
Unscored —
In checkKeyIntent of AccountManagerService.java, there is a possible permission bypass. This could lead to local inform…
-
Unscored —
In MediaProvider, there is a possible bypass of a permissions check due to a confused deputy. This could lead to local …
-
Unscored —
In MediaProvider, there is a possible way to access ContentResolver and MediaStore entries the app shouldn't have acces…
-
Unscored —
In WindowManager, there is a possible launch of an unexpected app due to a confused deputy. This could lead to local es…
-
Unscored —
In iorap, there is a possible memory corruption due to a use after free. This could lead to local escalation of privile…
-
Low 3.7
Aliases are never checked in Helm
In Helm before versions 2.16.11 and 3.3.2 there is a bug in which the `alias` field on a `Chart.yaml` is not properly sanitized. This could lead to the injection of unwanted information into a chart. This issue has been patched in Helm 3.3.2 and 2.16.11. A po…
-
High 8.4
Reflected XSS leading to RCE in SoyCMS
SoyCMS 3.0.2 and earlier is affected by Reflected Cross-Site Scripting (XSS) which leads to Remote Code Execution (RCE) from a known vulnerability. This allows remote attackers to force the administrator to edit files once the adminsitrator loads a specially …
-
Unscored —CVE-2020-13260 Public exploit
A vulnerability in the web-based management interface of RAD SecFlow-1v through 2020-05-21 could allow an authenticated…
-
High 8.4
Cross-site Request Forgery leading to RCE in SOY CMS
The SOY Inquiry component of SOY CMS is affected by Cross-site Request Forgery (CSRF) and Remote Code Execution (RCE). The vulnerability affects versions 2.0.0.3 and earlier of SOY Inquiry. This allows remote attackers to force the administrator to edit files…
-
Unscored —
In Pixel's use of the Catpipe library, there is possible memory corruption due to a use after free. This could lead to …
-
Unscored —
In blk_mq_queue_tag_busy_iter of blk-mq-tag.c, there is a possible use after free due to improper locking. This could l…
-
Unscored —
In skb_to_mamac of networking.c, there is a possible out of bounds write due to an integer overflow. This could lead to…
-
Unscored —
In kbd_keycode of keyboard.c, there is a possible out of bounds write due to a missing bounds check. This could lead to…
-
Unscored —
In skb_headlen of /include/linux/skbuff.h, there is a possible out of bounds read due to memory corruption. This could …
-
Unscored —
In l2tp_session_delete and related functions of l2tp_core.c, there is possible memory corruption due to a use after fre…
-
Unscored —
In CamX code, there is a possible use after free due to a race condition. This could lead to local escalation of privil…