{"vulnerability": "CVE-2024-5013", "sightings": [{"uuid": "4101d1a0-1c5a-4027-88df-158c2f5b03b5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50139", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113440984913066438", "content": "", "creation_timestamp": "2024-11-07T09:34:20.341916Z"}, {"uuid": "84343efd-c0fb-4d1f-a868-639f819dccaa", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50139", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113440996205884449", "content": "", "creation_timestamp": "2024-11-07T09:37:12.597733Z"}, {"uuid": "b3f2e3a1-d6d5-445d-b4b9-13751e380683", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50130", "type": "seen", "source": "Telegram/z9UMiF2wbzIvuPNfjokOH3MfMP4l-JzMiQXGUG-ema-mlExO", "content": "", "creation_timestamp": "2025-03-08T04:34:10.000000Z"}, {"uuid": "6c5a859e-b373-448a-b739-731dfb1935f5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-50135", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "0ad8a557-84b4-468e-b495-eaeb62ea9556", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-50135", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "2e244b0f-5c37-46df-91e7-a20bcafa5d84", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-50138", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "dd05c67a-b401-44de-b1b6-785251edd145", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50137", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/10683", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-50137\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nreset: starfive: jh71x0: Fix accessing the empty member on JH7110 SoC\n\ndata->asserted will be NULL on JH7110 SoC since commit 82327b127d41\n(\"reset: starfive: Add StarFive JH7110 reset driver\") was added. Add\nthe judgment condition to avoid errors when calling reset_control_status\non JH7110 SoC.\n\ud83d\udccf Published: 2024-11-05T17:11:00.861Z\n\ud83d\udccf Modified: 2025-04-07T08:36:55.150Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/3918b2016d28c9b2bddd5ab194ab366a4e2310f5\n2. https://git.kernel.org/stable/c/c923f1fb8ae8627322d167b73bb4f978404a05de\n3. https://git.kernel.org/stable/c/2cf59663660799ce16f4dfbed97cdceac7a7fa11", "creation_timestamp": "2025-04-07T08:44:50.000000Z"}, {"uuid": "c0b98874-bdcd-4d86-905a-a2f7d2218bf2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50131", "type": "seen", "source": "https://t.me/cvedetector/9929", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50131 - \"Linux Kernel Tracing Buffer Overflow Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-50131 \nPublished : Nov. 5, 2024, 6:15 p.m. | 22\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ntracing: Consider the NULL character when validating the event length  \n  \nstrlen() returns a string length excluding the null byte. If the string  \nlength equals to the maximum buffer length, the buffer will have no  \nspace for the NULL terminating character.  \n  \nThis commit checks this condition and returns failure for it. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T19:44:35.000000Z"}, {"uuid": "fb86c93b-b864-4ae0-9a13-c579339f53c2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50132", "type": "seen", "source": "https://t.me/cvedetector/9926", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50132 - Linux Kernel Tracing Probe Array Overflow Null Pointer Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-50132 \nPublished : Nov. 5, 2024, 6:15 p.m. | 22\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ntracing/probes: Fix MAX_TRACE_ARGS limit handling  \n  \nWhen creating a trace_probe we would set nr_args prior to truncating the  \narguments to MAX_TRACE_ARGS. However, we would only initialize arguments  \nup to the limit.  \n  \nThis caused invalid memory access when attempting to set up probes with  \nmore than 128 fetchargs.  \n  \n  BUG: kernel NULL pointer dereference, address: 0000000000000020  \n  #PF: supervisor read access in kernel mode  \n  #PF: error_code(0x0000) - not-present page  \n  PGD 0 P4D 0  \n  Oops: Oops: 0000 [#1] PREEMPT SMP PTI  \n  CPU: 0 UID: 0 PID: 1769 Comm: cat Not tainted 6.11.0-rc7+ #8  \n  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-1.fc39 04/01/2014  \n  RIP: 0010:__set_print_fmt+0x134/0x330  \n  \nResolve the issue by applying the MAX_TRACE_ARGS limit earlier. Return  \nan error when there are too many arguments instead of silently  \ntruncating. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T19:44:29.000000Z"}, {"uuid": "b3666b43-f12b-44cb-8a2d-3f36600fd116", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50137", "type": "seen", "source": "https://t.me/cvedetector/9917", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50137 - StarFive JH7110 SoC NULL Pointer Dereference Vulnerability in Linux Kernel Boot Controller\", \n  \"Content\": \"CVE ID : CVE-2024-50137 \nPublished : Nov. 5, 2024, 6:15 p.m. | 22\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nreset: starfive: jh71x0: Fix accessing the empty member on JH7110 SoC  \n  \ndata->asserted will be NULL on JH7110 SoC since commit 82327b127d41  \n(\"reset: starfive: Add StarFive JH7110 reset driver\") was added. Add  \nthe judgment condition to avoid errors when calling reset_control_status  \non JH7110 SoC. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T19:44:18.000000Z"}, {"uuid": "f1a614ef-a42c-413d-8b1d-ac38a32419f1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50136", "type": "seen", "source": "https://t.me/cvedetector/9916", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50136 - Mellanox MLX5 Unregistered Notifier Registration Warning\", \n  \"Content\": \"CVE ID : CVE-2024-50136 \nPublished : Nov. 5, 2024, 6:15 p.m. | 22\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnet/mlx5: Unregister notifier on eswitch init failure  \n  \nIt otherwise remains registered and a subsequent attempt at eswitch  \nenabling might trigger warnings of the sort:  \n  \n[  682.589148] ------------[ cut here ]------------  \n[  682.590204] notifier callback eswitch_vport_event [mlx5_core] already registered  \n[  682.590256] WARNING: CPU: 13 PID: 2660 at kernel/notifier.c:31 notifier_chain_register+0x3e/0x90  \n[...snipped]  \n[  682.610052] Call Trace:  \n[  682.610369]    \n[  682.610663]  ? __warn+0x7c/0x110  \n[  682.611050]  ? notifier_chain_register+0x3e/0x90  \n[  682.611556]  ? report_bug+0x148/0x170  \n[  682.611977]  ? handle_bug+0x36/0x70  \n[  682.612384]  ? exc_invalid_op+0x13/0x60  \n[  682.612817]  ? asm_exc_invalid_op+0x16/0x20  \n[  682.613284]  ? notifier_chain_register+0x3e/0x90  \n[  682.613789]  atomic_notifier_chain_register+0x25/0x40  \n[  682.614322]  mlx5_eswitch_enable_locked+0x1d4/0x3b0 [mlx5_core]  \n[  682.614965]  mlx5_eswitch_enable+0xc9/0x100 [mlx5_core]  \n[  682.615551]  mlx5_device_enable_sriov+0x25/0x340 [mlx5_core]  \n[  682.616170]  mlx5_core_sriov_configure+0x50/0x170 [mlx5_core]  \n[  682.616789]  sriov_numvfs_store+0xb0/0x1b0  \n[  682.617248]  kernfs_fop_write_iter+0x117/0x1a0  \n[  682.617734]  vfs_write+0x231/0x3f0  \n[  682.618138]  ksys_write+0x63/0xe0  \n[  682.618536]  do_syscall_64+0x4c/0x100  \n[  682.618958]  entry_SYSCALL_64_after_hwframe+0x4b/0x53 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T19:44:14.000000Z"}, {"uuid": "9883e558-7c90-493c-bcb6-ad943ad2d0c2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50135", "type": "seen", "source": "https://t.me/cvedetector/9915", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50135 - \"NVMe PCI Race Condition Allows Invalid Queue Values\"\", \n  \"Content\": \"CVE ID : CVE-2024-50135 \nPublished : Nov. 5, 2024, 6:15 p.m. | 22\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnvme-pci: fix race condition between reset and nvme_dev_disable()  \n  \nnvme_dev_disable() modifies the dev->online_queues field, therefore  \nnvme_pci_update_nr_queues() should avoid racing against it, otherwise  \nwe could end up passing invalid values to blk_mq_update_nr_hw_queues().  \n  \n WARNING: CPU: 39 PID: 61303 at drivers/pci/msi/api.c:347  \n          pci_irq_get_affinity+0x187/0x210  \n Workqueue: nvme-reset-wq nvme_reset_work [nvme]  \n RIP: 0010:pci_irq_get_affinity+0x187/0x210  \n Call Trace:  \n    \n  ? blk_mq_pci_map_queues+0x87/0x3c0  \n  ? pci_irq_get_affinity+0x187/0x210  \n  blk_mq_pci_map_queues+0x87/0x3c0  \n  nvme_pci_map_queues+0x189/0x460 [nvme]  \n  blk_mq_update_nr_hw_queues+0x2a/0x40  \n  nvme_reset_work+0x1be/0x2a0 [nvme]  \n  \nFix the bug by locking the shutdown_lock mutex before using  \ndev->online_queues. Give up if nvme_dev_disable() is running or if  \nit has been executed already. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T19:44:14.000000Z"}, {"uuid": "2254bbfd-31b1-4178-8dd4-5c4f2c236340", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50133", "type": "seen", "source": "https://t.me/cvedetector/9914", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50133 - LoongArch Linux Kernel NULL Pointer Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-50133 \nPublished : Nov. 5, 2024, 6:15 p.m. | 22\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nLoongArch: Don't crash in stack_top() for tasks without vDSO  \n  \nNot all tasks have a vDSO mapped, for example kthreads never do. If such  \na task ever ends up calling stack_top(), it will derefence the NULL vdso  \npointer and crash.  \n  \nThis can for example happen when using kunit:  \n  \n [<9000000000203874] stack_top+0x58/0xa8  \n [<90000000002956cc] arch_pick_mmap_layout+0x164/0x220  \n [<90000000003c284c] kunit_vm_mmap_init+0x108/0x12c  \n [<90000000003c1fbc] __kunit_add_resource+0x38/0x8c  \n [<90000000003c2704] kunit_vm_mmap+0x88/0xc8  \n [<9000000000410b14] usercopy_test_init+0xbc/0x25c  \n [<90000000003c1db4] kunit_try_run_case+0x5c/0x184  \n [<90000000003c3d54] kunit_generic_run_threadfn_adapter+0x24/0x48  \n [<900000000022e4bc] kthread+0xc8/0xd4  \n [<9000000000200ce8] ret_from_kernel_thread+0xc/0xa4 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T19:44:13.000000Z"}, {"uuid": "5c5dddbd-db48-4872-ae89-fd8d10e12038", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50138", "type": "seen", "source": "https://t.me/cvedetector/9913", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50138 - Qualcomm Linux BPF Ringbuf Spinlock Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-50138 \nPublished : Nov. 5, 2024, 6:15 p.m. | 22\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nbpf: Use raw_spinlock_t in ringbuf  \n  \nThe function __bpf_ringbuf_reserve is invoked from a tracepoint, which  \ndisables preemption. Using spinlock_t in this context can lead to a  \n\"sleep in atomic\" warning in the RT variant. This issue is illustrated  \nin the example below:  \n  \nBUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48  \nin_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 556208, name: test_progs  \npreempt_count: 1, expected: 0  \nRCU nest depth: 1, expected: 1  \nINFO: lockdep is turned off.  \nPreemption disabled at:  \n[] migrate_enable+0xc0/0x39c  \nCPU: 7 PID: 556208 Comm: test_progs Tainted: G  \nHardware name: Qualcomm SA8775P Ride (DT)  \nCall trace:  \n dump_backtrace+0xac/0x130  \n show_stack+0x1c/0x30  \n dump_stack_lvl+0xac/0xe8  \n dump_stack+0x18/0x30  \n __might_resched+0x3bc/0x4fc  \n rt_spin_lock+0x8c/0x1a4  \n __bpf_ringbuf_reserve+0xc4/0x254  \n bpf_ringbuf_reserve_dynptr+0x5c/0xdc  \n bpf_prog_ac3d15160d62622a_test_read_write+0x104/0x238  \n trace_call_bpf+0x238/0x774  \n perf_call_bpf_enter.isra.0+0x104/0x194  \n perf_syscall_enter+0x2f8/0x510  \n trace_sys_enter+0x39c/0x564  \n syscall_trace_enter+0x220/0x3c0  \n do_el0_svc+0x138/0x1dc  \n el0_svc+0x54/0x130  \n el0t_64_sync_handler+0x134/0x150  \n el0t_64_sync+0x17c/0x180  \n  \nSwitch the spinlock to raw_spinlock_t to avoid this error. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T19:44:12.000000Z"}, {"uuid": "3950cab4-903d-4fce-8cfd-4cd1324d4d77", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50134", "type": "seen", "source": "https://t.me/cvedetector/9912", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50134 - Oracle VirtualBox Scatter Write Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-50134 \nPublished : Nov. 5, 2024, 6:15 p.m. | 22\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ndrm/vboxvideo: Replace fake VLA at end of vbva_mouse_pointer_shape with real VLA  \n  \nReplace the fake VLA at end of the vbva_mouse_pointer_shape shape with  \na real VLA to fix a \"memcpy: detected field-spanning write error\" warning:  \n  \n[   13.319813] memcpy: detected field-spanning write (size 16896) of single field \"p->data\" at drivers/gpu/drm/vboxvideo/hgsmi_base.c:154 (size 4)  \n[   13.319841] WARNING: CPU: 0 PID: 1105 at drivers/gpu/drm/vboxvideo/hgsmi_base.c:154 hgsmi_update_pointer_shape+0x192/0x1c0 [vboxvideo]  \n[   13.320038] Call Trace:  \n[   13.320173]  hgsmi_update_pointer_shape [vboxvideo]  \n[   13.320184]  vbox_cursor_atomic_update [vboxvideo]  \n  \nNote as mentioned in the added comment it seems the original length  \ncalculation for the allocated and send hgsmi buffer is 4 bytes too large.  \nChanging this is not the goal of this patch, so this behavior is kept. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T19:44:11.000000Z"}, {"uuid": "85bc6fc9-0555-433d-b8e5-41bc0bb0f2ef", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50130", "type": "seen", "source": "https://t.me/cvedetector/9931", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50130 - Linux Netfilter BPF NetNamespace Reference Leak Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-50130 \nPublished : Nov. 5, 2024, 6:15 p.m. | 22\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnetfilter: bpf: must hold reference on net namespace  \n  \nBUG: KASAN: slab-use-after-free in __nf_unregister_net_hook+0x640/0x6b0  \nRead of size 8 at addr ffff8880106fe400 by task repro/72=  \nbpf_nf_link_release+0xda/0x1e0  \nbpf_link_free+0x139/0x2d0  \nbpf_link_release+0x68/0x80  \n__fput+0x414/0xb60  \n  \nEric says:  \n It seems that bpf was able to defer the __nf_unregister_net_hook()  \n after exit()/close() time.  \n Perhaps a netns reference is missing, because the netns has been  \n dismantled/freed already.  \n bpf_nf_link_attach() does :  \n link->net = net;  \n But I do not see a reference being taken on net.  \n  \nAdd such a reference and release it after hook unreg.  \nNote that I was unable to get syzbot reproducer to work, so I  \ndo not know if this resolves this splat. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T19:44:36.000000Z"}]}