https://db.gcve.eu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Thu, 21 May 2026 21:15:50 +0000 https://db.gcve.eu/sighting/4845da41-aa9e-4ff7-9d08-524098e75036/export {"uuid": "4845da41-aa9e-4ff7-9d08-524098e75036", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "GHSA-HX5V-J59Q-C3J8", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14865", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2022-2741\n\ud83d\udd25 CVSS Score: 8.2 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H)\n\ud83d\udd39 Description: The denial-of-service can be triggered by transmitting a carefully crafted CAN frame on the same CAN network as the vulnerable node. The frame must have a CAN ID matching an installed filter in the vulnerable node (this can easily be guessed based on CAN traffic analyses). The frame must contain the opposite RTR bit as what the filter installed in the vulnerable node contains (if the filter matches RTR frames, the frame must be a data frame or vice versa).\n\ud83d\udccf Published: 2022-10-31T17:45:09.741Z\n\ud83d\udccf Modified: 2025-05-05T14:06:07.171Z\n\ud83d\udd17 References:\n1. https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-hx5v-j59q-c3j8", "creation_timestamp": "2025-05-05T14:20:35.000000Z"} {"uuid": "4845da41-aa9e-4ff7-9d08-524098e75036", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "GHSA-HX5V-J59Q-C3J8", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14865", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2022-2741\n\ud83d\udd25 CVSS Score: 8.2 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H)\n\ud83d\udd39 Description: The denial-of-service can be triggered by transmitting a carefully crafted CAN frame on the same CAN network as the vulnerable node. The frame must have a CAN ID matching an installed filter in the vulnerable node (this can easily be guessed based on CAN traffic analyses). The frame must contain the opposite RTR bit as what the filter installed in the vulnerable node contains (if the filter matches RTR frames, the frame must be a data frame or vice versa).\n\ud83d\udccf Published: 2022-10-31T17:45:09.741Z\n\ud83d\udccf Modified: 2025-05-05T14:06:07.171Z\n\ud83d\udd17 References:\n1. https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-hx5v-j59q-c3j8", "creation_timestamp": "2025-05-05T14:20:35.000000Z"} https://db.gcve.eu/sighting/4845da41-aa9e-4ff7-9d08-524098e75036/export Mon, 05 May 2025 14:20:35 +0000