{"vulnerability": "CVE-2024-4687", "sightings": [{"uuid": "bc236e7a-6c56-4f0f-b811-9e6d4a2a2af0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-46872", "type": "seen", "source": "https://t.me/cvedetector/9272", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-46872 - Mattermost CSRF Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-46872 \nPublished : Oct. 29, 2024, 9:15 a.m. | 19\u00a0minutes ago \nDescription : Mattermost versions 9.10.x &lt;=&lt;=&lt;=\nSeverity: 4.6 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-29T10:35:21.000000Z"}, {"uuid": "3995fe9a-ab0a-47ce-9761-19c4bac76fef", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-46871", "type": "seen", "source": "https://t.me/cvedetector/7467", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-46871 - \"AMDGPU_DMUB_NOTIFICATION_MAX Array Out-of-Bounds Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-46871 \nPublished : Oct. 9, 2024, 2:15 p.m. | 38\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ndrm/amd/display: Correct the defined value for AMDGPU_DMUB_NOTIFICATION_MAX  \n  \n[Why &amp; How]  \nIt actually exposes '6' types in enum dmub_notification_type. Not 5. Using smaller  \nnumber to create array dmub_callback &amp; dmub_thread_offload has potential to access  \nitem out of array bound. Fix it. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-09T17:19:10.000000Z"}, {"uuid": "15b7a054-8345-49cd-9173-c080d179f137", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-46874", "type": "seen", "source": "https://t.me/cvedetector/12273", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-46874 - Ruijie Reyee OS versions 2.206.x up to but not inc\", \n  \"Content\": \"CVE ID : CVE-2024-46874 \nPublished : Dec. 6, 2024, 7:15 p.m. | 19\u00a0minutes ago \nDescription : Ruijie Reyee OS versions 2.206.x up to but not including 2.320.x could allow MQTT clients connecting with device credentials to send messages to some topics. Attackers with device credentials could issue commands to other devices on behalf of Ruijie's cloud. \nSeverity: 8.1 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"06 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-06T20:38:59.000000Z"}, {"uuid": "75bde78d-0a3e-497d-94bc-2e25dc97857f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-46874", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113607286230169597", "content": "", "creation_timestamp": "2024-12-06T18:26:57.136202Z"}, {"uuid": "08cb8fd0-3e8f-4aa1-b562-d8484cc16214", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-46873", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113699339293135358", "content": "", "creation_timestamp": "2024-12-23T00:37:15.395566Z"}, {"uuid": "44f8d074-9e46-41ff-a978-df20c5997c9c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-46873", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113699351908622129", "content": "", "creation_timestamp": "2024-12-23T00:40:27.863912Z"}, {"uuid": "9adc8d30-7fb8-480a-9c83-707fae494b53", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-46873", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3ldwqxvpoyb25", "content": "", "creation_timestamp": "2024-12-23T01:15:35.144700Z"}, {"uuid": "72f8a7a7-2d49-4a62-8c30-b8499e6a65ea", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-46873", "type": "seen", "source": "https://cyberplace.social/users/GossiTheDog/statuses/113702428189011075", "content": "", "creation_timestamp": "2024-12-23T13:43:03.600015Z"}, {"uuid": "5d518baa-584a-4766-8481-2c22205c9261", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-46873", "type": "seen", "source": "https://bsky.app/profile/GossiTheDog.cyberplace.social.ap.brid.gy/post/3ldy2qnrrb372", "content": "", "creation_timestamp": "2024-12-23T13:43:14.604620Z"}, {"uuid": "cb19fe82-776b-4027-bdc9-0687d0873a19", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "4f29edb9-4c4b-44ca-b041-9b050656b6ae", "vulnerability": "CVE-2024-46870", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "3cbb2c9a-a094-4126-99ad-9a6b964c37e7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-46873", "type": "seen", "source": "https://t.me/cvedetector/13524", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-46873 - SHARP Router Debug Command Injection Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-46873 \nPublished : Dec. 23, 2024, 1:15 a.m. | 41\u00a0minutes ago \nDescription : Multiple SHARP routers leave the hidden debug function enabled. An arbitrary OS command may be executed with the root privilege by a remote unauthenticated attacker. \nSeverity: 9.8 | CRITICAL \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"23 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-23T03:17:12.000000Z"}, {"uuid": "025ae1af-efc9-444a-a8f1-293c249ee309", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-46870", "type": "seen", "source": "https://t.me/cvedetector/7465", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-46870 - \"Linux Kernel AMD Display System Hang/Crash Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-46870 \nPublished : Oct. 9, 2024, 2:15 p.m. | 38\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ndrm/amd/display: Disable DMCUB timeout for DCN35  \n  \n[Why]  \nDMCUB can intermittently take longer than expected to process commands.  \n  \nOld ASIC policy was to continue while logging a diagnostic error - which  \nworks fine for ASIC without IPS, but with IPS this could lead to a race  \ncondition where we attempt to access DCN state while it's inaccessible,  \nleading to a system hang when the NIU port is not disabled or register  \naccesses that timeout and the display configuration in an undefined  \nstate.  \n  \n[How]  \nWe need to investigate why these accesses take longer than expected, but  \nfor now we should disable the timeout on DCN35 to avoid this race  \ncondition. Since the waits happen only at lower interrupt levels the  \nrisk of taking too long at higher IRQ and causing a system watchdog  \ntimeout are minimal. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-09T17:19:08.000000Z"}, {"uuid": "4f025e30-2f50-45bc-b6bb-b518b08164b2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-46874", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-24-338-01", "content": "", "creation_timestamp": "2024-12-03T11:00:00.000000Z"}, {"uuid": "e69195c6-d5a1-487c-95c4-c8545dd117ab", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-46871", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "8e215966-2754-4824-802a-f6d88deaf869", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-46870", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "7b2fba5e-a031-4a75-90ee-76de8f0e4091", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-4687", "type": "seen", "source": "Telegram/shO2tYvv6agwgrkf1z6vLAX6NC-Qf2uf6nX0Ft0QvfnOdWyW", "content": "", "creation_timestamp": "2025-02-19T22:21:29.000000Z"}]}