NetSight

Security Dashboard

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

Reset
337 matching advisories · page 9 of 12Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.6 CVE-2024-6259 BT: HCI: adv_ext_report Improper discarding in adv_ext_report zephyrproject · zephyr 2024-09-13 high7.6 CVE-2024-6137 BT: Classic: SDP OOB access in get_att_search_list zephyrproject · zephyr 2024-09-13 high7.6 CVE-2024-6135 BT:Classic: Multiple missing buf length checks zephyrproject · zephyr 2024-09-13 medium6.3 CVE-2024-5931 BT: Unchecked user input in bap_broadcast_assistant zephyrproject · zephyr 2024-09-13 medium6.8 CVE-2024-6258 BT: Missing length checks of net_buf in rfcomm_handle_data zephyrproject · zephyr 2024-09-13 high8.2 CVE-2024-5754 BT: Encryption procedure host vulnerability zephyrproject · zephyr 2024-09-13 high7.6 CVE-2024-4785 BT: Missing Check in LL_CONNECTION_UPDATE_IND Packet Leads to Division by Zero zephyrproject · zephyr 2024-08-19 medium6.5 CVE-2024-3332 A malicious BLE device can send a specific order of packet sequence to cause a DoS attack on the victim BLE device zephyrproject · zephyr 2024-07-03 medium6.8 CVE-2024-3077 An malicious BLE device can crash BLE victim device by sending malformed gatt packet zephyrproject · zephyr 2024-03-29 high8.6 CVE-2023-7060 Zephyr OS IP packet handling does not properly drop IP packets arriving on an external interface with a source address equal to 127.0.01 or the destination add… zephyrproject · zephyr 2024-03-15 high7.3 CVE-2023-6881 Possible buffer overflow in is_mount_point zephyrproject · zephyr 2024-02-29 high8.2 CVE-2024-1638 The documentation specifies that the BT_GATT_PERM_READ_LESC and BT_GATT_PERM_WRITE_LESC defines for a Bluetooth characteristic: Attribute read/write permission… zephyrproject · zephyr 2024-02-19 high8.0 CVE-2023-6249 Signed to unsigned conversion esp32_ipm_send zephyrproject · zephyr 2024-02-18 medium4.4 CVE-2023-5779 can: out of bounds in remove_rx_filter function zephyrproject · zephyr 2024-02-18 high8.0 CVE-2023-6749 Unchecked length coming from user input in settings shell zephyrproject · zephyr 2024-02-18 high8.3 CVE-2023-5055 Possible variant of CVE-2021-3434 in function le_ecred_reconf_req. zephyrproject · zephyr 2023-11-21 high8.3 CVE-2023-4424 An malicious BLE device can cause buffer overflow by sending malformed advertising packet BLE device using Zephyr OS, leading to DoS or potential RCE on the vi… zephyrproject · zephyr 2023-11-21 medium4.4 CVE-2023-5139 Potential buffer overflow vulnerability at the following location in the Zephyr STM32 Crypto driver zephyrproject · zephyr 2023-10-26 medium6.3 CVE-2023-5753 Potential buffer overflows in the Bluetooth subsystem due to asserts being disabled in /subsys/bluetooth/host/hci_core.c zephyrproject · zephyr 2023-10-25 high7.6 CVE-2023-4257 Unchecked user input length in /subsys/net/l2/wifi/wifi_shell.c can cause buffer overflows. zephyrproject · zephyr 2023-10-13 high7.6 CVE-2023-4263 Potential buffer overflow vulnerability in the Zephyr IEEE 802.15.4 nRF 15.4 driver zephyrproject · zephyr 2023-10-13 high7.1 CVE-2023-5563 The SJA1000 CAN controller driver backend automatically attempt to recover from a bus-off event when built with CONFIG_CAN_AUTO_BUS_OFF_RECOVERY=y. zephyrproject · zephyr 2023-10-13 high7.6 CVE-2023-3725 Potential buffer overflow vulnerability in the Zephyr CAN bus subsystem zephyrproject · zephyr 2023-10-06 high7.0 CVE-2023-5184 Two potential signed to unsigned conversion errors and buffer overflow vulnerabilities at the following locations in the Zephyr IPM drivers. zephyrproject · zephyr 2023-09-27 high7.1 CVE-2023-4264 Potential buffer overflow vulnerabilities n the Zephyr Bluetooth subsystem. zephyrproject · zephyr 2023-09-27 medium6.3 CVE-2023-4260 Potential off-by-one buffer overflow vulnerability in the Zephyr fuse file system. zephyrproject · zephyr 2023-09-27 high7.1 CVE-2023-4259 Two potential buffer overflow vulnerabilities at the following locations in the Zephyr eS-WiFi driver source code. zephyrproject · zephyr 2023-09-26 high8.6 CVE-2023-4258 In Bluetooth mesh implementation If provisionee has a public key that is sent OOB then during provisioning it can be sent back and will be accepted by provisio… zephyrproject · zephyr 2023-09-25 medium6.4 CVE-2023-4265 Potential buffer overflow vulnerabilities in the following locations: https://github.com/zephyrproject-rtos/zephyr/blob/main/drivers/usb/device/usb_dc_native_p… zephyrproject · zephyr 2023-08-12 medium6.8 CVE-2023-2234 Union variant confusion allows any malicious BT controller to execute arbitrary code on the Zephyr host. zephyrproject · zephyr 2023-07-10

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.