NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
579 matching advisories · page 11 of 20Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.3 CVE-2022-20335 In Wifi Slice, there is a possible way to adjust Wi-Fi settings even when the permission has been disabled due to a missing permission check. google · android 2022-08-12 low3.5 CVE-2022-20330 In Bluetooth, there is a possible way to connect or disconnect bluetooth devices without user awareness due to a missing permission check. google · android 2022-08-12 low3.3 CVE-2022-20328 In PackageManager, there is a possible way to determine whether an app is installed due to a missing permission check. google · android 2022-08-12 low2.8 CVE-2022-20327 In Wi-Fi, there is a possible way to retrieve the WiFi SSID without location permissions due to a missing permission check. google · android 2022-08-12 low3.3 CVE-2022-20321 In Settings, there is a possible way for an application without permissions to read content of WiFi QR codes due to a missing permission check. google · android 2022-08-12 low3.3 CVE-2022-20320 In ActivityManager, there is a possible way to determine whether an app is installed, without query permissions, due to side channel information disclosure. google · android 2022-08-12 low3.3 CVE-2022-20318 In PackageInstaller, there is a possible way to determine whether an app is installed, without query permissions, due to side channel information disclosure. google · android 2022-08-12 low3.3 CVE-2022-20316 In ContentResolver, there is a possible way to determine whether an app is installed, without query permissions, due to side channel information disclosure. google · android 2022-08-12 low3.3 CVE-2022-20315 In ActivityManager, there is a possible disclosure of installed packages due to a missing permission check. google · android 2022-08-12 low3.3 CVE-2022-20311 In Telecomm, there is a possible disclosure of registered self managed phone accounts due to a missing permission check. google · android 2022-08-12 low3.3 CVE-2022-20310 In Telecomm, there is a possible disclosure of registered self managed phone accounts due to a missing permission check. google · android 2022-08-12 low3.3 CVE-2022-20309 In PackageInstaller, there is a possible way to determine whether an app is installed, without query permissions, due to side channel information disclosure. google · android 2022-08-12 low3.3 CVE-2022-20307 In AlarmManagerService, there is a possible way to determine whether an app is installed, without query permissions, due to side channel information disclosure. google · android 2022-08-12 low3.3 CVE-2022-20305 In ContentService, there is a possible disclosure of available account types due to a missing permission check. google · android 2022-08-12 low3.3 CVE-2022-20280 In MMSProvider, there is a possible read of protected data due to improper input validationSQL injection. google · android 2022-08-12 low3.3 CVE-2022-20267 In bluetooth, there is a possible way to enable or disable bluetooth connection without user consent due to a missing permission check. google · android 2022-08-12 low3.3 CVE-2022-20262 In ActivityManager, there is a possible way to check another process's capabilities due to a missing permission check. google · android 2022-08-12 low2.3 CVE-2022-20261 In LocationManager, there is a possible way to get location information due to a missing permission check. google · android 2022-08-12 low3.3 CVE-2022-20257 In Bluetooth, there is a possible way to pair a display only device without PIN confirmation due to a logic error in the code. google · android 2022-08-12 low3.3 CVE-2022-20252 In PackageManager, there is a possible way to determine whether an app is installed, without query permissions, due to side channel information disclosure. google · android 2022-08-11 low3.3 CVE-2022-20251 In LocaleManager, there is a possible way to determine whether an app is installed, without query permissions, due to side channel information disclosure. google · android 2022-08-11 low3.3 CVE-2022-20249 In LocaleManager, there is a possible way to determine whether an app is installed, without query permissions, due to side channel information disclosure. google · android 2022-08-11 low2.4 CVE-2022-20245 In WindowManager, there is a possible method to create a recording of the lock screen due to an insecure default value. google · android 2022-08-11 low3.3 CVE-2022-20241 In Messaging, there is a possible way to attach a private file to an SMS message due to improper input validation. google · android 2022-08-11 low3.3 CVE-2022-20358 In startSync of AbstractThreadedSyncAdapter.java, there is a possible way to access protected content of content providers due to a missing permission check. google · android 2022-08-10 low3.3 CVE-2022-33726 Unprotected dynamic receiver in Samsung Galaxy Friends prior to SMR Aug-2022 Release 1 allows attacker to launch activity. google · android 2022-08-05 low3.3 CVE-2022-33724 Exposure of Sensitive Information in Samsung Dialer application?prior to SMR Aug-2022 Release 1 allows local attackers to access ICCID via log. google · android 2022-08-05 low2.4 CVE-2022-33720 Improper authentication vulnerability in AppLock prior to SMR Aug-2022 Release 1 allows physical attacker to access Chrome locked by AppLock via new tap shortc… google · android 2022-08-05 low2.3 CVE-2022-33716 An absence of variable initialization in ICCC TA prior to SMR Aug-2022 Release 1 allows local attacker to read uninitialized memory. google · android 2022-08-05 low3.9 CVE-2022-20226 In finishDrawingWindow of WindowManagerService.java, there is a possible tapjacking due to improper input validation. google · android 2022-07-13

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.