mirror of
https://github.com/fkie-cad/nvd-json-data-feeds.git
synced 2025-05-08 11:37:26 +00:00
Auto-Update: 2024-06-25T16:00:18.962894+00:00
This commit is contained in:
parent
61587a7a64
commit
b941cd8b5f
20
CVE-2021/CVE-2021-44xx/CVE-2021-4440.json
Normal file
20
CVE-2021/CVE-2021-44xx/CVE-2021-4440.json
Normal file
@ -0,0 +1,20 @@
|
||||
{
|
||||
"id": "CVE-2021-4440",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-06-25T15:15:11.137",
|
||||
"lastModified": "2024-06-25T15:15:11.137",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nx86/xen: Drop USERGS_SYSRET64 paravirt call\n\ncommit afd30525a659ac0ae0904f0cb4a2ca75522c3123 upstream.\n\nUSERGS_SYSRET64 is used to return from a syscall via SYSRET, but\na Xen PV guest will nevertheless use the IRET hypercall, as there\nis no sysret PV hypercall defined.\n\nSo instead of testing all the prerequisites for doing a sysret and\nthen mangling the stack for Xen PV again for doing an iret just use\nthe iret exit from the beginning.\n\nThis can easily be done via an ALTERNATIVE like it is done for the\nsysenter compat case already.\n\nIt should be noted that this drops the optimization in Xen for not\nrestoring a few registers when returning to user mode, but it seems\nas if the saved instructions in the kernel more than compensate for\nthis drop (a kernel build in a Xen PV guest was slightly faster with\nthis patch applied).\n\nWhile at it remove the stale sysret32 remnants.\n\n [ pawan: Brad Spengler and Salvatore Bonaccorso <carnil@debian.org>\n\t reported a problem with the 5.10 backport commit edc702b4a820\n\t (\"x86/entry_64: Add VERW just before userspace transition\").\n\n\t When CONFIG_PARAVIRT_XXL=y, CLEAR_CPU_BUFFERS is not executed in\n\t syscall_return_via_sysret path as USERGS_SYSRET64 is runtime\n\t patched to:\n\n\t.cpu_usergs_sysret64 = { 0x0f, 0x01, 0xf8,\n\t\t\t\t 0x48, 0x0f, 0x07 }, // swapgs; sysretq\n\n\t which is missing CLEAR_CPU_BUFFERS. It turns out dropping\n\t USERGS_SYSRET64 simplifies the code, allowing CLEAR_CPU_BUFFERS\n\t to be explicitly added to syscall_return_via_sysret path. Below\n\t is with CONFIG_PARAVIRT_XXL=y and this patch applied:\n\n\t syscall_return_via_sysret:\n\t ...\n\t <+342>: swapgs\n\t <+345>: xchg %ax,%ax\n\t <+347>: verw -0x1a2(%rip) <------\n\t <+354>: sysretq\n ]"
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/1424ab4bb386df9cc590c73afa55f13e9b00dea2",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
44
CVE-2022/CVE-2022-487xx/CVE-2022-48772.json
Normal file
44
CVE-2022/CVE-2022-487xx/CVE-2022-48772.json
Normal file
@ -0,0 +1,44 @@
|
||||
{
|
||||
"id": "CVE-2022-48772",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-06-25T15:15:11.233",
|
||||
"lastModified": "2024-06-25T15:15:11.233",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: lgdt3306a: Add a check against null-pointer-def\n\nThe driver should check whether the client provides the platform_data.\n\nThe following log reveals it:\n\n[ 29.610324] BUG: KASAN: null-ptr-deref in kmemdup+0x30/0x40\n[ 29.610730] Read of size 40 at addr 0000000000000000 by task bash/414\n[ 29.612820] Call Trace:\n[ 29.613030] <TASK>\n[ 29.613201] dump_stack_lvl+0x56/0x6f\n[ 29.613496] ? kmemdup+0x30/0x40\n[ 29.613754] print_report.cold+0x494/0x6b7\n[ 29.614082] ? kmemdup+0x30/0x40\n[ 29.614340] kasan_report+0x8a/0x190\n[ 29.614628] ? kmemdup+0x30/0x40\n[ 29.614888] kasan_check_range+0x14d/0x1d0\n[ 29.615213] memcpy+0x20/0x60\n[ 29.615454] kmemdup+0x30/0x40\n[ 29.615700] lgdt3306a_probe+0x52/0x310\n[ 29.616339] i2c_device_probe+0x951/0xa90"
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/526238d32c3acc3d597fd8c9a34652bfe9086cea",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/7d12e918f2994c883f41f22552a61b9310fa1e87",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/8915dcd29a82096acacf54364a8425363782aea0",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/8e1e00718d0d9dd83337300572561e30b9c0d115",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/b479fd59a1f4a342b69fce34f222d93bf791dca4",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/c1115ddbda9c930fba0fdd062e7a8873ebaf898d",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/d082757b8359201c3864323cea4b91ea30a1e676",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
43
CVE-2023/CVE-2023-375xx/CVE-2023-37541.json
Normal file
43
CVE-2023/CVE-2023-375xx/CVE-2023-37541.json
Normal file
@ -0,0 +1,43 @@
|
||||
{
|
||||
"id": "CVE-2023-37541",
|
||||
"sourceIdentifier": "psirt@hcl.com",
|
||||
"published": "2024-06-25T15:15:11.363",
|
||||
"lastModified": "2024-06-25T15:15:11.363",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "HCL Connections contains a broken access control vulnerability that may allow unauthorized user to update data in certain scenarios."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV31": [
|
||||
{
|
||||
"source": "psirt@hcl.com",
|
||||
"type": "Secondary",
|
||||
"cvssData": {
|
||||
"version": "3.1",
|
||||
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N",
|
||||
"attackVector": "NETWORK",
|
||||
"attackComplexity": "LOW",
|
||||
"privilegesRequired": "LOW",
|
||||
"userInteraction": "REQUIRED",
|
||||
"scope": "UNCHANGED",
|
||||
"confidentialityImpact": "NONE",
|
||||
"integrityImpact": "LOW",
|
||||
"availabilityImpact": "NONE",
|
||||
"baseScore": 3.5,
|
||||
"baseSeverity": "LOW"
|
||||
},
|
||||
"exploitabilityScore": 2.1,
|
||||
"impactScore": 1.4
|
||||
}
|
||||
]
|
||||
},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0114156",
|
||||
"source": "psirt@hcl.com"
|
||||
}
|
||||
]
|
||||
}
|
@ -2,7 +2,7 @@
|
||||
"id": "CVE-2023-49115",
|
||||
"sourceIdentifier": "ics-cert@hq.dhs.gov",
|
||||
"published": "2024-02-01T23:15:09.773",
|
||||
"lastModified": "2024-05-17T02:30:59.670",
|
||||
"lastModified": "2024-06-25T14:15:10.687",
|
||||
"vulnStatus": "Modified",
|
||||
"descriptions": [
|
||||
{
|
||||
|
59
CVE-2024/CVE-2024-218xx/CVE-2024-21827.json
Normal file
59
CVE-2024/CVE-2024-218xx/CVE-2024-21827.json
Normal file
@ -0,0 +1,59 @@
|
||||
{
|
||||
"id": "CVE-2024-21827",
|
||||
"sourceIdentifier": "talos-cna@cisco.com",
|
||||
"published": "2024-06-25T14:15:10.940",
|
||||
"lastModified": "2024-06-25T15:15:11.783",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "A leftover debug code vulnerability exists in the cli_server debug functionality of Tp-Link ER7206 Omada Gigabit VPN Router 1.4.1 Build 20240117 Rel.57421. A specially crafted series of network requests can lead to arbitrary command execution. An attacker can send a sequence of requests to trigger this vulnerability."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV31": [
|
||||
{
|
||||
"source": "talos-cna@cisco.com",
|
||||
"type": "Primary",
|
||||
"cvssData": {
|
||||
"version": "3.1",
|
||||
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
|
||||
"attackVector": "NETWORK",
|
||||
"attackComplexity": "LOW",
|
||||
"privilegesRequired": "HIGH",
|
||||
"userInteraction": "NONE",
|
||||
"scope": "UNCHANGED",
|
||||
"confidentialityImpact": "HIGH",
|
||||
"integrityImpact": "HIGH",
|
||||
"availabilityImpact": "HIGH",
|
||||
"baseScore": 7.2,
|
||||
"baseSeverity": "HIGH"
|
||||
},
|
||||
"exploitabilityScore": 1.2,
|
||||
"impactScore": 5.9
|
||||
}
|
||||
]
|
||||
},
|
||||
"weaknesses": [
|
||||
{
|
||||
"source": "talos-cna@cisco.com",
|
||||
"type": "Primary",
|
||||
"description": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "CWE-489"
|
||||
}
|
||||
]
|
||||
}
|
||||
],
|
||||
"references": [
|
||||
{
|
||||
"url": "https://talosintelligence.com/vulnerability_reports/TALOS-2024-1947",
|
||||
"source": "talos-cna@cisco.com"
|
||||
},
|
||||
{
|
||||
"url": "https://www.talosintelligence.com/vulnerability_reports/TALOS-2024-1947",
|
||||
"source": "talos-cna@cisco.com"
|
||||
}
|
||||
]
|
||||
}
|
59
CVE-2024/CVE-2024-321xx/CVE-2024-32111.json
Normal file
59
CVE-2024/CVE-2024-321xx/CVE-2024-32111.json
Normal file
@ -0,0 +1,59 @@
|
||||
{
|
||||
"id": "CVE-2024-32111",
|
||||
"sourceIdentifier": "audit@patchstack.com",
|
||||
"published": "2024-06-25T14:15:11.630",
|
||||
"lastModified": "2024-06-25T14:15:11.630",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Automattic WordPress allows Relative Path Traversal.This issue affects WordPress: from 6.5 through 6.5.4, from 6.4 through 6.4.4, from 6.3 through 6.3.4, from 6.2 through 6.2.5, from 6.1 through 6.1.6, from 6.0 through 6.0.8, from 5.9 through 5.9.9, from 5.8 through 5.8.9, from 5.7 through 5.7.11, from 5.6 through 5.6.13, from 5.5 through 5.5.14, from 5.4 through 5.4.15, from 5.3 through 5.3.17, from 5.2 through 5.2.20, from 5.1 through 5.1.18, from 5.0 through 5.0.21, from 4.9 through 4.9.25, from 4.8 through 4.8.24, from 4.7 through 4.7.28, from 4.6 through 4.6.28, from 4.5 through 4.5.31, from 4.4 through 4.4.32, from 4.3 through 4.3.33, from 4.2 through 4.2.37, from 4.1 through 4.1.40."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV31": [
|
||||
{
|
||||
"source": "audit@patchstack.com",
|
||||
"type": "Secondary",
|
||||
"cvssData": {
|
||||
"version": "3.1",
|
||||
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L",
|
||||
"attackVector": "NETWORK",
|
||||
"attackComplexity": "HIGH",
|
||||
"privilegesRequired": "LOW",
|
||||
"userInteraction": "NONE",
|
||||
"scope": "UNCHANGED",
|
||||
"confidentialityImpact": "LOW",
|
||||
"integrityImpact": "LOW",
|
||||
"availabilityImpact": "LOW",
|
||||
"baseScore": 5.0,
|
||||
"baseSeverity": "MEDIUM"
|
||||
},
|
||||
"exploitabilityScore": 1.6,
|
||||
"impactScore": 3.4
|
||||
}
|
||||
]
|
||||
},
|
||||
"weaknesses": [
|
||||
{
|
||||
"source": "audit@patchstack.com",
|
||||
"type": "Primary",
|
||||
"description": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "CWE-22"
|
||||
}
|
||||
]
|
||||
}
|
||||
],
|
||||
"references": [
|
||||
{
|
||||
"url": "https://patchstack.com/database/vulnerability/wordpress/wordpress-core-6-5-5-contributor-arbitrary-html-file-read-windows-only-vulnerability?_s_id=cve",
|
||||
"source": "audit@patchstack.com"
|
||||
},
|
||||
{
|
||||
"url": "https://wordpress.org/news/2024/06/wordpress-6-5-5/",
|
||||
"source": "audit@patchstack.com"
|
||||
}
|
||||
]
|
||||
}
|
32
CVE-2024/CVE-2024-370xx/CVE-2024-37078.json
Normal file
32
CVE-2024/CVE-2024-370xx/CVE-2024-37078.json
Normal file
@ -0,0 +1,32 @@
|
||||
{
|
||||
"id": "CVE-2024-37078",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-06-25T15:15:12.287",
|
||||
"lastModified": "2024-06-25T15:15:12.287",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnilfs2: fix potential kernel bug due to lack of writeback flag waiting\n\nDestructive writes to a block device on which nilfs2 is mounted can cause\na kernel bug in the folio/page writeback start routine or writeback end\nroutine (__folio_start_writeback in the log below):\n\n kernel BUG at mm/page-writeback.c:3070!\n Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI\n ...\n RIP: 0010:__folio_start_writeback+0xbaa/0x10e0\n Code: 25 ff 0f 00 00 0f 84 18 01 00 00 e8 40 ca c6 ff e9 17 f6 ff ff\n e8 36 ca c6 ff 4c 89 f7 48 c7 c6 80 c0 12 84 e8 e7 b3 0f 00 90 <0f>\n 0b e8 1f ca c6 ff 4c 89 f7 48 c7 c6 a0 c6 12 84 e8 d0 b3 0f 00\n ...\n Call Trace:\n <TASK>\n nilfs_segctor_do_construct+0x4654/0x69d0 [nilfs2]\n nilfs_segctor_construct+0x181/0x6b0 [nilfs2]\n nilfs_segctor_thread+0x548/0x11c0 [nilfs2]\n kthread+0x2f0/0x390\n ret_from_fork+0x4b/0x80\n ret_from_fork_asm+0x1a/0x30\n </TASK>\n\nThis is because when the log writer starts a writeback for segment summary\nblocks or a super root block that use the backing device's page cache, it\ndoes not wait for the ongoing folio/page writeback, resulting in an\ninconsistent writeback state.\n\nFix this issue by waiting for ongoing writebacks when putting\nfolios/pages on the backing device into writeback state."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/1f3bff69f1214fe03a02bc650d5bbfaa6e65ae7d",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/271dcd977ccda8c7a26e360425ae7b4db7d2ecc0",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/614d397be0cf43412b3f94a0f6460eddced8ce92",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/a4ca369ca221bb7e06c725792ac107f0e48e82e7",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
43
CVE-2024/CVE-2024-370xx/CVE-2024-37085.json
Normal file
43
CVE-2024/CVE-2024-370xx/CVE-2024-37085.json
Normal file
@ -0,0 +1,43 @@
|
||||
{
|
||||
"id": "CVE-2024-37085",
|
||||
"sourceIdentifier": "security@vmware.com",
|
||||
"published": "2024-06-25T15:15:12.377",
|
||||
"lastModified": "2024-06-25T15:15:12.377",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "VMware ESXi contains an authentication bypass vulnerability.\u00a0A malicious actor with sufficient Active Directory (AD) permissions can gain full access to an ESXi host that was previously configured to use AD for user management https://blogs.vmware.com/vsphere/2012/09/joining-vsphere-hosts-to-active-directory.html by re-creating the configured AD group ('ESXi Admins' by default) after it was deleted from AD."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV31": [
|
||||
{
|
||||
"source": "security@vmware.com",
|
||||
"type": "Secondary",
|
||||
"cvssData": {
|
||||
"version": "3.1",
|
||||
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H",
|
||||
"attackVector": "NETWORK",
|
||||
"attackComplexity": "LOW",
|
||||
"privilegesRequired": "HIGH",
|
||||
"userInteraction": "REQUIRED",
|
||||
"scope": "UNCHANGED",
|
||||
"confidentialityImpact": "HIGH",
|
||||
"integrityImpact": "HIGH",
|
||||
"availabilityImpact": "HIGH",
|
||||
"baseScore": 6.8,
|
||||
"baseSeverity": "MEDIUM"
|
||||
},
|
||||
"exploitabilityScore": 0.9,
|
||||
"impactScore": 5.9
|
||||
}
|
||||
]
|
||||
},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/24505",
|
||||
"source": "security@vmware.com"
|
||||
}
|
||||
]
|
||||
}
|
43
CVE-2024/CVE-2024-370xx/CVE-2024-37086.json
Normal file
43
CVE-2024/CVE-2024-370xx/CVE-2024-37086.json
Normal file
@ -0,0 +1,43 @@
|
||||
{
|
||||
"id": "CVE-2024-37086",
|
||||
"sourceIdentifier": "security@vmware.com",
|
||||
"published": "2024-06-25T15:15:12.570",
|
||||
"lastModified": "2024-06-25T15:15:12.570",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "VMware ESXi contains an out-of-bounds read vulnerability.\u00a0A\n malicious actor with local administrative privileges on a virtual \nmachine with an existing snapshot may trigger an out-of-bounds read \nleading to a denial-of-service condition of the host."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV31": [
|
||||
{
|
||||
"source": "security@vmware.com",
|
||||
"type": "Secondary",
|
||||
"cvssData": {
|
||||
"version": "3.1",
|
||||
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H",
|
||||
"attackVector": "LOCAL",
|
||||
"attackComplexity": "LOW",
|
||||
"privilegesRequired": "NONE",
|
||||
"userInteraction": "NONE",
|
||||
"scope": "UNCHANGED",
|
||||
"confidentialityImpact": "NONE",
|
||||
"integrityImpact": "LOW",
|
||||
"availabilityImpact": "HIGH",
|
||||
"baseScore": 6.8,
|
||||
"baseSeverity": "MEDIUM"
|
||||
},
|
||||
"exploitabilityScore": 2.5,
|
||||
"impactScore": 4.2
|
||||
}
|
||||
]
|
||||
},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/24505",
|
||||
"source": "security@vmware.com"
|
||||
}
|
||||
]
|
||||
}
|
43
CVE-2024/CVE-2024-370xx/CVE-2024-37087.json
Normal file
43
CVE-2024/CVE-2024-370xx/CVE-2024-37087.json
Normal file
@ -0,0 +1,43 @@
|
||||
{
|
||||
"id": "CVE-2024-37087",
|
||||
"sourceIdentifier": "security@vmware.com",
|
||||
"published": "2024-06-25T15:15:12.767",
|
||||
"lastModified": "2024-06-25T15:15:12.767",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "The vCenter Server contains a denial-of-service vulnerability.\u00a0A malicious actor with network access to vCenter Server may create a denial-of-service condition."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV31": [
|
||||
{
|
||||
"source": "security@vmware.com",
|
||||
"type": "Secondary",
|
||||
"cvssData": {
|
||||
"version": "3.1",
|
||||
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
|
||||
"attackVector": "NETWORK",
|
||||
"attackComplexity": "LOW",
|
||||
"privilegesRequired": "NONE",
|
||||
"userInteraction": "NONE",
|
||||
"scope": "UNCHANGED",
|
||||
"confidentialityImpact": "NONE",
|
||||
"integrityImpact": "NONE",
|
||||
"availabilityImpact": "LOW",
|
||||
"baseScore": 5.3,
|
||||
"baseSeverity": "MEDIUM"
|
||||
},
|
||||
"exploitabilityScore": 3.9,
|
||||
"impactScore": 1.4
|
||||
}
|
||||
]
|
||||
},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/24505",
|
||||
"source": "security@vmware.com"
|
||||
}
|
||||
]
|
||||
}
|
32
CVE-2024/CVE-2024-373xx/CVE-2024-37354.json
Normal file
32
CVE-2024/CVE-2024-373xx/CVE-2024-37354.json
Normal file
@ -0,0 +1,32 @@
|
||||
{
|
||||
"id": "CVE-2024-37354",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-06-25T15:15:13.177",
|
||||
"lastModified": "2024-06-25T15:15:13.177",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: fix crash on racing fsync and size-extending write into prealloc\n\nWe have been seeing crashes on duplicate keys in\nbtrfs_set_item_key_safe():\n\n BTRFS critical (device vdb): slot 4 key (450 108 8192) new key (450 108 8192)\n ------------[ cut here ]------------\n kernel BUG at fs/btrfs/ctree.c:2620!\n invalid opcode: 0000 [#1] PREEMPT SMP PTI\n CPU: 0 PID: 3139 Comm: xfs_io Kdump: loaded Not tainted 6.9.0 #6\n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-2.fc40 04/01/2014\n RIP: 0010:btrfs_set_item_key_safe+0x11f/0x290 [btrfs]\n\nWith the following stack trace:\n\n #0 btrfs_set_item_key_safe (fs/btrfs/ctree.c:2620:4)\n #1 btrfs_drop_extents (fs/btrfs/file.c:411:4)\n #2 log_one_extent (fs/btrfs/tree-log.c:4732:9)\n #3 btrfs_log_changed_extents (fs/btrfs/tree-log.c:4955:9)\n #4 btrfs_log_inode (fs/btrfs/tree-log.c:6626:9)\n #5 btrfs_log_inode_parent (fs/btrfs/tree-log.c:7070:8)\n #6 btrfs_log_dentry_safe (fs/btrfs/tree-log.c:7171:8)\n #7 btrfs_sync_file (fs/btrfs/file.c:1933:8)\n #8 vfs_fsync_range (fs/sync.c:188:9)\n #9 vfs_fsync (fs/sync.c:202:9)\n #10 do_fsync (fs/sync.c:212:9)\n #11 __do_sys_fdatasync (fs/sync.c:225:9)\n #12 __se_sys_fdatasync (fs/sync.c:223:1)\n #13 __x64_sys_fdatasync (fs/sync.c:223:1)\n #14 do_syscall_x64 (arch/x86/entry/common.c:52:14)\n #15 do_syscall_64 (arch/x86/entry/common.c:83:7)\n #16 entry_SYSCALL_64+0xaf/0x14c (arch/x86/entry/entry_64.S:121)\n\nSo we're logging a changed extent from fsync, which is splitting an\nextent in the log tree. But this split part already exists in the tree,\ntriggering the BUG().\n\nThis is the state of the log tree at the time of the crash, dumped with\ndrgn (https://github.com/osandov/drgn/blob/main/contrib/btrfs_tree.py)\nto get more details than btrfs_print_leaf() gives us:\n\n >>> print_extent_buffer(prog.crashed_thread().stack_trace()[0][\"eb\"])\n leaf 33439744 level 0 items 72 generation 9 owner 18446744073709551610\n leaf 33439744 flags 0x100000000000000\n fs uuid e5bd3946-400c-4223-8923-190ef1f18677\n chunk uuid d58cb17e-6d02-494a-829a-18b7d8a399da\n item 0 key (450 INODE_ITEM 0) itemoff 16123 itemsize 160\n generation 7 transid 9 size 8192 nbytes 8473563889606862198\n block group 0 mode 100600 links 1 uid 0 gid 0 rdev 0\n sequence 204 flags 0x10(PREALLOC)\n atime 1716417703.220000000 (2024-05-22 15:41:43)\n ctime 1716417704.983333333 (2024-05-22 15:41:44)\n mtime 1716417704.983333333 (2024-05-22 15:41:44)\n otime 17592186044416.000000000 (559444-03-08 01:40:16)\n item 1 key (450 INODE_REF 256) itemoff 16110 itemsize 13\n index 195 namelen 3 name: 193\n item 2 key (450 XATTR_ITEM 1640047104) itemoff 16073 itemsize 37\n location key (0 UNKNOWN.0 0) type XATTR\n transid 7 data_len 1 name_len 6\n name: user.a\n data a\n item 3 key (450 EXTENT_DATA 0) itemoff 16020 itemsize 53\n generation 9 type 1 (regular)\n extent data disk byte 303144960 nr 12288\n extent data offset 0 nr 4096 ram 12288\n extent compression 0 (none)\n item 4 key (450 EXTENT_DATA 4096) itemoff 15967 itemsize 53\n generation 9 type 2 (prealloc)\n prealloc data disk byte 303144960 nr 12288\n prealloc data offset 4096 nr 8192\n item 5 key (450 EXTENT_DATA 8192) itemoff 15914 itemsize 53\n generation 9 type 2 (prealloc)\n prealloc data disk byte 303144960 nr 12288\n prealloc data offset 8192 nr 4096\n ...\n\nSo the real problem happened earlier: notice that items 4 (4k-12k) and 5\n(8k-12k) overlap. Both are prealloc extents. Item 4 straddles i_size and\nitem 5 starts at i_size.\n\nHere is the state of \n---truncated---"
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/1ff2bd566fbcefcb892be85c493bdb92b911c428",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/3d08c52ba1887a1ff9c179d4b6a18b427bcb2097",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/9d274c19a71b3a276949933859610721a453946b",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/f4e5ed974876c14d3623e04dc43d3e3281bc6011",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
24
CVE-2024/CVE-2024-383xx/CVE-2024-38306.json
Normal file
24
CVE-2024/CVE-2024-383xx/CVE-2024-38306.json
Normal file
@ -0,0 +1,24 @@
|
||||
{
|
||||
"id": "CVE-2024-38306",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-06-25T15:15:13.367",
|
||||
"lastModified": "2024-06-25T15:15:13.367",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: protect folio::private when attaching extent buffer folios\n\n[BUG]\nSince v6.8 there are rare kernel crashes reported by various people,\nthe common factor is bad page status error messages like this:\n\n BUG: Bad page state in process kswapd0 pfn:d6e840\n page: refcount:0 mapcount:0 mapping:000000007512f4f2 index:0x2796c2c7c\n pfn:0xd6e840\n aops:btree_aops ino:1\n flags: 0x17ffffe0000008(uptodate|node=0|zone=2|lastcpupid=0x3fffff)\n page_type: 0xffffffff()\n raw: 0017ffffe0000008 dead000000000100 dead000000000122 ffff88826d0be4c0\n raw: 00000002796c2c7c 0000000000000000 00000000ffffffff 0000000000000000\n page dumped because: non-NULL mapping\n\n[CAUSE]\nCommit 09e6cef19c9f (\"btrfs: refactor alloc_extent_buffer() to\nallocate-then-attach method\") changes the sequence when allocating a new\nextent buffer.\n\nPreviously we always called grab_extent_buffer() under\nmapping->i_private_lock, to ensure the safety on modification on\nfolio::private (which is a pointer to extent buffer for regular\nsectorsize).\n\nThis can lead to the following race:\n\nThread A is trying to allocate an extent buffer at bytenr X, with 4\n4K pages, meanwhile thread B is trying to release the page at X + 4K\n(the second page of the extent buffer at X).\n\n Thread A | Thread B\n-----------------------------------+-------------------------------------\n | btree_release_folio()\n\t\t\t\t | | This is for the page at X + 4K,\n\t\t\t\t | | Not page X.\n\t\t\t\t | |\nalloc_extent_buffer() | |- release_extent_buffer()\n|- filemap_add_folio() for the | | |- atomic_dec_and_test(eb->refs)\n| page at bytenr X (the first | | |\n| page). | | |\n| Which returned -EEXIST. | | |\n| | | |\n|- filemap_lock_folio() | | |\n| Returned the first page locked. | | |\n| | | |\n|- grab_extent_buffer() | | |\n| |- atomic_inc_not_zero() | | |\n| | Returned false | | |\n| |- folio_detach_private() | | |- folio_detach_private() for X\n| |- folio_test_private() | | |- folio_test_private()\n | Returned true | | | Returned true\n |- folio_put() | |- folio_put()\n\nNow there are two puts on the same folio at folio X, leading to refcount\nunderflow of the folio X, and eventually causing the BUG_ON() on the\npage->mapping.\n\nThe condition is not that easy to hit:\n\n- The release must be triggered for the middle page of an eb\n If the release is on the same first page of an eb, page lock would kick\n in and prevent the race.\n\n- folio_detach_private() has a very small race window\n It's only between folio_test_private() and folio_clear_private().\n\nThat's exactly when mapping->i_private_lock is used to prevent such race,\nand commit 09e6cef19c9f (\"btrfs: refactor alloc_extent_buffer() to\nallocate-then-attach method\") screwed that up.\n\nAt that time, I thought the page lock would kick in as\nfilemap_release_folio() also requires the page to be locked, but forgot\nthe filemap_release_folio() only locks one page, not all pages of an\nextent buffer.\n\n[FIX]\nMove all the code requiring i_private_lock into\nattach_eb_folio_to_filemap(), so that everything is done with proper\nlock protection.\n\nFurthermore to prevent future problems, add an extra\nlockdep_assert_locked() to ensure we're holding the proper lock.\n\nTo reproducer that is able to hit the race (takes a few minutes with\ninstrumented code inserting delays to alloc_extent_buffer()):\n\n #!/bin/sh\n drop_caches () {\n\t while(true); do\n\t\t echo 3 > /proc/sys/vm/drop_caches\n\t\t echo 1 > /proc/sys/vm/compact_memory\n\t done\n }\n\n run_tar () {\n\t while(true); do\n\t\t for x in `seq 1 80` ; do\n\t\t\t tar cf /dev/zero /mnt > /dev/null &\n\t\t done\n\t\t wait\n\t done\n }\n\n mkfs.btrfs -f -d single -m single\n---truncated---"
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/952f048eb901881a7cc6f7c1368b53cd386ead7b",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/f3a5367c679d31473d3fbb391675055b4792c309",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
28
CVE-2024/CVE-2024-383xx/CVE-2024-38385.json
Normal file
28
CVE-2024/CVE-2024-383xx/CVE-2024-38385.json
Normal file
@ -0,0 +1,28 @@
|
||||
{
|
||||
"id": "CVE-2024-38385",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-06-25T15:15:13.487",
|
||||
"lastModified": "2024-06-25T15:15:13.487",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ngenirq/irqdesc: Prevent use-after-free in irq_find_at_or_after()\n\nirq_find_at_or_after() dereferences the interrupt descriptor which is\nreturned by mt_find() while neither holding sparse_irq_lock nor RCU read\nlock, which means the descriptor can be freed between mt_find() and the\ndereference:\n\n CPU0 CPU1\n desc = mt_find()\n delayed_free_desc(desc)\n irq_desc_get_irq(desc)\n\nThe use-after-free is reported by KASAN:\n\n Call trace:\n irq_get_next_irq+0x58/0x84\n show_stat+0x638/0x824\n seq_read_iter+0x158/0x4ec\n proc_reg_read_iter+0x94/0x12c\n vfs_read+0x1e0/0x2c8\n\n Freed by task 4471:\n slab_free_freelist_hook+0x174/0x1e0\n __kmem_cache_free+0xa4/0x1dc\n kfree+0x64/0x128\n irq_kobj_release+0x28/0x3c\n kobject_put+0xcc/0x1e0\n delayed_free_desc+0x14/0x2c\n rcu_do_batch+0x214/0x720\n\nGuard the access with a RCU read lock section."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/1c7891812d85500ae2ca4051fa5683fcf29930d8",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/b84a8aba806261d2f759ccedf4a2a6a80a5e55ba",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/d084aa022f84319f8079e30882cbcbc026af9f21",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
48
CVE-2024/CVE-2024-386xx/CVE-2024-38661.json
Normal file
48
CVE-2024/CVE-2024-386xx/CVE-2024-38661.json
Normal file
@ -0,0 +1,48 @@
|
||||
{
|
||||
"id": "CVE-2024-38661",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-06-25T15:15:13.630",
|
||||
"lastModified": "2024-06-25T15:15:13.630",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ns390/ap: Fix crash in AP internal function modify_bitmap()\n\nA system crash like this\n\n Failing address: 200000cb7df6f000 TEID: 200000cb7df6f403\n Fault in home space mode while using kernel ASCE.\n AS:00000002d71bc007 R3:00000003fe5b8007 S:000000011a446000 P:000000015660c13d\n Oops: 0038 ilc:3 [#1] PREEMPT SMP\n Modules linked in: mlx5_ib ...\n CPU: 8 PID: 7556 Comm: bash Not tainted 6.9.0-rc7 #8\n Hardware name: IBM 3931 A01 704 (LPAR)\n Krnl PSW : 0704e00180000000 0000014b75e7b606 (ap_parse_bitmap_str+0x10e/0x1f8)\n R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3\n Krnl GPRS: 0000000000000001 ffffffffffffffc0 0000000000000001 00000048f96b75d3\n 000000cb00000100 ffffffffffffffff ffffffffffffffff 000000cb7df6fce0\n 000000cb7df6fce0 00000000ffffffff 000000000000002b 00000048ffffffff\n 000003ff9b2dbc80 200000cb7df6fcd8 0000014bffffffc0 000000cb7df6fbc8\n Krnl Code: 0000014b75e7b5fc: a7840047 brc 8,0000014b75e7b68a\n 0000014b75e7b600: 18b2 lr %r11,%r2\n #0000014b75e7b602: a7f4000a brc 15,0000014b75e7b616\n >0000014b75e7b606: eb22d00000e6 laog %r2,%r2,0(%r13)\n 0000014b75e7b60c: a7680001 lhi %r6,1\n 0000014b75e7b610: 187b lr %r7,%r11\n 0000014b75e7b612: 84960021 brxh %r9,%r6,0000014b75e7b654\n 0000014b75e7b616: 18e9 lr %r14,%r9\n Call Trace:\n [<0000014b75e7b606>] ap_parse_bitmap_str+0x10e/0x1f8\n ([<0000014b75e7b5dc>] ap_parse_bitmap_str+0xe4/0x1f8)\n [<0000014b75e7b758>] apmask_store+0x68/0x140\n [<0000014b75679196>] kernfs_fop_write_iter+0x14e/0x1e8\n [<0000014b75598524>] vfs_write+0x1b4/0x448\n [<0000014b7559894c>] ksys_write+0x74/0x100\n [<0000014b7618a440>] __do_syscall+0x268/0x328\n [<0000014b761a3558>] system_call+0x70/0x98\n INFO: lockdep is turned off.\n Last Breaking-Event-Address:\n [<0000014b75e7b636>] ap_parse_bitmap_str+0x13e/0x1f8\n Kernel panic - not syncing: Fatal exception: panic_on_oops\n\noccured when /sys/bus/ap/a[pq]mask was updated with a relative mask value\n(like +0x10-0x12,+60,-90) with one of the numeric values exceeding INT_MAX.\n\nThe fix is simple: use unsigned long values for the internal variables. The\ncorrect checks are already in place in the function but a simple int for\nthe internal variables was used with the possibility to overflow."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/2062e3f1f2374102f8014d7ca286b9aa527bd558",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/4c0bfb4e867c1ec6616a5049bd3618021e127056",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/67011123453b91ec03671d40712fa213e94a01b9",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/7360cef95aa1ea2b5efb7b5e2ed32e941664e1f0",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/7c72af16abf2ec7520407098360bbba312289e05",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/7dabe54a016defe11bb2a278cd9f1ff6db3feba6",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/8c5f5911c1b13170d3404eb992c6a0deaa8d81ad",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/d4f9d5a99a3fd1b1c691b7a1a6f8f3f25f4116c9",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
20
CVE-2024/CVE-2024-389xx/CVE-2024-38951.json
Normal file
20
CVE-2024/CVE-2024-389xx/CVE-2024-38951.json
Normal file
@ -0,0 +1,20 @@
|
||||
{
|
||||
"id": "CVE-2024-38951",
|
||||
"sourceIdentifier": "cve@mitre.org",
|
||||
"published": "2024-06-25T14:15:12.403",
|
||||
"lastModified": "2024-06-25T14:15:12.403",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "A buffer overflow in PX4-Autopilot v1.12.3 allows attackers to cause a Denial of Service (DoS) via a crafted MavLink message."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://github.com/PX4/PX4-Autopilot/issues/23251",
|
||||
"source": "cve@mitre.org"
|
||||
}
|
||||
]
|
||||
}
|
28
CVE-2024/CVE-2024-389xx/CVE-2024-38952.json
Normal file
28
CVE-2024/CVE-2024-389xx/CVE-2024-38952.json
Normal file
@ -0,0 +1,28 @@
|
||||
{
|
||||
"id": "CVE-2024-38952",
|
||||
"sourceIdentifier": "cve@mitre.org",
|
||||
"published": "2024-06-25T14:15:12.517",
|
||||
"lastModified": "2024-06-25T14:15:12.517",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "PX4-Autopilot v1.14.3 was discovered to contain a buffer overflow via the topic_name parameter at /logger/logged_topics.cpp."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/logger/logged_topics.cpp#L440",
|
||||
"source": "cve@mitre.org"
|
||||
},
|
||||
{
|
||||
"url": "https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/logger/logged_topics.cpp#L561",
|
||||
"source": "cve@mitre.org"
|
||||
},
|
||||
{
|
||||
"url": "https://github.com/PX4/PX4-Autopilot/issues/23258",
|
||||
"source": "cve@mitre.org"
|
||||
}
|
||||
]
|
||||
}
|
48
CVE-2024/CVE-2024-392xx/CVE-2024-39276.json
Normal file
48
CVE-2024/CVE-2024-392xx/CVE-2024-39276.json
Normal file
@ -0,0 +1,48 @@
|
||||
{
|
||||
"id": "CVE-2024-39276",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-06-25T15:15:13.903",
|
||||
"lastModified": "2024-06-25T15:15:13.903",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\next4: fix mb_cache_entry's e_refcnt leak in ext4_xattr_block_cache_find()\n\nSyzbot reports a warning as follows:\n\n============================================\nWARNING: CPU: 0 PID: 5075 at fs/mbcache.c:419 mb_cache_destroy+0x224/0x290\nModules linked in:\nCPU: 0 PID: 5075 Comm: syz-executor199 Not tainted 6.9.0-rc6-gb947cc5bf6d7\nRIP: 0010:mb_cache_destroy+0x224/0x290 fs/mbcache.c:419\nCall Trace:\n <TASK>\n ext4_put_super+0x6d4/0xcd0 fs/ext4/super.c:1375\n generic_shutdown_super+0x136/0x2d0 fs/super.c:641\n kill_block_super+0x44/0x90 fs/super.c:1675\n ext4_kill_sb+0x68/0xa0 fs/ext4/super.c:7327\n[...]\n============================================\n\nThis is because when finding an entry in ext4_xattr_block_cache_find(), if\next4_sb_bread() returns -ENOMEM, the ce's e_refcnt, which has already grown\nin the __entry_find(), won't be put away, and eventually trigger the above\nissue in mb_cache_destroy() due to reference count leakage.\n\nSo call mb_cache_entry_put() on the -ENOMEM error branch as a quick fix."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/0c0b4a49d3e7f49690a6827a41faeffad5df7e21",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/681ff9a09accd8a4379f8bd30b7a1641ee19bb3e",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/76dc776153a47372719d664e0fc50d6355791abb",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/896a7e7d0d555ad8b2b46af0c2fa7de7467f9483",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/9ad75e78747b5a50dc5a52f0f8e92e920a653f16",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/a95df6f04f2c37291adf26a74205cde0314d4577",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/b37c0edef4e66fb21a2fbc211471195a383e5ab8",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/e941b712e758f615d311946bf98216e79145ccd9",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
24
CVE-2024/CVE-2024-392xx/CVE-2024-39293.json
Normal file
24
CVE-2024/CVE-2024-392xx/CVE-2024-39293.json
Normal file
@ -0,0 +1,24 @@
|
||||
{
|
||||
"id": "CVE-2024-39293",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-06-25T15:15:13.993",
|
||||
"lastModified": "2024-06-25T15:15:13.993",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nRevert \"xsk: Support redirect to any socket bound to the same umem\"\n\nThis reverts commit 2863d665ea41282379f108e4da6c8a2366ba66db.\n\nThis patch introduced a potential kernel crash when multiple napi instances\nredirect to the same AF_XDP socket. By removing the queue_index check, it is\npossible for multiple napi instances to access the Rx ring at the same time,\nwhich will result in a corrupted ring state which can lead to a crash when\nflushing the rings in __xsk_flush(). This can happen when the linked list of\nsockets to flush gets corrupted by concurrent accesses. A quick and small fix\nis not possible, so let us revert this for now."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/19cb40b1064566ea09538289bfcf5bc7ecb9b6f5",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/7fcf26b315bbb728036da0862de6b335da83dff2",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
28
CVE-2024/CVE-2024-392xx/CVE-2024-39296.json
Normal file
28
CVE-2024/CVE-2024-392xx/CVE-2024-39296.json
Normal file
@ -0,0 +1,28 @@
|
||||
{
|
||||
"id": "CVE-2024-39296",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-06-25T15:15:14.070",
|
||||
"lastModified": "2024-06-25T15:15:14.070",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbonding: fix oops during rmmod\n\n\"rmmod bonding\" causes an oops ever since commit cc317ea3d927 (\"bonding:\nremove redundant NULL check in debugfs function\"). Here are the relevant\nfunctions being called:\n\nbonding_exit()\n bond_destroy_debugfs()\n debugfs_remove_recursive(bonding_debug_root);\n bonding_debug_root = NULL; <--------- SET TO NULL HERE\n bond_netlink_fini()\n rtnl_link_unregister()\n __rtnl_link_unregister()\n unregister_netdevice_many_notify()\n bond_uninit()\n bond_debug_unregister()\n (commit removed check for bonding_debug_root == NULL)\n debugfs_remove()\n simple_recursive_removal()\n down_write() -> OOPS\n\nHowever, reverting the bad commit does not solve the problem completely\nbecause the original code contains a race that could cause the same\noops, although it was much less likely to be triggered unintentionally:\n\nCPU1\n rmmod bonding\n bonding_exit()\n bond_destroy_debugfs()\n debugfs_remove_recursive(bonding_debug_root);\n\nCPU2\n echo -bond0 > /sys/class/net/bonding_masters\n bond_uninit()\n bond_debug_unregister()\n if (!bonding_debug_root)\n\nCPU1\n bonding_debug_root = NULL;\n\nSo do NOT revert the bad commit (since the removed checks were racy\nanyway), and instead change the order of actions taken during module\nremoval. The same oops can also happen if there is an error during\nmodule init, so apply the same fix there."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/a45835a0bb6ef7d5ddbc0714dd760de979cb6ece",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/cf48aee81103ca06d09d73d33fb72f1191069aa6",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/f07224c16678a8af54ddc059b3d2d51885d7f35e",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
32
CVE-2024/CVE-2024-392xx/CVE-2024-39298.json
Normal file
32
CVE-2024/CVE-2024-392xx/CVE-2024-39298.json
Normal file
@ -0,0 +1,32 @@
|
||||
{
|
||||
"id": "CVE-2024-39298",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-06-25T15:15:14.160",
|
||||
"lastModified": "2024-06-25T15:15:14.160",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/memory-failure: fix handling of dissolved but not taken off from buddy pages\n\nWhen I did memory failure tests recently, below panic occurs:\n\npage: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x8cee00\nflags: 0x6fffe0000000000(node=1|zone=2|lastcpupid=0x7fff)\nraw: 06fffe0000000000 dead000000000100 dead000000000122 0000000000000000\nraw: 0000000000000000 0000000000000009 00000000ffffffff 0000000000000000\npage dumped because: VM_BUG_ON_PAGE(!PageBuddy(page))\n------------[ cut here ]------------\nkernel BUG at include/linux/page-flags.h:1009!\ninvalid opcode: 0000 [#1] PREEMPT SMP NOPTI\nRIP: 0010:__del_page_from_free_list+0x151/0x180\nRSP: 0018:ffffa49c90437998 EFLAGS: 00000046\nRAX: 0000000000000035 RBX: 0000000000000009 RCX: ffff8dd8dfd1c9c8\nRDX: 0000000000000000 RSI: 0000000000000027 RDI: ffff8dd8dfd1c9c0\nRBP: ffffd901233b8000 R08: ffffffffab5511f8 R09: 0000000000008c69\nR10: 0000000000003c15 R11: ffffffffab5511f8 R12: ffff8dd8fffc0c80\nR13: 0000000000000001 R14: ffff8dd8fffc0c80 R15: 0000000000000009\nFS: 00007ff916304740(0000) GS:ffff8dd8dfd00000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 000055eae50124c8 CR3: 00000008479e0000 CR4: 00000000000006f0\nCall Trace:\n <TASK>\n __rmqueue_pcplist+0x23b/0x520\n get_page_from_freelist+0x26b/0xe40\n __alloc_pages_noprof+0x113/0x1120\n __folio_alloc_noprof+0x11/0xb0\n alloc_buddy_hugetlb_folio.isra.0+0x5a/0x130\n __alloc_fresh_hugetlb_folio+0xe7/0x140\n alloc_pool_huge_folio+0x68/0x100\n set_max_huge_pages+0x13d/0x340\n hugetlb_sysctl_handler_common+0xe8/0x110\n proc_sys_call_handler+0x194/0x280\n vfs_write+0x387/0x550\n ksys_write+0x64/0xe0\n do_syscall_64+0xc2/0x1d0\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0033:0x7ff916114887\nRSP: 002b:00007ffec8a2fd78 EFLAGS: 00000246 ORIG_RAX: 0000000000000001\nRAX: ffffffffffffffda RBX: 000055eae500e350 RCX: 00007ff916114887\nRDX: 0000000000000004 RSI: 000055eae500e390 RDI: 0000000000000003\nRBP: 000055eae50104c0 R08: 0000000000000000 R09: 000055eae50104c0\nR10: 0000000000000077 R11: 0000000000000246 R12: 0000000000000004\nR13: 0000000000000004 R14: 00007ff916216b80 R15: 00007ff916216a00\n </TASK>\nModules linked in: mce_inject hwpoison_inject\n---[ end trace 0000000000000000 ]---\n\nAnd before the panic, there had an warning about bad page state:\n\nBUG: Bad page state in process page-types pfn:8cee00\npage: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x8cee00\nflags: 0x6fffe0000000000(node=1|zone=2|lastcpupid=0x7fff)\npage_type: 0xffffff7f(buddy)\nraw: 06fffe0000000000 ffffd901241c0008 ffffd901240f8008 0000000000000000\nraw: 0000000000000000 0000000000000009 00000000ffffff7f 0000000000000000\npage dumped because: nonzero mapcount\nModules linked in: mce_inject hwpoison_inject\nCPU: 8 PID: 154211 Comm: page-types Not tainted 6.9.0-rc4-00499-g5544ec3178e2-dirty #22\nCall Trace:\n <TASK>\n dump_stack_lvl+0x83/0xa0\n bad_page+0x63/0xf0\n free_unref_page+0x36e/0x5c0\n unpoison_memory+0x50b/0x630\n simple_attr_write_xsigned.constprop.0.isra.0+0xb3/0x110\n debugfs_attr_write+0x42/0x60\n full_proxy_write+0x5b/0x80\n vfs_write+0xcd/0x550\n ksys_write+0x64/0xe0\n do_syscall_64+0xc2/0x1d0\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0033:0x7f189a514887\nRSP: 002b:00007ffdcd899718 EFLAGS: 00000246 ORIG_RAX: 0000000000000001\nRAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f189a514887\nRDX: 0000000000000009 RSI: 00007ffdcd899730 RDI: 0000000000000003\nRBP: 00007ffdcd8997a0 R08: 0000000000000000 R09: 00007ffdcd8994b2\nR10: 0000000000000000 R11: 0000000000000246 R12: 00007ffdcda199a8\nR13: 0000000000404af1 R14: 000000000040ad78 R15: 00007f189a7a5040\n </TASK>\n\nThe root cause should be the below race:\n\n memory_failure\n try_memory_failure_hugetlb\n me_huge_page\n __page_handle_poison\n dissolve_free_hugetlb_folio\n drain_all_pages -- Buddy page can be isolated e.g. for compaction.\n take_page_off_buddy -- Failed as page is not in the \n---truncated---"
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/00b0752c7f15dfdf129cacc6a27d61c54141182b",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/41cd2de3c95020b7f86a3cb5fab42fbf454a63bd",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/8cf360b9d6a840700e06864236a01a883b34bbad",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/bb9bb13ce64cc7cae47f5e2ab9ce93b7bfa0117e",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
48
CVE-2024/CVE-2024-393xx/CVE-2024-39301.json
Normal file
48
CVE-2024/CVE-2024-393xx/CVE-2024-39301.json
Normal file
@ -0,0 +1,48 @@
|
||||
{
|
||||
"id": "CVE-2024-39301",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-06-25T15:15:14.240",
|
||||
"lastModified": "2024-06-25T15:15:14.240",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/9p: fix uninit-value in p9_client_rpc()\n\nSyzbot with the help of KMSAN reported the following error:\n\nBUG: KMSAN: uninit-value in trace_9p_client_res include/trace/events/9p.h:146 [inline]\nBUG: KMSAN: uninit-value in p9_client_rpc+0x1314/0x1340 net/9p/client.c:754\n trace_9p_client_res include/trace/events/9p.h:146 [inline]\n p9_client_rpc+0x1314/0x1340 net/9p/client.c:754\n p9_client_create+0x1551/0x1ff0 net/9p/client.c:1031\n v9fs_session_init+0x1b9/0x28e0 fs/9p/v9fs.c:410\n v9fs_mount+0xe2/0x12b0 fs/9p/vfs_super.c:122\n legacy_get_tree+0x114/0x290 fs/fs_context.c:662\n vfs_get_tree+0xa7/0x570 fs/super.c:1797\n do_new_mount+0x71f/0x15e0 fs/namespace.c:3352\n path_mount+0x742/0x1f20 fs/namespace.c:3679\n do_mount fs/namespace.c:3692 [inline]\n __do_sys_mount fs/namespace.c:3898 [inline]\n __se_sys_mount+0x725/0x810 fs/namespace.c:3875\n __x64_sys_mount+0xe4/0x150 fs/namespace.c:3875\n do_syscall_64+0xd5/0x1f0\n entry_SYSCALL_64_after_hwframe+0x6d/0x75\n\nUninit was created at:\n __alloc_pages+0x9d6/0xe70 mm/page_alloc.c:4598\n __alloc_pages_node include/linux/gfp.h:238 [inline]\n alloc_pages_node include/linux/gfp.h:261 [inline]\n alloc_slab_page mm/slub.c:2175 [inline]\n allocate_slab mm/slub.c:2338 [inline]\n new_slab+0x2de/0x1400 mm/slub.c:2391\n ___slab_alloc+0x1184/0x33d0 mm/slub.c:3525\n __slab_alloc mm/slub.c:3610 [inline]\n __slab_alloc_node mm/slub.c:3663 [inline]\n slab_alloc_node mm/slub.c:3835 [inline]\n kmem_cache_alloc+0x6d3/0xbe0 mm/slub.c:3852\n p9_tag_alloc net/9p/client.c:278 [inline]\n p9_client_prepare_req+0x20a/0x1770 net/9p/client.c:641\n p9_client_rpc+0x27e/0x1340 net/9p/client.c:688\n p9_client_create+0x1551/0x1ff0 net/9p/client.c:1031\n v9fs_session_init+0x1b9/0x28e0 fs/9p/v9fs.c:410\n v9fs_mount+0xe2/0x12b0 fs/9p/vfs_super.c:122\n legacy_get_tree+0x114/0x290 fs/fs_context.c:662\n vfs_get_tree+0xa7/0x570 fs/super.c:1797\n do_new_mount+0x71f/0x15e0 fs/namespace.c:3352\n path_mount+0x742/0x1f20 fs/namespace.c:3679\n do_mount fs/namespace.c:3692 [inline]\n __do_sys_mount fs/namespace.c:3898 [inline]\n __se_sys_mount+0x725/0x810 fs/namespace.c:3875\n __x64_sys_mount+0xe4/0x150 fs/namespace.c:3875\n do_syscall_64+0xd5/0x1f0\n entry_SYSCALL_64_after_hwframe+0x6d/0x75\n\nIf p9_check_errors() fails early in p9_client_rpc(), req->rc.tag\nwill not be properly initialized. However, trace_9p_client_res()\nends up trying to print it out anyway before p9_client_rpc()\nfinishes.\n\nFix this issue by assigning default values to p9_fcall fields\nsuch as 'tag' and (just in case KMSAN unearths something new) 'id'\nduring the tag allocation stage."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/124947855564572713d705a13be7d0c9dae16a17",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/2101901dd58c6da4924bc5efb217a1d83436290b",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/25460d6f39024cc3b8241b14c7ccf0d6f11a736a",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/6c1791130b781c843572fb6391c4a4c5d857ab17",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/72c5d8e416ecc46af370a1340b3db5ff0b0cc867",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/89969ffbeb948ffc159d19252e7469490103011b",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/ca71f204711ad24113e8b344dc5bb8b0385f5672",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/fe5c604053c36c62af24eee8a76407d026ea5163",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
32
CVE-2024/CVE-2024-393xx/CVE-2024-39362.json
Normal file
32
CVE-2024/CVE-2024-393xx/CVE-2024-39362.json
Normal file
@ -0,0 +1,32 @@
|
||||
{
|
||||
"id": "CVE-2024-39362",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-06-25T15:15:14.327",
|
||||
"lastModified": "2024-06-25T15:15:14.327",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ni2c: acpi: Unbind mux adapters before delete\n\nThere is an issue with ACPI overlay table removal specifically related\nto I2C multiplexers.\n\nConsider an ACPI SSDT Overlay that defines a PCA9548 I2C mux on an\nexisting I2C bus. When this table is loaded we see the creation of a\ndevice for the overall PCA9548 chip and 8 further devices - one\ni2c_adapter each for the mux channels. These are all bound to their\nACPI equivalents via an eventual invocation of acpi_bind_one().\n\nWhen we unload the SSDT overlay we run into the problem. The ACPI\ndevices are deleted as normal via acpi_device_del_work_fn() and the\nacpi_device_del_list.\n\nHowever, the following warning and stack trace is output as the\ndeletion does not go smoothly:\n------------[ cut here ]------------\nkernfs: can not remove 'physical_node', no directory\nWARNING: CPU: 1 PID: 11 at fs/kernfs/dir.c:1674 kernfs_remove_by_name_ns+0xb9/0xc0\nModules linked in:\nCPU: 1 PID: 11 Comm: kworker/u128:0 Not tainted 6.8.0-rc6+ #1\nHardware name: congatec AG conga-B7E3/conga-B7E3, BIOS 5.13 05/16/2023\nWorkqueue: kacpi_hotplug acpi_device_del_work_fn\nRIP: 0010:kernfs_remove_by_name_ns+0xb9/0xc0\nCode: e4 00 48 89 ef e8 07 71 db ff 5b b8 fe ff ff ff 5d 41 5c 41 5d e9 a7 55 e4 00 0f 0b eb a6 48 c7 c7 f0 38 0d 9d e8 97 0a d5 ff <0f> 0b eb dc 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90\nRSP: 0018:ffff9f864008fb28 EFLAGS: 00010286\nRAX: 0000000000000000 RBX: ffff8ef90a8d4940 RCX: 0000000000000000\nRDX: ffff8f000e267d10 RSI: ffff8f000e25c780 RDI: ffff8f000e25c780\nRBP: ffff8ef9186f9870 R08: 0000000000013ffb R09: 00000000ffffbfff\nR10: 00000000ffffbfff R11: ffff8f000e0a0000 R12: ffff9f864008fb50\nR13: ffff8ef90c93dd60 R14: ffff8ef9010d0958 R15: ffff8ef9186f98c8\nFS: 0000000000000000(0000) GS:ffff8f000e240000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f48f5253a08 CR3: 00000003cb82e000 CR4: 00000000003506f0\nCall Trace:\n <TASK>\n ? kernfs_remove_by_name_ns+0xb9/0xc0\n ? __warn+0x7c/0x130\n ? kernfs_remove_by_name_ns+0xb9/0xc0\n ? report_bug+0x171/0x1a0\n ? handle_bug+0x3c/0x70\n ? exc_invalid_op+0x17/0x70\n ? asm_exc_invalid_op+0x1a/0x20\n ? kernfs_remove_by_name_ns+0xb9/0xc0\n ? kernfs_remove_by_name_ns+0xb9/0xc0\n acpi_unbind_one+0x108/0x180\n device_del+0x18b/0x490\n ? srso_return_thunk+0x5/0x5f\n ? srso_return_thunk+0x5/0x5f\n device_unregister+0xd/0x30\n i2c_del_adapter.part.0+0x1bf/0x250\n i2c_mux_del_adapters+0xa1/0xe0\n i2c_device_remove+0x1e/0x80\n device_release_driver_internal+0x19a/0x200\n bus_remove_device+0xbf/0x100\n device_del+0x157/0x490\n ? __pfx_device_match_fwnode+0x10/0x10\n ? srso_return_thunk+0x5/0x5f\n device_unregister+0xd/0x30\n i2c_acpi_notify+0x10f/0x140\n notifier_call_chain+0x58/0xd0\n blocking_notifier_call_chain+0x3a/0x60\n acpi_device_del_work_fn+0x85/0x1d0\n process_one_work+0x134/0x2f0\n worker_thread+0x2f0/0x410\n ? __pfx_worker_thread+0x10/0x10\n kthread+0xe3/0x110\n ? __pfx_kthread+0x10/0x10\n ret_from_fork+0x2f/0x50\n ? __pfx_kthread+0x10/0x10\n ret_from_fork_asm+0x1b/0x30\n </TASK>\n---[ end trace 0000000000000000 ]---\n...\nrepeated 7 more times, 1 for each channel of the mux\n...\n\nThe issue is that the binding of the ACPI devices to their peer I2C\nadapters is not correctly cleaned up. Digging deeper into the issue we\nsee that the deletion order is such that the ACPI devices matching the\nmux channel i2c adapters are deleted first during the SSDT overlay\nremoval. For each of the channels we see a call to i2c_acpi_notify()\nwith ACPI_RECONFIG_DEVICE_REMOVE but, because these devices are not\nactually i2c_clients, nothing is done for them.\n\nLater on, after each of the mux channels has been dealt with, we come\nto delete the i2c_client representing the PCA9548 device. This is the\ncall stack we see above, whereby the kernel cleans up the i2c_client\nincluding destruction of the mux and its channel adapters. At this\npoint we do attempt to unbind from the ACPI peers but those peers \n---truncated---"
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/3f858bbf04dbac934ac279aaee05d49eb9910051",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/4f08050a47a59d199e214d711b989bb4f5150373",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/90dd0592b3b005d6f15c4e23e1364d3ae95e588d",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/b1574c8c0a80bd587a7651bf64f00be1f5391d27",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
32
CVE-2024/CVE-2024-393xx/CVE-2024-39371.json
Normal file
32
CVE-2024/CVE-2024-393xx/CVE-2024-39371.json
Normal file
@ -0,0 +1,32 @@
|
||||
{
|
||||
"id": "CVE-2024-39371",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-06-25T15:15:14.410",
|
||||
"lastModified": "2024-06-25T15:15:14.410",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nio_uring: check for non-NULL file pointer in io_file_can_poll()\n\nIn earlier kernels, it was possible to trigger a NULL pointer\ndereference off the forced async preparation path, if no file had\nbeen assigned. The trace leading to that looks as follows:\n\nBUG: kernel NULL pointer dereference, address: 00000000000000b0\nPGD 0 P4D 0\nOops: 0000 [#1] PREEMPT SMP\nCPU: 67 PID: 1633 Comm: buf-ring-invali Not tainted 6.8.0-rc3+ #1\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS unknown 2/2/2022\nRIP: 0010:io_buffer_select+0xc3/0x210\nCode: 00 00 48 39 d1 0f 82 ae 00 00 00 48 81 4b 48 00 00 01 00 48 89 73 70 0f b7 50 0c 66 89 53 42 85 ed 0f 85 d2 00 00 00 48 8b 13 <48> 8b 92 b0 00 00 00 48 83 7a 40 00 0f 84 21 01 00 00 4c 8b 20 5b\nRSP: 0018:ffffb7bec38c7d88 EFLAGS: 00010246\nRAX: ffff97af2be61000 RBX: ffff97af234f1700 RCX: 0000000000000040\nRDX: 0000000000000000 RSI: ffff97aecfb04820 RDI: ffff97af234f1700\nRBP: 0000000000000000 R08: 0000000000200030 R09: 0000000000000020\nR10: ffffb7bec38c7dc8 R11: 000000000000c000 R12: ffffb7bec38c7db8\nR13: ffff97aecfb05800 R14: ffff97aecfb05800 R15: ffff97af2be5e000\nFS: 00007f852f74b740(0000) GS:ffff97b1eeec0000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00000000000000b0 CR3: 000000016deab005 CR4: 0000000000370ef0\nCall Trace:\n <TASK>\n ? __die+0x1f/0x60\n ? page_fault_oops+0x14d/0x420\n ? do_user_addr_fault+0x61/0x6a0\n ? exc_page_fault+0x6c/0x150\n ? asm_exc_page_fault+0x22/0x30\n ? io_buffer_select+0xc3/0x210\n __io_import_iovec+0xb5/0x120\n io_readv_prep_async+0x36/0x70\n io_queue_sqe_fallback+0x20/0x260\n io_submit_sqes+0x314/0x630\n __do_sys_io_uring_enter+0x339/0xbc0\n ? __do_sys_io_uring_register+0x11b/0xc50\n ? vm_mmap_pgoff+0xce/0x160\n do_syscall_64+0x5f/0x180\n entry_SYSCALL_64_after_hwframe+0x46/0x4e\nRIP: 0033:0x55e0a110a67e\nCode: ba cc 00 00 00 45 31 c0 44 0f b6 92 d0 00 00 00 31 d2 41 b9 08 00 00 00 41 83 e2 01 41 c1 e2 04 41 09 c2 b8 aa 01 00 00 0f 05 <c3> 90 89 30 eb a9 0f 1f 40 00 48 8b 42 20 8b 00 a8 06 75 af 85 f6\n\nbecause the request is marked forced ASYNC and has a bad file fd, and\nhence takes the forced async prep path.\n\nCurrent kernels with the request async prep cleaned up can no longer hit\nthis issue, but for ease of backporting, let's add this safety check in\nhere too as it really doesn't hurt. For both cases, this will inevitably\nend with a CQE posted with -EBADF."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/43cfac7b88adedfb26c27834386992650f1642f3",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/5fc16fa5f13b3c06fdb959ef262050bd810416a2",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/65561b4c1c9e01443cb76387eb36a9109e7048ee",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/c2844d5e58576c55d8e8d4a9f74902d3f7be8044",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
28
CVE-2024/CVE-2024-394xx/CVE-2024-39461.json
Normal file
28
CVE-2024/CVE-2024-394xx/CVE-2024-39461.json
Normal file
@ -0,0 +1,28 @@
|
||||
{
|
||||
"id": "CVE-2024-39461",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-06-25T15:15:14.500",
|
||||
"lastModified": "2024-06-25T15:15:14.500",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nclk: bcm: rpi: Assign ->num before accessing ->hws\n\nCommit f316cdff8d67 (\"clk: Annotate struct clk_hw_onecell_data with\n__counted_by\") annotated the hws member of 'struct clk_hw_onecell_data'\nwith __counted_by, which informs the bounds sanitizer about the number\nof elements in hws, so that it can warn when hws is accessed out of\nbounds. As noted in that change, the __counted_by member must be\ninitialized with the number of elements before the first array access\nhappens, otherwise there will be a warning from each access prior to the\ninitialization because the number of elements is zero. This occurs in\nraspberrypi_discover_clocks() due to ->num being assigned after ->hws\nhas been accessed:\n\n UBSAN: array-index-out-of-bounds in drivers/clk/bcm/clk-raspberrypi.c:374:4\n index 3 is out of range for type 'struct clk_hw *[] __counted_by(num)' (aka 'struct clk_hw *[]')\n\nMove the ->num initialization to before the first access of ->hws, which\nclears up the warning."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/6dc445c1905096b2ed4db1a84570375b4e00cc0f",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/9562dbe5cdbb16ac887d27ef6f179980bb99193c",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/cdf9c7871d58d3df59d2775982e3533adb8ec920",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
28
CVE-2024/CVE-2024-394xx/CVE-2024-39462.json
Normal file
28
CVE-2024/CVE-2024-394xx/CVE-2024-39462.json
Normal file
@ -0,0 +1,28 @@
|
||||
{
|
||||
"id": "CVE-2024-39462",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-06-25T15:15:14.580",
|
||||
"lastModified": "2024-06-25T15:15:14.580",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nclk: bcm: dvp: Assign ->num before accessing ->hws\n\nCommit f316cdff8d67 (\"clk: Annotate struct clk_hw_onecell_data with\n__counted_by\") annotated the hws member of 'struct clk_hw_onecell_data'\nwith __counted_by, which informs the bounds sanitizer about the number\nof elements in hws, so that it can warn when hws is accessed out of\nbounds. As noted in that change, the __counted_by member must be\ninitialized with the number of elements before the first array access\nhappens, otherwise there will be a warning from each access prior to the\ninitialization because the number of elements is zero. This occurs in\nclk_dvp_probe() due to ->num being assigned after ->hws has been\naccessed:\n\n UBSAN: array-index-out-of-bounds in drivers/clk/bcm/clk-bcm2711-dvp.c:59:2\n index 0 is out of range for type 'struct clk_hw *[] __counted_by(num)' (aka 'struct clk_hw *[]')\n\nMove the ->num initialization to before the first access of ->hws, which\nclears up the warning."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/0dc913217fb79096597005bba9ba738e2db5cd02",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/9368cdf90f52a68120d039887ccff74ff33b4444",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/a1dd92fca0d6b58b55ed0484f75d4205dbb77010",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
32
CVE-2024/CVE-2024-394xx/CVE-2024-39463.json
Normal file
32
CVE-2024/CVE-2024-394xx/CVE-2024-39463.json
Normal file
@ -0,0 +1,32 @@
|
||||
{
|
||||
"id": "CVE-2024-39463",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-06-25T15:15:14.760",
|
||||
"lastModified": "2024-06-25T15:15:14.760",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\n9p: add missing locking around taking dentry fid list\n\nFix a use-after-free on dentry's d_fsdata fid list when a thread\nlooks up a fid through dentry while another thread unlinks it:\n\nUAF thread:\nrefcount_t: addition on 0; use-after-free.\n p9_fid_get linux/./include/net/9p/client.h:262\n v9fs_fid_find+0x236/0x280 linux/fs/9p/fid.c:129\n v9fs_fid_lookup_with_uid linux/fs/9p/fid.c:181\n v9fs_fid_lookup+0xbf/0xc20 linux/fs/9p/fid.c:314\n v9fs_vfs_getattr_dotl+0xf9/0x360 linux/fs/9p/vfs_inode_dotl.c:400\n vfs_statx+0xdd/0x4d0 linux/fs/stat.c:248\n\nFreed by:\n p9_fid_destroy (inlined)\n p9_client_clunk+0xb0/0xe0 linux/net/9p/client.c:1456\n p9_fid_put linux/./include/net/9p/client.h:278\n v9fs_dentry_release+0xb5/0x140 linux/fs/9p/vfs_dentry.c:55\n v9fs_remove+0x38f/0x620 linux/fs/9p/vfs_inode.c:518\n vfs_unlink+0x29a/0x810 linux/fs/namei.c:4335\n\nThe problem is that d_fsdata was not accessed under d_lock, because\nd_release() normally is only called once the dentry is otherwise no\nlonger accessible but since we also call it explicitly in v9fs_remove\nthat lock is required:\nmove the hlist out of the dentry under lock then unref its fids once\nthey are no longer accessible."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/c898afdc15645efb555acb6d85b484eb40a45409",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/cb299cdba09f46f090b843d78ba26b667d50a456",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/f0c5c944c6d8614c19e6e9a97fd2011dcd30e8f5",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/fe17ebf22feb4ad7094d597526d558a49aac92b4",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
28
CVE-2024/CVE-2024-394xx/CVE-2024-39464.json
Normal file
28
CVE-2024/CVE-2024-394xx/CVE-2024-39464.json
Normal file
@ -0,0 +1,28 @@
|
||||
{
|
||||
"id": "CVE-2024-39464",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-06-25T15:15:14.953",
|
||||
"lastModified": "2024-06-25T15:15:14.953",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: v4l: async: Fix notifier list entry init\n\nstruct v4l2_async_notifier has several list_head members, but only\nwaiting_list and done_list are initialized. notifier_entry was kept\n'zeroed' leading to an uninitialized list_head.\nThis results in a NULL-pointer dereference if csi2_async_register() fails,\ne.g. node for remote endpoint is disabled, and returns -ENOTCONN.\nThe following calls to v4l2_async_nf_unregister() results in a NULL\npointer dereference.\nAdd the missing list head initializer."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/44f6d619c30f0c65fcdd2b6eba70fdb4460d87ad",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/6d8acd02c4c6a8f917eefac1de2e035521ca119d",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/a80d1da923f671c1e6a14e8417cd2f117b27a442",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
24
CVE-2024/CVE-2024-394xx/CVE-2024-39465.json
Normal file
24
CVE-2024/CVE-2024-394xx/CVE-2024-39465.json
Normal file
@ -0,0 +1,24 @@
|
||||
{
|
||||
"id": "CVE-2024-39465",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-06-25T15:15:15.037",
|
||||
"lastModified": "2024-06-25T15:15:15.037",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: mgb4: Fix double debugfs remove\n\nFixes an error where debugfs_remove_recursive() is called first on a parent\ndirectory and then again on a child which causes a kernel panic.\n\n[hverkuil: added Fixes/Cc tags]"
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/252204b634efffd8b167d77413c93d0192aaf5f6",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/825fc49497957310e421454fe3fb8b8d8d8e2dd2",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
36
CVE-2024/CVE-2024-394xx/CVE-2024-39466.json
Normal file
36
CVE-2024/CVE-2024-394xx/CVE-2024-39466.json
Normal file
@ -0,0 +1,36 @@
|
||||
{
|
||||
"id": "CVE-2024-39466",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-06-25T15:15:15.117",
|
||||
"lastModified": "2024-06-25T15:15:15.117",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nthermal/drivers/qcom/lmh: Check for SCM availability at probe\n\nUp until now, the necessary scm availability check has not been\nperformed, leading to possible null pointer dereferences (which did\nhappen for me on RB1).\n\nFix that."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/0a47ba94ec3d8f782b33e3d970cfcb769b962464",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/2226b145afa5e13cb60dbe77fb20fb0666a1caf3",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/560d69c975072974c11434ca6953891e74c1a665",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/aa1a0807b4a76b44fb6b58a7e9087cd4b18ab41b",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/d9d3490c48df572edefc0b64655259eefdcbb9be",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
44
CVE-2024/CVE-2024-394xx/CVE-2024-39467.json
Normal file
44
CVE-2024/CVE-2024-394xx/CVE-2024-39467.json
Normal file
@ -0,0 +1,44 @@
|
||||
{
|
||||
"id": "CVE-2024-39467",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-06-25T15:15:15.190",
|
||||
"lastModified": "2024-06-25T15:15:15.190",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to do sanity check on i_xattr_nid in sanity_check_inode()\n\nsyzbot reports a kernel bug as below:\n\nF2FS-fs (loop0): Mounted with checkpoint version = 48b305e4\n==================================================================\nBUG: KASAN: slab-out-of-bounds in f2fs_test_bit fs/f2fs/f2fs.h:2933 [inline]\nBUG: KASAN: slab-out-of-bounds in current_nat_addr fs/f2fs/node.h:213 [inline]\nBUG: KASAN: slab-out-of-bounds in f2fs_get_node_info+0xece/0x1200 fs/f2fs/node.c:600\nRead of size 1 at addr ffff88807a58c76c by task syz-executor280/5076\n\nCPU: 1 PID: 5076 Comm: syz-executor280 Not tainted 6.9.0-rc5-syzkaller #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024\nCall Trace:\n <TASK>\n __dump_stack lib/dump_stack.c:88 [inline]\n dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114\n print_address_description mm/kasan/report.c:377 [inline]\n print_report+0x169/0x550 mm/kasan/report.c:488\n kasan_report+0x143/0x180 mm/kasan/report.c:601\n f2fs_test_bit fs/f2fs/f2fs.h:2933 [inline]\n current_nat_addr fs/f2fs/node.h:213 [inline]\n f2fs_get_node_info+0xece/0x1200 fs/f2fs/node.c:600\n f2fs_xattr_fiemap fs/f2fs/data.c:1848 [inline]\n f2fs_fiemap+0x55d/0x1ee0 fs/f2fs/data.c:1925\n ioctl_fiemap fs/ioctl.c:220 [inline]\n do_vfs_ioctl+0x1c07/0x2e50 fs/ioctl.c:838\n __do_sys_ioctl fs/ioctl.c:902 [inline]\n __se_sys_ioctl+0x81/0x170 fs/ioctl.c:890\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nThe root cause is we missed to do sanity check on i_xattr_nid during\nf2fs_iget(), so that in fiemap() path, current_nat_addr() will access\nnat_bitmap w/ offset from invalid i_xattr_nid, result in triggering\nkasan bug report, fix it."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/1640dcf383cdba52be8b28d2a1a2aa7ef7a30c98",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/20faaf30e55522bba2b56d9c46689233205d7717",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/68e3cd4ecb8603936cccdc338929130045df2e57",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/75c87e2ac6149abf44bdde0dd6d541763ddb0dff",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/8c8aa473fe6eb46a4bf99f3ea2dbe52bf0c1a1f0",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/be0155202e431f3007778568a72432c68f8946ba",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/c559a8d840562fbfce9f318448dda2f7d3e6d8e8",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
32
CVE-2024/CVE-2024-394xx/CVE-2024-39468.json
Normal file
32
CVE-2024/CVE-2024-394xx/CVE-2024-39468.json
Normal file
@ -0,0 +1,32 @@
|
||||
{
|
||||
"id": "CVE-2024-39468",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-06-25T15:15:15.270",
|
||||
"lastModified": "2024-06-25T15:15:15.270",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix deadlock in smb2_find_smb_tcon()\n\nUnlock cifs_tcp_ses_lock before calling cifs_put_smb_ses() to avoid such\ndeadlock."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/02c418774f76a0a36a6195c9dbf8971eb4130a15",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/225de871ddf994f69a57f035709cad9c0ab8615a",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/8d0f5f1ccf675454a833a573c53830a49b7d1a47",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/b09b556e48968317887a11243a5331a7bc00ece5",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
32
CVE-2024/CVE-2024-394xx/CVE-2024-39469.json
Normal file
32
CVE-2024/CVE-2024-394xx/CVE-2024-39469.json
Normal file
@ -0,0 +1,32 @@
|
||||
{
|
||||
"id": "CVE-2024-39469",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-06-25T15:15:15.340",
|
||||
"lastModified": "2024-06-25T15:15:15.340",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnilfs2: fix nilfs_empty_dir() misjudgment and long loop on I/O errors\n\nThe error handling in nilfs_empty_dir() when a directory folio/page read\nfails is incorrect, as in the old ext2 implementation, and if the\nfolio/page cannot be read or nilfs_check_folio() fails, it will falsely\ndetermine the directory as empty and corrupt the file system.\n\nIn addition, since nilfs_empty_dir() does not immediately return on a\nfailed folio/page read, but continues to loop, this can cause a long loop\nwith I/O if i_size of the directory's inode is also corrupted, causing the\nlog writer thread to wait and hang, as reported by syzbot.\n\nFix these issues by making nilfs_empty_dir() immediately return a false\nvalue (0) if it fails to get a directory folio/page."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/129dcd3e7d036218db3f59c82d82004b9539ed82",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/59f14875a96ef93f05b82ad3c980605f2cb444b5",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/7373a51e7998b508af7136530f3a997b286ce81c",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/d18b05eda7fa77f02114f15b02c009f28ee42346",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
28
CVE-2024/CVE-2024-394xx/CVE-2024-39470.json
Normal file
28
CVE-2024/CVE-2024-394xx/CVE-2024-39470.json
Normal file
@ -0,0 +1,28 @@
|
||||
{
|
||||
"id": "CVE-2024-39470",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-06-25T15:15:15.417",
|
||||
"lastModified": "2024-06-25T15:15:15.417",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\neventfs: Fix a possible null pointer dereference in eventfs_find_events()\n\nIn function eventfs_find_events,there is a potential null pointer\nthat may be caused by calling update_events_attr which will perform\nsome operations on the members of the ei struct when ei is NULL.\n\nHence,When ei->is_freed is set,return NULL directly."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/5ade5fbdbbb1f023bb70730ba4d74146c8bc7eb9",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/7a1b2d138189375ed1dcd7d0851118230221bd1d",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/d4e9a968738bf66d3bb852dd5588d4c7afd6d7f4",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
44
CVE-2024/CVE-2024-394xx/CVE-2024-39471.json
Normal file
44
CVE-2024/CVE-2024-394xx/CVE-2024-39471.json
Normal file
@ -0,0 +1,44 @@
|
||||
{
|
||||
"id": "CVE-2024-39471",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-06-25T15:15:15.490",
|
||||
"lastModified": "2024-06-25T15:15:15.490",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: add error handle to avoid out-of-bounds\n\nif the sdma_v4_0_irq_id_to_seq return -EINVAL, the process should\nbe stop to avoid out-of-bounds read, so directly return -EINVAL."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/011552f29f20842c9a7a21bffe1f6a2d6457ba46",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/0964c84b93db7fbf74f357c1e20957850e092db3",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/5594971e02764aa1c8210ffb838cb4e7897716e8",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/5b0a3dc3e87821acb80e841b464d335aff242691",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/8112fa72b7f139052843ff484130d6f97e9f052f",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/8b2faf1a4f3b6c748c0da36cda865a226534d520",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/ea906e9ac61e3152bef63597f2d9f4a812fc346a",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
51
CVE-2024/CVE-2024-54xx/CVE-2024-5451.json
Normal file
51
CVE-2024/CVE-2024-54xx/CVE-2024-5451.json
Normal file
@ -0,0 +1,51 @@
|
||||
{
|
||||
"id": "CVE-2024-5451",
|
||||
"sourceIdentifier": "security@wordfence.com",
|
||||
"published": "2024-06-25T14:15:12.777",
|
||||
"lastModified": "2024-06-25T14:15:12.777",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "The The7 \u2014 Website and eCommerce Builder for WordPress theme for WordPress is vulnerable to Stored Cross-Site Scripting via the 'url' attribute within the plugin's Icon and Heading widgets in all versions up to, and including, 11.13.0 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV31": [
|
||||
{
|
||||
"source": "security@wordfence.com",
|
||||
"type": "Primary",
|
||||
"cvssData": {
|
||||
"version": "3.1",
|
||||
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N",
|
||||
"attackVector": "NETWORK",
|
||||
"attackComplexity": "LOW",
|
||||
"privilegesRequired": "LOW",
|
||||
"userInteraction": "NONE",
|
||||
"scope": "CHANGED",
|
||||
"confidentialityImpact": "LOW",
|
||||
"integrityImpact": "LOW",
|
||||
"availabilityImpact": "NONE",
|
||||
"baseScore": 6.4,
|
||||
"baseSeverity": "MEDIUM"
|
||||
},
|
||||
"exploitabilityScore": 3.1,
|
||||
"impactScore": 2.7
|
||||
}
|
||||
]
|
||||
},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://the7.io/changelog/",
|
||||
"source": "security@wordfence.com"
|
||||
},
|
||||
{
|
||||
"url": "https://themeforest.net/item/the7-responsive-multipurpose-wordpress-theme/5556590",
|
||||
"source": "security@wordfence.com"
|
||||
},
|
||||
{
|
||||
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/c4555cd1-5ae5-42b3-938f-ffce5ba4fe56?source=cve",
|
||||
"source": "security@wordfence.com"
|
||||
}
|
||||
]
|
||||
}
|
59
CVE-2024/CVE-2024-58xx/CVE-2024-5805.json
Normal file
59
CVE-2024/CVE-2024-58xx/CVE-2024-5805.json
Normal file
@ -0,0 +1,59 @@
|
||||
{
|
||||
"id": "CVE-2024-5805",
|
||||
"sourceIdentifier": "security@progress.com",
|
||||
"published": "2024-06-25T15:15:15.603",
|
||||
"lastModified": "2024-06-25T15:15:15.603",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "Improper Authentication vulnerability in Progress MOVEit Gateway (SFTP modules) allows Authentication Bypass.This issue affects MOVEit Gateway: 2024.0.0."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV31": [
|
||||
{
|
||||
"source": "security@progress.com",
|
||||
"type": "Secondary",
|
||||
"cvssData": {
|
||||
"version": "3.1",
|
||||
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
|
||||
"attackVector": "NETWORK",
|
||||
"attackComplexity": "LOW",
|
||||
"privilegesRequired": "NONE",
|
||||
"userInteraction": "NONE",
|
||||
"scope": "UNCHANGED",
|
||||
"confidentialityImpact": "HIGH",
|
||||
"integrityImpact": "HIGH",
|
||||
"availabilityImpact": "NONE",
|
||||
"baseScore": 9.1,
|
||||
"baseSeverity": "CRITICAL"
|
||||
},
|
||||
"exploitabilityScore": 3.9,
|
||||
"impactScore": 5.2
|
||||
}
|
||||
]
|
||||
},
|
||||
"weaknesses": [
|
||||
{
|
||||
"source": "security@progress.com",
|
||||
"type": "Secondary",
|
||||
"description": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "CWE-287"
|
||||
}
|
||||
]
|
||||
}
|
||||
],
|
||||
"references": [
|
||||
{
|
||||
"url": "https://community.progress.com/s/article/MOVEit-Gateway-Critical-Security-Alert-Bulletin-June-2024-CVE-2024-5805",
|
||||
"source": "security@progress.com"
|
||||
},
|
||||
{
|
||||
"url": "https://www.progress.com/moveit",
|
||||
"source": "security@progress.com"
|
||||
}
|
||||
]
|
||||
}
|
59
CVE-2024/CVE-2024-58xx/CVE-2024-5806.json
Normal file
59
CVE-2024/CVE-2024-58xx/CVE-2024-5806.json
Normal file
@ -0,0 +1,59 @@
|
||||
{
|
||||
"id": "CVE-2024-5806",
|
||||
"sourceIdentifier": "security@progress.com",
|
||||
"published": "2024-06-25T15:15:15.850",
|
||||
"lastModified": "2024-06-25T15:15:15.850",
|
||||
"vulnStatus": "Received",
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "Improper Authentication vulnerability in Progress MOVEit Transfer (SFTP module) can lead to Authentication Bypass in limited scenarios.This issue affects MOVEit Transfer: from 2023.0.0 before 2023.0.11, from 2023.1.0 before 2023.1.6, from 2024.0.0 before 2024.0.2."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV31": [
|
||||
{
|
||||
"source": "security@progress.com",
|
||||
"type": "Secondary",
|
||||
"cvssData": {
|
||||
"version": "3.1",
|
||||
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N",
|
||||
"attackVector": "NETWORK",
|
||||
"attackComplexity": "HIGH",
|
||||
"privilegesRequired": "NONE",
|
||||
"userInteraction": "NONE",
|
||||
"scope": "UNCHANGED",
|
||||
"confidentialityImpact": "HIGH",
|
||||
"integrityImpact": "HIGH",
|
||||
"availabilityImpact": "NONE",
|
||||
"baseScore": 7.4,
|
||||
"baseSeverity": "HIGH"
|
||||
},
|
||||
"exploitabilityScore": 2.2,
|
||||
"impactScore": 5.2
|
||||
}
|
||||
]
|
||||
},
|
||||
"weaknesses": [
|
||||
{
|
||||
"source": "security@progress.com",
|
||||
"type": "Secondary",
|
||||
"description": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "CWE-287"
|
||||
}
|
||||
]
|
||||
}
|
||||
],
|
||||
"references": [
|
||||
{
|
||||
"url": "https://community.progress.com/s/article/MOVEit-Transfer-Product-Security-Alert-Bulletin-June-2024-CVE-2024-5806",
|
||||
"source": "security@progress.com"
|
||||
},
|
||||
{
|
||||
"url": "https://www.progress.com/moveit",
|
||||
"source": "security@progress.com"
|
||||
}
|
||||
]
|
||||
}
|
71
README.md
71
README.md
@ -13,13 +13,13 @@ Repository synchronizes with the NVD every 2 hours.
|
||||
### Last Repository Update
|
||||
|
||||
```plain
|
||||
2024-06-25T14:00:27.950713+00:00
|
||||
2024-06-25T16:00:18.962894+00:00
|
||||
```
|
||||
|
||||
### Most recent CVE Modification Timestamp synchronized with NVD
|
||||
|
||||
```plain
|
||||
2024-06-25T13:15:51.550000+00:00
|
||||
2024-06-25T15:15:15.850000+00:00
|
||||
```
|
||||
|
||||
### Last Data Feed Release
|
||||
@ -33,54 +33,45 @@ Download and Changelog: [Click](https://github.com/fkie-cad/nvd-json-data-feeds/
|
||||
### Total Number of included CVEs
|
||||
|
||||
```plain
|
||||
255122
|
||||
255158
|
||||
```
|
||||
|
||||
### CVEs added in the last Commit
|
||||
|
||||
Recently added CVEs: `10`
|
||||
Recently added CVEs: `36`
|
||||
|
||||
- [CVE-2024-28831](CVE-2024/CVE-2024-288xx/CVE-2024-28831.json) (`2024-06-25T12:15:09.490`)
|
||||
- [CVE-2024-28832](CVE-2024/CVE-2024-288xx/CVE-2024-28832.json) (`2024-06-25T12:15:09.713`)
|
||||
- [CVE-2024-31111](CVE-2024/CVE-2024-311xx/CVE-2024-31111.json) (`2024-06-25T13:15:49.383`)
|
||||
- [CVE-2024-4846](CVE-2024/CVE-2024-48xx/CVE-2024-4846.json) (`2024-06-25T13:15:50.120`)
|
||||
- [CVE-2024-5261](CVE-2024/CVE-2024-52xx/CVE-2024-5261.json) (`2024-06-25T13:15:50.220`)
|
||||
- [CVE-2024-6299](CVE-2024/CVE-2024-62xx/CVE-2024-6299.json) (`2024-06-25T13:15:50.587`)
|
||||
- [CVE-2024-6300](CVE-2024/CVE-2024-63xx/CVE-2024-6300.json) (`2024-06-25T13:15:50.847`)
|
||||
- [CVE-2024-6301](CVE-2024/CVE-2024-63xx/CVE-2024-6301.json) (`2024-06-25T13:15:51.077`)
|
||||
- [CVE-2024-6302](CVE-2024/CVE-2024-63xx/CVE-2024-6302.json) (`2024-06-25T13:15:51.313`)
|
||||
- [CVE-2024-6303](CVE-2024/CVE-2024-63xx/CVE-2024-6303.json) (`2024-06-25T13:15:51.550`)
|
||||
- [CVE-2024-38385](CVE-2024/CVE-2024-383xx/CVE-2024-38385.json) (`2024-06-25T15:15:13.487`)
|
||||
- [CVE-2024-38661](CVE-2024/CVE-2024-386xx/CVE-2024-38661.json) (`2024-06-25T15:15:13.630`)
|
||||
- [CVE-2024-38951](CVE-2024/CVE-2024-389xx/CVE-2024-38951.json) (`2024-06-25T14:15:12.403`)
|
||||
- [CVE-2024-38952](CVE-2024/CVE-2024-389xx/CVE-2024-38952.json) (`2024-06-25T14:15:12.517`)
|
||||
- [CVE-2024-39276](CVE-2024/CVE-2024-392xx/CVE-2024-39276.json) (`2024-06-25T15:15:13.903`)
|
||||
- [CVE-2024-39293](CVE-2024/CVE-2024-392xx/CVE-2024-39293.json) (`2024-06-25T15:15:13.993`)
|
||||
- [CVE-2024-39296](CVE-2024/CVE-2024-392xx/CVE-2024-39296.json) (`2024-06-25T15:15:14.070`)
|
||||
- [CVE-2024-39298](CVE-2024/CVE-2024-392xx/CVE-2024-39298.json) (`2024-06-25T15:15:14.160`)
|
||||
- [CVE-2024-39301](CVE-2024/CVE-2024-393xx/CVE-2024-39301.json) (`2024-06-25T15:15:14.240`)
|
||||
- [CVE-2024-39362](CVE-2024/CVE-2024-393xx/CVE-2024-39362.json) (`2024-06-25T15:15:14.327`)
|
||||
- [CVE-2024-39371](CVE-2024/CVE-2024-393xx/CVE-2024-39371.json) (`2024-06-25T15:15:14.410`)
|
||||
- [CVE-2024-39461](CVE-2024/CVE-2024-394xx/CVE-2024-39461.json) (`2024-06-25T15:15:14.500`)
|
||||
- [CVE-2024-39462](CVE-2024/CVE-2024-394xx/CVE-2024-39462.json) (`2024-06-25T15:15:14.580`)
|
||||
- [CVE-2024-39463](CVE-2024/CVE-2024-394xx/CVE-2024-39463.json) (`2024-06-25T15:15:14.760`)
|
||||
- [CVE-2024-39464](CVE-2024/CVE-2024-394xx/CVE-2024-39464.json) (`2024-06-25T15:15:14.953`)
|
||||
- [CVE-2024-39465](CVE-2024/CVE-2024-394xx/CVE-2024-39465.json) (`2024-06-25T15:15:15.037`)
|
||||
- [CVE-2024-39466](CVE-2024/CVE-2024-394xx/CVE-2024-39466.json) (`2024-06-25T15:15:15.117`)
|
||||
- [CVE-2024-39467](CVE-2024/CVE-2024-394xx/CVE-2024-39467.json) (`2024-06-25T15:15:15.190`)
|
||||
- [CVE-2024-39468](CVE-2024/CVE-2024-394xx/CVE-2024-39468.json) (`2024-06-25T15:15:15.270`)
|
||||
- [CVE-2024-39469](CVE-2024/CVE-2024-394xx/CVE-2024-39469.json) (`2024-06-25T15:15:15.340`)
|
||||
- [CVE-2024-39470](CVE-2024/CVE-2024-394xx/CVE-2024-39470.json) (`2024-06-25T15:15:15.417`)
|
||||
- [CVE-2024-39471](CVE-2024/CVE-2024-394xx/CVE-2024-39471.json) (`2024-06-25T15:15:15.490`)
|
||||
- [CVE-2024-5451](CVE-2024/CVE-2024-54xx/CVE-2024-5451.json) (`2024-06-25T14:15:12.777`)
|
||||
- [CVE-2024-5805](CVE-2024/CVE-2024-58xx/CVE-2024-5805.json) (`2024-06-25T15:15:15.603`)
|
||||
- [CVE-2024-5806](CVE-2024/CVE-2024-58xx/CVE-2024-5806.json) (`2024-06-25T15:15:15.850`)
|
||||
|
||||
|
||||
### CVEs modified in the last Commit
|
||||
|
||||
Recently modified CVEs: `82`
|
||||
Recently modified CVEs: `1`
|
||||
|
||||
- [CVE-2024-38897](CVE-2024/CVE-2024-388xx/CVE-2024-38897.json) (`2024-06-25T12:24:17.873`)
|
||||
- [CVE-2024-38902](CVE-2024/CVE-2024-389xx/CVE-2024-38902.json) (`2024-06-25T12:24:17.873`)
|
||||
- [CVE-2024-38903](CVE-2024/CVE-2024-389xx/CVE-2024-38903.json) (`2024-06-25T12:24:17.873`)
|
||||
- [CVE-2024-4196](CVE-2024/CVE-2024-41xx/CVE-2024-4196.json) (`2024-06-25T12:24:17.873`)
|
||||
- [CVE-2024-4197](CVE-2024/CVE-2024-41xx/CVE-2024-4197.json) (`2024-06-25T12:24:17.873`)
|
||||
- [CVE-2024-4638](CVE-2024/CVE-2024-46xx/CVE-2024-4638.json) (`2024-06-25T12:24:17.873`)
|
||||
- [CVE-2024-4639](CVE-2024/CVE-2024-46xx/CVE-2024-4639.json) (`2024-06-25T12:24:17.873`)
|
||||
- [CVE-2024-4640](CVE-2024/CVE-2024-46xx/CVE-2024-4640.json) (`2024-06-25T12:24:17.873`)
|
||||
- [CVE-2024-4641](CVE-2024/CVE-2024-46xx/CVE-2024-4641.json) (`2024-06-25T12:24:17.873`)
|
||||
- [CVE-2024-4757](CVE-2024/CVE-2024-47xx/CVE-2024-4757.json) (`2024-06-25T12:24:17.873`)
|
||||
- [CVE-2024-4759](CVE-2024/CVE-2024-47xx/CVE-2024-4759.json) (`2024-06-25T12:24:17.873`)
|
||||
- [CVE-2024-5216](CVE-2024/CVE-2024-52xx/CVE-2024-5216.json) (`2024-06-25T12:24:17.873`)
|
||||
- [CVE-2024-5431](CVE-2024/CVE-2024-54xx/CVE-2024-5431.json) (`2024-06-25T12:24:17.873`)
|
||||
- [CVE-2024-6028](CVE-2024/CVE-2024-60xx/CVE-2024-6028.json) (`2024-06-25T12:24:17.873`)
|
||||
- [CVE-2024-6273](CVE-2024/CVE-2024-62xx/CVE-2024-6273.json) (`2024-06-25T13:15:50.403`)
|
||||
- [CVE-2024-6290](CVE-2024/CVE-2024-62xx/CVE-2024-6290.json) (`2024-06-25T12:24:17.873`)
|
||||
- [CVE-2024-6291](CVE-2024/CVE-2024-62xx/CVE-2024-6291.json) (`2024-06-25T12:24:17.873`)
|
||||
- [CVE-2024-6292](CVE-2024/CVE-2024-62xx/CVE-2024-6292.json) (`2024-06-25T12:24:17.873`)
|
||||
- [CVE-2024-6293](CVE-2024/CVE-2024-62xx/CVE-2024-6293.json) (`2024-06-25T12:24:17.873`)
|
||||
- [CVE-2024-6294](CVE-2024/CVE-2024-62xx/CVE-2024-6294.json) (`2024-06-25T12:24:17.873`)
|
||||
- [CVE-2024-6295](CVE-2024/CVE-2024-62xx/CVE-2024-6295.json) (`2024-06-25T12:24:17.873`)
|
||||
- [CVE-2024-6297](CVE-2024/CVE-2024-62xx/CVE-2024-6297.json) (`2024-06-25T12:24:17.873`)
|
||||
- [CVE-2024-6305](CVE-2024/CVE-2024-63xx/CVE-2024-6305.json) (`2024-06-25T12:24:17.873`)
|
||||
- [CVE-2024-6306](CVE-2024/CVE-2024-63xx/CVE-2024-6306.json) (`2024-06-25T12:24:17.873`)
|
||||
- [CVE-2024-6307](CVE-2024/CVE-2024-63xx/CVE-2024-6307.json) (`2024-06-25T12:24:17.873`)
|
||||
- [CVE-2023-49115](CVE-2023/CVE-2023-491xx/CVE-2023-49115.json) (`2024-06-25T14:15:10.687`)
|
||||
|
||||
|
||||
## Download and Usage
|
||||
|
222
_state.csv
222
_state.csv
@ -185126,6 +185126,7 @@ CVE-2021-44396,0,0,7c0ba48df549e25e005295bbe627041950189a573d8758add2ca397b502be
|
||||
CVE-2021-44397,0,0,aeede1d53bd2f94396aba7592014a0f445309317bb79c0c7fdefa09f8e68a5cc,2022-10-25T17:40:14.183000
|
||||
CVE-2021-44398,0,0,555e554f6904e149f92b31d145cec3fd8d8d4f433c4c7cb018d9ef385828e3b5,2022-10-25T17:40:21.837000
|
||||
CVE-2021-44399,0,0,8351d48ef470fa1034a9534b3958230b5279d3245a336ecc1fca4eba670b40e9,2022-10-25T17:40:29.917000
|
||||
CVE-2021-4440,1,1,07606ee6b27ac154d34d88368fc272200e58054cba7dd3112ae7fbbfdbe61bbb,2024-06-25T15:15:11.137000
|
||||
CVE-2021-44400,0,0,4bf726c514ec568544515b2748f948e99c81db36c2c66f97b411537a96b3cae0,2022-10-25T17:40:36.487000
|
||||
CVE-2021-44401,0,0,68d7d93d9e3f406a7ab164303254465fd18dc424fd00d011aee0e99433fcfe2c,2022-10-25T17:40:42.937000
|
||||
CVE-2021-44402,0,0,145a71ca0f99e2e160a739601e598a913b8350298bfa2d402e99094a1715380d,2022-10-25T17:40:50.610000
|
||||
@ -212186,6 +212187,7 @@ CVE-2022-48769,0,0,d91719a0d33489128abf3f79e40a4d452424581467f9c54e1dc5a4ec1803b
|
||||
CVE-2022-4877,0,0,f2130ce984ecc4a7ab39ad237fb93ed91ee6583213d9752d5a3b6539de11f505,2024-05-17T02:17:00.577000
|
||||
CVE-2022-48770,0,0,59af73fda569680598cec6ae61cf3113302f7c002ca441726d23aa2b40d6e50d,2024-06-20T12:43:25.663000
|
||||
CVE-2022-48771,0,0,b9cb574532c8cc5c6f9a1746390a230f9cef8e365740ee8df5cdd90f9ec2b028,2024-06-20T12:43:25.663000
|
||||
CVE-2022-48772,1,1,6800db80e25c8d090e612cfa33bc627785088d68e8a4425c0d6013102f0f7dd9,2024-06-25T15:15:11.233000
|
||||
CVE-2022-4878,0,0,299ee6479f083f259bdf084b35f63f9b7f08419d0f34f7a269e509fd602e1b4e,2024-05-17T02:17:00.683000
|
||||
CVE-2022-4879,0,0,f0df7ea99784f1d952c95e73e0c6b13e618ff8f4b46c80af6508d975b338aaaa,2024-05-17T02:17:00.797000
|
||||
CVE-2022-4880,0,0,ee251947c736e879ebc14c1cac8b9f415167d50ab4d5717800dd5911361afca2,2024-05-17T02:17:00.927000
|
||||
@ -227827,6 +227829,7 @@ CVE-2023-37538,0,0,2e3ab908ded045f3cb71d752e478696df3532097f747245caae75e491c757
|
||||
CVE-2023-37539,0,0,fe4406511a2092f04bafa14f10aee93f6b4ca7a9de1b6733953234a6b61a132e,2024-06-07T14:56:05.647000
|
||||
CVE-2023-3754,0,0,5f6b8f96d4590040aa350c1dd3ab2738d4b82887085506b845deafcec4c19e00,2024-05-17T02:27:45.643000
|
||||
CVE-2023-37540,0,0,12f3689b3ddb4d201c51279c60534122a2f05c59ebf7083151345550669320dc,2024-02-23T16:14:43.447000
|
||||
CVE-2023-37541,1,1,be78ed3070357cc2e95750e90aa5c80b64ead59030c4d3ffd427133fc5f7dbf8,2024-06-25T15:15:11.363000
|
||||
CVE-2023-37543,0,0,3d96eefef3971bb20f74a508435ca4222398e4a6d5bf603850624625cb29632e,2023-11-07T04:16:58.957000
|
||||
CVE-2023-37544,0,0,a02f2460fc3781b2604f33e1b52f5222d505118187d1430419076dd130d4ddee,2024-01-04T18:52:01.020000
|
||||
CVE-2023-37545,0,0,09164d7d1efe81bf2ac2e973985e277e15e6b2c824203f7dc3490dfb47590fdb,2023-08-07T19:29:27.573000
|
||||
@ -233368,8 +233371,8 @@ CVE-2023-45191,0,0,0471d71b4e832eeadfce865b6a4a3f21dfa7a9078549997d149920fc7d734
|
||||
CVE-2023-45192,0,0,9b3331ad67e9e1a89b019f9431a09b60b39c9c9dc236135dc341290555b6f6d8,2024-06-07T14:56:05.647000
|
||||
CVE-2023-45193,0,0,74568a9a8ac5466cce17b97fc2aa48957015444a92e43d7710c1164db296930b,2024-03-07T17:15:09.880000
|
||||
CVE-2023-45194,0,0,d5c89e53cbf9029912da4482ada08495c9f99ebbbb14329dd33526185af3bf8f,2023-10-31T18:08:52.140000
|
||||
CVE-2023-45195,0,1,2acd08332590519f07dec66408bb370bd3f8232a9a4a4343bcf3a35992f2ea2e,2024-06-25T12:24:17.873000
|
||||
CVE-2023-45196,0,1,5d386b70422907714f6fdf8e44288e7ce5b7b1429d32668992ee04c6169c4465,2024-06-25T12:24:17.873000
|
||||
CVE-2023-45195,0,0,2acd08332590519f07dec66408bb370bd3f8232a9a4a4343bcf3a35992f2ea2e,2024-06-25T12:24:17.873000
|
||||
CVE-2023-45196,0,0,5d386b70422907714f6fdf8e44288e7ce5b7b1429d32668992ee04c6169c4465,2024-06-25T12:24:17.873000
|
||||
CVE-2023-45197,0,0,c0d17f1ad7bbed426d147463e2778851696bf61332804cb6168757444d8a7309,2024-06-24T21:15:25.760000
|
||||
CVE-2023-45198,0,0,e83575150f55c9693ecaa3d3d8ecc28b28389ef4c4551e169f843e36cfbc4ca1,2023-10-11T17:15:31.923000
|
||||
CVE-2023-45199,0,0,ffec34f4347277cf1a81398e2045556919c611109a0a71706ab507c8e66ad4f5,2023-10-12T18:19:39.860000
|
||||
@ -236189,7 +236192,7 @@ CVE-2023-49111,0,0,39eaef1b1cefe18a93fba8917b64eadec3fbfd3722261b5867f4dd77a2add
|
||||
CVE-2023-49112,0,0,dd4452bd1c78d0b19ca25cc28d4bc8e567b574019a48944860d3858d0f452c4b,2024-06-20T16:07:50.417000
|
||||
CVE-2023-49113,0,0,ebec5dd238079a4b14d06678dfa32d79eabf90e2d5277d1c4f610738deab797c,2024-06-20T16:07:50.417000
|
||||
CVE-2023-49114,0,0,1149e9644a812fe979090b00a81f87220fd6ab37816f13bf4a0117849686b510,2024-03-03T03:15:07.170000
|
||||
CVE-2023-49115,0,0,d4487cb956fe9cb8f01ce6d3732e2ed47fd143cb71a5d17fa9999fc2467e49a2,2024-05-17T02:30:59.670000
|
||||
CVE-2023-49115,0,1,019d00f8cd47d0d4ab5c2a9b4a196e0dcc127c776e1573171e9c26d9b4a2ce51,2024-06-25T14:15:10.687000
|
||||
CVE-2023-49117,0,0,532b60b363b961206673339ea571d1dbd7872affd35f7cb4f7e7a5be2e8191ec,2024-01-04T02:42:06.503000
|
||||
CVE-2023-49118,0,0,5c6aa9616c5f177131f61705f7516de74cbb3dc30b50259d70310941b6331639,2024-02-07T18:15:10.577000
|
||||
CVE-2023-49119,0,0,48da9ba870a35b29121630e46cbd338ee444a715558047c8ad56edfa7dbf2851,2024-01-02T19:54:09.417000
|
||||
@ -236819,7 +236822,7 @@ CVE-2023-50020,0,0,0420bf44f3192678835af5943c71c435d383debc14787f6862dfd11873466
|
||||
CVE-2023-50026,0,0,ddb63f64ad9db005831a0adfbb131b3f4a80d06c694a28549975d090519ef096,2024-06-07T14:12:14.943000
|
||||
CVE-2023-50027,0,0,cc6332349beda48de311c789172519792bf0e1d73915b299358aaf3ebbfbd533,2024-01-11T14:26:14.217000
|
||||
CVE-2023-50028,0,0,c4dec5d92b9d7082f423a44ec040b850ebf7d261529103270f04a2098eaade81,2024-01-25T19:55:05.850000
|
||||
CVE-2023-50029,0,1,7c9bacbacbf165ee4707b0129bcdc91ac10f64d0a4f7c58838d3265ccd9ec1e8,2024-06-25T12:24:17.873000
|
||||
CVE-2023-50029,0,0,7c9bacbacbf165ee4707b0129bcdc91ac10f64d0a4f7c58838d3265ccd9ec1e8,2024-06-25T12:24:17.873000
|
||||
CVE-2023-5003,0,0,2849233ffe4afb30b72aadd62309b165bd2ceffb201a5ac14f68b09d02b2ba14,2023-11-07T04:23:17.990000
|
||||
CVE-2023-50030,0,0,6c466acfd9c93ba20780248d726b1091908b80e5ee7f2c9d8b4bffa54cf157fa,2024-01-25T17:10:31.103000
|
||||
CVE-2023-50035,0,0,7af1ae42c48e4a2c0ccb4a35436abe8d24603d49181e707354cb51c037ebe841,2024-01-05T19:14:27.160000
|
||||
@ -237031,7 +237034,7 @@ CVE-2023-50363,0,0,007beb9c9c826c8ff3ba07c2de46061e06937bd3e1177219f5c49a9bb2333
|
||||
CVE-2023-50364,0,0,e47604eb43c17aadb72d581e49581bad4589eac6cac682ed1340e87038a754a0,2024-05-09T01:15:06.410000
|
||||
CVE-2023-50368,0,0,822f875a462c17b899bc5907af8a90bdf88b03f70fa2a47891ff0cc8e05f7ab1,2023-12-18T18:51:37.847000
|
||||
CVE-2023-50369,0,0,5473010ca0d536c23d0126860849245f23a6b5fb4418917816ad2a87231e17a3,2023-12-18T18:57:46.290000
|
||||
CVE-2023-5037,0,1,f164cfec8e7f1d00c559d76365ccbd071d432f38c0203cbb40689a289695bcb4,2024-06-25T12:24:17.873000
|
||||
CVE-2023-5037,0,0,f164cfec8e7f1d00c559d76365ccbd071d432f38c0203cbb40689a289695bcb4,2024-06-25T12:24:17.873000
|
||||
CVE-2023-50370,0,0,cb41cea2750640931e440868ffef0cc7f55b13bd1e4ad5828cdfccae735b6980,2023-12-18T19:02:02.957000
|
||||
CVE-2023-50371,0,0,04d4e098cc36a4f0bfdfb2f80d9ef226cb1335fcf83d29c3ea30e956873d64b8,2023-12-18T20:14:34.887000
|
||||
CVE-2023-50372,0,0,f1e1782fe08d93899978169515a94f6ddbf7dcded46e93a6577a24065511b513,2023-12-20T04:28:48.440000
|
||||
@ -237040,7 +237043,7 @@ CVE-2023-50376,0,0,c951f73eaa1568ec16d7bbf28755aacf2580409c4a177851a557b18edbeae
|
||||
CVE-2023-50377,0,0,3acd97ab69c2403c419288f2e19070989327aa6f1425e1a9c076820c259b93c2,2023-12-27T21:34:56.883000
|
||||
CVE-2023-50378,0,0,0f4c193757a21745622df68ec0aa88b8a213c4603a70a54e94c4c05a8dadb60b,2024-05-01T18:15:11.097000
|
||||
CVE-2023-50379,0,0,2ba768024158d3957bf97073914ab21cf6e76e13687c6569b9647fa3455e4c0b,2024-02-27T14:20:06.637000
|
||||
CVE-2023-5038,0,1,c668300db7cd4659815bd5c9c5d6f057352641e6622bd7161af1cb7ae2d6857d,2024-06-25T12:24:17.873000
|
||||
CVE-2023-5038,0,0,c668300db7cd4659815bd5c9c5d6f057352641e6622bd7161af1cb7ae2d6857d,2024-06-25T12:24:17.873000
|
||||
CVE-2023-50380,0,0,b5737d428cd7d3280b11a55da8c282450fdebb25171b34cbfbfc4de989e3a9f5,2024-02-28T14:06:45.783000
|
||||
CVE-2023-50386,0,0,eb9175c624998374fffbb8bbdcfbc3fcd759c84a0c5cafd0e6294c2d31318a7f,2024-02-15T18:40:48.837000
|
||||
CVE-2023-50387,0,0,86a696af4d06d31d7c5b6089ba1f856732aed20b18c54efa9645210962ecc2d6,2024-06-10T17:16:15.963000
|
||||
@ -239658,7 +239661,7 @@ CVE-2023-6193,0,0,b9900119542cd00ca545fa465375df17aaa2236304c15239a12e8730d3c671
|
||||
CVE-2023-6194,0,0,adca1836721719b5860e52cb41398c44be6db56a1fe0603258d70cab514c2618,2023-12-13T22:02:56.613000
|
||||
CVE-2023-6196,0,0,f56d61f9e2bd859b9d4b61f6a34e06caffb31a0f56e7eb46b17c194be4b8ce85,2023-11-25T02:20:08.637000
|
||||
CVE-2023-6197,0,0,c4382b52f534913e65ee4b1feb523e73025e33dfe7d74d8aade2f3fac6e8f295,2023-11-25T02:19:51.733000
|
||||
CVE-2023-6198,0,1,49c7fb0ced8e0330c64c8b0049c2cc20f5df37d29946bf7b0cae32f72f1e2627,2024-06-25T12:24:17.873000
|
||||
CVE-2023-6198,0,0,49c7fb0ced8e0330c64c8b0049c2cc20f5df37d29946bf7b0cae32f72f1e2627,2024-06-25T12:24:17.873000
|
||||
CVE-2023-6199,0,0,12541221a80e0f3a78050b48fb01f9ad223a7ac2b781b75a0ff9d1a5e3de1cb1,2024-06-07T14:12:05.897000
|
||||
CVE-2023-6200,0,0,6ad93b2827d0905ddada23ed9c26c8cd7cbada143bc86cea06b89b646e3f7634,2024-02-02T15:38:42.870000
|
||||
CVE-2023-6201,0,0,e641a830aa857fff950829529f9d4b150c6030d683c3c3799f55892ea8553251,2023-12-05T07:15:11.860000
|
||||
@ -243413,6 +243416,7 @@ CVE-2024-21823,0,0,74719d5742bbb3be35d0b1cdb36c92652040d8c6a54fcb1cde7d61e193ab5
|
||||
CVE-2024-21824,0,0,3bddb01433a875d84e1ff57d3fa88062c16a6aea3448fe5a7afcbbae2986da28,2024-03-18T12:38:25.490000
|
||||
CVE-2024-21825,0,0,1b47c3f0e2bb27ba429b8b0ff73ec4e737b53c8991d881956fe812d8a2d73bd5,2024-02-26T18:15:07.390000
|
||||
CVE-2024-21826,0,0,db46d5d52cce4b3faca9d1878c694b0b714eba4ae02907457ece6927043134cc,2024-03-04T13:58:23.447000
|
||||
CVE-2024-21827,1,1,0443be3f57aa6ab0c6062e2734badab47b95fdabb1da7fbd74a5e859487043a6,2024-06-25T15:15:11.783000
|
||||
CVE-2024-21828,0,0,0250a3d20529676ff2fa7d6979ac4bf5ca8f87e28525553552c2706e5c45d931,2024-05-17T18:36:05.263000
|
||||
CVE-2024-2183,0,0,d2fc5903dd12fc59dfdda0bd9c528b50368a6c295b02593ecad0115a711b3755,2024-04-10T13:23:38.787000
|
||||
CVE-2024-21831,0,0,80cadbf10c91b711fa3e2dfce5f1386f490c30f51eb3986f8ac8665da82300fe,2024-05-17T18:36:05.263000
|
||||
@ -243622,7 +243626,7 @@ CVE-2024-22163,0,0,c83e1ba1846b1fce21c84865fbae3a4da5f3738a4cbae342d708ebb4390db
|
||||
CVE-2024-22164,0,0,4dea6ba8f1b0f10f3e8121d8aed37ba56e363e8df8631ec93a1e9db3a5dd3c55,2024-04-10T01:15:17.713000
|
||||
CVE-2024-22165,0,0,556c59738fa3a69567bd56c76c812950d0a8343ccfbb26557b3cdc60c3bc8d41,2024-04-10T01:15:17.890000
|
||||
CVE-2024-22167,0,0,6c810ad0cbcba53d787a1a5d3c16777ada312b7a75654a62e0a2b663baaf8fed,2024-06-24T23:15:10.280000
|
||||
CVE-2024-22168,0,1,361b9285da035556b893923fe386dbf458ddb137cab6952092f4005fe06fba10,2024-06-25T12:24:17.873000
|
||||
CVE-2024-22168,0,0,361b9285da035556b893923fe386dbf458ddb137cab6952092f4005fe06fba10,2024-06-25T12:24:17.873000
|
||||
CVE-2024-2217,0,0,07b67ca85e13a2c6962db1475a9d0f8a931b674f51497121f9a33c8078bd4b4f,2024-04-10T19:49:51.183000
|
||||
CVE-2024-22177,0,0,1ff2297e612a95969b8693bc6a53ecafa7223eba267b1cfe298d3bc1fedfbe99,2024-04-02T12:50:42.233000
|
||||
CVE-2024-22178,0,0,894383da751aaa1046c611146ada59662a01e512644efee9e31c744bf34674c7,2024-04-03T17:24:18.150000
|
||||
@ -243797,7 +243801,7 @@ CVE-2024-22380,0,0,fbb17e03b7392116b029e62cf5fc227ae3083f2acc9171774ca51468933ea
|
||||
CVE-2024-22382,0,0,794bb38486bda8b27dc8f67ecedfc3d38e34616c9029ee0f738dfbf4c6312f15,2024-05-17T18:36:05.263000
|
||||
CVE-2024-22383,0,0,810a6e86f28ef493260b232f9a886a5828bc2cb5687e22ad7a4e8bfc9a3765be,2024-03-05T13:41:01.900000
|
||||
CVE-2024-22384,0,0,22d927b3eda23e776929f3eee7e12761fd0a5866a79fd2edf20febc4242f7c70,2024-05-17T18:36:05.263000
|
||||
CVE-2024-22385,0,1,83fe63d5df6ef3c9cc40e2c081e8f947a095c2af1ce72eddf83967c3653b9c45,2024-06-25T12:24:17.873000
|
||||
CVE-2024-22385,0,0,83fe63d5df6ef3c9cc40e2c081e8f947a095c2af1ce72eddf83967c3653b9c45,2024-06-25T12:24:17.873000
|
||||
CVE-2024-22386,0,0,9bb868760c88683007f1f54485a980666afe5aeeb8bc008d8d811fea3dbfe22d,2024-02-10T04:05:26.383000
|
||||
CVE-2024-22388,0,0,c4d155a1650cf8d6f3af35aa33a3624b01d880288d632870cec483f12be1e88c,2024-02-14T20:59:09.660000
|
||||
CVE-2024-22389,0,0,96781b551653662b24bed6c6167841567f0e5e4776b3fb44064036280367773a,2024-02-14T18:04:45.380000
|
||||
@ -244151,26 +244155,26 @@ CVE-2024-23137,0,0,a3dfbd98c2dc1ba45435d76ef85744b5c19037c4a2624aa7d2b0ff334bf9c
|
||||
CVE-2024-23138,0,0,6b090492cd013e3e650e24e59443f58d52996df0034c406247881d7acc03e3d0,2024-03-18T01:13:31.203000
|
||||
CVE-2024-23139,0,0,3d593be31839f5d86966b7965df31cd04e51b507bda09669a8893d4214cfafec,2024-03-18T01:13:31.203000
|
||||
CVE-2024-2314,0,0,ed96f7e1946840e93c2198da1169aca1bfa11c5d8065acfea02e9fe912a3e6df,2024-03-11T01:32:29.610000
|
||||
CVE-2024-23140,0,1,45b423c206cd93b0b6587c84982cd33f24d34738ace5bfaf02bb18136b0e15fd,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23141,0,1,6156b394eb6e79fa9a17bebcd5fc737f297f563b0194ca943ea0eebf0754097c,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23142,0,1,096985f813211f49425cf60983ae8768243f7ea9929c029b5af48e4447b52c16,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23143,0,1,e04fc7de80232e9def9aad9bd71721080df1a77e6f21130a4d79e9cbce277124,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23144,0,1,c31cb5fec76300a6d3c629f8f5885b765d4ad3d1e91354d74cfbe57aba8e8838,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23145,0,1,7c671b2f51bfa6aa5016830bb862be73a0a0eece1d7798fa0500ce17c76a3e32,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23146,0,1,e81497684c72b1bd3cc1af5deb5f9b4c7206bf86962657914742725702890fd4,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23147,0,1,c6ac950efc2e67ad0d6affbb86588e8ab4329ae68b5c8063ce63e1f6470b5acc,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23148,0,1,0cc3f09ea3cee3bb4d4c6d1a5f626cccbc1087c36c80a1c06bb3c47d72cbeda6,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23149,0,1,242d8caf5deb75b9fbd1f60b635cd54b2b743a36dfa977ecbeafb68c5bb6441d,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23150,0,1,e73e4adcb67ba199ececb516776757e2a7c933e76c1c7239fcf3ff9aaf2eb649,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23151,0,1,b29d40e3cefbbec81e68405bffac98bc5e7c10dc76dec3d6cd672fea6115bc13,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23152,0,1,c5c382b3ba462bda0286084969263304e92f041f435cc9b3b38363a1158fa042,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23153,0,1,9d7347511f82e37de9feda8cd1fc6313bd959f7bc9d299f8d211f89badb7ac92,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23154,0,1,a6c6e4310a54363850435549aa4e4279e6a151c01e421c1f811c260fef759458,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23155,0,1,b5a5ca511786ec9141eb382a511c04b70c91f341a2813d1c1ec6e9c48c8d96b1,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23156,0,1,e1f5520a59ddec83f572dcf695fe92cff509dd03c13f3d318df346b51f9b5e3c,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23157,0,1,6ac68778d6c1e076b700f51d7d7684dcf94e8bd1ae968969a45b3908e8cb1e56,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23158,0,1,b84602d24a72e01827a3d987ac0b33544320a773792ea1b6a27fefb21d82fde6,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23159,0,1,867090c90435d6cc8f32c15176430032240814c1a4a9ec9e13851a45e57591d8,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23140,0,0,45b423c206cd93b0b6587c84982cd33f24d34738ace5bfaf02bb18136b0e15fd,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23141,0,0,6156b394eb6e79fa9a17bebcd5fc737f297f563b0194ca943ea0eebf0754097c,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23142,0,0,096985f813211f49425cf60983ae8768243f7ea9929c029b5af48e4447b52c16,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23143,0,0,e04fc7de80232e9def9aad9bd71721080df1a77e6f21130a4d79e9cbce277124,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23144,0,0,c31cb5fec76300a6d3c629f8f5885b765d4ad3d1e91354d74cfbe57aba8e8838,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23145,0,0,7c671b2f51bfa6aa5016830bb862be73a0a0eece1d7798fa0500ce17c76a3e32,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23146,0,0,e81497684c72b1bd3cc1af5deb5f9b4c7206bf86962657914742725702890fd4,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23147,0,0,c6ac950efc2e67ad0d6affbb86588e8ab4329ae68b5c8063ce63e1f6470b5acc,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23148,0,0,0cc3f09ea3cee3bb4d4c6d1a5f626cccbc1087c36c80a1c06bb3c47d72cbeda6,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23149,0,0,242d8caf5deb75b9fbd1f60b635cd54b2b743a36dfa977ecbeafb68c5bb6441d,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23150,0,0,e73e4adcb67ba199ececb516776757e2a7c933e76c1c7239fcf3ff9aaf2eb649,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23151,0,0,b29d40e3cefbbec81e68405bffac98bc5e7c10dc76dec3d6cd672fea6115bc13,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23152,0,0,c5c382b3ba462bda0286084969263304e92f041f435cc9b3b38363a1158fa042,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23153,0,0,9d7347511f82e37de9feda8cd1fc6313bd959f7bc9d299f8d211f89badb7ac92,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23154,0,0,a6c6e4310a54363850435549aa4e4279e6a151c01e421c1f811c260fef759458,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23155,0,0,b5a5ca511786ec9141eb382a511c04b70c91f341a2813d1c1ec6e9c48c8d96b1,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23156,0,0,e1f5520a59ddec83f572dcf695fe92cff509dd03c13f3d318df346b51f9b5e3c,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23157,0,0,6ac68778d6c1e076b700f51d7d7684dcf94e8bd1ae968969a45b3908e8cb1e56,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23158,0,0,b84602d24a72e01827a3d987ac0b33544320a773792ea1b6a27fefb21d82fde6,2024-06-25T12:24:17.873000
|
||||
CVE-2024-23159,0,0,867090c90435d6cc8f32c15176430032240814c1a4a9ec9e13851a45e57591d8,2024-06-25T12:24:17.873000
|
||||
CVE-2024-2316,0,0,b19568c74ff3303e21c6f779d3f7251e97a598ce30370572128b37d7e3b8336b,2024-05-17T02:38:09.927000
|
||||
CVE-2024-2317,0,0,a696c117ae514f4e733f3f16d6619ea5748142dccfe9e4a63d423b5b3c8772c3,2024-05-17T02:38:10.027000
|
||||
CVE-2024-23170,0,0,13146081a2acee1dfc9938d9131a35ea909e72090f99ea62e52485862035b1b1,2024-02-22T03:15:08.297000
|
||||
@ -247930,8 +247934,8 @@ CVE-2024-28824,0,0,5a9476ae0fdb0520e3a986c832f5f9e27a50da5cb3aa11e06910544296f0e
|
||||
CVE-2024-28825,0,0,9e6f2228e06896e59bb560ffc81c60a9a09c25eeaded2122eaaaf9d670949d13,2024-04-24T13:39:42.883000
|
||||
CVE-2024-28826,0,0,af714d67b245e2002324726263b60e676423e9fa16954adb4190fa57b660a93f,2024-05-29T13:02:09.280000
|
||||
CVE-2024-2883,0,0,e66be81816608580e2e81ffcb02cca4ae9a2aa5cbea60907cc2e1d80cffbaf4a,2024-03-29T04:15:08.743000
|
||||
CVE-2024-28831,1,1,53daadc6768590b1e9dcc34c033a018728a5349f5fb865309e9216560e5790eb,2024-06-25T12:24:17.873000
|
||||
CVE-2024-28832,1,1,e20e133fb158c153d5c99472d0490b974e0599ab693822dcae94c1e3de7df5f9,2024-06-25T12:24:17.873000
|
||||
CVE-2024-28831,0,0,53daadc6768590b1e9dcc34c033a018728a5349f5fb865309e9216560e5790eb,2024-06-25T12:24:17.873000
|
||||
CVE-2024-28832,0,0,e20e133fb158c153d5c99472d0490b974e0599ab693822dcae94c1e3de7df5f9,2024-06-25T12:24:17.873000
|
||||
CVE-2024-28833,0,0,c28d0621123671b94853f5763fc92ce8098ea4f6621d0443f950677dd9d3b57a,2024-06-12T17:53:57.103000
|
||||
CVE-2024-28834,0,0,af4d9c1dfe16b4591e02664fd7ad00b6706b6af449eca3208820bfc8e9b376f7,2024-06-10T17:16:24.560000
|
||||
CVE-2024-28835,0,0,7ffb3867ffb469cae5c61eed57191c292b3344e17f215833454f077170fed24a,2024-05-16T23:15:47.883000
|
||||
@ -249465,7 +249469,7 @@ CVE-2024-31107,0,0,b69b8308dca1c03345bc5c4ddd842b58a0a34c0913dd806068e33a5a7ea13
|
||||
CVE-2024-31108,0,0,e198cb5e9a429619e29a035a74c1776abb842099061e8ee67790619ad5916e5b,2024-04-01T01:12:59.077000
|
||||
CVE-2024-31109,0,0,3766de0285c03422fb77f1fd2a4106a3e09e42f3bd086e20e704d883507e7c67,2024-04-02T20:31:58.463000
|
||||
CVE-2024-31110,0,0,cc696090cfd929541a1ca3b42d624a66dc89644b2049217890247603bee15f04,2024-04-01T01:12:59.077000
|
||||
CVE-2024-31111,1,1,3c33f0dd94b30fb54892688e318f10e292610205a90e63772c776e941f0b6f71,2024-06-25T13:15:49.383000
|
||||
CVE-2024-31111,0,0,3c33f0dd94b30fb54892688e318f10e292610205a90e63772c776e941f0b6f71,2024-06-25T13:15:49.383000
|
||||
CVE-2024-31112,0,0,4c0b6d124815c5fbc71413fa9db9ceb5adb5efe4d3f57754f8397ffa9f3c1ac9,2024-04-01T01:12:59.077000
|
||||
CVE-2024-31113,0,0,8671ed7f526e5f0c07d7c719521b3a251fbbb02fdb46ea221592e94e946d87b8,2024-05-14T16:13:02.773000
|
||||
CVE-2024-31114,0,0,2db2f19bbb762fd0846a2fd0f4c21316984760b44cf0e285d2fa1b7eb4e97fa5,2024-04-01T01:12:59.077000
|
||||
@ -250087,6 +250091,7 @@ CVE-2024-32107,0,0,b90c8135a82473fde7e5bf44c3c1cf9d7846ba95270115659d7d68306d87c
|
||||
CVE-2024-32108,0,0,950a29a68ef37c40439ae0dcf3c3d4b039242eaece664c349c7d4089e193ee6e,2024-04-11T13:30:38
|
||||
CVE-2024-32109,0,0,4ab4248625b2b88c43ecf2bed644e80e80c54bafb94ddc41cebae0bbd84f78ff,2024-04-29T09:15:07.707000
|
||||
CVE-2024-3211,0,0,d6d8ef851a76d01f08b13c4c6093534cf0125e4133f007b8f3a299cb3bb38192,2024-04-12T12:43:46.210000
|
||||
CVE-2024-32111,1,1,ca759a18f28f89e667f906f772c5e58c5ca127793b3a6033b9631417f54605ca,2024-06-25T14:15:11.630000
|
||||
CVE-2024-32112,0,0,2df62c2ad1478d07a612eff17f984ad78c51d3b47027012c1c38076227812cd3,2024-04-11T12:47:44.137000
|
||||
CVE-2024-32113,0,0,30f5550c85c7aa669125053de7ee7f1fe700c5bf3550eeb727f2adbc5c6683ff,2024-06-10T18:15:32.687000
|
||||
CVE-2024-32114,0,0,f86e794836506b6f3debc92c788cbea6d342740812ff0770c4838ed0614d76f2,2024-05-02T13:27:25.103000
|
||||
@ -250284,7 +250289,7 @@ CVE-2024-32482,0,0,e0309808bf3b2543b39750b9d9b0b794ac723e1476b62ac8f4870801d35fc
|
||||
CVE-2024-32487,0,0,3964df55462d4b69b3a47831a0425ebab17556f2b889b4db15caceabcb50c1e8,2024-06-10T18:15:33.640000
|
||||
CVE-2024-32488,0,0,6ce6bcee8af0a677e98d2bf7a3efd66cf8a3e580423515387116f39d710ba974,2024-04-15T13:15:31.997000
|
||||
CVE-2024-32489,0,0,cbc8895e7f5e99c09f7bd505220fcc5514b4573939580e3f381a933acf3c9ef0,2024-04-15T13:15:31.997000
|
||||
CVE-2024-3249,0,1,76c646e2435d001bf01037ff3fd93961dd050fc46c496185359532e97ed741fe,2024-06-25T12:24:17.873000
|
||||
CVE-2024-3249,0,0,76c646e2435d001bf01037ff3fd93961dd050fc46c496185359532e97ed741fe,2024-06-25T12:24:17.873000
|
||||
CVE-2024-32491,0,0,0ef1d844738414cdd89361991aa89a441a6f02a4affed1e8b95f4fdb3144ccd8,2024-04-30T13:11:16.690000
|
||||
CVE-2024-32492,0,0,fbdbe605158ebb859c2c70df9471eb17e0db1ec1e36b709d629be4fcd2dc71e5,2024-04-30T13:11:16.690000
|
||||
CVE-2024-32493,0,0,99ad93b821b9120b3f9479fdbc637b6bf229eed0c91d108f68192b4be876e696,2024-04-30T13:11:16.690000
|
||||
@ -250611,7 +250616,7 @@ CVE-2024-32836,0,0,b79abde0b1fb00c320171e12e4361e475bc7a0910a68d24b478ff673cfed4
|
||||
CVE-2024-32849,0,0,911a7e29746f175fb19c3c12d66bd3772f826858bf332bb5f36bdbd074fef2ea,2024-06-11T13:54:12.057000
|
||||
CVE-2024-3285,0,0,ea17e16acaa3172cbcc052cf9bfb1b3e7ee2b004434b062b8e67c1c1ed8bff14,2024-04-11T12:47:44.137000
|
||||
CVE-2024-32850,0,0,e2d3ad4052fd34b4d59fd5011cddd317b3140c292d5e36efda816fa3450f0d6b,2024-05-31T13:01:46.727000
|
||||
CVE-2024-32855,0,1,8cb97336fb50074b0c95cfbd9b638b900dee92e764d86802a9c150ab163d7f17,2024-06-25T12:24:17.873000
|
||||
CVE-2024-32855,0,0,8cb97336fb50074b0c95cfbd9b638b900dee92e764d86802a9c150ab163d7f17,2024-06-25T12:24:17.873000
|
||||
CVE-2024-32856,0,0,c66e0032823df2ab62cafb6d5a2421b4fad1250be2cc10f286c67e596ee15268,2024-06-13T18:35:19.777000
|
||||
CVE-2024-32858,0,0,79d18eec7b44766d877a51554ad6fffacddeb7b9d7d3ee892654656112996acb,2024-06-13T18:35:19.777000
|
||||
CVE-2024-32859,0,0,1cd4720bd8930641d05bcace2e14674b0b863b6c41ac70fe7386b92bb7a292b0,2024-06-13T18:35:19.777000
|
||||
@ -251173,7 +251178,7 @@ CVE-2024-33880,0,0,6e36b0fb5fe2b32e2817592006df5d8a4056f26237538fac1581301ce44f3
|
||||
CVE-2024-33881,0,0,fe245f6a598cf69e9a799928f3ddd050be59db62f7dc0626f6b1e68c6a66b11a,2024-06-24T19:26:35.967000
|
||||
CVE-2024-33883,0,0,c3d4ca3457f68fb83203c8f7576ab4f6d2af7e59b5901cd64501370e80dea4a9,2024-06-10T17:16:28.217000
|
||||
CVE-2024-33891,0,0,dbfd0a46c344c55dc0dc7b94e4bd09b3968a700bb28b10a9c34051909c1cf008,2024-04-29T12:42:03.667000
|
||||
CVE-2024-33898,0,1,fce817d892a67a37756f05aa1b381dbae2c15aaf04344df974a9160309f3b986,2024-06-25T12:24:17.873000
|
||||
CVE-2024-33898,0,0,fce817d892a67a37756f05aa1b381dbae2c15aaf04344df974a9160309f3b986,2024-06-25T12:24:17.873000
|
||||
CVE-2024-33899,0,0,a7d045f337995c763b9659e78955fd4f45f7736540a0f2de3af7e2f3a386fc9f,2024-05-21T17:15:08.907000
|
||||
CVE-2024-33900,0,0,22109cfa8453d6fac86d432cd9f4ebf584447af3cc6b5e9bb8f885da3aec714f,2024-06-06T18:15:16.170000
|
||||
CVE-2024-33901,0,0,75e1f4bc73d73047b93bc18aaf649342f4e272c76affbb46aef808d0b0e62e7d,2024-05-21T17:15:09.143000
|
||||
@ -251334,8 +251339,8 @@ CVE-2024-34129,0,0,d3dc43049d80f783794d9399825be80ea683040539452e8a7be93120bda8c
|
||||
CVE-2024-3413,0,0,8bf7e231eaef8a1fb270998ee982f12463c5a7d17ff17eb8735dbc8fc584bd57,2024-05-17T02:39:54.073000
|
||||
CVE-2024-34130,0,0,89584332f9dd3125064424fac4aabed722eb075df05ba25c9a02617aa8a6856c,2024-06-13T18:35:19.777000
|
||||
CVE-2024-3414,0,0,69231815197d8c759df4a79a39950c8d4f6258471ea32f1c29be1a7038b6ec47,2024-05-17T02:39:54.160000
|
||||
CVE-2024-34141,0,1,0328c765f70a818d854683e04e980b09961525d5dd8879ace860d192776bc00d,2024-06-25T12:24:17.873000
|
||||
CVE-2024-34142,0,1,c526b1831039e375b135e55cb58a71752c1b1dd1103a82d9d4050eb194a5f7f7,2024-06-25T12:24:17.873000
|
||||
CVE-2024-34141,0,0,0328c765f70a818d854683e04e980b09961525d5dd8879ace860d192776bc00d,2024-06-25T12:24:17.873000
|
||||
CVE-2024-34142,0,0,c526b1831039e375b135e55cb58a71752c1b1dd1103a82d9d4050eb194a5f7f7,2024-06-25T12:24:17.873000
|
||||
CVE-2024-34144,0,0,161e418bd2efea8731bcf0c84ef4939748aabfddbc9f310a20f204f2b5cb4158,2024-05-02T18:00:37.360000
|
||||
CVE-2024-34145,0,0,8976018515653d9edfc24ef743cee1c2f455c68450e5a16824609e8151c9f246,2024-05-02T18:00:37.360000
|
||||
CVE-2024-34146,0,0,57b55472d7ef8f36d24d72d33ce2a7a08770dabb111aaf45da4e0803162f240d,2024-05-02T18:00:37.360000
|
||||
@ -251409,8 +251414,8 @@ CVE-2024-3430,0,0,26511d7640da51b7d570c3e3e64dcd51a1ae1a874f887e17d0418717614048
|
||||
CVE-2024-34308,0,0,a9106d3038ea0861ae87e336ed29b09bed158322011782013165b4fda14eb836,2024-05-14T16:12:23.490000
|
||||
CVE-2024-3431,0,0,455a9b01059963fcb0a3456cd2358856e44f5db237eb4ee1c03f1b9fc99bc502,2024-05-17T02:39:55.597000
|
||||
CVE-2024-34310,0,0,66df9c89974c6825f0e7d33b795a4985a07b16f5413b2fe4d7327eaf5fe9cf52,2024-05-14T16:12:23.490000
|
||||
CVE-2024-34312,0,1,42ebb218a5fc0e270a6fe4891325f23ff4f98cc82876e3ff17e1e916fd05efa1,2024-06-25T12:24:17.873000
|
||||
CVE-2024-34313,0,1,15128d3b92dd6f905ce9cb237344765c2f7b5ca6a8a27d077c1112c393fdd36d,2024-06-25T12:24:17.873000
|
||||
CVE-2024-34312,0,0,42ebb218a5fc0e270a6fe4891325f23ff4f98cc82876e3ff17e1e916fd05efa1,2024-06-25T12:24:17.873000
|
||||
CVE-2024-34313,0,0,15128d3b92dd6f905ce9cb237344765c2f7b5ca6a8a27d077c1112c393fdd36d,2024-06-25T12:24:17.873000
|
||||
CVE-2024-34314,0,0,0107b5ea4eb283c867d7bcf45b9a1b1b8c09b93e02d17eb326a855e2eae22472,2024-05-07T20:07:58.737000
|
||||
CVE-2024-34315,0,0,36ad48654c2445849405bf408af6abf3947e9c641efabc13ad4dfd6e6d40c74e,2024-05-07T20:07:58.737000
|
||||
CVE-2024-3432,0,0,c54577582bdbc3937c3144599074e1b9739b0a7ed62b33767d62fe9e77c22e2b,2024-05-17T02:39:55.693000
|
||||
@ -251786,12 +251791,12 @@ CVE-2024-34974,0,0,519613cdbc229706fafa4388ed0de03632496af6e2fd3a5450a4996c9b966
|
||||
CVE-2024-3498,0,0,5a88bde38eadc03f84603569fdec38fe83a6606de78277714e78faa80a5569cc,2024-06-17T12:42:04.623000
|
||||
CVE-2024-34982,0,0,ef460a32eb987949d8c2a373dc7919974bee9f6e2b2a3c53ead2e4138396cd2a,2024-05-17T18:35:35.070000
|
||||
CVE-2024-34987,0,0,262d3ccca2f7e7df7be241d8326c4714ae2b44466572454690af1a110c26db06,2024-06-18T19:15:59.873000
|
||||
CVE-2024-34988,0,1,b3467eb38646e4d8a6df0704cef40b0e453cfb971357b3ffba531bed667671a0,2024-06-25T12:24:17.873000
|
||||
CVE-2024-34988,0,0,b3467eb38646e4d8a6df0704cef40b0e453cfb971357b3ffba531bed667671a0,2024-06-25T12:24:17.873000
|
||||
CVE-2024-34989,0,0,a75d8ba41908a8d4a011a34c5328e77e756e2c0766173d0c2f6d80fbf3e9fc4f,2024-06-24T12:57:36.513000
|
||||
CVE-2024-3499,0,0,38e1f3a6ce5aff826b19a73a4f796b980cc1161eaf58f8fada2f6f87e54573a4,2024-05-02T18:00:37.360000
|
||||
CVE-2024-34990,0,0,954e9cad148d93781e06727d2db5247f2f552d787151dbf2d18611cf67a55aa3,2024-06-20T12:43:25.663000
|
||||
CVE-2024-34991,0,1,780a03bdc762fbb7188d00cefe07a50db49ebd1ee5a53f96d48d3d1cd68fcaf7,2024-06-25T12:24:17.873000
|
||||
CVE-2024-34992,0,1,497a097d0e0e3b9258450d28cd0c4bb5357bfd0b4b76c0b1ba867b7545310b74,2024-06-25T12:24:17.873000
|
||||
CVE-2024-34991,0,0,780a03bdc762fbb7188d00cefe07a50db49ebd1ee5a53f96d48d3d1cd68fcaf7,2024-06-25T12:24:17.873000
|
||||
CVE-2024-34992,0,0,497a097d0e0e3b9258450d28cd0c4bb5357bfd0b4b76c0b1ba867b7545310b74,2024-06-25T12:24:17.873000
|
||||
CVE-2024-34993,0,0,88520e58b3968956ee44832ef9bca602378dea4f2524d5113c2eaf5052b0d026,2024-06-20T12:43:25.663000
|
||||
CVE-2024-34994,0,0,2d37bfb277f5e0193ed8c82676312446b855d68532288e194c45848265ea0e23,2024-06-20T12:43:25.663000
|
||||
CVE-2024-34995,0,0,ff7295f94bdc66d877986c97deb7981eb83c3e840f72ac7a8ee7543b9685ad7b,2024-05-24T18:09:20.027000
|
||||
@ -252828,9 +252833,9 @@ CVE-2024-36678,0,0,b40bcef505929051186338018132624ab6cbb572787979182cd8c6d269894
|
||||
CVE-2024-36679,0,0,8821e4eea3e4aeed8d65a516b06861a5717cd50e7124b3274b0fd92bade0c86c,2024-06-20T12:43:25.663000
|
||||
CVE-2024-3668,0,0,49d55bc0cfb418bcfc9437877f4056373badba24215047598ce2c0a1a6dfb761,2024-06-10T02:52:08.267000
|
||||
CVE-2024-36680,0,0,d0d5945762cb2164a2282b055a60546e9c27ff729e4565b5f8f11eb263a62624,2024-06-20T12:43:25.663000
|
||||
CVE-2024-36681,0,1,ccf99be2d41fa72a8eb3bbea6be382a291c87a641b5a5b5f4cd17b9c70b6a3ff,2024-06-25T12:24:17.873000
|
||||
CVE-2024-36682,0,1,866e96df4efc86beadf4475f6c4cd90092f5a3c14d138f91c23e3822ce3f1b58,2024-06-25T12:24:17.873000
|
||||
CVE-2024-36683,0,1,44182fb4ce182abc4714324cf5c81e3c173647eec66ba51bd23b657303771b58,2024-06-25T12:24:17.873000
|
||||
CVE-2024-36681,0,0,ccf99be2d41fa72a8eb3bbea6be382a291c87a641b5a5b5f4cd17b9c70b6a3ff,2024-06-25T12:24:17.873000
|
||||
CVE-2024-36682,0,0,866e96df4efc86beadf4475f6c4cd90092f5a3c14d138f91c23e3822ce3f1b58,2024-06-25T12:24:17.873000
|
||||
CVE-2024-36683,0,0,44182fb4ce182abc4714324cf5c81e3c173647eec66ba51bd23b657303771b58,2024-06-25T12:24:17.873000
|
||||
CVE-2024-36684,0,0,04438f1f2d344e3fc16c304c18197337a565e4aba220854d4ffac5c0b815632e,2024-06-20T12:43:25.663000
|
||||
CVE-2024-36691,0,0,eb8762b05fd0460b1321a45df3641c06640e12f5ae9e65b313352697eb6ff0d2,2024-06-13T18:36:09.010000
|
||||
CVE-2024-36699,0,0,4c8862d154ba42ed56a4ce8bf1e6f3cc34d74fcc619fdd49ec3e97bb2690a0fe,2024-06-14T15:15:50.967000
|
||||
@ -253000,16 +253005,16 @@ CVE-2024-36978,0,0,880aef92604c27e5578b53720d6ee7e213e82be3de9f91ee8b3173e75f4b8
|
||||
CVE-2024-36979,0,0,b5c86fe1e151f03cc7911f2db726f75e908559d8b3402d6614d6fdbd11ceb079,2024-06-20T12:44:01.637000
|
||||
CVE-2024-3698,0,0,13b4029eb6179dbe788598788e16556a1995d850ddfc4af1ee0c4e86961a3a21,2024-05-17T02:40:04.800000
|
||||
CVE-2024-3699,0,0,6e64dedcb1ec83e842b9c3ed18b374381a62ef4f7982a43d9405eeb95e55d0fc,2024-06-12T17:53:09.130000
|
||||
CVE-2024-36999,0,1,e623ac69d78c1d872fd9d23ebed97cd66e8b6293086bcd7909366177ce71d4fe,2024-06-25T12:24:17.873000
|
||||
CVE-2024-36999,0,0,e623ac69d78c1d872fd9d23ebed97cd66e8b6293086bcd7909366177ce71d4fe,2024-06-25T12:24:17.873000
|
||||
CVE-2024-3700,0,0,f1913b84964a9a87ca4f78bbad55a262819a35385e2c066c91eaa7c4a1891262,2024-06-12T17:51:52.710000
|
||||
CVE-2024-37000,0,1,a7ce938c2375111dcdf9fa56d08df7bf8307bd849e0b0ce2b6f89977fd5cc422,2024-06-25T12:24:17.873000
|
||||
CVE-2024-37001,0,1,4d1c5c28a7e84d12a719a4e4c73b1ebd37cf9a762fd9671fffb22a1b37047fa8,2024-06-25T12:24:17.873000
|
||||
CVE-2024-37002,0,1,1d8ea789fd94d1d9e45333bd1688c87d3bf0a220ea9399871cecf34bec5c4335,2024-06-25T12:24:17.873000
|
||||
CVE-2024-37003,0,1,42b026fd72bb40667980364b96d99f029ab43db04399d50d09f7cbff523326e8,2024-06-25T12:24:17.873000
|
||||
CVE-2024-37004,0,1,8876c8d2dd305512fdd4804d192c33aa2b5a192415a76bd52d7210f63087a080,2024-06-25T12:24:17.873000
|
||||
CVE-2024-37005,0,1,930bf62043bdff1a520d38cced5d6267328c06e2533705ccaa1b2c49a23a9e24,2024-06-25T12:24:17.873000
|
||||
CVE-2024-37006,0,1,d327f4f7ed2697ce1c5c1578094835d020ae3c80106e42d3c9884d76d8adcd98,2024-06-25T12:24:17.873000
|
||||
CVE-2024-37007,0,1,f1ec814e6ec207423c623e10fc49c73b92ce1524507fa65a91b9138d6cc06e4b,2024-06-25T12:24:17.873000
|
||||
CVE-2024-37000,0,0,a7ce938c2375111dcdf9fa56d08df7bf8307bd849e0b0ce2b6f89977fd5cc422,2024-06-25T12:24:17.873000
|
||||
CVE-2024-37001,0,0,4d1c5c28a7e84d12a719a4e4c73b1ebd37cf9a762fd9671fffb22a1b37047fa8,2024-06-25T12:24:17.873000
|
||||
CVE-2024-37002,0,0,1d8ea789fd94d1d9e45333bd1688c87d3bf0a220ea9399871cecf34bec5c4335,2024-06-25T12:24:17.873000
|
||||
CVE-2024-37003,0,0,42b026fd72bb40667980364b96d99f029ab43db04399d50d09f7cbff523326e8,2024-06-25T12:24:17.873000
|
||||
CVE-2024-37004,0,0,8876c8d2dd305512fdd4804d192c33aa2b5a192415a76bd52d7210f63087a080,2024-06-25T12:24:17.873000
|
||||
CVE-2024-37005,0,0,930bf62043bdff1a520d38cced5d6267328c06e2533705ccaa1b2c49a23a9e24,2024-06-25T12:24:17.873000
|
||||
CVE-2024-37006,0,0,d327f4f7ed2697ce1c5c1578094835d020ae3c80106e42d3c9884d76d8adcd98,2024-06-25T12:24:17.873000
|
||||
CVE-2024-37007,0,0,f1ec814e6ec207423c623e10fc49c73b92ce1524507fa65a91b9138d6cc06e4b,2024-06-25T12:24:17.873000
|
||||
CVE-2024-3701,0,0,d78f52a76181001272debccb095fb5971bb478ebc111313d9ff2994f4ec0598f,2024-04-15T13:15:31.997000
|
||||
CVE-2024-37014,0,0,c47c2b09802b94267a83a7981860e8f6f71032b8440b3dd55d1a2f768ec7199d,2024-06-12T17:57:01.660000
|
||||
CVE-2024-37017,0,0,fd4284c5a2195342d9622b5d20527d4d58db85192e227730c5a741287dc835e4,2024-05-31T13:01:46.727000
|
||||
@ -253046,10 +253051,14 @@ CVE-2024-37063,0,0,89f5547c55b84eeb002f751591163c2bac39f3ef815bb40a0ef85dcc0021b
|
||||
CVE-2024-37064,0,0,543b04bd3e0b4f44701f2ff590d34ccaab537b577720c450f51bc177073db1e8,2024-06-04T16:57:41.053000
|
||||
CVE-2024-37065,0,0,77b183f2030b7bd581e452e09e55b74dee78fc06c1bd0201bb553e7d45698d31,2024-06-04T16:57:41.053000
|
||||
CVE-2024-3707,0,0,cb892298714e8d1628bf09ece0bc00ef0a1a1429034ce83bb3286f4d822c160d,2024-04-15T13:15:51.577000
|
||||
CVE-2024-37078,1,1,dd434c49eb427c93dad4412cff3f92a91f77f54989e79dae34da92157d6a9785,2024-06-25T15:15:12.287000
|
||||
CVE-2024-37079,0,0,9bbd76d5444005ceb39d0ac68b0b4e335d82d5da3fc1107a95914993fa985b9a,2024-06-20T12:44:01.637000
|
||||
CVE-2024-3708,0,0,09132fb1644ebf0c808002aa8ac15b19f13ae71d0beb378f7a9664a5ae685f9a,2024-05-24T01:15:30.977000
|
||||
CVE-2024-37080,0,0,c953e426661198e9665c742ef09fb44af751efb40a1f491b02b9f5389b1d3d21,2024-06-20T12:44:01.637000
|
||||
CVE-2024-37081,0,0,462e18659ef5f7f4965b221966912e397932217f36959496e3a505bf8400d835,2024-06-20T12:44:01.637000
|
||||
CVE-2024-37085,1,1,5d04c83ae99e96df1d79263888bc91a92a2fb34ab6ef5e40f3da6255731bbf44,2024-06-25T15:15:12.377000
|
||||
CVE-2024-37086,1,1,b7a71c682eed6b779f49ebad48388e8da4997905ace870e367e98391f8ed9278,2024-06-25T15:15:12.570000
|
||||
CVE-2024-37087,1,1,780c7429dff76910702369f128d2f3264ba363c37d7bd1dbd2c75ba736aa9125,2024-06-25T15:15:12.767000
|
||||
CVE-2024-37089,0,0,546734d08a472f24d21b11f96a62ff07ba2d9777252aa2840029efb67a03052d,2024-06-24T12:57:36.513000
|
||||
CVE-2024-37091,0,0,70ef4cb5aa59df22f5d9bec3c45f39a3b926dd43e7416671f8860a54328745e5,2024-06-24T12:57:36.513000
|
||||
CVE-2024-37092,0,0,ddf8bb50ed996f71f2c9e3e9b63faabe2c52ea8cb34e6f0fcdb53b1c55be2132,2024-06-24T19:26:54.367000
|
||||
@ -253146,6 +253155,7 @@ CVE-2024-37350,0,0,6f569f37031ea31b0ceea4b3d467eb77e14b3c8cee6ee77458cd2e0600338
|
||||
CVE-2024-37351,0,0,cdc3c0ef3ab09be219d92fdd9e1055808b1607ac62477549cb15639333a9968a,2024-06-21T11:22:01.687000
|
||||
CVE-2024-37352,0,0,6443263682d93e12b4e835549dfa667a0a90916246faa316867370df7949047e,2024-06-21T11:22:01.687000
|
||||
CVE-2024-37353,0,0,3218e91db90d09d49e79b28603de0ae8faa69d3bdfc26cdc7998e6bbb477c22d,2024-06-21T11:22:01.687000
|
||||
CVE-2024-37354,1,1,4de56f7b1dbd2b0d610070763d8920a9bf4251ec339ba5dada21d90fbc46ffe7,2024-06-25T15:15:13.177000
|
||||
CVE-2024-37356,0,0,b4435171622daced3e2b7e47c676acc1991dccc0bf8888cdf2ee310e8709075b,2024-06-21T11:22:01.687000
|
||||
CVE-2024-3736,0,0,8212a13db4363d6279d1d8c19924659c1f0cf224cf46584ea7e82cad3d6da340,2024-06-04T19:20:23.987000
|
||||
CVE-2024-37364,0,0,070f30cc4e6616b0f0ef3a023c4cee97eb2b6bdbb7bd742359fc5c6826335718,2024-06-07T14:56:05.647000
|
||||
@ -253229,11 +253239,11 @@ CVE-2024-37674,0,0,10f19cbc643eab387106fb4d2dc47ca0de793db105c70cb22aa76c9f07603
|
||||
CVE-2024-37675,0,0,b8b2966e003a7477c4ef0b8bf3338112186a7b55754a1c2931ac546b40adcb30,2024-06-24T19:41:31.713000
|
||||
CVE-2024-37676,0,0,9b6174275e973fa26ace8eeff114e47be3264bfcc9cbe3eb6174581137c23815,2024-06-21T11:22:01.687000
|
||||
CVE-2024-37677,0,0,fcf625d4177bbf42c416afe6002c6bcc807035f6d7fa24fc8ff69b831313f374,2024-06-24T19:26:35.967000
|
||||
CVE-2024-37678,0,1,5fe19e5914948d3b0a107d3111ab1682cae3de028d4c044825890d7965bf9ab2,2024-06-25T12:24:17.873000
|
||||
CVE-2024-37678,0,0,5fe19e5914948d3b0a107d3111ab1682cae3de028d4c044825890d7965bf9ab2,2024-06-25T12:24:17.873000
|
||||
CVE-2024-37679,0,0,4c53176267ecf7654c3c07db7d877f12ab8730b8556c2b32193fb0dd75e4c7ec,2024-06-24T20:15:10.743000
|
||||
CVE-2024-3768,0,0,778d3eea8bf87c1f80239f04628ed71cfd577dabb0ce88459344c4cd4d61bb16,2024-05-17T02:40:07.203000
|
||||
CVE-2024-37680,0,0,672397ddab7e53f7332f79063ee0b2552f6259ce26078e5361ab7163777a894f,2024-06-24T19:26:35.967000
|
||||
CVE-2024-37681,0,1,9c6c2701baa4acf84102747d461045da29c4e50bac29e2d41efbf39c81d0f787,2024-06-25T12:24:17.873000
|
||||
CVE-2024-37681,0,0,9c6c2701baa4acf84102747d461045da29c4e50bac29e2d41efbf39c81d0f787,2024-06-25T12:24:17.873000
|
||||
CVE-2024-3769,0,0,a35a1a6580261497cd040b87c6b68395a49a236a06454712c9a126123641e120,2024-05-17T02:40:07.297000
|
||||
CVE-2024-37694,0,0,5368167ec99eb6ece190aa9225c5926bf9e44c57bc2336a35816fa241ead9559,2024-06-24T12:57:36.513000
|
||||
CVE-2024-37699,0,0,e6aa9aad96c5cb91a6fa4201b1b47001ba232f78e3136af80ddfa6d4248f51dc,2024-06-21T11:22:01.687000
|
||||
@ -253243,7 +253253,7 @@ CVE-2024-3772,0,0,184d29c2faf230c27e7c42ad45c478e7862cbffdde795ec4220824e36861b5
|
||||
CVE-2024-37732,0,0,6a86ff5d31f2b347e744ff4e9df1b84cb4205a66e561799f1161776dd71f288a,2024-06-24T19:26:35.967000
|
||||
CVE-2024-3774,0,0,430454733381ff5a96eb00158d8d932d4c087496720223836bce2968611b5152,2024-04-15T13:15:31.997000
|
||||
CVE-2024-3775,0,0,a79253f4f0c7633f40fa5e33903553d0137ff03b4a2d8425a028bb5ddf1c6b0a,2024-04-15T13:15:31.997000
|
||||
CVE-2024-37759,0,1,a304f980fb14a8758546bd8c3d1faef10aef26758667c469c634d191404d3cd2,2024-06-25T12:24:17.873000
|
||||
CVE-2024-37759,0,0,a304f980fb14a8758546bd8c3d1faef10aef26758667c469c634d191404d3cd2,2024-06-25T12:24:17.873000
|
||||
CVE-2024-3776,0,0,55056178a3d988ca6f5c349416a81e65818f1f748e962aa89ca62657bc61cdbb,2024-04-15T13:15:31.997000
|
||||
CVE-2024-3777,0,0,2d62b43478a2af7b370a2abe8fef4e62ecbb9b40c3be97e2e0fc1ef910b6e9d4,2024-04-15T13:15:31.997000
|
||||
CVE-2024-3778,0,0,c2c38fcb38179fdb87f4043dc10c922f64da16bb588bfaf10dd1fb23e229fcc9,2024-04-15T13:15:31.997000
|
||||
@ -253345,6 +253355,7 @@ CVE-2024-3829,0,0,3665a2ef01b9d2a532a67b6bd535e92cc829779e81e658e1b77983bbc06d00
|
||||
CVE-2024-38293,0,0,a9b1fe23a5b7aceb305df22b9e5e69d11cc40f1bf66bedc9fa76d7158e801196,2024-06-13T18:36:09.010000
|
||||
CVE-2024-38294,0,0,5ead4befff2b61ceb0efdd186e7234e4e666514924ffa35ab4e04f3aea639e9b,2024-06-13T18:36:09.010000
|
||||
CVE-2024-38295,0,0,c0872c7c53c37c26d78f688a94fd2e7f57965fc18ec3a253d1cbc168692f708b,2024-06-13T18:36:09.010000
|
||||
CVE-2024-38306,1,1,b125820c7a72581af61f3bf97ecd85ae4f071d4d81c2651f58a213e344d403b5,2024-06-25T15:15:13.367000
|
||||
CVE-2024-3831,0,0,28fa4e2fb2524144138a610966fa5501c7b19e1083bb04e4062bd6679bbd2a31,2024-05-14T16:11:39.510000
|
||||
CVE-2024-38312,0,0,a025bc282a0932c71cb95ccc5342a2a383a8f77cb388790ae2ac3d82d89cfc0a,2024-06-17T12:43:31.090000
|
||||
CVE-2024-38313,0,0,1c234fe7a87659718d48f2a88e14944f64c41ea923fa0d6325e8d4b1e192fda1,2024-06-17T12:43:31.090000
|
||||
@ -253370,6 +253381,7 @@ CVE-2024-38379,0,0,d0af2d7e81a6285c1c7099c958a4a50ce3d2f639bd068091599f2b1327853
|
||||
CVE-2024-3838,0,0,bd55ca068ebe4472845bce1f3d037932d27279da54b129864c942318cbf6c399,2024-04-23T18:15:15.410000
|
||||
CVE-2024-38381,0,0,57bad93cce191bbc955387dd0e3d9e6db94203bba2cb2542c0250ea811d81445,2024-06-21T11:22:01.687000
|
||||
CVE-2024-38384,0,0,706997b8bd74b4e945fb4ea92c7b860b5f40f54233d054279ff0854095c4eca9,2024-06-24T19:26:47.037000
|
||||
CVE-2024-38385,1,1,dcdae5b02561d450a27b773a9400f77aaedd417227b5f4a08ad5979370bb2428,2024-06-25T15:15:13.487000
|
||||
CVE-2024-38388,0,0,7c0bb01f9b9fb79d83dbd6e2c27fd6e239bc8d3e90d248b1b279840e35bf7176,2024-06-21T11:22:01.687000
|
||||
CVE-2024-3839,0,0,5078cfd1c7c68c41b30fd8b0c9c6a095120ec81bc8166ccecb75ba3c8be530b5,2024-05-03T04:15:09.127000
|
||||
CVE-2024-38390,0,0,d3cec8cf37055d7984956bdcdf2d47c2af6b037bed7779bdf5635c68af266a42,2024-06-21T11:22:01.687000
|
||||
@ -253528,6 +253540,7 @@ CVE-2024-38637,0,0,b24638a5f79654eb503a0ab5361d905066f0c21bc6fbaef24d4384d6188e4
|
||||
CVE-2024-3864,0,0,19d7836c62228b8f626d6423c9bc9a43211c93bf4b17c3a151f2e9e764cbca42,2024-04-24T10:15:07.597000
|
||||
CVE-2024-3865,0,0,8b230c3d643bf4def0090616d3b729148802c45f8b0915e5522b00babc710a03,2024-04-17T12:48:31.863000
|
||||
CVE-2024-38659,0,0,f28961b0676a5448bd17e73bb1a6deb01287f9c08ed62cfca5dcb9aaeb49ab7b,2024-06-21T11:22:01.687000
|
||||
CVE-2024-38661,1,1,5e002124fa1ceef6d426601437752f36feaa78edc466d1eec1126f03c7a2ed33,2024-06-25T15:15:13.630000
|
||||
CVE-2024-38662,0,0,df490b2d1680f03df6de3bc588b5285cb29614d4f952810a45c332f43aef3cdd,2024-06-24T18:34:17.547000
|
||||
CVE-2024-38663,0,0,3ea2d49b13b5a6417be2e2e46e01198d7a523f2e1f725a81c5446a7828b4f9eb,2024-06-24T19:26:47.037000
|
||||
CVE-2024-38664,0,0,a8395bd0a97034fb9d591ca23c72f10e556094be356a10c281591bb618a39a41,2024-06-24T19:26:35.967000
|
||||
@ -253556,19 +253569,21 @@ CVE-2024-38873,0,0,480e62ff44ca44c60b79669b7942679e9800aada230c257b18bef37e33b79
|
||||
CVE-2024-38874,0,0,84b324545c03e3af351829556c1e9c9a1e19bfbe37e66a75476dbe17e7f3fa44,2024-06-21T11:22:01.687000
|
||||
CVE-2024-3888,0,0,edb7c29072abf78278f8742356d5aae8212665d8818b230c40ee3cc957ee71c6,2024-06-04T16:57:41.053000
|
||||
CVE-2024-3889,0,0,c4039354ee4d81ce5faec2ce618c8f0af30c97c1ad1feeb689836cb585b438a6,2024-04-23T12:52:09.397000
|
||||
CVE-2024-38892,0,1,78d50090c0cd68a53a439e4db95d8ebbbb280cddaddd36aaf2dcff2e1879f912,2024-06-25T12:24:17.873000
|
||||
CVE-2024-38894,0,1,dea608eba996bae3013e076f41afceb1493408ea073ac1870e8972060846eec0,2024-06-25T12:24:17.873000
|
||||
CVE-2024-38895,0,1,61077d24fa95181b9332258ae85828569e123f2d00cfb6c572e81418ff3f976b,2024-06-25T12:24:17.873000
|
||||
CVE-2024-38896,0,1,76d4dd2fcd38152cd7c2cb770dda2534ec93a9ba2be489143fc2689cd178c4d6,2024-06-25T12:24:17.873000
|
||||
CVE-2024-38897,0,1,4e649a2b89613154255ebb9b7ab7e562726af38e1abb31a0b1fdd69d940ea658,2024-06-25T12:24:17.873000
|
||||
CVE-2024-38892,0,0,78d50090c0cd68a53a439e4db95d8ebbbb280cddaddd36aaf2dcff2e1879f912,2024-06-25T12:24:17.873000
|
||||
CVE-2024-38894,0,0,dea608eba996bae3013e076f41afceb1493408ea073ac1870e8972060846eec0,2024-06-25T12:24:17.873000
|
||||
CVE-2024-38895,0,0,61077d24fa95181b9332258ae85828569e123f2d00cfb6c572e81418ff3f976b,2024-06-25T12:24:17.873000
|
||||
CVE-2024-38896,0,0,76d4dd2fcd38152cd7c2cb770dda2534ec93a9ba2be489143fc2689cd178c4d6,2024-06-25T12:24:17.873000
|
||||
CVE-2024-38897,0,0,4e649a2b89613154255ebb9b7ab7e562726af38e1abb31a0b1fdd69d940ea658,2024-06-25T12:24:17.873000
|
||||
CVE-2024-3890,0,0,167befe3a418fe829a07bf47548aa5d5c5fe13f91b75a3184f188bef038919b6,2024-04-26T12:58:17.720000
|
||||
CVE-2024-38902,0,1,23ffdd6776811ca6c01033cc338f472c4356d79587b08691b797afafd051f7d1,2024-06-25T12:24:17.873000
|
||||
CVE-2024-38903,0,1,7fcdbee1ab2a5ddb09039c821fd90546668576169f9797a60d69a1cce1f325d1,2024-06-25T12:24:17.873000
|
||||
CVE-2024-38902,0,0,23ffdd6776811ca6c01033cc338f472c4356d79587b08691b797afafd051f7d1,2024-06-25T12:24:17.873000
|
||||
CVE-2024-38903,0,0,7fcdbee1ab2a5ddb09039c821fd90546668576169f9797a60d69a1cce1f325d1,2024-06-25T12:24:17.873000
|
||||
CVE-2024-3891,0,0,8daff08d10085680eb7790a9a2c0ef842bf636f7de8dcdfbf7cd60ad81535ead,2024-05-02T18:00:37.360000
|
||||
CVE-2024-3892,0,0,fd27f7808afa94cc2c75f61cd235edb0c08399fa20b15f6c79b02a7674d8055a,2024-05-15T18:35:11.453000
|
||||
CVE-2024-3893,0,0,44a15b07d473e504956c2fc6e9bdbbb981ef84a8f1b69c702ee1ea4228dd1195,2024-04-25T13:18:13.537000
|
||||
CVE-2024-3894,0,0,edf80459282b8df89b54e83306b1e3308990b8425170b8aae8ee5dd50d193a39,2024-06-20T12:44:01.637000
|
||||
CVE-2024-3895,0,0,e17d122bfb4ca0c486d0790093f87ef90da21ea7556181e7099c23bc52ef24ea,2024-05-02T18:00:37.360000
|
||||
CVE-2024-38951,1,1,1b6e4be6a2d17dc70dfe924e59db47b2c76c3dcd9e807a6c55a2bd5b821e407c,2024-06-25T14:15:12.403000
|
||||
CVE-2024-38952,1,1,bd523216d104e96455ab057ef0722cc2bdd744f9e485cde9b2cadabf8ce1940a,2024-06-25T14:15:12.517000
|
||||
CVE-2024-3897,0,0,2e6547d98bffe49274878683fd846b0dea4d063f5cc123163d759ecec392b068,2024-05-02T18:00:37.360000
|
||||
CVE-2024-3900,0,0,5bafaa90d65e26f460054cb65a089d31ecb0030e0f85c3f0ee595a0cce123691,2024-04-17T20:08:21.887000
|
||||
CVE-2024-3903,0,0,b17bb4ec6e0e391a38b8cd510c422de68900922cf0bf4c2e4e48aa68680d6339,2024-05-14T16:11:39.510000
|
||||
@ -253593,11 +253608,16 @@ CVE-2024-3924,0,0,396cfe762c72fbd5a1960b1ddaed612b95d18abd602e0e4dd151e2967ca06c
|
||||
CVE-2024-3925,0,0,fcd3c5c763e8e19f599e796d0209af93ac6baa71961ded5ca72feb787efdbcae,2024-06-13T18:36:09.010000
|
||||
CVE-2024-3926,0,0,95647e23a8e9831b3425be75c3a5409a951b8ebef070821e4342ccb8d8ffe085,2024-05-22T18:59:20.240000
|
||||
CVE-2024-3927,0,0,b62a8fbb5cbf577eaf3c7a81b1c47c6d426f2a5dda5ebe7d2d0cc2ac17b12044,2024-05-22T12:46:53.887000
|
||||
CVE-2024-39276,1,1,44e776eb7b435d0ba76a8d04d095c4c59b147118ef5031bcc9c09c69aca4af8d,2024-06-25T15:15:13.903000
|
||||
CVE-2024-39277,0,0,6e7801911264b763408b9f899358179fb95a98312e78f4ee1fc3e7073d7a1c52,2024-06-24T19:17:48.380000
|
||||
CVE-2024-3928,0,0,43ee632eccbea17dded882a6bd84de69427d4224bfef339281c0d3b1909e8b06,2024-06-06T20:15:13.813000
|
||||
CVE-2024-3929,0,0,31d0a734bfd88727a2a61deb7a29595ac9c8ac4a930ee35c31639990489d025d,2024-04-25T13:18:13.537000
|
||||
CVE-2024-39291,0,0,5390e4dbd75c6e4ce181627716144a7cb6eedbe64b09f6a7a7f71d9048b32398,2024-06-24T19:26:35.967000
|
||||
CVE-2024-39292,0,0,8d48547d663a6a633698f73122eab71c0fa02ba65e6be79df62c1c1783187995,2024-06-24T19:26:35.967000
|
||||
CVE-2024-39293,1,1,e7ec385e80b9c4db9f397a7498dc991bd824ac985493516702aaa4bd7d0be291,2024-06-25T15:15:13.993000
|
||||
CVE-2024-39296,1,1,292b2415d4c7b893b297b89a928d0b7a6a563d3fe4fa293f409a8006d66548f1,2024-06-25T15:15:14.070000
|
||||
CVE-2024-39298,1,1,2cb34d37f2bfb3f3648682901b1e463da35a2504b260b4907b16ac90a65f1ea6,2024-06-25T15:15:14.160000
|
||||
CVE-2024-39301,1,1,f42ebecfb6713c8097d1018e5ee2df051f16be7034f891289945938ee02e63b9,2024-06-25T15:15:14.240000
|
||||
CVE-2024-3931,0,0,ff26b5a8728d6a7f3e1f8095f9d431d98f0c624577950ceaf4dc1cf9ad688034,2024-06-06T20:15:13.933000
|
||||
CVE-2024-3932,0,0,371291a71f9c99e371f96e7d7b61e3e11967567047c07fae80310c4772d1c0c7,2024-06-06T20:15:14.030000
|
||||
CVE-2024-3933,0,0,1d08d4e317596700be65ef5300f76b449794bb2d8b1542a98c34b9cd74fea015,2024-05-28T12:39:28.377000
|
||||
@ -253605,7 +253625,9 @@ CVE-2024-39331,0,0,d1461e039a637b8713f6e32e0beebb2ef4c2e762f105aa6c4f21bab6716ed
|
||||
CVE-2024-39334,0,0,7a242c73a28ed17874e43348a26da2104869d7ef8d91c48fe0d8d7e00f57c31d,2024-06-24T12:57:36.513000
|
||||
CVE-2024-39337,0,0,7c96f97902de4594057b22d7507f3218093cc9f703d055990179db138387110a,2024-06-24T12:57:36.513000
|
||||
CVE-2024-3936,0,0,1a9ebdb5653b792bdb8abb0138184d539d6d0e0c9af8da519de630a92cc0aee0,2024-05-02T18:00:37.360000
|
||||
CVE-2024-39362,1,1,43d310ceed7077d7cd254d45e4080989077d545631961b3e98ee74fb0d6e3f92,2024-06-25T15:15:14.327000
|
||||
CVE-2024-3937,0,0,47b49a69bcae07617978c4de23b5bd0d4eef565a4a3d61421481625d7a4abea5,2024-05-29T13:02:09.280000
|
||||
CVE-2024-39371,1,1,f2dc67af67f34424db8b866ac1c44475a9844876282e04646f22984178bc74ed,2024-06-25T15:15:14.410000
|
||||
CVE-2024-3939,0,0,8db4cbfcc78e197894431199cdad6af4ac1ac13ee2f1028e231ba1f907931766,2024-05-28T12:39:28.377000
|
||||
CVE-2024-3940,0,0,52f7bf6d70193ddf6b45db8d32585f84af1f44b7487d20897766e34b437b8581,2024-05-14T16:11:39.510000
|
||||
CVE-2024-3941,0,0,3315566f834adaa65bc779c72609390662785ebcc4aac50a6cb30731cb96d90c,2024-05-14T16:11:39.510000
|
||||
@ -253613,7 +253635,18 @@ CVE-2024-3942,0,0,e822d69f7c80cdc7914f6c6d228f749a2878411b19bb34f624a4ef0b72687e
|
||||
CVE-2024-3943,0,0,e07ef944084da93a178b1d893c19c63f640132688c11e19da99f30e04e5e47e2,2024-05-30T13:15:41.297000
|
||||
CVE-2024-3945,0,0,87d1ab8fe16ba408f307c5379ed22b3c751c5d4b07b1a3f5bec08826673ff46f,2024-05-30T13:15:41.297000
|
||||
CVE-2024-3946,0,0,af95d5e46eb992f74c75866328fad3ff861f42ea88ebd6ef22645eb1de333586,2024-05-30T13:15:41.297000
|
||||
CVE-2024-39461,1,1,2746c196f18cf90824ade849ced220cedf7f4d7eeb39a2ca157870215bd57cfe,2024-06-25T15:15:14.500000
|
||||
CVE-2024-39462,1,1,0007893a5ccf37986a8c2b35bf4d2eacedcd2a32d0a9f2e322189686ef5c972d,2024-06-25T15:15:14.580000
|
||||
CVE-2024-39463,1,1,8ec79ee3c368ba4aa1cffd52ad0b8276d77f8f59b9c97c0853dc602e862316af,2024-06-25T15:15:14.760000
|
||||
CVE-2024-39464,1,1,fa28296cc74b151fd26e14289521500e78aa702e71759c2562ca0a441bd3772d,2024-06-25T15:15:14.953000
|
||||
CVE-2024-39465,1,1,55dd31fea5738cdc5a35f7dc2826a9bd839f6cdb28b16bbf4eed48ceafe53d48,2024-06-25T15:15:15.037000
|
||||
CVE-2024-39466,1,1,f7c95dfec3e17bb45a8a3e735029a2ae1ded28c87a63dc18df6f7b7f7ca3a829,2024-06-25T15:15:15.117000
|
||||
CVE-2024-39467,1,1,452f6795671e7e8464ec3dca372c9ad421fc6c7924ed3806bd7adbbe093c7ed5,2024-06-25T15:15:15.190000
|
||||
CVE-2024-39468,1,1,803f1db50d0925abb74cfdbf7646a3a884df09c4f867574c5e5ea78efb66235e,2024-06-25T15:15:15.270000
|
||||
CVE-2024-39469,1,1,14ed36de1c503206d55f562a5887a13c8f0dda42044ecb17f3cd681541548d20,2024-06-25T15:15:15.340000
|
||||
CVE-2024-3947,0,0,6b686b580be940e69d22db9dc22782fabd42ffc94dd05568de0bb8f1494d4474,2024-05-30T13:15:41.297000
|
||||
CVE-2024-39470,1,1,19afa3be5359988e22398fd7f5faee3ab7da1bffd302857f76b73bf20e6147d1,2024-06-25T15:15:15.417000
|
||||
CVE-2024-39471,1,1,e1d0206cf797a30c22b6dc107648a02e8bcd3ff296b305fe98105bc6872f535b,2024-06-25T15:15:15.490000
|
||||
CVE-2024-3948,0,0,376ea8906f03fda3c144927b149cbacf34b84dec1b654121329bc158cfe1d518,2024-05-17T02:40:12.107000
|
||||
CVE-2024-3951,0,0,d1eb572088193a792816003caae4c8900ea1808fb70b3f34eb162771a0d73b1e,2024-05-08T17:05:24.083000
|
||||
CVE-2024-3952,0,0,92f1da274771947c3cb4a43546670c1af8a997980dc361a71cd2fb07f162ad15,2024-05-14T16:11:39.510000
|
||||
@ -253790,8 +253823,8 @@ CVE-2024-4192,0,0,d6751fa9142aaa91446de5baa4aa2b6db344761a0aff4ab695cf6603148e6a
|
||||
CVE-2024-4193,0,0,34caa150e2a546168eedf60ed0041c1af9a5a97d1e635e24d38bfff73af8076d,2024-05-14T16:11:39.510000
|
||||
CVE-2024-4194,0,0,205e2b5a2f07968c592d660b3e76de377655cfeebffc35ccc9754d5f0c3bfee6,2024-06-06T14:17:35.017000
|
||||
CVE-2024-4195,0,0,320e8c641dbb71fd3a637ea44d2a1260b2aea61b9d12f44c9e97c80bff500815,2024-04-26T12:58:17.720000
|
||||
CVE-2024-4196,0,1,12230d63e6850d29b2f27733e8e035ec39a7a566231dfc0b91f95d62cdfa7473,2024-06-25T12:24:17.873000
|
||||
CVE-2024-4197,0,1,e8cc7a5084d2d1cfb081a07dc25d0fc1762437134b32c8f450bcd83f8492edbc,2024-06-25T12:24:17.873000
|
||||
CVE-2024-4196,0,0,12230d63e6850d29b2f27733e8e035ec39a7a566231dfc0b91f95d62cdfa7473,2024-06-25T12:24:17.873000
|
||||
CVE-2024-4197,0,0,e8cc7a5084d2d1cfb081a07dc25d0fc1762437134b32c8f450bcd83f8492edbc,2024-06-25T12:24:17.873000
|
||||
CVE-2024-4198,0,0,845a410de3c7b102462b76b86fccfba72df0a0950e69dc55e9742bae00fec8d9,2024-04-26T12:58:17.720000
|
||||
CVE-2024-4199,0,0,afdafa31ddacec6eea606de503a440282409912f425fdd165997fbd1146b1fe5,2024-05-15T16:40:19.330000
|
||||
CVE-2024-4200,0,0,3860d9f44aab141dd4f8c683b4681cf6d16e9750bea07e4efd68dbdbbe0ba40d,2024-05-15T18:35:11.453000
|
||||
@ -254157,10 +254190,10 @@ CVE-2024-4634,0,0,26305cc83de7193b57243a5cab6ca5caf74694a0d7bbca15218a554118aa8e
|
||||
CVE-2024-4635,0,0,39b2c6bf6977107b11329776563f920ebcfe13f250d063c0984d8282a28a8353,2024-05-16T13:03:05.353000
|
||||
CVE-2024-4636,0,0,408131d6e6f7a1de019141a0a08ced7ddc9316cec6084c2dbfd44b2d5b664bc5,2024-05-15T16:40:19.330000
|
||||
CVE-2024-4637,0,0,21c5b691b799fa0ad4b2a54783a02d470d1ce61487f2f97641252b6306511e58,2024-06-04T16:57:41.053000
|
||||
CVE-2024-4638,0,1,bdf6b6ab0b6d6b511a8b5d8622691540358be94136fe6054bb729c0a284ad4ec,2024-06-25T12:24:17.873000
|
||||
CVE-2024-4639,0,1,6d311417f53e6f93449c4abf32d46e0120abf6848b16330b4d451bb0135857d8,2024-06-25T12:24:17.873000
|
||||
CVE-2024-4640,0,1,e68791ea41deb673497d10c695d66c0d6d3b59bafb173b75233d258608f89ffd,2024-06-25T12:24:17.873000
|
||||
CVE-2024-4641,0,1,5420787ebd10c997bd4b87d56061f819a498141f3109f827a653e58aebe81825,2024-06-25T12:24:17.873000
|
||||
CVE-2024-4638,0,0,bdf6b6ab0b6d6b511a8b5d8622691540358be94136fe6054bb729c0a284ad4ec,2024-06-25T12:24:17.873000
|
||||
CVE-2024-4639,0,0,6d311417f53e6f93449c4abf32d46e0120abf6848b16330b4d451bb0135857d8,2024-06-25T12:24:17.873000
|
||||
CVE-2024-4640,0,0,e68791ea41deb673497d10c695d66c0d6d3b59bafb173b75233d258608f89ffd,2024-06-25T12:24:17.873000
|
||||
CVE-2024-4641,0,0,5420787ebd10c997bd4b87d56061f819a498141f3109f827a653e58aebe81825,2024-06-25T12:24:17.873000
|
||||
CVE-2024-4642,0,0,af413e9c39a7a95f4fad15629993388538023a0a54f7d3f1141388f9a4b404f9,2024-05-20T17:15:09.667000
|
||||
CVE-2024-4644,0,0,5d38890bfca86b13a178b6ea41ebf3343b04f0eb53943a12f40545b93c47b88a,2024-06-04T19:20:44.287000
|
||||
CVE-2024-4645,0,0,029fc657c20e99e63c4a0896df7eaed00c7e95079c841983238fcd27dbc9082f,2024-05-29T20:15:13.240000
|
||||
@ -254255,8 +254288,8 @@ CVE-2024-4751,0,0,980cee331660133759599aaa98eeae384de48fe7bcc98af4a2333b20d054b0
|
||||
CVE-2024-4754,0,0,65f7d30a77e8c92b9ac1114b7ed7f43c32a5bfb34fe46cea0e558e1fff1e464e,2024-06-24T12:57:36.513000
|
||||
CVE-2024-4755,0,0,8a7a71d94c74cb52dec815eae51a85f655e8bbdb14fb2727ec4857b0eeba2dfa,2024-06-24T19:31:03.263000
|
||||
CVE-2024-4756,0,0,b303493fc627eee25a3b39c986ea25472e7aab1866612b83c9a7c14522d2c360,2024-06-07T14:56:05.647000
|
||||
CVE-2024-4757,0,1,73657ac01744c501b9896ce49d4f00383a32113d3f80fad0403d338908d3a4f5,2024-06-25T12:24:17.873000
|
||||
CVE-2024-4759,0,1,8b059e177c76b9c2cc6c55c4c3ef3e13274f4cfdcd4ecb6a7973f71b5eda00d8,2024-06-25T12:24:17.873000
|
||||
CVE-2024-4757,0,0,73657ac01744c501b9896ce49d4f00383a32113d3f80fad0403d338908d3a4f5,2024-06-25T12:24:17.873000
|
||||
CVE-2024-4759,0,0,8b059e177c76b9c2cc6c55c4c3ef3e13274f4cfdcd4ecb6a7973f71b5eda00d8,2024-06-25T12:24:17.873000
|
||||
CVE-2024-4760,0,0,8b9593f0d88cbd24a061db082c8cd5c20f19b8a61431542d1ce576639ef3bdc0,2024-05-16T15:44:44.683000
|
||||
CVE-2024-4761,0,0,1a5c101148c08794fbcc9293bdcf48ea45ef131413b853bd53bee7bfdc7d1522,2024-06-10T18:15:36.997000
|
||||
CVE-2024-4764,0,0,9a13ff0309ce1e5420716f8085db95df94fd2bab38dc643251ec74d75f275fe3,2024-05-14T19:17:55.627000
|
||||
@ -254325,7 +254358,7 @@ CVE-2024-4842,0,0,42725480e618d2e75cdf5b0a1412ffa80e3600e0a1a1d76c6fd07755cc858e
|
||||
CVE-2024-4843,0,0,58cfe808f738fd9393d526b6ae9c349063459aa7046a90d478177ce3db0c98a6,2024-05-16T13:03:05.353000
|
||||
CVE-2024-4844,0,0,9cc52c71da3e5a51bc8bac3549d843df2f9b393e878f774cc4555ff01bf8c6f2,2024-05-16T13:03:05.353000
|
||||
CVE-2024-4845,0,0,49e106026fb765942417704e94874a810d1a26b789c9742002fd8f57d37391a4,2024-06-13T18:36:09.010000
|
||||
CVE-2024-4846,1,1,b30bfd6e3dc9f8d6155c93cb2835fb3aadf0529a85db3c7ccb8368b62ef604a6,2024-06-25T13:15:50.120000
|
||||
CVE-2024-4846,0,0,b30bfd6e3dc9f8d6155c93cb2835fb3aadf0529a85db3c7ccb8368b62ef604a6,2024-06-25T13:15:50.120000
|
||||
CVE-2024-4847,0,0,32ddfef9f80253c5a21bc72781721681ecd0f980bfe2a62002a407f007722d53,2024-05-15T16:40:19.330000
|
||||
CVE-2024-4849,0,0,4cca6bf882fb6160af4b1080a2e76a5af3ab9a12c0263aee0523e12c17c0bace,2024-05-20T13:00:34.807000
|
||||
CVE-2024-4851,0,0,1f8e5e94c777c1818792dda00d9eb1239c51f6ea5c6da1418188a32e5d023203,2024-06-07T14:56:05.647000
|
||||
@ -254580,7 +254613,7 @@ CVE-2024-5208,0,0,3985337bac39b70213766ebf64511613ec02cc254f1933a2c8ecd567239b3c
|
||||
CVE-2024-5211,0,0,a4277f26aaa565cc417eac86a473b48ddc12386cf29490b9b3d30644e664c347,2024-06-13T18:36:09.010000
|
||||
CVE-2024-5213,0,0,5a68006f91028e70fb3202f4e898c6483c20faed2d33be845b22e07c07dc81e8,2024-06-20T12:43:25.663000
|
||||
CVE-2024-5214,0,0,77a86526714522a20940695733fe46b4562089752d3c663cf289b583b7c6bbda,2024-06-03T19:15:09.360000
|
||||
CVE-2024-5216,0,1,f74916bcde595c5203a7e0644e281dc01f68ce529e1f3e14cc74a2e3eb525ca3,2024-06-25T12:24:17.873000
|
||||
CVE-2024-5216,0,0,f74916bcde595c5203a7e0644e281dc01f68ce529e1f3e14cc74a2e3eb525ca3,2024-06-25T12:24:17.873000
|
||||
CVE-2024-5218,0,0,928b5f8d4e08afc285c0cf6e370373ec87899b716b1cb4db68027907b01d2a82,2024-05-28T12:39:42.673000
|
||||
CVE-2024-5220,0,0,f61a4e43424028e9a9336f6f6ed766295c86a8a5421f6ff87daa2be13ac80d02,2024-05-28T12:39:42.673000
|
||||
CVE-2024-5221,0,0,6f51797e5b3c0557a37760dbd03fa62a550b475fd63c18dbeda417440e82bc1e,2024-06-11T17:45:05.337000
|
||||
@ -254613,7 +254646,7 @@ CVE-2024-5248,0,0,b78352407aadb212f93e70af46347d9b26fbbca7606ce8cffa82c8de632819
|
||||
CVE-2024-5256,0,0,aef556d8e7eef39a9e473d71cb0baaf9ddd8441bfdba9b715777a96b312eec3d,2024-06-07T14:56:05.647000
|
||||
CVE-2024-5258,0,0,44dc29bb0ed4f47fbd56a17c4d4592048fc8f73fd8d93b1b1d7d82e5e8477ede,2024-05-24T01:15:30.977000
|
||||
CVE-2024-5259,0,0,1133f2690684f5fa329a88cb6129c4f77126359850c2cd2c69369073dabe319e,2024-06-11T17:44:42.783000
|
||||
CVE-2024-5261,1,1,f4daa80a87a6415f03332dbfc275e4b8df91adb38252c05b68ca55ef580c9ee8,2024-06-25T13:15:50.220000
|
||||
CVE-2024-5261,0,0,f4daa80a87a6415f03332dbfc275e4b8df91adb38252c05b68ca55ef580c9ee8,2024-06-25T13:15:50.220000
|
||||
CVE-2024-5262,0,0,9ac0e56dcac973bc4b8e5b6fa9933e9dd09a608d6b80fb71c1aa4404fea36f64,2024-06-11T17:18:50.600000
|
||||
CVE-2024-5263,0,0,796ba510b7017654bdfbf9b75644ebd80198f9cf52c47b5302f3a82ca304a5bf,2024-06-17T12:42:04.623000
|
||||
CVE-2024-5264,0,0,ee26fa1cdb46887f4a061b2862ebd7aa837d5beaa51e34b236fe172dd36cc1a5,2024-06-21T17:18:00.973000
|
||||
@ -254743,7 +254776,7 @@ CVE-2024-5425,0,0,198a56668ec12904be81f8cc7c88bdb7cf556c1b42bf2a53d8f10dc0d316d5
|
||||
CVE-2024-5426,0,0,463afa72e5ec754a0d270917d456b87514b8458a939d0b61aeddc71dea0e191e,2024-06-11T18:03:58.213000
|
||||
CVE-2024-5427,0,0,e86cc201b7d64d377c97e091606dc3804ebb54017d6aedd32a3c8a9e9f3ee33f,2024-05-31T13:01:46.727000
|
||||
CVE-2024-5428,0,0,febfd9b4f977de4c3dc04e5fc8e71b9454e3ad809e74595cd325ad9561a295a7,2024-05-28T14:59:09.827000
|
||||
CVE-2024-5431,0,1,42e70412ed260a519e4eab6a93ce97c65de39fa732f015eeb2fa3ed75a13dc72,2024-06-25T12:24:17.873000
|
||||
CVE-2024-5431,0,0,42e70412ed260a519e4eab6a93ce97c65de39fa732f015eeb2fa3ed75a13dc72,2024-06-25T12:24:17.873000
|
||||
CVE-2024-5432,0,0,ab9a775fb9b6438a5280e4ab8778e43fe4811f4ee641a114adeb9e5317236c9d,2024-06-20T12:43:25.663000
|
||||
CVE-2024-5433,0,0,d0946774ada383b4af0e78f23b9c449d05f83a7124810af4e383f90b0cdbda75,2024-05-29T13:02:09.280000
|
||||
CVE-2024-5434,0,0,dc2716eb218edba725ac85c17a2930de7a00b6563d0ca53040574106ea0b92ed,2024-05-29T13:02:09.280000
|
||||
@ -254755,6 +254788,7 @@ CVE-2024-5443,0,0,925856e128685c50d1cb7d9e876369e7979bded1a2c53610b230353ba1bb3f
|
||||
CVE-2024-5447,0,0,3e4699962d14ab3efd1df3e7ced79104a7a31cb3cb23dd36b2e05295f49fdfa3,2024-06-24T19:27:17.300000
|
||||
CVE-2024-5448,0,0,24e00b17d44c355a66337f1b8192b4308b013ec9be7e4e68644f82dd25cbb76e,2024-06-24T19:26:43.517000
|
||||
CVE-2024-5449,0,0,98f03fd41a859602711a787e6c6738ac5b4c6552335bab31c9f953ba2b79cc72,2024-06-06T14:17:35.017000
|
||||
CVE-2024-5451,1,1,ac3eef632f00be2df57cb7836b071ce5abdd2823f9bcb160c76cf504db382aac,2024-06-25T14:15:12.777000
|
||||
CVE-2024-5452,0,0,27a87c5d81b8c2c688ae4d039463a5b6ff5c5d7de26437cd334595b44d7597a4,2024-06-07T14:56:05.647000
|
||||
CVE-2024-5453,0,0,f53a0f7c14e91f56fc73f4b75f7a3c7cc751f83b7f0078edb3a1d42587e45496,2024-06-11T17:34:52.263000
|
||||
CVE-2024-5455,0,0,fba0854666bb0b703a1a17496073d4cacfc80d7dfcf08ea3fd5bf7812a480359,2024-06-21T11:22:01.687000
|
||||
@ -254921,6 +254955,8 @@ CVE-2024-5786,0,0,ed5396800d42f59a8cc5d452fd1faa0265b1965bb10ec68fd437a404a4a909
|
||||
CVE-2024-5787,0,0,a3d405a0f4e66faab3a863affeada58e47a227c5d73cf2b53ea525af4385d342,2024-06-13T18:36:09.010000
|
||||
CVE-2024-5791,0,0,424014ca254e257c8c57009775e061d0dd2abf87fc81691a50ea6d1a360bb310,2024-06-24T20:00:46.390000
|
||||
CVE-2024-5798,0,0,f6c60b5ac812e7711b355fdc9c4ea7ca1c381d5fa9189e95b5ac079c15b31d9c,2024-06-13T18:36:09.010000
|
||||
CVE-2024-5805,1,1,541c1379b9c2e80d6b2ef59fbaf3ccffc7fc44897f1829ffbed4dc8acdfbfceb,2024-06-25T15:15:15.603000
|
||||
CVE-2024-5806,1,1,c3c63dee76b4ef7ea834c5897d3164cb4b040fe51200a41b23a395e3109fc512,2024-06-25T15:15:15.850000
|
||||
CVE-2024-5812,0,0,b231b6b4b2edc3b100956cc90803ec880aa99de51e5a0f50bc4b9e381c5722ed,2024-06-13T18:36:45.417000
|
||||
CVE-2024-5813,0,0,d695683c807a1777a11ef158e495934f31ab7056ebdb25d58f5f11112f2d1965,2024-06-13T18:36:45.417000
|
||||
CVE-2024-5825,0,0,800930249192b4fb36871d2a50a6622621c6dfa5eae6376e2c2995741b4630b2,2024-06-11T10:15:13.960000
|
||||
@ -255003,7 +255039,7 @@ CVE-2024-6014,0,0,6f42b027c41cbc2bef7f3eccd4ed3d2b0646bd4a1028da377690698f146442
|
||||
CVE-2024-6015,0,0,b5dd732698ac918c4f9a100a042e5587c72b21ba3272e6fc136fa01311e31fdc,2024-06-17T15:15:52.830000
|
||||
CVE-2024-6016,0,0,c54c9dea249da6152524c81283c2e2c500a502b8999814b114c6434b99c2c3ed,2024-06-17T14:15:12.487000
|
||||
CVE-2024-6027,0,0,b2fd57616c7b740fff1978bda2368fdc3959192a2c78f320629b1920784145fa,2024-06-24T19:17:50.240000
|
||||
CVE-2024-6028,0,1,a53cebc0801a7944b049693d6e4ba090f6ff8943c9a085ad6c29614624cd6988,2024-06-25T12:24:17.873000
|
||||
CVE-2024-6028,0,0,a53cebc0801a7944b049693d6e4ba090f6ff8943c9a085ad6c29614624cd6988,2024-06-25T12:24:17.873000
|
||||
CVE-2024-6039,0,0,266923799676f8be01eee28d4a84714045ee9a927bc992eaf897cc5b748105d7,2024-06-17T14:15:12.620000
|
||||
CVE-2024-6041,0,0,a295768a83c71f46593370532a5a859cd3d130f4e3527299fc42bdf02397e4d4,2024-06-17T14:15:12.733000
|
||||
CVE-2024-6042,0,0,6d196e9da9a08d79a22225e118daa7f0e4c238306b694dbe66ba5d1dac9a15e7,2024-06-17T12:42:04.623000
|
||||
@ -255096,7 +255132,7 @@ CVE-2024-6266,0,0,f14331da5cd861226d53e015f2a1f08c9e1d5e7f7b1b843a3feb7cb151cc14
|
||||
CVE-2024-6267,0,0,d0d81696a0fe56042eb20b9f0c7d606c3ec4ab44f43adaf7633e08749cae8d6a,2024-06-24T15:15:12.093000
|
||||
CVE-2024-6268,0,0,57211ae22f5487b97f011249bf73edd578474123c48952c8421da87d99ef64f9,2024-06-24T12:57:36.513000
|
||||
CVE-2024-6269,0,0,cc9e0267763ecfac41b5d3a517fdba068b6a2da99f320a35204e8092ecb68d40,2024-06-24T12:57:36.513000
|
||||
CVE-2024-6273,0,1,3762052fe8e80a0821e2c255e2e5c53f153fd13f917287ec89dc154fc72a6ee2,2024-06-25T13:15:50.403000
|
||||
CVE-2024-6273,0,0,3762052fe8e80a0821e2c255e2e5c53f153fd13f917287ec89dc154fc72a6ee2,2024-06-25T13:15:50.403000
|
||||
CVE-2024-6274,0,0,972129c4472795babca7e5a09e6780210c3b4bbedc3590b6f184f318bcd2e09e,2024-06-24T12:57:36.513000
|
||||
CVE-2024-6275,0,0,427c51c43b1773ea1cd67396c445c590a48390d4be1c9b6b63f99972e6a5594b,2024-06-24T12:57:36.513000
|
||||
CVE-2024-6276,0,0,e2a6801962ea8f1b3d31d222e76c410cafc3abcc0ed09f0e3a5a01d0baeceab1,2024-06-24T15:15:12.200000
|
||||
@ -255106,18 +255142,18 @@ CVE-2024-6279,0,0,b4db90bd3c185f4671769d36fcbbafe037e9aff6dc24be7990311f62fb441a
|
||||
CVE-2024-6280,0,0,4e5bdd720fdc6d68a51312dcfd366ac88ed5daebd5ed348aefe6d5aa74c57712,2024-06-24T12:57:36.513000
|
||||
CVE-2024-6285,0,0,34110f18d2d014a03942c35a79ce17194b0084a2878f4b020f2dba6dca54aee0,2024-06-24T19:26:35.967000
|
||||
CVE-2024-6287,0,0,0b0bce9b8d1b199b7c73f866fab5dde80baa7d074079e3f6b0a56aa3ba19b021,2024-06-24T19:26:35.967000
|
||||
CVE-2024-6290,0,1,6aa2cae539f1c9f41088f0703b4aee116cc1bee84161aa127f51e9c9594fd411,2024-06-25T12:24:17.873000
|
||||
CVE-2024-6291,0,1,70de438a927c128012d38d4afc7d2d8d9c680b7e9dfb04f35c597ef6d72299d7,2024-06-25T12:24:17.873000
|
||||
CVE-2024-6292,0,1,2fa8429b99eb5150e0440f0885f1b9bbe5f5489a0aa79f2bf3eeb4b574c5d11b,2024-06-25T12:24:17.873000
|
||||
CVE-2024-6293,0,1,7ae6676c3b6d14cfa7a42356a4855f8441a14b7c38f52d5c00b87765edee0647,2024-06-25T12:24:17.873000
|
||||
CVE-2024-6294,0,1,6e157447a380471b4e672432441b0d5dbba0fc67bea6ec1145ba68325fae735e,2024-06-25T12:24:17.873000
|
||||
CVE-2024-6295,0,1,34be56c45a4536c17926fc9c9d678ef84cff2fe2a1e2b1e6898c4c1a47aa2e9c,2024-06-25T12:24:17.873000
|
||||
CVE-2024-6297,0,1,4335adc3c6f03845409551a993bf84e337f4db092e95dafe9b538168f2fdbc65,2024-06-25T12:24:17.873000
|
||||
CVE-2024-6299,1,1,5104e3612d74ad38bfd02ce56d6e9894470507eb284e52ca7ce6241938eb0ec0,2024-06-25T13:15:50.587000
|
||||
CVE-2024-6300,1,1,449df0c67fa7c68146db2edf12d4e988f31febd1b90ee114ac6317bc6ceda428,2024-06-25T13:15:50.847000
|
||||
CVE-2024-6301,1,1,c7bb012c6205318c3a43efd0ed2d9f75b1f160da0b117a29cd2de1b54d03c68b,2024-06-25T13:15:51.077000
|
||||
CVE-2024-6302,1,1,6558c5a3561cbc2ca57f303ee20f7a27a6ccc197f7c30d253a8d601c820707b7,2024-06-25T13:15:51.313000
|
||||
CVE-2024-6303,1,1,c7bf582e6f2bba826d29f7fee87eaa1fd6269b6c523e22193866c78a587c429b,2024-06-25T13:15:51.550000
|
||||
CVE-2024-6305,0,1,df9da8f464de5da7e26f22eae0e8134164bd3de20319a65cee59709c696d430a,2024-06-25T12:24:17.873000
|
||||
CVE-2024-6306,0,1,6783eaf13b1bbdc3a425c73b850afc368cd13f93eefb52afb05fc8fb147af6ec,2024-06-25T12:24:17.873000
|
||||
CVE-2024-6307,0,1,8ab5a431e062520bb1ad7f310d46410dbbde3d3f7608d294c115bc975c016c27,2024-06-25T12:24:17.873000
|
||||
CVE-2024-6290,0,0,6aa2cae539f1c9f41088f0703b4aee116cc1bee84161aa127f51e9c9594fd411,2024-06-25T12:24:17.873000
|
||||
CVE-2024-6291,0,0,70de438a927c128012d38d4afc7d2d8d9c680b7e9dfb04f35c597ef6d72299d7,2024-06-25T12:24:17.873000
|
||||
CVE-2024-6292,0,0,2fa8429b99eb5150e0440f0885f1b9bbe5f5489a0aa79f2bf3eeb4b574c5d11b,2024-06-25T12:24:17.873000
|
||||
CVE-2024-6293,0,0,7ae6676c3b6d14cfa7a42356a4855f8441a14b7c38f52d5c00b87765edee0647,2024-06-25T12:24:17.873000
|
||||
CVE-2024-6294,0,0,6e157447a380471b4e672432441b0d5dbba0fc67bea6ec1145ba68325fae735e,2024-06-25T12:24:17.873000
|
||||
CVE-2024-6295,0,0,34be56c45a4536c17926fc9c9d678ef84cff2fe2a1e2b1e6898c4c1a47aa2e9c,2024-06-25T12:24:17.873000
|
||||
CVE-2024-6297,0,0,4335adc3c6f03845409551a993bf84e337f4db092e95dafe9b538168f2fdbc65,2024-06-25T12:24:17.873000
|
||||
CVE-2024-6299,0,0,5104e3612d74ad38bfd02ce56d6e9894470507eb284e52ca7ce6241938eb0ec0,2024-06-25T13:15:50.587000
|
||||
CVE-2024-6300,0,0,449df0c67fa7c68146db2edf12d4e988f31febd1b90ee114ac6317bc6ceda428,2024-06-25T13:15:50.847000
|
||||
CVE-2024-6301,0,0,c7bb012c6205318c3a43efd0ed2d9f75b1f160da0b117a29cd2de1b54d03c68b,2024-06-25T13:15:51.077000
|
||||
CVE-2024-6302,0,0,6558c5a3561cbc2ca57f303ee20f7a27a6ccc197f7c30d253a8d601c820707b7,2024-06-25T13:15:51.313000
|
||||
CVE-2024-6303,0,0,c7bf582e6f2bba826d29f7fee87eaa1fd6269b6c523e22193866c78a587c429b,2024-06-25T13:15:51.550000
|
||||
CVE-2024-6305,0,0,df9da8f464de5da7e26f22eae0e8134164bd3de20319a65cee59709c696d430a,2024-06-25T12:24:17.873000
|
||||
CVE-2024-6306,0,0,6783eaf13b1bbdc3a425c73b850afc368cd13f93eefb52afb05fc8fb147af6ec,2024-06-25T12:24:17.873000
|
||||
CVE-2024-6307,0,0,8ab5a431e062520bb1ad7f310d46410dbbde3d3f7608d294c115bc975c016c27,2024-06-25T12:24:17.873000
|
||||
|
Can't render this file because it is too large.
|
Loading…
x
Reference in New Issue
Block a user