mirror of
https://github.com/fkie-cad/nvd-json-data-feeds.git
synced 2025-05-08 11:37:26 +00:00
Auto-Update: 2024-10-23T08:01:03.514896+00:00
This commit is contained in:
parent
544b228796
commit
af224e3c32
@ -2,32 +2,15 @@
|
||||
"id": "CVE-2024-47725",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-10-21T13:15:02.673",
|
||||
"lastModified": "2024-10-21T17:09:45.417",
|
||||
"vulnStatus": "Awaiting Analysis",
|
||||
"lastModified": "2024-10-23T06:15:05.200",
|
||||
"vulnStatus": "Rejected",
|
||||
"cveTags": [],
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndm-verity: restart or panic on an I/O error\n\nMaxim Suhanov reported that dm-verity doesn't crash if an I/O error\nhappens. In theory, this could be used to subvert security, because an\nattacker can create sectors that return error with the Write Uncorrectable\ncommand. Some programs may misbehave if they have to deal with EIO.\n\nThis commit fixes dm-verity, so that if \"panic_on_corruption\" or\n\"restart_on_corruption\" was specified and an I/O error happens, the\nmachine will panic or restart.\n\nThis commit also changes kernel_restart to emergency_restart -\nkernel_restart calls reboot notifiers and these reboot notifiers may wait\nfor the bio that failed. emergency_restart doesn't call the notifiers."
|
||||
"value": "Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/338b32a232bbee39e52dd1486cbc0c9f458d4d69",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/b332bcca59143cfdd000957f8b78c28dd2ac1da4",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/cada2646b7483cce370eb3b046659df31d9d34d1",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/e6a3531dd542cb127c8de32ab1e54a48ae19962b",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
"references": []
|
||||
}
|
@ -2,130 +2,15 @@
|
||||
"id": "CVE-2024-47755",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-10-21T13:15:05.467",
|
||||
"lastModified": "2024-10-22T15:46:38.027",
|
||||
"vulnStatus": "Analyzed",
|
||||
"lastModified": "2024-10-23T06:15:09.873",
|
||||
"vulnStatus": "Rejected",
|
||||
"cveTags": [],
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnvdimm: Fix devs leaks in scan_labels()\n\nscan_labels() leaks memory when label scanning fails and it falls back\nto just creating a default \"seed\" namespace for userspace to configure.\nRoot can force the kernel to leak memory.\n\nAllocate the minimum resources unconditionally and release them when\nunneeded to avoid the memory leak.\n\nA kmemleak reports:\nunreferenced object 0xffff88800dda1980 (size 16):\n comm \"kworker/u10:5\", pid 69, jiffies 4294671781\n hex dump (first 16 bytes):\n 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n backtrace (crc 0):\n [<00000000c5dea560>] __kmalloc+0x32c/0x470\n [<000000009ed43c83>] nd_region_register_namespaces+0x6fb/0x1120 [libnvdimm]\n [<000000000e07a65c>] nd_region_probe+0xfe/0x210 [libnvdimm]\n [<000000007b79ce5f>] nvdimm_bus_probe+0x7a/0x1e0 [libnvdimm]\n [<00000000a5f3da2e>] really_probe+0xc6/0x390\n [<00000000129e2a69>] __driver_probe_device+0x78/0x150\n [<000000002dfed28b>] driver_probe_device+0x1e/0x90\n [<00000000e7048de2>] __device_attach_driver+0x85/0x110\n [<0000000032dca295>] bus_for_each_drv+0x85/0xe0\n [<00000000391c5a7d>] __device_attach+0xbe/0x1e0\n [<0000000026dabec0>] bus_probe_device+0x94/0xb0\n [<00000000c590d936>] device_add+0x656/0x870\n [<000000003d69bfaa>] nd_async_device_register+0xe/0x50 [libnvdimm]\n [<000000003f4c52a4>] async_run_entry_fn+0x2e/0x110\n [<00000000e201f4b0>] process_one_work+0x1ee/0x600\n [<000000006d90d5a9>] worker_thread+0x183/0x350"
|
||||
},
|
||||
{
|
||||
"lang": "es",
|
||||
"value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: nvdimm: Se corrigen las fugas de memoria de los desarrolladores en scan_labels() scan_labels() pierde memoria cuando falla el escaneo de etiquetas y vuelve a crear un espacio de nombres \"seed\" predeterminado para que el espacio de usuario lo configure. El usuario root puede obligar al kernel a perder memoria. Asigne los recursos m\u00ednimos incondicionalmente y lib\u00e9relos cuando no sean necesarios para evitar la fuga de memoria. Un kmemleak informa: objeto no referenciado 0xffff88800dda1980 (tama\u00f1o 16): comm \"kworker/u10:5\", pid 69, jiffies 4294671781 volcado hexadecimal (primeros 16 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace (crc 0): [<00000000c5dea560>] __kmalloc+0x32c/0x470 [<000000009ed43c83>] nd_region_register_namespaces+0x6fb/0x1120 [libnvdimm] [<000000000e07a65c>] nd_region_probe+0xfe/0x210 [libnvdimm] [<000000007b79ce5f>] nvdimm_bus_probe+0x7a/0x1e0 [libnvdimm] [<00000000a5f3da2e>] really_probe+0xc6/0x390 [<00000000129e2a69>] __driver_probe_device+0x78/0x150 [<000000002dfed28b>] driver_probe_device+0x1e/0x90 [<00000000e7048de2>] __device_attach_driver+0x85/0x110 [<0000000032dca295>] bus_for_each_drv+0x85/0xe0 [<00000000391c5a7d>] __device_attach+0xbe/0x1e0 [<0000000026dabec0>] bus_probe_device+0x94/0xb0 [<00000000c590d936>] device_add+0x656/0x870 [<000000003d69bfaa>] nd_async_device_register+0xe/0x50 [libnvdimm] [<000000003f4c52a4>] async_run_entry_fn+0x2e/0x110 [<00000000e201f4b0>] process_one_work+0x1ee/0x600 [<000000006d90d5a9>] worker_thread+0x183/0x350"
|
||||
"value": "Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV31": [
|
||||
{
|
||||
"source": "nvd@nist.gov",
|
||||
"type": "Primary",
|
||||
"cvssData": {
|
||||
"version": "3.1",
|
||||
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
|
||||
"attackVector": "LOCAL",
|
||||
"attackComplexity": "LOW",
|
||||
"privilegesRequired": "LOW",
|
||||
"userInteraction": "NONE",
|
||||
"scope": "UNCHANGED",
|
||||
"confidentialityImpact": "NONE",
|
||||
"integrityImpact": "NONE",
|
||||
"availabilityImpact": "HIGH",
|
||||
"baseScore": 5.5,
|
||||
"baseSeverity": "MEDIUM"
|
||||
},
|
||||
"exploitabilityScore": 1.8,
|
||||
"impactScore": 3.6
|
||||
}
|
||||
]
|
||||
},
|
||||
"weaknesses": [
|
||||
{
|
||||
"source": "nvd@nist.gov",
|
||||
"type": "Primary",
|
||||
"description": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "CWE-401"
|
||||
}
|
||||
]
|
||||
}
|
||||
],
|
||||
"configurations": [
|
||||
{
|
||||
"nodes": [
|
||||
{
|
||||
"operator": "OR",
|
||||
"negate": false,
|
||||
"cpeMatch": [
|
||||
{
|
||||
"vulnerable": true,
|
||||
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
|
||||
"versionStartIncluding": "4.2",
|
||||
"versionEndExcluding": "6.1.113",
|
||||
"matchCriteriaId": "8102F9FA-E460-401D-B624-0C10DE09E53F"
|
||||
},
|
||||
{
|
||||
"vulnerable": true,
|
||||
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
|
||||
"versionStartIncluding": "6.2",
|
||||
"versionEndExcluding": "6.6.54",
|
||||
"matchCriteriaId": "D448821D-C085-4CAF-88FA-2DDE7BE21976"
|
||||
},
|
||||
{
|
||||
"vulnerable": true,
|
||||
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
|
||||
"versionStartIncluding": "6.7",
|
||||
"versionEndExcluding": "6.10.13",
|
||||
"matchCriteriaId": "CE94BB8D-B0AB-4563-9ED7-A12122B56EBE"
|
||||
},
|
||||
{
|
||||
"vulnerable": true,
|
||||
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
|
||||
"versionStartIncluding": "6.11",
|
||||
"versionEndExcluding": "6.11.2",
|
||||
"matchCriteriaId": "AB755D26-97F4-43B6-8604-CD076811E181"
|
||||
}
|
||||
]
|
||||
}
|
||||
]
|
||||
}
|
||||
],
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/18a672c62d735744c6340eb3f5e58934a5d34cf2",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"tags": [
|
||||
"Patch"
|
||||
]
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/45db20bdb5695d06478d35e05fb2550441bed890",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"tags": [
|
||||
"Patch"
|
||||
]
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/62c2aa6b1f565d2fc1ec11a6e9e8336ce37a6426",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"tags": [
|
||||
"Patch"
|
||||
]
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/939053737edb49ba5bdc5846acb45f11d15b7ab4",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"tags": [
|
||||
"Patch"
|
||||
]
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/cdf0dfb3d183bbe0d0b6a6622c53d105074ad384",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"tags": [
|
||||
"Patch"
|
||||
]
|
||||
}
|
||||
]
|
||||
"metrics": {},
|
||||
"references": []
|
||||
}
|
29
CVE-2024/CVE-2024-500xx/CVE-2024-50066.json
Normal file
29
CVE-2024/CVE-2024-500xx/CVE-2024-50066.json
Normal file
@ -0,0 +1,29 @@
|
||||
{
|
||||
"id": "CVE-2024-50066",
|
||||
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||||
"published": "2024-10-23T06:15:10.467",
|
||||
"lastModified": "2024-10-23T06:15:10.467",
|
||||
"vulnStatus": "Received",
|
||||
"cveTags": [],
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/mremap: fix move_normal_pmd/retract_page_tables race\n\nIn mremap(), move_page_tables() looks at the type of the PMD entry and the\nspecified address range to figure out by which method the next chunk of\npage table entries should be moved.\n\nAt that point, the mmap_lock is held in write mode, but no rmap locks are\nheld yet. For PMD entries that point to page tables and are fully covered\nby the source address range, move_pgt_entry(NORMAL_PMD, ...) is called,\nwhich first takes rmap locks, then does move_normal_pmd(). \nmove_normal_pmd() takes the necessary page table locks at source and\ndestination, then moves an entire page table from the source to the\ndestination.\n\nThe problem is: The rmap locks, which protect against concurrent page\ntable removal by retract_page_tables() in the THP code, are only taken\nafter the PMD entry has been read and it has been decided how to move it. \nSo we can race as follows (with two processes that have mappings of the\nsame tmpfs file that is stored on a tmpfs mount with huge=advise); note\nthat process A accesses page tables through the MM while process B does it\nthrough the file rmap:\n\nprocess A process B\n========= =========\nmremap\n mremap_to\n move_vma\n move_page_tables\n get_old_pmd\n alloc_new_pmd\n *** PREEMPT ***\n madvise(MADV_COLLAPSE)\n do_madvise\n madvise_walk_vmas\n madvise_vma_behavior\n madvise_collapse\n hpage_collapse_scan_file\n collapse_file\n retract_page_tables\n i_mmap_lock_read(mapping)\n pmdp_collapse_flush\n i_mmap_unlock_read(mapping)\n move_pgt_entry(NORMAL_PMD, ...)\n take_rmap_locks\n move_normal_pmd\n drop_rmap_locks\n\nWhen this happens, move_normal_pmd() can end up creating bogus PMD entries\nin the line `pmd_populate(mm, new_pmd, pmd_pgtable(pmd))`. The effect\ndepends on arch-specific and machine-specific details; on x86, you can end\nup with physical page 0 mapped as a page table, which is likely\nexploitable for user->kernel privilege escalation.\n\nFix the race by letting process B recheck that the PMD still points to a\npage table after the rmap locks have been taken. Otherwise, we bail and\nlet the caller fall back to the PTE-level copying path, which will then\nbail immediately at the pmd_none() check.\n\nBug reachability: Reaching this bug requires that you can create\nshmem/file THP mappings - anonymous THP uses different code that doesn't\nzap stuff under rmap locks. File THP is gated on an experimental config\nflag (CONFIG_READ_ONLY_THP_FOR_FS), so on normal distro kernels you need\nshmem THP to hit this bug. As far as I know, getting shmem THP normally\nrequires that you can mount your own tmpfs with the right mount flags,\nwhich would require creating your own user+mount namespace; though I don't\nknow if some distros maybe enable shmem THP by default or something like\nthat.\n\nBug impact: This issue can likely be used for user->kernel privilege\nescalation when it is reachable."
|
||||
}
|
||||
],
|
||||
"metrics": {},
|
||||
"references": [
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/1552ce9ce8af47c0fe911682e5e1855e25851ca9",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/17396e32f975130b3e6251f024c8807d192e4c3e",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
},
|
||||
{
|
||||
"url": "https://git.kernel.org/stable/c/6fa1066fc5d00cb9f1b0e83b7ff6ef98d26ba2aa",
|
||||
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||||
}
|
||||
]
|
||||
}
|
64
CVE-2024/CVE-2024-95xx/CVE-2024-9583.json
Normal file
64
CVE-2024/CVE-2024-95xx/CVE-2024-9583.json
Normal file
@ -0,0 +1,64 @@
|
||||
{
|
||||
"id": "CVE-2024-9583",
|
||||
"sourceIdentifier": "security@wordfence.com",
|
||||
"published": "2024-10-23T07:15:03.283",
|
||||
"lastModified": "2024-10-23T07:15:03.283",
|
||||
"vulnStatus": "Received",
|
||||
"cveTags": [],
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "The RSS Aggregator \u2013 RSS Import, News Feeds, Feed to Post, and Autoblogging plugin for WordPress is vulnerable to unauthorized use of functionality due to a missing capability check on the wprss_ajax_send_premium_support function in all versions up to, and including, 4.23.12. This makes it possible for authenticated attackers, with Subscriber-level access and above, to send premium support requests with an attacker-controlled subject line and email address to support allowing them to impersonate the site owner. License information may also be leaked."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV31": [
|
||||
{
|
||||
"source": "security@wordfence.com",
|
||||
"type": "Secondary",
|
||||
"cvssData": {
|
||||
"version": "3.1",
|
||||
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
|
||||
"attackVector": "NETWORK",
|
||||
"attackComplexity": "LOW",
|
||||
"privilegesRequired": "LOW",
|
||||
"userInteraction": "NONE",
|
||||
"scope": "UNCHANGED",
|
||||
"confidentialityImpact": "LOW",
|
||||
"integrityImpact": "NONE",
|
||||
"availabilityImpact": "NONE",
|
||||
"baseScore": 4.3,
|
||||
"baseSeverity": "MEDIUM"
|
||||
},
|
||||
"exploitabilityScore": 2.8,
|
||||
"impactScore": 1.4
|
||||
}
|
||||
]
|
||||
},
|
||||
"weaknesses": [
|
||||
{
|
||||
"source": "security@wordfence.com",
|
||||
"type": "Primary",
|
||||
"description": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "CWE-862"
|
||||
}
|
||||
]
|
||||
}
|
||||
],
|
||||
"references": [
|
||||
{
|
||||
"url": "https://plugins.trac.wordpress.org/browser/wp-rss-aggregator/trunk/includes/admin-help.php#L274",
|
||||
"source": "security@wordfence.com"
|
||||
},
|
||||
{
|
||||
"url": "https://plugins.trac.wordpress.org/changeset/3168468/wp-rss-aggregator/trunk/includes/admin-help.php",
|
||||
"source": "security@wordfence.com"
|
||||
},
|
||||
{
|
||||
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/126c77fa-11c5-431f-8fc9-0375ed6c8a91?source=cve",
|
||||
"source": "security@wordfence.com"
|
||||
}
|
||||
]
|
||||
}
|
72
CVE-2024/CVE-2024-98xx/CVE-2024-9829.json
Normal file
72
CVE-2024/CVE-2024-98xx/CVE-2024-9829.json
Normal file
@ -0,0 +1,72 @@
|
||||
{
|
||||
"id": "CVE-2024-9829",
|
||||
"sourceIdentifier": "security@wordfence.com",
|
||||
"published": "2024-10-23T06:15:11.007",
|
||||
"lastModified": "2024-10-23T06:15:11.007",
|
||||
"vulnStatus": "Received",
|
||||
"cveTags": [],
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "The Download Plugin plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability checks on the 'dpwap_handle_download_user' and 'dpwap_handle_download_comment' functions in all versions up to, and including, 2.2.0. This makes it possible for authenticated attackers, with Subscriber-level access and above, to download any comment, and download metadata for any user including user PII and sensitive information including username, email, hashed passwords and application passwords, session token information and more depending on set up and additional plugins installed."
|
||||
}
|
||||
],
|
||||
"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:U/C:H/I:N/A:N",
|
||||
"attackVector": "NETWORK",
|
||||
"attackComplexity": "LOW",
|
||||
"privilegesRequired": "LOW",
|
||||
"userInteraction": "NONE",
|
||||
"scope": "UNCHANGED",
|
||||
"confidentialityImpact": "HIGH",
|
||||
"integrityImpact": "NONE",
|
||||
"availabilityImpact": "NONE",
|
||||
"baseScore": 6.5,
|
||||
"baseSeverity": "MEDIUM"
|
||||
},
|
||||
"exploitabilityScore": 2.8,
|
||||
"impactScore": 3.6
|
||||
}
|
||||
]
|
||||
},
|
||||
"weaknesses": [
|
||||
{
|
||||
"source": "security@wordfence.com",
|
||||
"type": "Primary",
|
||||
"description": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "CWE-862"
|
||||
}
|
||||
]
|
||||
}
|
||||
],
|
||||
"references": [
|
||||
{
|
||||
"url": "https://plugins.trac.wordpress.org/browser/download-plugin/trunk/download-plugin.php#L242",
|
||||
"source": "security@wordfence.com"
|
||||
},
|
||||
{
|
||||
"url": "https://plugins.trac.wordpress.org/browser/download-plugin/trunk/download-plugin.php#L262",
|
||||
"source": "security@wordfence.com"
|
||||
},
|
||||
{
|
||||
"url": "https://plugins.trac.wordpress.org/browser/download-plugin/trunk/download-plugin.php#L335",
|
||||
"source": "security@wordfence.com"
|
||||
},
|
||||
{
|
||||
"url": "https://plugins.trac.wordpress.org/changeset/3170600/",
|
||||
"source": "security@wordfence.com"
|
||||
},
|
||||
{
|
||||
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/e0891211-e4b3-4dcf-8ee0-e20abeb91640?source=cve",
|
||||
"source": "security@wordfence.com"
|
||||
}
|
||||
]
|
||||
}
|
60
CVE-2024/CVE-2024-99xx/CVE-2024-9947.json
Normal file
60
CVE-2024/CVE-2024-99xx/CVE-2024-9947.json
Normal file
@ -0,0 +1,60 @@
|
||||
{
|
||||
"id": "CVE-2024-9947",
|
||||
"sourceIdentifier": "security@wordfence.com",
|
||||
"published": "2024-10-23T07:15:04.560",
|
||||
"lastModified": "2024-10-23T07:15:04.560",
|
||||
"vulnStatus": "Received",
|
||||
"cveTags": [],
|
||||
"descriptions": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "The ProfilePress Pro plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 4.11.1. This is due to insufficient verification on the user being returned by the social login token. This makes it possible for unauthenticated attackers to log in as any existing user on the site, such as an administrator, if they have access to the email and the user does not have an already-existing account for the service returning the token."
|
||||
}
|
||||
],
|
||||
"metrics": {
|
||||
"cvssMetricV31": [
|
||||
{
|
||||
"source": "security@wordfence.com",
|
||||
"type": "Primary",
|
||||
"cvssData": {
|
||||
"version": "3.1",
|
||||
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
|
||||
"attackVector": "NETWORK",
|
||||
"attackComplexity": "HIGH",
|
||||
"privilegesRequired": "NONE",
|
||||
"userInteraction": "NONE",
|
||||
"scope": "UNCHANGED",
|
||||
"confidentialityImpact": "HIGH",
|
||||
"integrityImpact": "HIGH",
|
||||
"availabilityImpact": "HIGH",
|
||||
"baseScore": 8.1,
|
||||
"baseSeverity": "HIGH"
|
||||
},
|
||||
"exploitabilityScore": 2.2,
|
||||
"impactScore": 5.9
|
||||
}
|
||||
]
|
||||
},
|
||||
"weaknesses": [
|
||||
{
|
||||
"source": "security@wordfence.com",
|
||||
"type": "Primary",
|
||||
"description": [
|
||||
{
|
||||
"lang": "en",
|
||||
"value": "CWE-287"
|
||||
}
|
||||
]
|
||||
}
|
||||
],
|
||||
"references": [
|
||||
{
|
||||
"url": "https://profilepress.com/",
|
||||
"source": "security@wordfence.com"
|
||||
},
|
||||
{
|
||||
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/61b477c3-88b7-45a4-9fc4-6bca6f7c3604?source=cve",
|
||||
"source": "security@wordfence.com"
|
||||
}
|
||||
]
|
||||
}
|
18
README.md
18
README.md
@ -13,13 +13,13 @@ Repository synchronizes with the NVD every 2 hours.
|
||||
### Last Repository Update
|
||||
|
||||
```plain
|
||||
2024-10-23T04:00:17.806395+00:00
|
||||
2024-10-23T08:01:03.514896+00:00
|
||||
```
|
||||
|
||||
### Most recent CVE Modification Timestamp synchronized with NVD
|
||||
|
||||
```plain
|
||||
2024-10-23T02:15:07.467000+00:00
|
||||
2024-10-23T07:15:04.560000+00:00
|
||||
```
|
||||
|
||||
### Last Data Feed Release
|
||||
@ -33,21 +33,25 @@ Download and Changelog: [Click](https://github.com/fkie-cad/nvd-json-data-feeds/
|
||||
### Total Number of included CVEs
|
||||
|
||||
```plain
|
||||
266768
|
||||
266772
|
||||
```
|
||||
|
||||
### CVEs added in the last Commit
|
||||
|
||||
Recently added CVEs: `2`
|
||||
Recently added CVEs: `4`
|
||||
|
||||
- [CVE-2024-31880](CVE-2024/CVE-2024-318xx/CVE-2024-31880.json) (`2024-10-23T02:15:07.167`)
|
||||
- [CVE-2024-9927](CVE-2024/CVE-2024-99xx/CVE-2024-9927.json) (`2024-10-23T02:15:07.467`)
|
||||
- [CVE-2024-50066](CVE-2024/CVE-2024-500xx/CVE-2024-50066.json) (`2024-10-23T06:15:10.467`)
|
||||
- [CVE-2024-9583](CVE-2024/CVE-2024-95xx/CVE-2024-9583.json) (`2024-10-23T07:15:03.283`)
|
||||
- [CVE-2024-9829](CVE-2024/CVE-2024-98xx/CVE-2024-9829.json) (`2024-10-23T06:15:11.007`)
|
||||
- [CVE-2024-9947](CVE-2024/CVE-2024-99xx/CVE-2024-9947.json) (`2024-10-23T07:15:04.560`)
|
||||
|
||||
|
||||
### CVEs modified in the last Commit
|
||||
|
||||
Recently modified CVEs: `0`
|
||||
Recently modified CVEs: `2`
|
||||
|
||||
- [CVE-2024-47725](CVE-2024/CVE-2024-477xx/CVE-2024-47725.json) (`2024-10-23T06:15:05.200`)
|
||||
- [CVE-2024-47755](CVE-2024/CVE-2024-477xx/CVE-2024-47755.json) (`2024-10-23T06:15:09.873`)
|
||||
|
||||
|
||||
## Download and Usage
|
||||
|
12
_state.csv
12
_state.csv
@ -251991,7 +251991,7 @@ CVE-2024-31874,0,0,2aaf0dfaa6414e1f138855d0f6d75787313d073eca635397ca103ff7f6449
|
||||
CVE-2024-31878,0,0,c6557222267c2e9c166ed275e7cc9327cfea0693e0a8976b187deb7865aacef5,2024-06-11T18:23:27.153000
|
||||
CVE-2024-31879,0,0,3d520028d5f0055139f730dd4a6eb2d11b7ab38a082798764c43108749c5b618,2024-05-20T13:00:34.807000
|
||||
CVE-2024-3188,0,0,0566f9bb8e826930c137ba20908e573874a3f34d7900cbdeff699f1e3434f595,2024-07-08T14:19:01.160000
|
||||
CVE-2024-31880,1,1,32067864538b60bbf3feba7f1c2b7fa82d95990b8fc56c301672ce33521f88bc,2024-10-23T02:15:07.167000
|
||||
CVE-2024-31880,0,0,32067864538b60bbf3feba7f1c2b7fa82d95990b8fc56c301672ce33521f88bc,2024-10-23T02:15:07.167000
|
||||
CVE-2024-31881,0,0,b3692d17c2d4f662273dec610556097ee0b8856656ac8f4835c5e840eb8a6228,2024-08-07T16:59:15.627000
|
||||
CVE-2024-31882,0,0,2166c1d8e88429778073b60eb2a31c41e2b55293434c096888febf101419ae12,2024-09-21T10:15:05.403000
|
||||
CVE-2024-31883,0,0,c4a2241ac7ebf5ea1afff59f8bf762360ac7a99942ee729cf3d03ae8864dc6f3,2024-08-02T15:06:08.297000
|
||||
@ -262248,7 +262248,7 @@ CVE-2024-47721,0,0,04edd5df09b5c82f2a2feeea71eab7461d88f3c2fa180c2013bad25f1ea8d
|
||||
CVE-2024-47722,0,0,68c8d2f090df61a9f49a1f01f75a7ac8cda9d407591cfa0dc0a92c1e0656c53f,2024-10-21T13:15:02.360000
|
||||
CVE-2024-47723,0,0,e78b215d0cbedf337fc4d670e1844dbbd29b556e5053e7d66b95322a621daa0b,2024-10-21T17:09:45.417000
|
||||
CVE-2024-47724,0,0,9c1d4dd363597ace78d1c7ebbef0e1f2e96a212b96b6a09618a577838f46fe1f,2024-10-21T17:09:45.417000
|
||||
CVE-2024-47725,0,0,5b041bb683211618550e4d3269ed83dc0c0e198d1ad8a3089e37417c858a4b04,2024-10-21T17:09:45.417000
|
||||
CVE-2024-47725,0,1,8d79cfc5f420589203ee56c1d45c4e18a5d4c2e87a501b10347996e89a7f75b1,2024-10-23T06:15:05.200000
|
||||
CVE-2024-47726,0,0,c446e3e2dffbcccbc0186f0322a85b4a05a0668ee60808d5804eca57a29d9a39,2024-10-21T17:09:45.417000
|
||||
CVE-2024-47727,0,0,b4841d049fe7977d7ae76ed99e0c8291d4ff9401863cf2613bdea9ae7e9a1347,2024-10-21T17:09:45.417000
|
||||
CVE-2024-47728,0,0,20d7130b4cb2af3704697b2735b8691238f821693df5a91fa37a4e7099218c8a,2024-10-21T17:09:45.417000
|
||||
@ -262281,7 +262281,7 @@ CVE-2024-47751,0,0,dbbb46f679c8ef6d582034b10e0fc5133e1862d2b7e7523462d867f3e651a
|
||||
CVE-2024-47752,0,0,65039c78bb19b3ece8928a956e9db0ee7719b3f114bcfd57c0c3ced74f237a1e,2024-10-22T16:11:09.037000
|
||||
CVE-2024-47753,0,0,b4bdc9a1d337353d37d865ac5f0c508d5e95f57a71156b3e1f6703729b56c2ad,2024-10-22T16:10:40.380000
|
||||
CVE-2024-47754,0,0,c998ddb7bc3dbcc169b2eae7169517ec00cc08562e1a7f8fb53bdf6d08fdcd47,2024-10-22T16:10:21.907000
|
||||
CVE-2024-47755,0,0,6cb13a363c1927340d57e298ac76078d7c78d1527e04987bda7bb702169c10cb,2024-10-22T15:46:38.027000
|
||||
CVE-2024-47755,0,1,8cf25d07e196e075734f98083f38dbef19fd8e91fd1c66d640e943585b9e2f41,2024-10-23T06:15:09.873000
|
||||
CVE-2024-47756,0,0,eb155bc0ec662a964b2c66ddbb8cf663bac19d4776af4da61c75acb4f1c74b8d,2024-10-22T16:09:56.570000
|
||||
CVE-2024-47757,0,0,500f4ed7f4cebe77f095eabe903396578ed13baff1d5a05afdbb14496b4b2006,2024-10-22T15:54:48.830000
|
||||
CVE-2024-4776,0,0,8d62a3fb449cd595ed01f29a43c4395459263028a3240838c3f471dfed40e010,2024-07-03T02:08:08.187000
|
||||
@ -263102,6 +263102,7 @@ CVE-2024-50062,0,0,6f5ca0ab24218bdc3a66845ef7a25d33f8fee4816aeb71f302bd0b77f4dbd
|
||||
CVE-2024-50063,0,0,d759cd8b06ee26350df3838a67993a2f428080f68be3d878c568416e1030f14f,2024-10-21T20:15:18.360000
|
||||
CVE-2024-50064,0,0,a9c0a9e4f0c519a4c22abec4357d9c45d0d914896a8ed6df430d438f3ba7542c,2024-10-21T20:15:18.440000
|
||||
CVE-2024-50065,0,0,8b2909d6581c9e4861514583ddb674698f4fdfdf8c4f85ae747650769c9c2972,2024-10-21T20:15:18.520000
|
||||
CVE-2024-50066,1,1,f285282ac4ec0f12fc9db20caf087bc402ef18a772b938e146fd347faa930bc5,2024-10-23T06:15:10.467000
|
||||
CVE-2024-5008,0,0,41c3cff745583fe16908c309126d70e41415ad78f2790f83925cbb0a70eb9065,2024-09-06T22:43:49.557000
|
||||
CVE-2024-5009,0,0,4fd7bfd86519955de695550b550ff6287bae2637bb330aab0edb8e0b318761f0,2024-09-06T22:43:04.747000
|
||||
CVE-2024-5010,0,0,3c850c266940942fbe09adbb4c98bc7afc61c3edf80ecba9d04f15eeefca6109,2024-09-06T22:42:39.017000
|
||||
@ -266602,6 +266603,7 @@ CVE-2024-9575,0,0,902a179ba291c73f1ff19f974c0569ed05c8dbb3d8914c4f7409455feb2bd5
|
||||
CVE-2024-9576,0,0,7a96a155cd09492144b259aa00c523497a7aeb66fdb84ed492d68f7654aa3880,2024-10-07T17:47:48.410000
|
||||
CVE-2024-9581,0,0,fb1d34fab9f94525003a0f26c830b830dcb7b4bdc92dd8a95590c26db891e7c3,2024-10-15T14:28:35.283000
|
||||
CVE-2024-9582,0,0,6ec198135418f168eaebdeafd2e2fe73c3f44201fb3d949937a7b4e70c974bf6,2024-10-16T16:38:14.557000
|
||||
CVE-2024-9583,1,1,4e2383151ac5b9c2acd8fcf3ac201e2935142bdaea8e4140c8c137167c2756dc,2024-10-23T07:15:03.283000
|
||||
CVE-2024-9586,0,0,a482a25f032ea940edbd74f8dc11272d0d4fecf517c5613466c04b8bd798dc3e,2024-10-15T12:58:51.050000
|
||||
CVE-2024-9587,0,0,081ae6ebdba381265a40b327141c3458d6ec1c5b94d7fb86236bf633a93923d3,2024-10-15T12:58:51.050000
|
||||
CVE-2024-9588,0,0,6a3f9ab7e270d754b223fcdbf2cacc2d2bdde581661fe0dd749d86129cb2d158,2024-10-22T08:15:03.563000
|
||||
@ -266685,6 +266687,7 @@ CVE-2024-9821,0,0,847982287e8db8d54661c5522d18fa833c3d9091b2ddb2afe78ab1e8077a47
|
||||
CVE-2024-9822,0,0,3245ced109c1c371c55834b9b14d881a9e8b7fd7c32c19b6e9a742506d7d4c79,2024-10-15T12:58:51.050000
|
||||
CVE-2024-9823,0,0,918595934cb9b43f50abc93ebc9bbb9148088fae18c39570ebc344ac634d3e40,2024-10-15T12:57:46.880000
|
||||
CVE-2024-9824,0,0,0b6b46e52b34b071e6f48e5304d76a541526a4368e490338503476fca424894a,2024-10-15T12:57:46.880000
|
||||
CVE-2024-9829,1,1,d830908c21d8114fe90e9bd180eef5e6d1b9af8f4bd56c24f825c37f79c0df45,2024-10-23T06:15:11.007000
|
||||
CVE-2024-9837,0,0,bb6af129df538114e71c369a037f26903d10504dcd81ada4fc7f4b05786c12dd,2024-10-15T12:57:46.880000
|
||||
CVE-2024-9848,0,0,b402d34d635014e43cf3d9b875728458bb9e45308a715285ac01e2036b42d252,2024-10-22T16:42:25.867000
|
||||
CVE-2024-9855,0,0,f4067d5f9739a4a46f27ed071acd023bca1d9a27db9968d98f329af2e8d70e8b,2024-10-15T12:58:51.050000
|
||||
@ -266727,11 +266730,12 @@ CVE-2024-9922,0,0,88ad74a9a80ef6250cad160a6da905c26f5539449069265fbdbc38c65f6e69
|
||||
CVE-2024-9923,0,0,1744d806aab87c1cbef5524d43cf9cad10cdae75dc6a2cfd8b34f2d3877dca94,2024-10-15T12:57:46.880000
|
||||
CVE-2024-9924,0,0,4d0aa49bc1047e2e0a23ab80e176dbdf70a0af5e82bea53f63a116cd5905286e,2024-10-15T12:57:46.880000
|
||||
CVE-2024-9925,0,0,d9114846b6ab22497d9820c775f40ff778b3a4311afada5c7a947fe6aafbbadc,2024-10-17T18:09:40.537000
|
||||
CVE-2024-9927,1,1,5dded3cf948971c198f725f290262f789bfb61e29a3f6bc3cc4557807d2417de,2024-10-23T02:15:07.467000
|
||||
CVE-2024-9927,0,0,5dded3cf948971c198f725f290262f789bfb61e29a3f6bc3cc4557807d2417de,2024-10-23T02:15:07.467000
|
||||
CVE-2024-9936,0,0,9b9410743fe1ca2f5a844c24ad20043ec989ced54414fa626e93bdc74b6425ff,2024-10-15T12:57:46.880000
|
||||
CVE-2024-9937,0,0,4e7ae54d6a9c5099857ac0a66ba44c96220fc2ab3e1844c918c371d4dbb6d38d,2024-10-16T16:38:14.557000
|
||||
CVE-2024-9940,0,0,0591f213f2bec6924fef18017d23419024c9c5bdc4c598c1e0fd80a492ebb13b,2024-10-18T12:53:04.627000
|
||||
CVE-2024-9944,0,0,0b8e9f26d6b78f71e8a64eb7650f72f57e1c6a31a17ce0fafe5b6b8377b71371,2024-10-17T20:47:35.817000
|
||||
CVE-2024-9947,1,1,740bc028aa20a59832eb7d25da2505972d1214d46e60732a3d1d1371d903a794,2024-10-23T07:15:04.560000
|
||||
CVE-2024-9951,0,0,5d941c75af8c4072e469beaa1d6ae2855b0ca23ecdce87314ecd326f6a54014a,2024-10-18T12:52:33.507000
|
||||
CVE-2024-9952,0,0,d5c643eb1b76a39b13753ce231704557bf9fa9c82efce6d96f1e313e65eab479,2024-10-16T15:05:13.467000
|
||||
CVE-2024-9953,0,0,d45e8bc6b31e34e84fbff0a12af100dea5cf3de9adda836e3ebc3a7410262455,2024-10-17T20:59:01.940000
|
||||
|
Can't render this file because it is too large.
|
Loading…
x
Reference in New Issue
Block a user