Skip to content

Commit

Permalink
generated content from 2024-03-03
Browse files Browse the repository at this point in the history
  • Loading branch information
github-actions[bot] committed Mar 3, 2024
1 parent a68f719 commit ac84e86
Show file tree
Hide file tree
Showing 75 changed files with 1,702 additions and 0 deletions.
74 changes: 74 additions & 0 deletions mapping.csv
Original file line number Diff line number Diff line change
Expand Up @@ -227085,3 +227085,77 @@ vulnerability,CVE-2021-47080,vulnerability--286bcfc5-e368-43d2-bb4a-caeea3b5d125
vulnerability,CVE-2021-47077,vulnerability--4d7e6476-0fa8-4929-a746-b0f32e94bf6f
vulnerability,CVE-2021-47076,vulnerability--4dc5730a-a2dc-448b-bc81-db480515749a
vulnerability,CVE-2021-47072,vulnerability--10c88075-b904-479b-b9f4-9e59f0e0d9ae
vulnerability,CVE-2023-52564,vulnerability--04832f55-4be1-4d20-978d-3d73af77e25c
vulnerability,CVE-2023-52579,vulnerability--4e6f8443-6087-47b4-83b4-03665e13452e
vulnerability,CVE-2023-52572,vulnerability--55b4a5f6-f452-45d8-b4c1-01b2d20cac27
vulnerability,CVE-2023-52504,vulnerability--0de7bfea-e133-44b2-a1a6-e7db5ae65510
vulnerability,CVE-2023-52562,vulnerability--d202c5b3-d8aa-445e-a135-7f16d66b519e
vulnerability,CVE-2023-52570,vulnerability--9795c44e-51ba-4762-8fd2-a30494a4ed60
vulnerability,CVE-2023-52530,vulnerability--7d508459-b30a-4769-b737-00a6734cd097
vulnerability,CVE-2023-52574,vulnerability--142cca65-8675-448a-b4b9-3f67f73906ac
vulnerability,CVE-2023-52514,vulnerability--c1c06518-4534-4435-9676-b60d1847ad29
vulnerability,CVE-2023-52531,vulnerability--915df851-0c69-4d93-87d8-d0b914d429a3
vulnerability,CVE-2023-52520,vulnerability--fce09b58-4a16-42ae-8c8d-9682e66da361
vulnerability,CVE-2023-52566,vulnerability--9e097180-4478-4858-92ba-8b054cb623b1
vulnerability,CVE-2023-52569,vulnerability--696a10c7-c2d2-455a-8db4-a617938b21d8
vulnerability,CVE-2023-52567,vulnerability--4e73a045-a2b4-410f-ad0d-524a8726f008
vulnerability,CVE-2023-52575,vulnerability--6e0577b8-af98-4a6e-89d0-f8291066ebb6
vulnerability,CVE-2023-52511,vulnerability--a7027e95-b457-4bf5-b7e4-e6057c762742
vulnerability,CVE-2023-52515,vulnerability--be84bcb4-b64f-47f6-9b29-d34e6055cf6d
vulnerability,CVE-2023-52501,vulnerability--ea8a781a-2c42-4743-9446-54fe91ec59ec
vulnerability,CVE-2023-52508,vulnerability--bbba0ff6-5526-4771-8a51-643593d49583
vulnerability,CVE-2023-52571,vulnerability--e801e45c-702e-4905-9f01-9dd7fecba599
vulnerability,CVE-2023-52573,vulnerability--59efe81c-f6ae-49c9-b792-ed09b5c89590
vulnerability,CVE-2023-52502,vulnerability--f9c7e9fd-5874-4420-9fbb-a7897324f358
vulnerability,CVE-2023-52568,vulnerability--61fac656-6145-4702-bc08-8f77f3b0578f
vulnerability,CVE-2023-52578,vulnerability--e4caadd8-1940-442c-bcec-75798af07d93
vulnerability,CVE-2023-52529,vulnerability--0fc21ed5-f968-4ddd-898a-fc4b08d92ff9
vulnerability,CVE-2023-52521,vulnerability--415d5ec2-4e4b-4309-a6ea-d8f4b7642f07
vulnerability,CVE-2023-52512,vulnerability--70bf28e8-c244-414c-8593-48b4ae4b9216
vulnerability,CVE-2023-52517,vulnerability--2f7be6d5-a916-4363-b5bb-21d6dca0db99
vulnerability,CVE-2023-52560,vulnerability--773d626f-5d9a-4238-b90e-98ff64c8e320
vulnerability,CVE-2023-52527,vulnerability--8abe938f-67b4-464e-be16-6131e97b6892
vulnerability,CVE-2023-52581,vulnerability--e7cc82bc-deca-4abf-ae72-f65e19829210
vulnerability,CVE-2023-52559,vulnerability--479fa90f-cded-4db1-b334-6f047ce3e282
vulnerability,CVE-2023-52503,vulnerability--81d47425-14d5-4a9a-9697-02378fbb48ab
vulnerability,CVE-2023-52513,vulnerability--771253ed-3254-4e0d-b27a-aa06613a2ed1
vulnerability,CVE-2023-52510,vulnerability--762433d3-43f1-427a-b78c-f97709f75ea9
vulnerability,CVE-2023-52507,vulnerability--a4064b19-f0be-4189-a850-bf62af9eaa66
vulnerability,CVE-2023-52526,vulnerability--66c78ecd-e52b-4c1f-ae3f-507e482030cf
vulnerability,CVE-2023-52509,vulnerability--e75695f6-7363-447d-afce-ffe864915707
vulnerability,CVE-2023-52525,vulnerability--7ac9ca9e-47da-4eff-b48d-43726da5976f
vulnerability,CVE-2023-52580,vulnerability--86f52f71-c019-4c32-affc-bf2845031db5
vulnerability,CVE-2023-52528,vulnerability--8198aee3-60a7-4fa9-b5e5-681eef95db70
vulnerability,CVE-2023-52518,vulnerability--73887382-7649-45a9-ba3a-03ff62e6634b
vulnerability,CVE-2023-52505,vulnerability--b11d9a4d-b8b0-4d8d-a94c-c2f6eb0c955f
vulnerability,CVE-2023-52506,vulnerability--787b3ef2-2482-4d15-9425-9f381bf2948b
vulnerability,CVE-2023-52519,vulnerability--c4eae00e-b88e-4ab7-acbe-8e941efe4252
vulnerability,CVE-2023-52523,vulnerability--6f099bcf-63e1-4c9b-88ae-1e02752130f8
vulnerability,CVE-2023-52516,vulnerability--7cc81d22-9a01-4cbc-bbc8-fdf1969045d5
vulnerability,CVE-2023-52565,vulnerability--db510681-418d-4bcd-ad89-1563daccc513
vulnerability,CVE-2023-52582,vulnerability--59e7486f-ab7e-40b5-bba0-6ea0f5985da6
vulnerability,CVE-2023-52577,vulnerability--1856925d-86d5-4f29-ab5d-a078cb62bad4
vulnerability,CVE-2023-52499,vulnerability--3fd99934-972b-4069-a988-31f9ab3c21bf
vulnerability,CVE-2023-52561,vulnerability--ee0d30b6-8989-4619-a4e7-43ea2661f775
vulnerability,CVE-2023-52524,vulnerability--12def761-59b2-4a56-a236-10eb2c3f94d3
vulnerability,CVE-2023-52500,vulnerability--22112368-12c4-4a1f-b012-d3fd9ae3d7d6
vulnerability,CVE-2023-52522,vulnerability--f29492f5-41d3-4a67-9e34-d1eb501a741d
vulnerability,CVE-2023-52563,vulnerability--c45027e8-60a7-4ac5-9b7b-98a3312d20ad
vulnerability,CVE-2023-52576,vulnerability--34857cb0-2b31-4faf-87f4-ed71f6344f7a
vulnerability,CVE-2023-52532,vulnerability--9749312b-b9a1-4e4d-beb4-86c05e5bac9f
vulnerability,CVE-2023-6326,vulnerability--d05d87ec-3157-411e-9f94-098141011a0b
vulnerability,CVE-2024-1398,vulnerability--95cb6efb-8594-4e93-9b6b-301db342bb32
vulnerability,CVE-2024-1449,vulnerability--7ed10d6e-a871-456c-8f72-f960288f6c72
vulnerability,CVE-2024-1775,vulnerability--02867746-6078-46ef-ba5b-20896443cfef
vulnerability,CVE-2024-1592,vulnerability--d7908765-ad69-473d-ab04-9d9e9dddd88c
vulnerability,CVE-2024-2133,vulnerability--d987a35f-a8bb-45bf-89d6-1fcac6ed4543
vulnerability,CVE-2024-26621,vulnerability--e7ac6463-fd4d-449b-8f94-c63e2007a4cd
vulnerability,CVE-2024-0378,vulnerability--e77ce173-ac9a-4927-9993-c27f549e5a1a
vulnerability,CVE-2024-0611,vulnerability--9a0a1908-466f-44e3-ba62-286835790518
vulnerability,CVE-2024-0795,vulnerability--ef422de8-74df-4b90-b721-431c3cf9142c
vulnerability,CVE-2024-0968,vulnerability--91a51649-9610-4374-88c5-603c4eb82ea3
vulnerability,CVE-2024-25865,vulnerability--51e82b20-7af6-42a8-aa1a-19985118347c
vulnerability,CVE-2024-25064,vulnerability--d6cf0ac7-649d-41c0-82e8-8a59490bc60c
vulnerability,CVE-2024-25063,vulnerability--aaf7cd84-9ee2-465b-bce6-2b6fa9122bb7
vulnerability,CVE-2022-48628,vulnerability--62ada9be-d114-47d7-a69a-12ea33797243
vulnerability,CVE-2022-48627,vulnerability--ea69b183-893a-4e53-b35f-e2a1448e0365
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
{
"type": "bundle",
"id": "bundle--7954d544-982d-4ea1-a542-10912b18bb0d",
"objects": [
{
"type": "vulnerability",
"spec_version": "2.1",
"id": "vulnerability--02867746-6078-46ef-ba5b-20896443cfef",
"created_by_ref": "identity--8ce3f695-d5a4-4dc8-9e93-a65af453a31a",
"created": "2024-03-03T00:29:04.083487Z",
"modified": "2024-03-03T00:29:04.083487Z",
"name": "CVE-2024-1775",
"description": "The Nextend Social Login and Register plugin for WordPress is vulnerable to a self-based Reflected Cross-Site Scripting via the ‘error_description’ parameter in all versions up to, and including, 3.1.12 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers, with access to a subscriber-level account, to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. NOTE: This vulnerability can be successfully exploited on a vulnerable WordPress instance against an OAuth pre-authenticated higher-level user (e.g., administrator) by leveraging a cross-site request forgery in conjunction with a certain social engineering technique to achieve a critical impact scenario (cross-site scripting to administrator-level account creation). However, successful exploitation requires \"Debug mode\" to be enabled in the plugin's \"Global Settings\".",
"external_references": [
{
"source_name": "cve",
"external_id": "CVE-2024-1775"
}
]
}
]
}
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
{
"type": "bundle",
"id": "bundle--7245c8d8-c479-45be-ab21-bf602b07244b",
"objects": [
{
"type": "vulnerability",
"spec_version": "2.1",
"id": "vulnerability--04832f55-4be1-4d20-978d-3d73af77e25c",
"created_by_ref": "identity--8ce3f695-d5a4-4dc8-9e93-a65af453a31a",
"created": "2024-03-03T00:29:00.82631Z",
"modified": "2024-03-03T00:29:00.82631Z",
"name": "CVE-2023-52564",
"description": "In the Linux kernel, the following vulnerability has been resolved:\n\nRevert \"tty: n_gsm: fix UAF in gsm_cleanup_mux\"\n\nThis reverts commit 9b9c8195f3f0d74a826077fc1c01b9ee74907239.\n\nThe commit above is reverted as it did not solve the original issue.\n\ngsm_cleanup_mux() tries to free up the virtual ttys by calling\ngsm_dlci_release() for each available DLCI. There, dlci_put() is called to\ndecrease the reference counter for the DLCI via tty_port_put() which\nfinally calls gsm_dlci_free(). This already clears the pointer which is\nbeing checked in gsm_cleanup_mux() before calling gsm_dlci_release().\nTherefore, it is not necessary to clear this pointer in gsm_cleanup_mux()\nas done in the reverted commit. The commit introduces a null pointer\ndereference:\n <TASK>\n ? __die+0x1f/0x70\n ? page_fault_oops+0x156/0x420\n ? search_exception_tables+0x37/0x50\n ? fixup_exception+0x21/0x310\n ? exc_page_fault+0x69/0x150\n ? asm_exc_page_fault+0x26/0x30\n ? tty_port_put+0x19/0xa0\n gsmtty_cleanup+0x29/0x80 [n_gsm]\n release_one_tty+0x37/0xe0\n process_one_work+0x1e6/0x3e0\n worker_thread+0x4c/0x3d0\n ? __pfx_worker_thread+0x10/0x10\n kthread+0xe1/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\nThe actual issue is that nothing guards dlci_put() from being called\nmultiple times while the tty driver was triggered but did not yet finished\ncalling gsm_dlci_free().",
"external_references": [
{
"source_name": "cve",
"external_id": "CVE-2023-52564"
}
]
}
]
}
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
{
"type": "bundle",
"id": "bundle--a7f2074d-fe81-474a-a996-f215f749d701",
"objects": [
{
"type": "vulnerability",
"spec_version": "2.1",
"id": "vulnerability--0de7bfea-e133-44b2-a1a6-e7db5ae65510",
"created_by_ref": "identity--8ce3f695-d5a4-4dc8-9e93-a65af453a31a",
"created": "2024-03-03T00:29:00.831288Z",
"modified": "2024-03-03T00:29:00.831288Z",
"name": "CVE-2023-52504",
"description": "In the Linux kernel, the following vulnerability has been resolved:\n\nx86/alternatives: Disable KASAN in apply_alternatives()\n\nFei has reported that KASAN triggers during apply_alternatives() on\na 5-level paging machine:\n\n\tBUG: KASAN: out-of-bounds in rcu_is_watching()\n\tRead of size 4 at addr ff110003ee6419a0 by task swapper/0/0\n\t...\n\t__asan_load4()\n\trcu_is_watching()\n\ttrace_hardirqs_on()\n\ttext_poke_early()\n\tapply_alternatives()\n\t...\n\nOn machines with 5-level paging, cpu_feature_enabled(X86_FEATURE_LA57)\ngets patched. It includes KASAN code, where KASAN_SHADOW_START depends on\n__VIRTUAL_MASK_SHIFT, which is defined with cpu_feature_enabled().\n\nKASAN gets confused when apply_alternatives() patches the\nKASAN_SHADOW_START users. A test patch that makes KASAN_SHADOW_START\nstatic, by replacing __VIRTUAL_MASK_SHIFT with 56, works around the issue.\n\nFix it for real by disabling KASAN while the kernel is patching alternatives.\n\n[ mingo: updated the changelog ]",
"external_references": [
{
"source_name": "cve",
"external_id": "CVE-2023-52504"
}
]
}
]
}
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
{
"type": "bundle",
"id": "bundle--aad58467-efa3-4498-84e6-3811fbe1b7e3",
"objects": [
{
"type": "vulnerability",
"spec_version": "2.1",
"id": "vulnerability--0fc21ed5-f968-4ddd-898a-fc4b08d92ff9",
"created_by_ref": "identity--8ce3f695-d5a4-4dc8-9e93-a65af453a31a",
"created": "2024-03-03T00:29:00.864747Z",
"modified": "2024-03-03T00:29:00.864747Z",
"name": "CVE-2023-52529",
"description": "In the Linux kernel, the following vulnerability has been resolved:\n\nHID: sony: Fix a potential memory leak in sony_probe()\n\nIf an error occurs after a successful usb_alloc_urb() call, usb_free_urb()\nshould be called.",
"external_references": [
{
"source_name": "cve",
"external_id": "CVE-2023-52529"
}
]
}
]
}
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
{
"type": "bundle",
"id": "bundle--65fb84a1-7391-4b2f-85a5-0639709e8692",
"objects": [
{
"type": "vulnerability",
"spec_version": "2.1",
"id": "vulnerability--12def761-59b2-4a56-a236-10eb2c3f94d3",
"created_by_ref": "identity--8ce3f695-d5a4-4dc8-9e93-a65af453a31a",
"created": "2024-03-03T00:29:00.905199Z",
"modified": "2024-03-03T00:29:00.905199Z",
"name": "CVE-2023-52524",
"description": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: nfc: llcp: Add lock when modifying device list\n\nThe device list needs its associated lock held when modifying it, or the\nlist could become corrupted, as syzbot discovered.",
"external_references": [
{
"source_name": "cve",
"external_id": "CVE-2023-52524"
}
]
}
]
}
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
{
"type": "bundle",
"id": "bundle--90a469a5-d5ec-4675-8e45-a9ee1b873611",
"objects": [
{
"type": "vulnerability",
"spec_version": "2.1",
"id": "vulnerability--142cca65-8675-448a-b4b9-3f67f73906ac",
"created_by_ref": "identity--8ce3f695-d5a4-4dc8-9e93-a65af453a31a",
"created": "2024-03-03T00:29:00.839448Z",
"modified": "2024-03-03T00:29:00.839448Z",
"name": "CVE-2023-52574",
"description": "In the Linux kernel, the following vulnerability has been resolved:\n\nteam: fix null-ptr-deref when team device type is changed\n\nGet a null-ptr-deref bug as follows with reproducer [1].\n\nBUG: kernel NULL pointer dereference, address: 0000000000000228\n...\nRIP: 0010:vlan_dev_hard_header+0x35/0x140 [8021q]\n...\nCall Trace:\n <TASK>\n ? __die+0x24/0x70\n ? page_fault_oops+0x82/0x150\n ? exc_page_fault+0x69/0x150\n ? asm_exc_page_fault+0x26/0x30\n ? vlan_dev_hard_header+0x35/0x140 [8021q]\n ? vlan_dev_hard_header+0x8e/0x140 [8021q]\n neigh_connected_output+0xb2/0x100\n ip6_finish_output2+0x1cb/0x520\n ? nf_hook_slow+0x43/0xc0\n ? ip6_mtu+0x46/0x80\n ip6_finish_output+0x2a/0xb0\n mld_sendpack+0x18f/0x250\n mld_ifc_work+0x39/0x160\n process_one_work+0x1e6/0x3f0\n worker_thread+0x4d/0x2f0\n ? __pfx_worker_thread+0x10/0x10\n kthread+0xe5/0x120\n ? __pfx_kthread+0x10/0x10\n ret_from_fork+0x34/0x50\n ? __pfx_kthread+0x10/0x10\n ret_from_fork_asm+0x1b/0x30\n\n[1]\n$ teamd -t team0 -d -c '{\"runner\": {\"name\": \"loadbalance\"}}'\n$ ip link add name t-dummy type dummy\n$ ip link add link t-dummy name t-dummy.100 type vlan id 100\n$ ip link add name t-nlmon type nlmon\n$ ip link set t-nlmon master team0\n$ ip link set t-nlmon nomaster\n$ ip link set t-dummy up\n$ ip link set team0 up\n$ ip link set t-dummy.100 down\n$ ip link set t-dummy.100 master team0\n\nWhen enslave a vlan device to team device and team device type is changed\nfrom non-ether to ether, header_ops of team device is changed to\nvlan_header_ops. That is incorrect and will trigger null-ptr-deref\nfor vlan->real_dev in vlan_dev_hard_header() because team device is not\na vlan device.\n\nCache eth_header_ops in team_setup(), then assign cached header_ops to\nheader_ops of team net device when its type is changed from non-ether\nto ether to fix the bug.",
"external_references": [
{
"source_name": "cve",
"external_id": "CVE-2023-52574"
}
]
}
]
}
Loading

0 comments on commit ac84e86

Please sign in to comment.