NetSight

Security Dashboard

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

Reset
152 matching advisories · page 5 of 6Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
low2.5 CVE-2021-25335 Improper lockscreen status check in cocktailbar service in Samsung mobile devices prior to SMR Mar-2021 Release 1 allows unauthenticated users to access hidden… samsung · one_ui, google · android 2021-03-04 low3.2 CVE-2021-25333 Improper access control in Samsung Pay mini application prior to v4.0.14 allows unauthorized access to balance information over the lockscreen via scanning spe… samsung · pay_mini 2021-03-04 low3.2 CVE-2021-25332 Improper access control in Samsung Pay mini application prior to v4.0.14 allows unauthorized access to contacts information over the lockscreen in specific con… samsung · pay_mini 2021-03-04 low3.2 CVE-2021-25331 Improper access control in Samsung Pay mini application prior to v4.0.14 allows unauthorized access to balance information over the lockscreen in specific cond… samsung · pay_mini 2021-03-04 low3.5 CVE-2020-13838 An issue was discovered on Samsung mobile devices with P(9.0) and Q(10.0) software. google · android 2020-06-04 low3.5 CVE-2020-13837 An issue was discovered on Samsung mobile devices with Q(10.0) software. google · android 2020-06-04 low2.4 CVE-2018-21077 An issue was discovered on Samsung mobile devices with M(6.0), N(7.x), and O(8.x) software. google · android 2020-04-08 low3.3 CVE-2018-21074 An issue was discovered on Samsung mobile devices with M(6.x) (Exynos or Qualcomm chipsets) software. google · android 2020-04-08 low2.4 CVE-2018-21073 An issue was discovered on Samsung mobile devices with N(7.x) and O(8.0) (Galaxy S9+, Galaxy S9, Galaxy S8+, Galaxy S8, Note 8). google · android 2020-04-08 low2.4 CVE-2018-21046 An issue was discovered on Samsung mobile devices with O(8.x) software. google · android 2020-04-08 low3.3 CVE-2018-21043 An issue was discovered on Samsung mobile devices with O(8.x) and P(9.0) (Exynos 9810 chipsets) software. google · android 2020-04-08 low2.4 CVE-2020-11606 An issue was discovered on Samsung mobile devices with Q(10.0) software. google · android 2020-04-08 low2.4 CVE-2020-11602 An issue was discovered on Samsung mobile devices with P(9.0) and Q(10.0) software. google · android 2020-04-08 low2.4 CVE-2017-18673 An issue was discovered on Samsung mobile devices with N(7.x) software. google · android 2020-04-07 low2.4 CVE-2016-11027 An issue was discovered on Samsung mobile devices with M(6.0) software. google · android 2020-04-07 low3.3 CVE-2019-20625 An issue was discovered on Samsung mobile devices with N(7.1) and O(8.x) (Exynos chipsets) software. google · android 2020-03-24 low3.3 CVE-2019-20623 An issue was discovered on Samsung mobile devices with N(7.1), O(8.x), and P(9.0) software. google · android 2020-03-24 low2.4 CVE-2019-20598 An issue was discovered on Samsung mobile devices with O(8.x) software. google · android 2020-03-24 low2.4 CVE-2019-20595 An issue was discovered on Samsung mobile devices with P(9.0) software. google · android 2020-03-24 low2.4 CVE-2019-20579 An issue was discovered on Samsung mobile devices with N(7.x), O(8.x), and P(9.0) software. google · android 2020-03-24 low2.4 CVE-2019-20559 An issue was discovered on Samsung mobile devices with P(9.0) software. google · android 2020-03-24 low2.4 CVE-2020-10830 An issue was discovered on Samsung mobile devices with P(9.0) and Q(10.0) software. google · android 2020-03-24 low2.4 CVE-2019-20534 An issue was discovered on Samsung mobile devices with P(9.0) software. google · android 2020-03-24 low3.3 CVE-2019-20533 An issue was discovered on Samsung mobile devices with N(7.x), O(8.x), and P(9.0) (released in China or India) software. google · android 2020-03-24 low3.3 CVE-2019-6331 An issue was found in Samsung Mobile Print (Android) versions prior to 4.08.007. hp · samsung_mobile_print 2020-01-09 low3.3 CVE-2016-2567 secfilter in the Samsung kernel for Android on SM-N9005 build N9005XXUGBOB6 (Note 3) and SM-G920F build G920FXXU2COH2 (Galaxy S6) devices allows attackers to b… samsung · galaxy_s6_firmware, samsung · galaxy_note_3_firmware 2017-04-13 low3.3 CVE-2016-2565 Samsung SecEmailSync on SM-G920F build G920FXXU2COH2 (Galaxy S6) devices allows attackers to read sent e-mail messages, aka SVE-2015-5081. samsung · galaxy_s6_firmware 2017-04-13 low3.3 CVE-2015-4033 Samsung SBeam allows remote attackers to read arbitrary images by leveraging an NFC connection to access the HTTP server on port 15000. samsung · s-beam 2015-07-06 low2.9 CVE-2015-4640 The SwiftKey language-pack update implementation on Samsung Galaxy S4, S4 Mini, S5, and S6 devices relies on an HTTP connection to the skslm.swiftkey.net serve… swiftkey · swiftkey_sdk 2015-06-19 low3.3 CVE-2013-2310 SoftBank Wi-Fi Spot Configuration Software, as used on SoftBank SHARP 3G handsets, SoftBank Panasonic 3G handsets, SoftBank NEC 3G handsets, SoftBank Samsung 3… softbank · wi-fi_spot_configuration_software, softbank · mobile_wi-fi_router, softbank · nec_3g_handset +9 2013-06-17

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.