NetSight

Security Dashboard

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

Reset
48 matching advisories · page 2 of 2Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.3 CVE-2022-45190 An issue was discovered on Microchip RN4870 1.43 devices. microchip · rn4870_firmware 2023-02-08 medium6.5 CVE-2022-40480 Nordic Semiconductor, Microchip Technology NRF5340-DK DT100112 was discovered to contain an issue which allows attackers to cause a Denial of Service (DoS) via… microchip · dt100112_firmware, nordicsemi · nrf5340-dk_firmware 2023-02-08 medium6.5 CVE-2022-46402 The Microchip RN4870 module firmware 1.43 (and the Microchip PIC LightBlue Explorer Demo 4.2 DT100112) accepts PairCon_rmSend with incorrect values. microchip · bm78_firmware, microchip · bm83_firmware, microchip · rn4870_firmware +6 2022-12-19 medium5.4 CVE-2022-46401 The Microchip RN4870 module firmware 1.43 (and the Microchip PIC LightBlue Explorer Demo 4.2 DT100112) accepts PauseEncReqPlainText before pairing is complete. microchip · bm78_firmware, microchip · bm83_firmware, microchip · rn4870_firmware +9 2022-12-19 medium5.4 CVE-2022-46400 The Microchip RN4870 module firmware 1.43 (and the Microchip PIC LightBlue Explorer Demo 4.2 DT100112) allows attackers to bypass passkey entry in legacy pairi… microchip · bm78_firmware, microchip · bm83_firmware, microchip · rn4870_firmware +6 2022-12-19 medium6.5 CVE-2021-41788 MediaTek microchips, as used in NETGEAR devices through 2021-12-13 and other devices, mishandle attempts at Wi-Fi authentication flooding. mediatek · mt7603e_firmware, mediatek · mt7612_firmware, mediatek · mt7613_firmware +5 2021-12-26 medium5.9 CVE-2020-20950 Bleichenbacher's attack on PKCS #1 v1.5 padding for RSA in Microchip Libraries for Applications 2018-11-26 All up to 2018-11-26. ietf · public_key_cryptography_standards_\#1, microchip · microchip_libraries_for_applications 2021-01-19 medium6.8 CVE-2019-16128 Microchip CryptoAuthentication Library CryptoAuthLib prior to 20191122 has a Buffer Overflow (issue 1 of 2). microchip · cryptoauthlib 2020-10-22 medium6.8 CVE-2019-16129 Microchip CryptoAuthentication Library CryptoAuthLib prior to 20191122 has a Buffer Overflow (issue 2 of 2). microchip · cryptoauthlib 2020-10-22 medium6.5 CVE-2020-9033 Symmetricom SyncServer S100 2.90.70.3, S200 1.30, S250 1.25, S300 2.65.0, and S350 2.80.1 devices allow Directory Traversal via the FileName parameter to authl… microchip · syncserver_s100_firmware, microchip · syncserver_s200_firmware, microchip · syncserver_s250_firmware +2 2020-02-17 medium6.5 CVE-2020-9032 Symmetricom SyncServer S100 2.90.70.3, S200 1.30, S250 1.25, S300 2.65.0, and S350 2.80.1 devices allow Directory Traversal via the FileName parameter to kernl… microchip · syncserver_s100_firmware, microchip · syncserver_s200_firmware, microchip · syncserver_s250_firmware +2 2020-02-17 medium6.5 CVE-2020-9031 Symmetricom SyncServer S100 2.90.70.3, S200 1.30, S250 1.25, S300 2.65.0, and S350 2.80.1 devices allow Directory Traversal via the FileName parameter to daemo… microchip · syncserver_s100_firmware, microchip · syncserver_s200_firmware, microchip · syncserver_s250_firmware +2 2020-02-17 medium6.5 CVE-2020-9030 Symmetricom SyncServer S100 2.90.70.3, S200 1.30, S250 1.25, S300 2.65.0, and S350 2.80.1 devices allow Directory Traversal via the FileName parameter to the s… microchip · syncserver_s100_firmware, microchip · syncserver_s200_firmware, microchip · syncserver_s250_firmware +2 2020-02-17 medium6.5 CVE-2020-9029 Symmetricom SyncServer S100 2.90.70.3, S200 1.30, S250 1.25, S300 2.65.0, and S350 2.80.1 devices allow Directory Traversal via the FileName parameter to messa… microchip · syncserver_s100_firmware, microchip · syncserver_s200_firmware, microchip · syncserver_s250_firmware +2 2020-02-17 medium6.1 CVE-2020-9028 Symmetricom SyncServer S100 2.90.70.3, S200 1.30, S250 1.25, S300 2.65.0, and S350 2.80.1 devices allow stored XSS via the newUserName parameter on the "User C… microchip · syncserver_s100_firmware, microchip · syncserver_s200_firmware, microchip · syncserver_s250_firmware +2 2020-02-17 medium6.5 CVE-2019-19195 The Bluetooth Low Energy implementation on Microchip Technology BluSDK Smart through 6.2 for ATSAMB11 devices does not properly restrict link-layer data length… microchip · atmsamb11_blusdk_smart 2020-02-10 medium4.7 CVE-2019-15809 Smart cards from the Athena SCS manufacturer, based on the Atmel Toolbox 00.03.11.05 and the AT90SC chip, contain a timing side channel in ECDSA signature gene… microchip · atmel_toolbox, athena-scs · idprotect, cryptsoft · s\/a_idflex_v +2 2019-10-03 medium6.8 CVE-2006-2482 Heap-based buffer overflow in the TZipTV component in (1) ZipTV for Delphi 7 2006.1.26 and for C++ Builder 2006-1.16, (2) PentaZip 8.5.1.190 and PentaSuite-PRO… microchip_data_systems · ziptv_for_c\+\+_builder, microchip_data_systems · ziptv_for_delphi_7, pentaware · pentasuite-pro +1 2006-09-08

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.