NetSight

Security Dashboard

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

Reset
337 matching advisories · page 10 of 12Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.9 CVE-2023-1902 The bluetooth HCI host layer logic not clearing a global reference to a state pointer after handling connection events may allow a malicious HCI Controller to … zephyrproject · zephyr 2023-07-10 medium5.9 CVE-2023-1901 The bluetooth HCI host layer logic not clearing a global reference to a semaphore after synchronously sending HCI commands may allow a malicious HCI Controller… zephyrproject · zephyr 2023-07-10 medium5.9 CVE-2023-0359 A missing nullptr-check in handle_ra_input can cause a nullptr-deref. zephyrproject · zephyr 2023-07-10 medium6.7 CVE-2023-0779 At the most basic level, an invalid pointer can be input that crashes the device, but with more knowledge of the device’s memory layout, further exploitation i… zephyrproject · zephyr 2023-05-30 critical9.6 CVE-2021-3329 Lack of proper validation in HCI Host stack initialization can cause a crash of the bluetooth stack zephyrproject · zephyr 2023-02-26 medium6.8 CVE-2023-0396 A malicious / defective bluetooth controller can cause buffer overreads in the most functions that process HCI command responses. zephyrproject · zephyr 2023-01-25 critical9.8 CVE-2022-3806 Inconsistent handling of error cases in bluetooth hci may lead to a double free condition of a network buffer. zephyrproject · zephyr 2023-01-25 critical9.6 CVE-2023-0397 A malicious / defect bluetooth controller can cause a Denial of Service due to unchecked input in le_read_buffer_size_complete. zephyrproject · zephyr 2023-01-19 critical9.6 CVE-2021-3966 usb device bluetooth class includes a buffer overflow related to implementation of net_buf_add_mem. zephyrproject · zephyr 2023-01-11 medium6.5 CVE-2022-0553 There is no check to see if slot 0 is being uploaded from the device to the host. zephyrproject · zephyr 2023-01-11 high8.6 CVE-2022-2993 There is an error in the condition of the last if-statement in the function smp_check_keys. zephyrproject · zephyr 2022-12-09 high8.2 CVE-2022-2741 The denial-of-service can be triggered by transmitting a carefully crafted CAN frame on the same CAN network as the vulnerable node. zephyrproject · zephyr 2022-10-31 high7.2 CVE-2022-1841 In subsys/net/ip/tcp.c , function tcp_flags , when the incoming parameter flags is ECN or CWR , the buf will out-of-bounds write a byte zero. zephyrproject · zephyr 2022-08-31 high8.2 CVE-2022-1042 In Zephyr bluetooth mesh core stack, an out-of-bound write vulnerability can be triggered during provisioning. zephyrproject · zephyr 2022-07-26 high8.2 CVE-2022-1041 In Zephyr bluetooth mesh core stack, an out-of-bound write vulnerability can be triggered during provisioning. zephyrproject · zephyr 2022-07-26 medium4.0 CVE-2021-3435 Information leakage in le_ecred_conn_req(). zephyrproject · zephyr 2022-06-28 medium4.9 CVE-2021-3434 Stack based buffer overflow in le_ecred_conn_req(). zephyrproject · zephyr 2022-06-28 medium4.0 CVE-2021-3433 Invalid channel map in CONNECT_IND results to Deadlock. zephyrproject · zephyr 2022-06-28 medium4.3 CVE-2021-3432 Invalid interval in CONNECT_IND leads to Division by Zero. zephyrproject · zephyr 2022-06-28 medium4.3 CVE-2021-3431 Assertion reachable with repeated LL_FEATURE_REQ. zephyrproject · zephyr 2022-06-28 medium6.5 CVE-2021-3430 Assertion reachable with repeated LL_CONNECTION_PARAM_REQ. zephyrproject · zephyr 2022-06-28 high8.2 CVE-2021-3861 The RNDIS USB device class includes a buffer overflow vulnerability. zephyrproject · zephyr 2022-02-07 high8.2 CVE-2021-3835 Buffer overflow in usb device class. zephyrproject · zephyr 2022-02-07 medium4.3 CVE-2021-3455 Disconnecting L2CAP channel right after invalid ATT request leads freeze. zephyrproject · zephyr 2021-10-19 medium4.3 CVE-2021-3454 Truncated L2CAP K-frame causes assertion failure. zephyrproject · zephyr 2021-10-19 high7.1 CVE-2021-3330 RCE/DOS: Linked-list corruption leading to large out-of-bounds write while sorting for forged fragment list in Zephyr. zephyrproject · zephyr 2021-10-12 high8.3 CVE-2021-3323 Integer Underflow in 6LoWPAN IPHC Header Uncompression in Zephyr. zephyrproject · zephyr 2021-10-12 medium6.5 CVE-2021-3322 Unexpected Pointer Aliasing in IEEE 802154 Fragment Reassembly in Zephyr. zephyrproject · zephyr 2021-10-12 high7.5 CVE-2021-3321 Integer Underflow in Zephyr in IEEE 802154 Fragment Reassembly Header Removal. zephyrproject · zephyr 2021-10-12 critical9.6 CVE-2021-3625 Buffer overflow in Zephyr USB DFU DNLOAD. zephyrproject · zephyr 2021-10-05

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.