NetSight

Security Dashboard

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

Reset
337 matching advisories · page 11 of 12Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.0 CVE-2021-3581 Buffer Access with Incorrect Length Value in zephyr. zephyrproject · zephyr 2021-10-05 high7.5 CVE-2021-3510 Zephyr JSON decoder incorrectly decodes array of array. zephyrproject · zephyr 2021-10-05 medium4.3 CVE-2021-3436 BT: Possible to overwrite an existing bond during keys distribution phase when the identity address of the bond is known. zephyrproject · zephyr 2021-10-05 medium6.5 CVE-2021-3319 DOS: Incorrect 802154 Frame Validation for Omitted Source / Dest Addresses. zephyrproject · zephyr 2021-10-05 medium5.9 CVE-2021-3320 Type Confusion in 802154 ACK Frames Handling. zephyrproject · zephyr 2021-05-25 medium6.9 CVE-2020-13603 Integer Overflow in memory allocating functions. zephyrproject · zephyr 2021-05-25 medium4.0 CVE-2020-13602 Remote Denial of Service in LwM2M do_write_op_tlv. zephyrproject · zephyr 2021-05-25 critical9.0 CVE-2020-13601 Possible read out of bounds in dns read. zephyrproject · zephyr 2021-05-25 high7.0 CVE-2020-13600 Malformed SPI in response for eswifi can corrupt kernel memory. zephyrproject · zephyr 2021-05-25 low3.3 CVE-2020-13599 Security problem with settings and littlefs. zephyrproject · zephyr 2021-05-25 medium6.3 CVE-2020-13598 FS: Buffer Overflow when enabling Long File Names in FAT_FS and calling fs_stat. zephyrproject · zephyr 2021-05-25 medium5.9 CVE-2020-10072 Improper Handling of Insufficient Permissions or Privileges in zephyr. zephyrproject · zephyr 2021-05-25 medium4.3 CVE-2020-10069 Zephyr Bluetooth unchecked packet data results in denial of service. zephyrproject · zephyr 2021-05-25 low2.5 CVE-2020-10066 Incorrect Error Handling in Bluetooth HCI core. zephyrproject · zephyr 2021-05-25 low3.8 CVE-2020-10065 Missing Size Checks in Bluetooth HCI over SPI. zephyrproject · zephyr 2021-05-25 high8.3 CVE-2020-10064 Improper Input Frame Validation in ieee802154 Processing. zephyrproject · zephyr 2021-05-25 critical9.0 CVE-2020-10071 The Zephyr MQTT parsing code performs insufficient checking of the length field on publish messages, allowing a buffer overflow and potentially remote code exe… zephyrproject · zephyr 2020-06-05 critical9.0 CVE-2020-10070 In the Zephyr Project MQTT code, improper bounds checking can result in memory corruption and possibly remote code execution. zephyrproject · zephyr 2020-06-05 medium5.1 CVE-2020-10068 In the Zephyr project Bluetooth subsystem, certain duplicate and back-to-back packets can cause incorrect behavior, resulting in a denial of service. zephyrproject · zephyr 2020-06-05 medium6.8 CVE-2020-10063 A remote adversary with the ability to send arbitrary CoAP packets to be parsed by Zephyr is able to cause a denial of service. zephyrproject · zephyr 2020-06-05 critical9.0 CVE-2020-10062 An off-by-one error in the Zephyr project MQTT packet length decoder can result in memory corruption and possible remote code execution. zephyrproject · zephyr 2020-06-05 high8.1 CVE-2020-10061 Improper handling of the full-buffer case in the Zephyr Bluetooth implementation can result in memory corruption. zephyrproject · zephyr 2020-06-05 high7.5 CVE-2020-10067 A malicious userspace application can cause a integer overflow and bypass security checks performed by system call handlers. zephyrproject · zephyr 2020-05-11 high8.0 CVE-2020-10060 In updatehub_probe, right after JSON parsing is complete, objects\[1] is accessed from the output structure in two different places. zephyrproject · zephyr 2020-05-11 medium4.8 CVE-2020-10059 The UpdateHub module disables DTLS peer checking, which allows for a man in the middle attack. zephyrproject · zephyr 2020-05-11 high7.8 CVE-2020-10058 Multiple syscalls in the Kscan subsystem perform insufficient argument validation, allowing code executing in userspace to potentially gain elevated privileges. zephyrproject · zephyr 2020-05-11 high7.8 CVE-2020-10028 Multiple syscalls with insufficient argument validation See NCC-ZEP-006 This issue affects: zephyrproject-rtos zephyr version 1.14.0 and later versions. zephyrproject · zephyr 2020-05-11 high7.8 CVE-2020-10027 An attacker who has obtained code execution within a user thread is able to elevate privileges to that of the kernel. zephyrproject · zephyr 2020-05-11 high7.8 CVE-2020-10024 The arm platform-specific code uses a signed integer comparison when validating system call numbers. zephyrproject · zephyr 2020-05-11 medium6.9 CVE-2020-10023 The shell subsystem contains a buffer overflow, whereby an adversary with physical access to the device is able to cause a memory corruption, resulting in deni… zephyrproject · zephyr 2020-05-11

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.