Skip to content

Commit

Permalink
generated content from 2025-01-12
Browse files Browse the repository at this point in the history
  • Loading branch information
github-actions[bot] committed Jan 12, 2025
1 parent e10bccd commit a93ea1c
Show file tree
Hide file tree
Showing 89 changed files with 2,024 additions and 0 deletions.
88 changes: 88 additions & 0 deletions mapping.csv
Original file line number Diff line number Diff line change
Expand Up @@ -262916,3 +262916,91 @@ vulnerability,CVE-2025-23078,vulnerability--4c2fae7e-fac8-4527-9d6d-198cb63dc104
vulnerability,CVE-2025-23016,vulnerability--03787242-183b-45a6-aec8-687072ab084c
vulnerability,CVE-2025-23079,vulnerability--091d1c97-18a2-497b-9917-40855ce16cfb
vulnerability,CVE-2025-0311,vulnerability--685024a3-d7b0-4766-b3c4-5fee0b4ecec4
vulnerability,CVE-2024-48873,vulnerability--014ae561-f5d1-410a-b5cd-88443946212c
vulnerability,CVE-2024-48881,vulnerability--7bf30e67-77f0-4fe6-965e-ee7e23b72c9d
vulnerability,CVE-2024-48875,vulnerability--64af324e-5546-4b13-9a25-64b3bb2cfecb
vulnerability,CVE-2024-48876,vulnerability--6032c00b-e8a1-48f6-8745-d6ea55cb5a1f
vulnerability,CVE-2024-52332,vulnerability--d8256fd1-fab2-4a3c-aed9-fa1e815367a4
vulnerability,CVE-2024-45828,vulnerability--62b6c9da-96b6-4bf7-9521-d7b1277fb938
vulnerability,CVE-2024-12520,vulnerability--8557a0ce-c721-4a17-93d3-8f18ff94474c
vulnerability,CVE-2024-12204,vulnerability--d64bfe37-d147-4942-bbfa-c2248582d3ac
vulnerability,CVE-2024-12627,vulnerability--fea4b886-7be8-48d7-a548-8077914ee0b5
vulnerability,CVE-2024-12472,vulnerability--1d7355a0-26a7-486c-9b70-bca40fcda56c
vulnerability,CVE-2024-12304,vulnerability--9a9cf425-f462-4c99-85f4-33afc71d471a
vulnerability,CVE-2024-12116,vulnerability--9c7de0df-5c15-498d-87b9-117b9c48e364
vulnerability,CVE-2024-12587,vulnerability--78fa1137-ef7d-4af7-a79f-5434685ceb19
vulnerability,CVE-2024-12527,vulnerability--8bb5e866-0f89-47bf-b7e4-866226d00e3f
vulnerability,CVE-2024-12519,vulnerability--d6a51e0e-b55c-4c6e-9893-067425748d40
vulnerability,CVE-2024-12407,vulnerability--d47aa4bf-e369-4977-9616-0c144820c5cc
vulnerability,CVE-2024-12404,vulnerability--b08ae1ef-ed83-4507-9a47-b8a83ee3f753
vulnerability,CVE-2024-12412,vulnerability--388e9388-fc6d-4c42-8591-b55766f7083b
vulnerability,CVE-2024-12505,vulnerability--886ca903-c0b9-437a-afd0-4f40bd3aedf3
vulnerability,CVE-2024-12877,vulnerability--f78dd09d-2c90-4ed4-921d-014840fc56f8
vulnerability,CVE-2024-47794,vulnerability--e7a23e5a-2fbc-466d-ae9f-28680252026b
vulnerability,CVE-2024-47143,vulnerability--f050577f-5420-4ca7-8d35-709b86cb79f3
vulnerability,CVE-2024-47809,vulnerability--8a0dea0e-38f8-4d3c-a1ec-42a32550b4d0
vulnerability,CVE-2024-47408,vulnerability--fd304b88-a717-4a56-8de1-2bdc268f7868
vulnerability,CVE-2024-47141,vulnerability--e06b7ed8-c0a1-46ae-a639-204a96960d94
vulnerability,CVE-2024-50051,vulnerability--d9c38196-8a56-4784-8dc8-11e84974111e
vulnerability,CVE-2024-11874,vulnerability--9f1ac88e-4721-470e-8ad9-dd75ac340b52
vulnerability,CVE-2024-11386,vulnerability--e1b8772a-f841-4882-b27f-0b2c9645bb94
vulnerability,CVE-2024-11327,vulnerability--2b31d55f-e185-4042-9179-192e24116594
vulnerability,CVE-2024-11892,vulnerability--8db2b69a-7b2e-4d58-9d07-4db1284a1452
vulnerability,CVE-2024-11758,vulnerability--39b8e725-d99b-4e0b-816d-173ba6a78746
vulnerability,CVE-2024-11915,vulnerability--451106de-4ac3-4843-ba98-e912938ca653
vulnerability,CVE-2024-53680,vulnerability--3de19761-8a87-4461-be09-ec351f710db7
vulnerability,CVE-2024-53687,vulnerability--960fcdbe-d490-46ea-9b0b-2274b55caa8d
vulnerability,CVE-2024-53682,vulnerability--429e9d62-faf6-4bd8-92c8-99bbc90dce42
vulnerability,CVE-2024-53689,vulnerability--f55aa9fc-10a2-404e-97c0-22f560d0b052
vulnerability,CVE-2024-41932,vulnerability--3e97788d-3e73-4420-9e08-e37a00717c92
vulnerability,CVE-2024-41935,vulnerability--112897d9-c625-4341-854b-8e68457fb576
vulnerability,CVE-2024-41149,vulnerability--b732fb0e-4e16-48c9-b53e-b77f23927286
vulnerability,CVE-2024-54683,vulnerability--baf197e7-9ef5-496b-a358-fb6594c64ef3
vulnerability,CVE-2024-54460,vulnerability--c388cb8f-bbb5-4f49-b68a-5cafde9c5d02
vulnerability,CVE-2024-54191,vulnerability--e7ea5539-7d65-4327-9a50-cc4f7b6e25a0
vulnerability,CVE-2024-55916,vulnerability--0792bbb5-a943-458f-b673-af1eb6f5be18
vulnerability,CVE-2024-55881,vulnerability--4b236d88-e7cd-4761-9504-5970de474369
vulnerability,CVE-2024-55642,vulnerability--cdb7be5e-b4a8-4f0b-9cba-52c29ff6c4c0
vulnerability,CVE-2024-55641,vulnerability--28ee1e04-5586-4ded-b11e-64d9965148bb
vulnerability,CVE-2024-55639,vulnerability--778e0443-a336-4ca0-a3ae-24052f2b086c
vulnerability,CVE-2024-49568,vulnerability--fe719ccb-3c29-479a-968a-36aabbe16689
vulnerability,CVE-2024-49569,vulnerability--ffc9bfea-1dc9-40fc-821c-58d79802fa90
vulnerability,CVE-2024-57838,vulnerability--acb8cf8c-5ba0-40e4-b936-c5192df7c8bc
vulnerability,CVE-2024-57849,vulnerability--893f5821-98a0-4156-8116-309222489843
vulnerability,CVE-2024-57877,vulnerability--21941b8b-24b0-45f9-9629-084d325ac4d6
vulnerability,CVE-2024-57843,vulnerability--367ca5be-b6fb-4e73-8d83-143257d774a6
vulnerability,CVE-2024-57809,vulnerability--36965fcd-1e34-4cc7-9b05-ffea18b83cc5
vulnerability,CVE-2024-57874,vulnerability--8125ba2c-63a0-46f1-a98e-3c2cac9ee9e5
vulnerability,CVE-2024-57881,vulnerability--1546f206-b249-4583-8575-ad2be3951b36
vulnerability,CVE-2024-57839,vulnerability--670b0d74-493a-4799-b161-f40129ce673e
vulnerability,CVE-2024-57872,vulnerability--51d35636-ff22-4fff-b42f-128f781cf71f
vulnerability,CVE-2024-57791,vulnerability--5e8fcbc3-92e7-4960-a1c7-e96cca51c4ec
vulnerability,CVE-2024-57879,vulnerability--8c45ec8b-c879-470c-beb8-a4ffff77d7e8
vulnerability,CVE-2024-57880,vulnerability--cf4dfbd1-b5d6-48af-a144-149da9d8e3e3
vulnerability,CVE-2024-57804,vulnerability--e2fbdd9a-ce55-4859-9f1b-4c4a223255d9
vulnerability,CVE-2024-57850,vulnerability--f269999d-83b0-4119-8608-0427970d4b52
vulnerability,CVE-2024-57876,vulnerability--78b049db-3ddb-41ed-9b50-fd4b6e8d0af3
vulnerability,CVE-2024-57875,vulnerability--93065a56-a497-410a-a3c6-c878c73f875e
vulnerability,CVE-2024-57878,vulnerability--2cfc634f-6324-4e44-b913-ac1ccff3b26a
vulnerability,CVE-2024-56788,vulnerability--c6ba7e2d-891e-4ea4-beff-c8966c5b34a5
vulnerability,CVE-2024-56368,vulnerability--9d60cfd7-7e21-467e-aea1-057c432070ac
vulnerability,CVE-2024-46896,vulnerability--57c9e3e4-1a52-4d80-99e3-7cc7a79dbadd
vulnerability,CVE-2024-42173,vulnerability--2f6b61d6-cede-4408-aac4-da87857008e5
vulnerability,CVE-2024-42175,vulnerability--cec1af85-b60e-4e24-a5ac-7f129be35bd7
vulnerability,CVE-2024-42170,vulnerability--9c4e8ce1-6607-4ca3-a14d-181804800371
vulnerability,CVE-2024-42168,vulnerability--80544640-af23-4fb9-96cf-57cc3991fe6f
vulnerability,CVE-2024-42172,vulnerability--b023bd0e-809d-4b0b-9758-33976641b31a
vulnerability,CVE-2024-42169,vulnerability--508a70ae-abe9-4d9c-836f-5f4784a54eb4
vulnerability,CVE-2024-42174,vulnerability--47b1edc0-c78c-418f-b2b5-eedc64bff448
vulnerability,CVE-2024-42171,vulnerability--7b922828-ee4c-4840-a4f9-034010fbf492
vulnerability,CVE-2024-43098,vulnerability--df37b937-9c76-4267-9a43-9505b1564cc7
vulnerability,CVE-2025-23108,vulnerability--ee2e8f9a-ed8d-49cf-8974-b5969ccb47ec
vulnerability,CVE-2025-23109,vulnerability--eb04c674-dc6b-46da-a55b-3c1f4e075846
vulnerability,CVE-2025-0106,vulnerability--a55e4fb3-21c2-496c-8324-e0aaa86698a8
vulnerability,CVE-2025-0105,vulnerability--a2afe342-585f-4ab6-abb3-9966959525b4
vulnerability,CVE-2025-0390,vulnerability--94939201-04a6-4609-ab3e-2373c0fb49fe
vulnerability,CVE-2025-0104,vulnerability--ea51c7f3-bce5-4305-9759-20406df5e4b0
vulnerability,CVE-2025-0392,vulnerability--26e75131-48c8-4ed9-b393-aa41ef175c2f
vulnerability,CVE-2025-0107,vulnerability--a42855ef-6f7e-48ec-917f-bcdb2bfefce5
vulnerability,CVE-2025-0391,vulnerability--d39a752c-fea1-4850-a767-6f686c2fc6a5
vulnerability,CVE-2025-0103,vulnerability--df60cb9b-0914-492f-9bff-080eafae42f6
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
{
"type": "bundle",
"id": "bundle--ea705c77-43f2-43f5-b306-2faca242d5ac",
"objects": [
{
"type": "vulnerability",
"spec_version": "2.1",
"id": "vulnerability--014ae561-f5d1-410a-b5cd-88443946212c",
"created_by_ref": "identity--8ce3f695-d5a4-4dc8-9e93-a65af453a31a",
"created": "2025-01-12T00:23:19.833041Z",
"modified": "2025-01-12T00:23:19.833041Z",
"name": "CVE-2024-48873",
"description": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: rtw89: check return value of ieee80211_probereq_get() for RNR\n\nThe return value of ieee80211_probereq_get() might be NULL, so check it\nbefore using to avoid NULL pointer access.\n\nAddresses-Coverity-ID: 1529805 (\"Dereference null return value\")",
"external_references": [
{
"source_name": "cve",
"external_id": "CVE-2024-48873"
}
]
}
]
}
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
{
"type": "bundle",
"id": "bundle--cd2b5739-318b-4a34-86ac-c7354d4f9e31",
"objects": [
{
"type": "vulnerability",
"spec_version": "2.1",
"id": "vulnerability--0792bbb5-a943-458f-b673-af1eb6f5be18",
"created_by_ref": "identity--8ce3f695-d5a4-4dc8-9e93-a65af453a31a",
"created": "2025-01-12T00:23:21.539564Z",
"modified": "2025-01-12T00:23:21.539564Z",
"name": "CVE-2024-55916",
"description": "In the Linux kernel, the following vulnerability has been resolved:\n\nDrivers: hv: util: Avoid accessing a ringbuffer not initialized yet\n\nIf the KVP (or VSS) daemon starts before the VMBus channel's ringbuffer is\nfully initialized, we can hit the panic below:\n\nhv_utils: Registering HyperV Utility Driver\nhv_vmbus: registering driver hv_utils\n...\nBUG: kernel NULL pointer dereference, address: 0000000000000000\nCPU: 44 UID: 0 PID: 2552 Comm: hv_kvp_daemon Tainted: G E 6.11.0-rc3+ #1\nRIP: 0010:hv_pkt_iter_first+0x12/0xd0\nCall Trace:\n...\n vmbus_recvpacket\n hv_kvp_onchannelcallback\n vmbus_on_event\n tasklet_action_common\n tasklet_action\n handle_softirqs\n irq_exit_rcu\n sysvec_hyperv_stimer0\n </IRQ>\n <TASK>\n asm_sysvec_hyperv_stimer0\n...\n kvp_register_done\n hvt_op_read\n vfs_read\n ksys_read\n __x64_sys_read\n\nThis can happen because the KVP/VSS channel callback can be invoked\neven before the channel is fully opened:\n1) as soon as hv_kvp_init() -> hvutil_transport_init() creates\n/dev/vmbus/hv_kvp, the kvp daemon can open the device file immediately and\nregister itself to the driver by writing a message KVP_OP_REGISTER1 to the\nfile (which is handled by kvp_on_msg() ->kvp_handle_handshake()) and\nreading the file for the driver's response, which is handled by\nhvt_op_read(), which calls hvt->on_read(), i.e. kvp_register_done().\n\n2) the problem with kvp_register_done() is that it can cause the\nchannel callback to be called even before the channel is fully opened,\nand when the channel callback is starting to run, util_probe()->\nvmbus_open() may have not initialized the ringbuffer yet, so the\ncallback can hit the panic of NULL pointer dereference.\n\nTo reproduce the panic consistently, we can add a \"ssleep(10)\" for KVP in\n__vmbus_open(), just before the first hv_ringbuffer_init(), and then we\nunload and reload the driver hv_utils, and run the daemon manually within\nthe 10 seconds.\n\nFix the panic by reordering the steps in util_probe() so the char dev\nentry used by the KVP or VSS daemon is not created until after\nvmbus_open() has completed. This reordering prevents the race condition\nfrom happening.",
"external_references": [
{
"source_name": "cve",
"external_id": "CVE-2024-55916"
}
]
}
]
}
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
{
"type": "bundle",
"id": "bundle--77994f96-8bfd-4d5d-8f98-4edca1d3e86c",
"objects": [
{
"type": "vulnerability",
"spec_version": "2.1",
"id": "vulnerability--112897d9-c625-4341-854b-8e68457fb576",
"created_by_ref": "identity--8ce3f695-d5a4-4dc8-9e93-a65af453a31a",
"created": "2025-01-12T00:23:21.203596Z",
"modified": "2025-01-12T00:23:21.203596Z",
"name": "CVE-2024-41935",
"description": "In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to shrink read extent node in batches\n\nWe use rwlock to protect core structure data of extent tree during\nits shrink, however, if there is a huge number of extent nodes in\nextent tree, during shrink of extent tree, it may hold rwlock for\na very long time, which may trigger kernel hang issue.\n\nThis patch fixes to shrink read extent node in batches, so that,\ncritical region of the rwlock can be shrunk to avoid its extreme\nlong time hold.",
"external_references": [
{
"source_name": "cve",
"external_id": "CVE-2024-41935"
}
]
}
]
}
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
{
"type": "bundle",
"id": "bundle--8f228117-1d3b-4b77-a782-e1488effa5ac",
"objects": [
{
"type": "vulnerability",
"spec_version": "2.1",
"id": "vulnerability--1546f206-b249-4583-8575-ad2be3951b36",
"created_by_ref": "identity--8ce3f695-d5a4-4dc8-9e93-a65af453a31a",
"created": "2025-01-12T00:23:21.786995Z",
"modified": "2025-01-12T00:23:21.786995Z",
"name": "CVE-2024-57881",
"description": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/page_alloc: don't call pfn_to_page() on possibly non-existent PFN in split_large_buddy()\n\nIn split_large_buddy(), we might call pfn_to_page() on a PFN that might\nnot exist. In corner cases, such as when freeing the highest pageblock in\nthe last memory section, this could result with CONFIG_SPARSEMEM &&\n!CONFIG_SPARSEMEM_EXTREME in __pfn_to_section() returning NULL and and\n__section_mem_map_addr() dereferencing that NULL pointer.\n\nLet's fix it, and avoid doing a pfn_to_page() call for the first\niteration, where we already have the page.\n\nSo far this was found by code inspection, but let's just CC stable as the\nfix is easy.",
"external_references": [
{
"source_name": "cve",
"external_id": "CVE-2024-57881"
}
]
}
]
}
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
{
"type": "bundle",
"id": "bundle--3b8fab9c-6fb1-4b90-8c22-b15af55a3830",
"objects": [
{
"type": "vulnerability",
"spec_version": "2.1",
"id": "vulnerability--1d7355a0-26a7-486c-9b70-bca40fcda56c",
"created_by_ref": "identity--8ce3f695-d5a4-4dc8-9e93-a65af453a31a",
"created": "2025-01-12T00:23:20.106525Z",
"modified": "2025-01-12T00:23:20.106525Z",
"name": "CVE-2024-12472",
"description": "The Post Duplicator plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 2.36 via the mtphr_duplicate_post() due to insufficient restrictions on which posts can be duplicated. This makes it possible for authenticated attackers, with Contributor-level access and above, to extract data from password protected, private, or draft posts that they should not have access to by duplicating the post.",
"external_references": [
{
"source_name": "cve",
"external_id": "CVE-2024-12472"
}
]
}
]
}
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
{
"type": "bundle",
"id": "bundle--f580a575-584b-45da-8b13-7dadcb6d99a6",
"objects": [
{
"type": "vulnerability",
"spec_version": "2.1",
"id": "vulnerability--21941b8b-24b0-45f9-9629-084d325ac4d6",
"created_by_ref": "identity--8ce3f695-d5a4-4dc8-9e93-a65af453a31a",
"created": "2025-01-12T00:23:21.76904Z",
"modified": "2025-01-12T00:23:21.76904Z",
"name": "CVE-2024-57877",
"description": "In the Linux kernel, the following vulnerability has been resolved:\n\narm64: ptrace: fix partial SETREGSET for NT_ARM_POE\n\nCurrently poe_set() doesn't initialize the temporary 'ctrl' variable,\nand a SETREGSET call with a length of zero will leave this\nuninitialized. Consequently an arbitrary value will be written back to\ntarget->thread.por_el0, potentially leaking up to 64 bits of memory from\nthe kernel stack. The read is limited to a specific slot on the stack,\nand the issue does not provide a write mechanism.\n\nFix this by initializing the temporary value before copying the regset\nfrom userspace, as for other regsets (e.g. NT_PRSTATUS, NT_PRFPREG,\nNT_ARM_SYSTEM_CALL). In the case of a zero-length write, the existing\ncontents of POR_EL1 will be retained.\n\nBefore this patch:\n\n| # ./poe-test\n| Attempting to write NT_ARM_POE::por_el0 = 0x900d900d900d900d\n| SETREGSET(nt=0x40f, len=8) wrote 8 bytes\n|\n| Attempting to read NT_ARM_POE::por_el0\n| GETREGSET(nt=0x40f, len=8) read 8 bytes\n| Read NT_ARM_POE::por_el0 = 0x900d900d900d900d\n|\n| Attempting to write NT_ARM_POE (zero length)\n| SETREGSET(nt=0x40f, len=0) wrote 0 bytes\n|\n| Attempting to read NT_ARM_POE::por_el0\n| GETREGSET(nt=0x40f, len=8) read 8 bytes\n| Read NT_ARM_POE::por_el0 = 0xffff8000839c3d50\n\nAfter this patch:\n\n| # ./poe-test\n| Attempting to write NT_ARM_POE::por_el0 = 0x900d900d900d900d\n| SETREGSET(nt=0x40f, len=8) wrote 8 bytes\n|\n| Attempting to read NT_ARM_POE::por_el0\n| GETREGSET(nt=0x40f, len=8) read 8 bytes\n| Read NT_ARM_POE::por_el0 = 0x900d900d900d900d\n|\n| Attempting to write NT_ARM_POE (zero length)\n| SETREGSET(nt=0x40f, len=0) wrote 0 bytes\n|\n| Attempting to read NT_ARM_POE::por_el0\n| GETREGSET(nt=0x40f, len=8) read 8 bytes\n| Read NT_ARM_POE::por_el0 = 0x900d900d900d900d",
"external_references": [
{
"source_name": "cve",
"external_id": "CVE-2024-57877"
}
]
}
]
}
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
{
"type": "bundle",
"id": "bundle--6f9a8003-2b8c-4e79-987b-1288d297d05c",
"objects": [
{
"type": "vulnerability",
"spec_version": "2.1",
"id": "vulnerability--26e75131-48c8-4ed9-b393-aa41ef175c2f",
"created_by_ref": "identity--8ce3f695-d5a4-4dc8-9e93-a65af453a31a",
"created": "2025-01-12T00:23:31.954645Z",
"modified": "2025-01-12T00:23:31.954645Z",
"name": "CVE-2025-0392",
"description": "A vulnerability, which was classified as critical, was found in Guangzhou Huayi Intelligent Technology Jeewms up to 20241229. Affected is the function datagridGraph of the file /graphReportController.do. The manipulation of the argument store_code leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 20250101 is able to address this issue. It is recommended to upgrade the affected component.",
"external_references": [
{
"source_name": "cve",
"external_id": "CVE-2025-0392"
}
]
}
]
}
Loading

0 comments on commit a93ea1c

Please sign in to comment.