From a8f86b31a4a889cbe1b201e46d89ff0559b35ca8 Mon Sep 17 00:00:00 2001 From: cad-safe-bot Date: Thu, 20 Jun 2024 14:03:13 +0000 Subject: [PATCH] Auto-Update: 2024-06-20T14:00:20.555063+00:00 --- CVE-2018/CVE-2018-251xx/CVE-2018-25103.json | 4 +- CVE-2021/CVE-2021-44xx/CVE-2021-4439.json | 48 ++ CVE-2021/CVE-2021-475xx/CVE-2021-47576.json | 8 +- CVE-2021/CVE-2021-475xx/CVE-2021-47577.json | 8 +- CVE-2021/CVE-2021-475xx/CVE-2021-47578.json | 8 +- CVE-2021/CVE-2021-475xx/CVE-2021-47579.json | 8 +- CVE-2021/CVE-2021-475xx/CVE-2021-47580.json | 8 +- CVE-2021/CVE-2021-475xx/CVE-2021-47582.json | 8 +- CVE-2021/CVE-2021-475xx/CVE-2021-47583.json | 8 +- CVE-2021/CVE-2021-475xx/CVE-2021-47584.json | 8 +- CVE-2021/CVE-2021-475xx/CVE-2021-47585.json | 8 +- CVE-2021/CVE-2021-475xx/CVE-2021-47586.json | 8 +- CVE-2021/CVE-2021-475xx/CVE-2021-47587.json | 8 +- CVE-2021/CVE-2021-475xx/CVE-2021-47588.json | 8 +- CVE-2021/CVE-2021-475xx/CVE-2021-47589.json | 8 +- CVE-2021/CVE-2021-475xx/CVE-2021-47590.json | 8 +- CVE-2021/CVE-2021-475xx/CVE-2021-47591.json | 8 +- CVE-2021/CVE-2021-475xx/CVE-2021-47592.json | 8 +- CVE-2021/CVE-2021-475xx/CVE-2021-47593.json | 8 +- CVE-2021/CVE-2021-475xx/CVE-2021-47594.json | 8 +- CVE-2021/CVE-2021-475xx/CVE-2021-47595.json | 8 +- CVE-2021/CVE-2021-475xx/CVE-2021-47596.json | 8 +- CVE-2021/CVE-2021-475xx/CVE-2021-47597.json | 8 +- CVE-2021/CVE-2021-475xx/CVE-2021-47598.json | 8 +- CVE-2021/CVE-2021-475xx/CVE-2021-47599.json | 8 +- CVE-2021/CVE-2021-476xx/CVE-2021-47600.json | 8 +- CVE-2021/CVE-2021-476xx/CVE-2021-47601.json | 8 +- CVE-2021/CVE-2021-476xx/CVE-2021-47602.json | 8 +- CVE-2021/CVE-2021-476xx/CVE-2021-47603.json | 8 +- CVE-2021/CVE-2021-476xx/CVE-2021-47604.json | 8 +- CVE-2021/CVE-2021-476xx/CVE-2021-47605.json | 8 +- CVE-2021/CVE-2021-476xx/CVE-2021-47606.json | 8 +- CVE-2021/CVE-2021-476xx/CVE-2021-47607.json | 8 +- CVE-2021/CVE-2021-476xx/CVE-2021-47608.json | 8 +- CVE-2021/CVE-2021-476xx/CVE-2021-47609.json | 8 +- CVE-2021/CVE-2021-476xx/CVE-2021-47610.json | 8 +- CVE-2021/CVE-2021-476xx/CVE-2021-47611.json | 8 +- CVE-2021/CVE-2021-476xx/CVE-2021-47612.json | 8 +- CVE-2021/CVE-2021-476xx/CVE-2021-47613.json | 8 +- CVE-2021/CVE-2021-476xx/CVE-2021-47614.json | 8 +- CVE-2021/CVE-2021-476xx/CVE-2021-47615.json | 8 +- CVE-2021/CVE-2021-476xx/CVE-2021-47616.json | 8 +- CVE-2021/CVE-2021-476xx/CVE-2021-47617.json | 8 +- CVE-2021/CVE-2021-476xx/CVE-2021-47618.json | 8 +- CVE-2021/CVE-2021-476xx/CVE-2021-47619.json | 8 +- CVE-2021/CVE-2021-476xx/CVE-2021-47620.json | 8 +- CVE-2022/CVE-2022-238xx/CVE-2022-23829.json | 8 +- CVE-2022/CVE-2022-458xx/CVE-2022-45832.json | 8 +- CVE-2022/CVE-2022-487xx/CVE-2022-48711.json | 8 +- CVE-2022/CVE-2022-487xx/CVE-2022-48712.json | 8 +- CVE-2022/CVE-2022-487xx/CVE-2022-48713.json | 8 +- CVE-2022/CVE-2022-487xx/CVE-2022-48714.json | 8 +- CVE-2022/CVE-2022-487xx/CVE-2022-48715.json | 8 +- CVE-2022/CVE-2022-487xx/CVE-2022-48716.json | 8 +- CVE-2022/CVE-2022-487xx/CVE-2022-48717.json | 8 +- CVE-2022/CVE-2022-487xx/CVE-2022-48718.json | 8 +- CVE-2022/CVE-2022-487xx/CVE-2022-48719.json | 8 +- CVE-2022/CVE-2022-487xx/CVE-2022-48720.json | 8 +- CVE-2022/CVE-2022-487xx/CVE-2022-48721.json | 8 +- CVE-2022/CVE-2022-487xx/CVE-2022-48722.json | 8 +- CVE-2022/CVE-2022-487xx/CVE-2022-48723.json | 8 +- CVE-2022/CVE-2022-487xx/CVE-2022-48724.json | 44 + CVE-2022/CVE-2022-487xx/CVE-2022-48725.json | 28 + CVE-2022/CVE-2022-487xx/CVE-2022-48726.json | 32 + CVE-2022/CVE-2022-487xx/CVE-2022-48727.json | 28 + CVE-2022/CVE-2022-487xx/CVE-2022-48728.json | 32 + CVE-2022/CVE-2022-487xx/CVE-2022-48729.json | 24 + CVE-2022/CVE-2022-487xx/CVE-2022-48730.json | 32 + CVE-2022/CVE-2022-487xx/CVE-2022-48731.json | 36 + CVE-2022/CVE-2022-487xx/CVE-2022-48732.json | 48 ++ CVE-2022/CVE-2022-487xx/CVE-2022-48733.json | 28 + CVE-2022/CVE-2022-487xx/CVE-2022-48734.json | 36 + CVE-2022/CVE-2022-487xx/CVE-2022-48735.json | 32 + CVE-2022/CVE-2022-487xx/CVE-2022-48736.json | 48 ++ CVE-2022/CVE-2022-487xx/CVE-2022-48737.json | 48 ++ CVE-2022/CVE-2022-487xx/CVE-2022-48738.json | 48 ++ CVE-2022/CVE-2022-487xx/CVE-2022-48739.json | 28 + CVE-2022/CVE-2022-487xx/CVE-2022-48740.json | 32 + CVE-2022/CVE-2022-487xx/CVE-2022-48741.json | 28 + CVE-2022/CVE-2022-487xx/CVE-2022-48742.json | 48 ++ CVE-2022/CVE-2022-487xx/CVE-2022-48743.json | 48 ++ CVE-2022/CVE-2022-487xx/CVE-2022-48744.json | 24 + CVE-2022/CVE-2022-487xx/CVE-2022-48745.json | 32 + CVE-2022/CVE-2022-487xx/CVE-2022-48746.json | 32 + CVE-2022/CVE-2022-487xx/CVE-2022-48747.json | 36 + CVE-2022/CVE-2022-487xx/CVE-2022-48748.json | 32 + CVE-2022/CVE-2022-487xx/CVE-2022-48749.json | 32 + CVE-2022/CVE-2022-487xx/CVE-2022-48750.json | 24 + CVE-2022/CVE-2022-487xx/CVE-2022-48751.json | 28 + CVE-2022/CVE-2022-487xx/CVE-2022-48752.json | 32 + CVE-2022/CVE-2022-487xx/CVE-2022-48753.json | 24 + CVE-2022/CVE-2022-487xx/CVE-2022-48754.json | 40 + CVE-2022/CVE-2022-487xx/CVE-2022-48755.json | 32 + CVE-2022/CVE-2022-487xx/CVE-2022-48756.json | 44 + CVE-2022/CVE-2022-487xx/CVE-2022-48757.json | 52 ++ CVE-2022/CVE-2022-487xx/CVE-2022-48758.json | 52 ++ CVE-2022/CVE-2022-487xx/CVE-2022-48759.json | 44 + CVE-2022/CVE-2022-487xx/CVE-2022-48760.json | 52 ++ CVE-2022/CVE-2022-487xx/CVE-2022-48761.json | 32 + CVE-2022/CVE-2022-487xx/CVE-2022-48762.json | 24 + CVE-2022/CVE-2022-487xx/CVE-2022-48763.json | 32 + CVE-2022/CVE-2022-487xx/CVE-2022-48764.json | 24 + CVE-2022/CVE-2022-487xx/CVE-2022-48765.json | 28 + CVE-2022/CVE-2022-487xx/CVE-2022-48766.json | 24 + CVE-2022/CVE-2022-487xx/CVE-2022-48767.json | 32 + CVE-2022/CVE-2022-487xx/CVE-2022-48768.json | 36 + CVE-2022/CVE-2022-487xx/CVE-2022-48769.json | 32 + CVE-2022/CVE-2022-487xx/CVE-2022-48770.json | 32 + CVE-2022/CVE-2022-487xx/CVE-2022-48771.json | 44 + CVE-2023/CVE-2023-256xx/CVE-2023-25646.json | 8 +- CVE-2023/CVE-2023-256xx/CVE-2023-25697.json | 8 +- CVE-2023/CVE-2023-32xx/CVE-2023-3204.json | 8 +- CVE-2023/CVE-2023-350xx/CVE-2023-35049.json | 8 +- CVE-2023/CVE-2023-350xx/CVE-2023-35050.json | 8 +- CVE-2023/CVE-2023-365xx/CVE-2023-36512.json | 8 +- CVE-2023/CVE-2023-365xx/CVE-2023-36515.json | 8 +- CVE-2023/CVE-2023-365xx/CVE-2023-36516.json | 8 +- CVE-2023/CVE-2023-366xx/CVE-2023-36676.json | 8 +- CVE-2023/CVE-2023-366xx/CVE-2023-36683.json | 8 +- CVE-2023/CVE-2023-366xx/CVE-2023-36684.json | 8 +- CVE-2023/CVE-2023-370xx/CVE-2023-37057.json | 8 +- CVE-2023/CVE-2023-370xx/CVE-2023-37058.json | 8 +- CVE-2023/CVE-2023-378xx/CVE-2023-37869.json | 8 +- CVE-2023/CVE-2023-378xx/CVE-2023-37870.json | 8 +- CVE-2023/CVE-2023-378xx/CVE-2023-37872.json | 8 +- CVE-2023/CVE-2023-383xx/CVE-2023-38386.json | 8 +- CVE-2023/CVE-2023-383xx/CVE-2023-38393.json | 8 +- CVE-2023/CVE-2023-383xx/CVE-2023-38394.json | 8 +- CVE-2023/CVE-2023-393xx/CVE-2023-39310.json | 8 +- CVE-2023/CVE-2023-393xx/CVE-2023-39312.json | 8 +- CVE-2023/CVE-2023-399xx/CVE-2023-39922.json | 8 +- CVE-2023/CVE-2023-399xx/CVE-2023-39990.json | 8 +- CVE-2023/CVE-2023-399xx/CVE-2023-39993.json | 8 +- CVE-2023/CVE-2023-399xx/CVE-2023-39998.json | 8 +- CVE-2023/CVE-2023-400xx/CVE-2023-40004.json | 8 +- CVE-2023/CVE-2023-406xx/CVE-2023-40608.json | 8 +- CVE-2023/CVE-2023-418xx/CVE-2023-41805.json | 8 +- CVE-2023/CVE-2023-441xx/CVE-2023-44148.json | 8 +- CVE-2023/CVE-2023-441xx/CVE-2023-44151.json | 8 +- CVE-2023/CVE-2023-456xx/CVE-2023-45658.json | 8 +- CVE-2023/CVE-2023-461xx/CVE-2023-46146.json | 8 +- CVE-2023/CVE-2023-461xx/CVE-2023-46148.json | 8 +- CVE-2023/CVE-2023-476xx/CVE-2023-47681.json | 8 +- CVE-2023/CVE-2023-477xx/CVE-2023-47726.json | 8 +- CVE-2023/CVE-2023-477xx/CVE-2023-47770.json | 8 +- CVE-2023/CVE-2023-477xx/CVE-2023-47771.json | 8 +- CVE-2023/CVE-2023-477xx/CVE-2023-47783.json | 8 +- CVE-2023/CVE-2023-477xx/CVE-2023-47788.json | 8 +- CVE-2023/CVE-2023-487xx/CVE-2023-48759.json | 8 +- CVE-2023/CVE-2023-487xx/CVE-2023-48760.json | 8 +- CVE-2023/CVE-2023-487xx/CVE-2023-48761.json | 8 +- CVE-2023/CVE-2023-491xx/CVE-2023-49110.json | 36 + CVE-2023/CVE-2023-491xx/CVE-2023-49111.json | 36 + CVE-2023/CVE-2023-491xx/CVE-2023-49112.json | 24 + CVE-2023/CVE-2023-491xx/CVE-2023-49113.json | 36 + CVE-2023/CVE-2023-509xx/CVE-2023-50900.json | 8 +- CVE-2023/CVE-2023-528xx/CVE-2023-52883.json | 24 + CVE-2023/CVE-2023-55xx/CVE-2023-5527.json | 8 +- CVE-2023/CVE-2023-64xx/CVE-2023-6495.json | 8 +- CVE-2023/CVE-2023-66xx/CVE-2023-6692.json | 8 +- CVE-2024/CVE-2024-00xx/CVE-2024-0066.json | 8 +- CVE-2024/CVE-2024-03xx/CVE-2024-0383.json | 8 +- CVE-2024/CVE-2024-03xx/CVE-2024-0397.json | 8 +- CVE-2024/CVE-2024-07xx/CVE-2024-0789.json | 8 +- CVE-2024/CVE-2024-08xx/CVE-2024-0845.json | 8 +- CVE-2024/CVE-2024-11xx/CVE-2024-1168.json | 8 +- CVE-2024/CVE-2024-14xx/CVE-2024-1407.json | 8 +- CVE-2024/CVE-2024-16xx/CVE-2024-1634.json | 8 +- CVE-2024/CVE-2024-216xx/CVE-2024-21685.json | 8 +- CVE-2024/CVE-2024-220xx/CVE-2024-22002.json | 8 +- CVE-2024/CVE-2024-222xx/CVE-2024-22263.json | 8 +- CVE-2024/CVE-2024-234xx/CVE-2024-23443.json | 8 +- CVE-2024/CVE-2024-23xx/CVE-2024-2381.json | 8 +- CVE-2024/CVE-2024-281xx/CVE-2024-28147.json | 8 +- CVE-2024/CVE-2024-290xx/CVE-2024-29012.json | 8 +- CVE-2024/CVE-2024-290xx/CVE-2024-29013.json | 8 +- CVE-2024/CVE-2024-320xx/CVE-2024-32030.json | 8 +- CVE-2024/CVE-2024-32xx/CVE-2024-3229.json | 8 +- CVE-2024/CVE-2024-32xx/CVE-2024-3276.json | 8 +- CVE-2024/CVE-2024-336xx/CVE-2024-33620.json | 8 +- CVE-2024/CVE-2024-336xx/CVE-2024-33622.json | 8 +- CVE-2024/CVE-2024-338xx/CVE-2024-33836.json | 8 +- CVE-2024/CVE-2024-340xx/CVE-2024-34024.json | 8 +- CVE-2024/CVE-2024-344xx/CVE-2024-34443.json | 8 +- CVE-2024/CVE-2024-344xx/CVE-2024-34444.json | 8 +- CVE-2024/CVE-2024-346xx/CVE-2024-34693.json | 8 +- CVE-2024/CVE-2024-348xx/CVE-2024-34833.json | 8 +- CVE-2024/CVE-2024-349xx/CVE-2024-34990.json | 8 +- CVE-2024/CVE-2024-349xx/CVE-2024-34993.json | 8 +- CVE-2024/CVE-2024-349xx/CVE-2024-34994.json | 8 +- CVE-2024/CVE-2024-352xx/CVE-2024-35298.json | 8 +- CVE-2024/CVE-2024-357xx/CVE-2024-35765.json | 8 +- CVE-2024/CVE-2024-357xx/CVE-2024-35780.json | 8 +- CVE-2024/CVE-2024-35xx/CVE-2024-3558.json | 8 +- CVE-2024/CVE-2024-35xx/CVE-2024-3561.json | 8 +- CVE-2024/CVE-2024-35xx/CVE-2024-3562.json | 8 +- CVE-2024/CVE-2024-35xx/CVE-2024-3597.json | 8 +- CVE-2024/CVE-2024-361xx/CVE-2024-36115.json | 8 +- CVE-2024/CVE-2024-361xx/CVE-2024-36116.json | 8 +- CVE-2024/CVE-2024-361xx/CVE-2024-36117.json | 8 +- CVE-2024/CVE-2024-362xx/CVE-2024-36252.json | 8 +- CVE-2024/CVE-2024-364xx/CVE-2024-36480.json | 8 +- CVE-2024/CVE-2024-365xx/CVE-2024-36527.json | 8 +- CVE-2024/CVE-2024-365xx/CVE-2024-36543.json | 8 +- CVE-2024/CVE-2024-365xx/CVE-2024-36573.json | 8 +- CVE-2024/CVE-2024-365xx/CVE-2024-36574.json | 8 +- CVE-2024/CVE-2024-365xx/CVE-2024-36575.json | 8 +- CVE-2024/CVE-2024-365xx/CVE-2024-36577.json | 8 +- CVE-2024/CVE-2024-365xx/CVE-2024-36578.json | 8 +- CVE-2024/CVE-2024-365xx/CVE-2024-36580.json | 8 +- CVE-2024/CVE-2024-365xx/CVE-2024-36581.json | 8 +- CVE-2024/CVE-2024-365xx/CVE-2024-36582.json | 8 +- CVE-2024/CVE-2024-365xx/CVE-2024-36583.json | 8 +- CVE-2024/CVE-2024-366xx/CVE-2024-36677.json | 8 +- CVE-2024/CVE-2024-366xx/CVE-2024-36678.json | 8 +- CVE-2024/CVE-2024-366xx/CVE-2024-36679.json | 8 +- CVE-2024/CVE-2024-366xx/CVE-2024-36680.json | 8 +- CVE-2024/CVE-2024-366xx/CVE-2024-36684.json | 8 +- CVE-2024/CVE-2024-369xx/CVE-2024-36973.json | 8 +- CVE-2024/CVE-2024-369xx/CVE-2024-36974.json | 8 +- CVE-2024/CVE-2024-369xx/CVE-2024-36975.json | 8 +- CVE-2024/CVE-2024-369xx/CVE-2024-36976.json | 8 +- CVE-2024/CVE-2024-369xx/CVE-2024-36977.json | 8 +- CVE-2024/CVE-2024-369xx/CVE-2024-36978.json | 8 +- CVE-2024/CVE-2024-369xx/CVE-2024-36979.json | 8 +- CVE-2024/CVE-2024-36xx/CVE-2024-3602.json | 8 +- CVE-2024/CVE-2024-36xx/CVE-2024-3605.json | 8 +- CVE-2024/CVE-2024-36xx/CVE-2024-3627.json | 8 +- CVE-2024/CVE-2024-370xx/CVE-2024-37079.json | 8 +- CVE-2024/CVE-2024-370xx/CVE-2024-37080.json | 8 +- CVE-2024/CVE-2024-370xx/CVE-2024-37081.json | 8 +- CVE-2024/CVE-2024-371xx/CVE-2024-37124.json | 8 +- CVE-2024/CVE-2024-371xx/CVE-2024-37158.json | 8 +- CVE-2024/CVE-2024-371xx/CVE-2024-37159.json | 8 +- CVE-2024/CVE-2024-373xx/CVE-2024-37305.json | 8 +- CVE-2024/CVE-2024-373xx/CVE-2024-37387.json | 8 +- CVE-2024/CVE-2024-376xx/CVE-2024-37619.json | 8 +- CVE-2024/CVE-2024-376xx/CVE-2024-37620.json | 8 +- CVE-2024/CVE-2024-376xx/CVE-2024-37621.json | 8 +- CVE-2024/CVE-2024-376xx/CVE-2024-37622.json | 8 +- CVE-2024/CVE-2024-376xx/CVE-2024-37623.json | 8 +- CVE-2024/CVE-2024-376xx/CVE-2024-37624.json | 8 +- CVE-2024/CVE-2024-376xx/CVE-2024-37625.json | 8 +- CVE-2024/CVE-2024-376xx/CVE-2024-37661.json | 8 +- CVE-2024/CVE-2024-376xx/CVE-2024-37662.json | 8 +- CVE-2024/CVE-2024-376xx/CVE-2024-37663.json | 8 +- CVE-2024/CVE-2024-376xx/CVE-2024-37664.json | 8 +- CVE-2024/CVE-2024-377xx/CVE-2024-37791.json | 8 +- CVE-2024/CVE-2024-377xx/CVE-2024-37794.json | 8 +- CVE-2024/CVE-2024-377xx/CVE-2024-37795.json | 8 +- CVE-2024/CVE-2024-377xx/CVE-2024-37798.json | 8 +- CVE-2024/CVE-2024-377xx/CVE-2024-37799.json | 8 +- CVE-2024/CVE-2024-378xx/CVE-2024-37800.json | 8 +- CVE-2024/CVE-2024-378xx/CVE-2024-37802.json | 8 +- CVE-2024/CVE-2024-378xx/CVE-2024-37803.json | 8 +- CVE-2024/CVE-2024-378xx/CVE-2024-37821.json | 8 +- CVE-2024/CVE-2024-378xx/CVE-2024-37828.json | 8 +- CVE-2024/CVE-2024-378xx/CVE-2024-37840.json | 8 +- CVE-2024/CVE-2024-378xx/CVE-2024-37848.json | 8 +- CVE-2024/CVE-2024-378xx/CVE-2024-37881.json | 8 +- CVE-2024/CVE-2024-378xx/CVE-2024-37890.json | 8 +- CVE-2024/CVE-2024-378xx/CVE-2024-37891.json | 8 +- CVE-2024/CVE-2024-378xx/CVE-2024-37893.json | 8 +- CVE-2024/CVE-2024-378xx/CVE-2024-37895.json | 8 +- CVE-2024/CVE-2024-378xx/CVE-2024-37896.json | 8 +- CVE-2024/CVE-2024-379xx/CVE-2024-37902.json | 8 +- CVE-2024/CVE-2024-379xx/CVE-2024-37904.json | 8 +- CVE-2024/CVE-2024-382xx/CVE-2024-38273.json | 8 +- CVE-2024/CVE-2024-382xx/CVE-2024-38274.json | 8 +- CVE-2024/CVE-2024-382xx/CVE-2024-38275.json | 8 +- CVE-2024/CVE-2024-382xx/CVE-2024-38276.json | 8 +- CVE-2024/CVE-2024-382xx/CVE-2024-38277.json | 8 +- CVE-2024/CVE-2024-383xx/CVE-2024-38329.json | 8 +- CVE-2024/CVE-2024-383xx/CVE-2024-38347.json | 8 +- CVE-2024/CVE-2024-383xx/CVE-2024-38348.json | 8 +- CVE-2024/CVE-2024-383xx/CVE-2024-38351.json | 8 +- CVE-2024/CVE-2024-383xx/CVE-2024-38355.json | 8 +- CVE-2024/CVE-2024-383xx/CVE-2024-38356.json | 8 +- CVE-2024/CVE-2024-383xx/CVE-2024-38357.json | 8 +- CVE-2024/CVE-2024-383xx/CVE-2024-38358.json | 8 +- CVE-2024/CVE-2024-384xx/CVE-2024-38449.json | 8 +- CVE-2024/CVE-2024-384xx/CVE-2024-38469.json | 8 +- CVE-2024/CVE-2024-384xx/CVE-2024-38470.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38504.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38505.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38506.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38507.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38538.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38539.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38540.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38541.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38542.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38543.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38544.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38545.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38546.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38547.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38548.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38549.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38550.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38551.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38552.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38553.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38554.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38555.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38556.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38557.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38558.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38559.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38560.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38561.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38562.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38563.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38564.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38565.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38566.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38567.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38568.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38569.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38570.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38571.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38572.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38573.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38574.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38575.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38576.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38577.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38578.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38579.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38580.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38581.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38582.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38583.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38584.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38585.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38586.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38587.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38588.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38589.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38590.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38591.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38592.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38593.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38594.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38595.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38596.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38597.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38598.json | 8 +- CVE-2024/CVE-2024-385xx/CVE-2024-38599.json | 8 +- CVE-2024/CVE-2024-386xx/CVE-2024-38600.json | 8 +- CVE-2024/CVE-2024-386xx/CVE-2024-38601.json | 8 +- CVE-2024/CVE-2024-386xx/CVE-2024-38602.json | 8 +- CVE-2024/CVE-2024-386xx/CVE-2024-38603.json | 8 +- CVE-2024/CVE-2024-386xx/CVE-2024-38604.json | 8 +- CVE-2024/CVE-2024-386xx/CVE-2024-38605.json | 8 +- CVE-2024/CVE-2024-386xx/CVE-2024-38606.json | 8 +- CVE-2024/CVE-2024-386xx/CVE-2024-38607.json | 8 +- CVE-2024/CVE-2024-386xx/CVE-2024-38608.json | 8 +- CVE-2024/CVE-2024-386xx/CVE-2024-38609.json | 8 +- CVE-2024/CVE-2024-386xx/CVE-2024-38610.json | 8 +- CVE-2024/CVE-2024-386xx/CVE-2024-38611.json | 8 +- CVE-2024/CVE-2024-386xx/CVE-2024-38612.json | 8 +- CVE-2024/CVE-2024-386xx/CVE-2024-38613.json | 8 +- CVE-2024/CVE-2024-386xx/CVE-2024-38614.json | 8 +- CVE-2024/CVE-2024-386xx/CVE-2024-38615.json | 8 +- CVE-2024/CVE-2024-386xx/CVE-2024-38616.json | 8 +- CVE-2024/CVE-2024-386xx/CVE-2024-38617.json | 8 +- CVE-2024/CVE-2024-386xx/CVE-2024-38618.json | 8 +- CVE-2024/CVE-2024-386xx/CVE-2024-38619.json | 8 +- CVE-2024/CVE-2024-386xx/CVE-2024-38620.json | 8 +- CVE-2024/CVE-2024-38xx/CVE-2024-3894.json | 8 +- CVE-2024/CVE-2024-39xx/CVE-2024-3984.json | 8 +- CVE-2024/CVE-2024-40xx/CVE-2024-4032.json | 8 +- CVE-2024/CVE-2024-40xx/CVE-2024-4094.json | 8 +- CVE-2024/CVE-2024-40xx/CVE-2024-4098.json | 8 +- CVE-2024/CVE-2024-43xx/CVE-2024-4375.json | 8 +- CVE-2024/CVE-2024-43xx/CVE-2024-4390.json | 8 +- CVE-2024/CVE-2024-44xx/CVE-2024-4450.json | 8 +- CVE-2024/CVE-2024-45xx/CVE-2024-4541.json | 8 +- CVE-2024/CVE-2024-45xx/CVE-2024-4565.json | 8 +- CVE-2024/CVE-2024-46xx/CVE-2024-4623.json | 8 +- CVE-2024/CVE-2024-46xx/CVE-2024-4626.json | 8 +- CVE-2024/CVE-2024-46xx/CVE-2024-4632.json | 8 +- CVE-2024/CVE-2024-46xx/CVE-2024-4663.json | 8 +- CVE-2024/CVE-2024-47xx/CVE-2024-4742.json | 8 +- CVE-2024/CVE-2024-47xx/CVE-2024-4787.json | 8 +- CVE-2024/CVE-2024-48xx/CVE-2024-4873.json | 8 +- CVE-2024/CVE-2024-50xx/CVE-2024-5021.json | 8 +- CVE-2024/CVE-2024-50xx/CVE-2024-5036.json | 8 +- CVE-2024/CVE-2024-51xx/CVE-2024-5172.json | 8 +- CVE-2024/CVE-2024-51xx/CVE-2024-5182.json | 8 +- CVE-2024/CVE-2024-52xx/CVE-2024-5208.json | 8 +- CVE-2024/CVE-2024-52xx/CVE-2024-5213.json | 8 +- CVE-2024/CVE-2024-52xx/CVE-2024-5275.json | 8 +- CVE-2024/CVE-2024-53xx/CVE-2024-5343.json | 8 +- CVE-2024/CVE-2024-54xx/CVE-2024-5432.json | 8 +- CVE-2024/CVE-2024-54xx/CVE-2024-5475.json | 8 +- CVE-2024/CVE-2024-55xx/CVE-2024-5522.json | 8 +- CVE-2024/CVE-2024-55xx/CVE-2024-5533.json | 8 +- CVE-2024/CVE-2024-55xx/CVE-2024-5541.json | 8 +- CVE-2024/CVE-2024-55xx/CVE-2024-5574.json | 8 +- CVE-2024/CVE-2024-56xx/CVE-2024-5605.json | 8 +- CVE-2024/CVE-2024-56xx/CVE-2024-5649.json | 8 +- CVE-2024/CVE-2024-56xx/CVE-2024-5676.json | 8 +- CVE-2024/CVE-2024-56xx/CVE-2024-5686.json | 8 +- CVE-2024/CVE-2024-57xx/CVE-2024-5724.json | 8 +- CVE-2024/CVE-2024-57xx/CVE-2024-5768.json | 8 +- CVE-2024/CVE-2024-58xx/CVE-2024-5843.json | 99 ++- CVE-2024/CVE-2024-58xx/CVE-2024-5844.json | 99 ++- CVE-2024/CVE-2024-58xx/CVE-2024-5845.json | 99 ++- CVE-2024/CVE-2024-58xx/CVE-2024-5846.json | 99 ++- CVE-2024/CVE-2024-58xx/CVE-2024-5847.json | 99 ++- CVE-2024/CVE-2024-58xx/CVE-2024-5853.json | 8 +- CVE-2024/CVE-2024-58xx/CVE-2024-5860.json | 8 +- CVE-2024/CVE-2024-58xx/CVE-2024-5899.json | 8 +- CVE-2024/CVE-2024-59xx/CVE-2024-5953.json | 4 +- CVE-2024/CVE-2024-59xx/CVE-2024-5967.json | 8 +- CVE-2024/CVE-2024-59xx/CVE-2024-5970.json | 8 +- CVE-2024/CVE-2024-60xx/CVE-2024-6055.json | 8 +- CVE-2024/CVE-2024-60xx/CVE-2024-6056.json | 8 +- CVE-2024/CVE-2024-60xx/CVE-2024-6057.json | 8 +- CVE-2024/CVE-2024-60xx/CVE-2024-6058.json | 4 +- CVE-2024/CVE-2024-60xx/CVE-2024-6059.json | 8 +- CVE-2024/CVE-2024-60xx/CVE-2024-6061.json | 4 +- CVE-2024/CVE-2024-60xx/CVE-2024-6062.json | 4 +- CVE-2024/CVE-2024-60xx/CVE-2024-6063.json | 4 +- CVE-2024/CVE-2024-60xx/CVE-2024-6064.json | 4 +- CVE-2024/CVE-2024-60xx/CVE-2024-6065.json | 4 +- CVE-2024/CVE-2024-60xx/CVE-2024-6066.json | 4 +- CVE-2024/CVE-2024-60xx/CVE-2024-6067.json | 8 +- CVE-2024/CVE-2024-60xx/CVE-2024-6080.json | 8 +- CVE-2024/CVE-2024-60xx/CVE-2024-6082.json | 8 +- CVE-2024/CVE-2024-60xx/CVE-2024-6083.json | 8 +- CVE-2024/CVE-2024-60xx/CVE-2024-6084.json | 4 +- CVE-2024/CVE-2024-61xx/CVE-2024-6100.json | 8 +- CVE-2024/CVE-2024-61xx/CVE-2024-6101.json | 8 +- CVE-2024/CVE-2024-61xx/CVE-2024-6102.json | 8 +- CVE-2024/CVE-2024-61xx/CVE-2024-6103.json | 8 +- CVE-2024/CVE-2024-61xx/CVE-2024-6108.json | 4 +- CVE-2024/CVE-2024-61xx/CVE-2024-6109.json | 8 +- CVE-2024/CVE-2024-61xx/CVE-2024-6110.json | 8 +- CVE-2024/CVE-2024-61xx/CVE-2024-6111.json | 8 +- CVE-2024/CVE-2024-61xx/CVE-2024-6112.json | 8 +- CVE-2024/CVE-2024-61xx/CVE-2024-6113.json | 8 +- CVE-2024/CVE-2024-61xx/CVE-2024-6114.json | 8 +- CVE-2024/CVE-2024-61xx/CVE-2024-6115.json | 8 +- CVE-2024/CVE-2024-61xx/CVE-2024-6116.json | 8 +- CVE-2024/CVE-2024-61xx/CVE-2024-6125.json | 8 +- CVE-2024/CVE-2024-61xx/CVE-2024-6128.json | 8 +- CVE-2024/CVE-2024-61xx/CVE-2024-6129.json | 8 +- CVE-2024/CVE-2024-61xx/CVE-2024-6132.json | 8 +- CVE-2024/CVE-2024-61xx/CVE-2024-6142.json | 8 +- CVE-2024/CVE-2024-61xx/CVE-2024-6143.json | 8 +- CVE-2024/CVE-2024-61xx/CVE-2024-6144.json | 8 +- CVE-2024/CVE-2024-61xx/CVE-2024-6145.json | 8 +- CVE-2024/CVE-2024-61xx/CVE-2024-6146.json | 8 +- CVE-2024/CVE-2024-61xx/CVE-2024-6176.json | 8 +- CVE-2024/CVE-2024-61xx/CVE-2024-6177.json | 8 +- CVE-2024/CVE-2024-61xx/CVE-2024-6178.json | 8 +- CVE-2024/CVE-2024-61xx/CVE-2024-6179.json | 8 +- CVE-2024/CVE-2024-61xx/CVE-2024-6181.json | 8 +- CVE-2024/CVE-2024-61xx/CVE-2024-6182.json | 8 +- CVE-2024/CVE-2024-61xx/CVE-2024-6183.json | 88 ++ CVE-2024/CVE-2024-61xx/CVE-2024-6184.json | 92 ++ CVE-2024/CVE-2024-61xx/CVE-2024-6185.json | 92 ++ CVE-2024/CVE-2024-61xx/CVE-2024-6186.json | 92 ++ CVE-2024/CVE-2024-61xx/CVE-2024-6187.json | 92 ++ README.md | 84 +- _state.csv | 879 +++++++++++--------- 469 files changed, 5698 insertions(+), 1280 deletions(-) create mode 100644 CVE-2021/CVE-2021-44xx/CVE-2021-4439.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48724.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48725.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48726.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48727.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48728.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48729.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48730.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48731.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48732.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48733.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48734.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48735.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48736.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48737.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48738.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48739.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48740.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48741.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48742.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48743.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48744.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48745.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48746.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48747.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48748.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48749.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48750.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48751.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48752.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48753.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48754.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48755.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48756.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48757.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48758.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48759.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48760.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48761.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48762.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48763.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48764.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48765.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48766.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48767.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48768.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48769.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48770.json create mode 100644 CVE-2022/CVE-2022-487xx/CVE-2022-48771.json create mode 100644 CVE-2023/CVE-2023-491xx/CVE-2023-49110.json create mode 100644 CVE-2023/CVE-2023-491xx/CVE-2023-49111.json create mode 100644 CVE-2023/CVE-2023-491xx/CVE-2023-49112.json create mode 100644 CVE-2023/CVE-2023-491xx/CVE-2023-49113.json create mode 100644 CVE-2023/CVE-2023-528xx/CVE-2023-52883.json create mode 100644 CVE-2024/CVE-2024-61xx/CVE-2024-6183.json create mode 100644 CVE-2024/CVE-2024-61xx/CVE-2024-6184.json create mode 100644 CVE-2024/CVE-2024-61xx/CVE-2024-6185.json create mode 100644 CVE-2024/CVE-2024-61xx/CVE-2024-6186.json create mode 100644 CVE-2024/CVE-2024-61xx/CVE-2024-6187.json diff --git a/CVE-2018/CVE-2018-251xx/CVE-2018-25103.json b/CVE-2018/CVE-2018-251xx/CVE-2018-25103.json index 590b10483ed..11490447071 100644 --- a/CVE-2018/CVE-2018-251xx/CVE-2018-25103.json +++ b/CVE-2018/CVE-2018-251xx/CVE-2018-25103.json @@ -2,8 +2,8 @@ "id": "CVE-2018-25103", "sourceIdentifier": "cret@cert.org", "published": "2024-06-17T18:15:12.650", - "lastModified": "2024-06-18T15:15:51.310", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", diff --git a/CVE-2021/CVE-2021-44xx/CVE-2021-4439.json b/CVE-2021/CVE-2021-44xx/CVE-2021-4439.json new file mode 100644 index 00000000000..0ef909fcb99 --- /dev/null +++ b/CVE-2021/CVE-2021-44xx/CVE-2021-4439.json @@ -0,0 +1,48 @@ +{ + "id": "CVE-2021-4439", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:10.447", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nisdn: cpai: check ctr->cnr to avoid array index out of bound\n\nThe cmtp_add_connection() would add a cmtp session to a controller\nand run a kernel thread to process cmtp.\n\n\t__module_get(THIS_MODULE);\n\tsession->task = kthread_run(cmtp_session, session, \"kcmtpd_ctr_%d\",\n\t\t\t\t\t\t\t\tsession->num);\n\nDuring this process, the kernel thread would call detach_capi_ctr()\nto detach a register controller. if the controller\nwas not attached yet, detach_capi_ctr() would\ntrigger an array-index-out-bounds bug.\n\n[ 46.866069][ T6479] UBSAN: array-index-out-of-bounds in\ndrivers/isdn/capi/kcapi.c:483:21\n[ 46.867196][ T6479] index -1 is out of range for type 'capi_ctr *[32]'\n[ 46.867982][ T6479] CPU: 1 PID: 6479 Comm: kcmtpd_ctr_0 Not tainted\n5.15.0-rc2+ #8\n[ 46.869002][ T6479] Hardware name: QEMU Standard PC (i440FX + PIIX,\n1996), BIOS 1.14.0-2 04/01/2014\n[ 46.870107][ T6479] Call Trace:\n[ 46.870473][ T6479] dump_stack_lvl+0x57/0x7d\n[ 46.870974][ T6479] ubsan_epilogue+0x5/0x40\n[ 46.871458][ T6479] __ubsan_handle_out_of_bounds.cold+0x43/0x48\n[ 46.872135][ T6479] detach_capi_ctr+0x64/0xc0\n[ 46.872639][ T6479] cmtp_session+0x5c8/0x5d0\n[ 46.873131][ T6479] ? __init_waitqueue_head+0x60/0x60\n[ 46.873712][ T6479] ? cmtp_add_msgpart+0x120/0x120\n[ 46.874256][ T6479] kthread+0x147/0x170\n[ 46.874709][ T6479] ? set_kthread_struct+0x40/0x40\n[ 46.875248][ T6479] ret_from_fork+0x1f/0x30\n[ 46.875773][ T6479]" + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/1f3e2e97c003f80c4b087092b225c8787ff91e4d", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/24219a977bfe3d658687e45615c70998acdbac5a", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/285e9210b1fab96a11c0be3ed5cea9dd48b6ac54", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/7d91adc0ccb060ce564103315189466eb822cc6a", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/7f221ccbee4ec662e2292d490a43ce6c314c4594", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/9b6b2db77bc3121fe435f1d4b56e34de443bec75", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/cc20226e218a2375d50dd9ac14fb4121b43375ff", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/e8b8de17e164c9f1b7777f1c6f99d05539000036", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2021/CVE-2021-475xx/CVE-2021-47576.json b/CVE-2021/CVE-2021-475xx/CVE-2021-47576.json index f884fa6ee37..516759a4ba2 100644 --- a/CVE-2021/CVE-2021-475xx/CVE-2021-47576.json +++ b/CVE-2021/CVE-2021-475xx/CVE-2021-47576.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47576", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:52.117", - "lastModified": "2024-06-19T15:15:52.117", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: scsi_debug: Sanity check block descriptor length in resp_mode_select()\n\nIn resp_mode_select() sanity check the block descriptor len to avoid UAF.\n\nBUG: KASAN: use-after-free in resp_mode_select+0xa4c/0xb40 drivers/scsi/scsi_debug.c:2509\nRead of size 1 at addr ffff888026670f50 by task scsicmd/15032\n\nCPU: 1 PID: 15032 Comm: scsicmd Not tainted 5.15.0-01d0625 #15\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS\nCall Trace:\n \n dump_stack_lvl+0x89/0xb5 lib/dump_stack.c:107\n print_address_description.constprop.9+0x28/0x160 mm/kasan/report.c:257\n kasan_report.cold.14+0x7d/0x117 mm/kasan/report.c:443\n __asan_report_load1_noabort+0x14/0x20 mm/kasan/report_generic.c:306\n resp_mode_select+0xa4c/0xb40 drivers/scsi/scsi_debug.c:2509\n schedule_resp+0x4af/0x1a10 drivers/scsi/scsi_debug.c:5483\n scsi_debug_queuecommand+0x8c9/0x1e70 drivers/scsi/scsi_debug.c:7537\n scsi_queue_rq+0x16b4/0x2d10 drivers/scsi/scsi_lib.c:1521\n blk_mq_dispatch_rq_list+0xb9b/0x2700 block/blk-mq.c:1640\n __blk_mq_sched_dispatch_requests+0x28f/0x590 block/blk-mq-sched.c:325\n blk_mq_sched_dispatch_requests+0x105/0x190 block/blk-mq-sched.c:358\n __blk_mq_run_hw_queue+0xe5/0x150 block/blk-mq.c:1762\n __blk_mq_delay_run_hw_queue+0x4f8/0x5c0 block/blk-mq.c:1839\n blk_mq_run_hw_queue+0x18d/0x350 block/blk-mq.c:1891\n blk_mq_sched_insert_request+0x3db/0x4e0 block/blk-mq-sched.c:474\n blk_execute_rq_nowait+0x16b/0x1c0 block/blk-exec.c:63\n sg_common_write.isra.18+0xeb3/0x2000 drivers/scsi/sg.c:837\n sg_new_write.isra.19+0x570/0x8c0 drivers/scsi/sg.c:775\n sg_ioctl_common+0x14d6/0x2710 drivers/scsi/sg.c:941\n sg_ioctl+0xa2/0x180 drivers/scsi/sg.c:1166\n __x64_sys_ioctl+0x19d/0x220 fs/ioctl.c:52\n do_syscall_64+0x3a/0x80 arch/x86/entry/common.c:50\n entry_SYSCALL_64_after_hwframe+0x44/0xae arch/x86/entry/entry_64.S:113" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: scsi: scsi_debug: Verifique la longitud del descriptor del bloque en resp_mode_select() En resp_mode_select(), verifique la longitud del descriptor del bloque para evitar UAF. ERROR: KASAN: use-after-free en resp_mode_select+0xa4c/0xb40 drivers/scsi/scsi_debug.c:2509 Lectura del tama\u00f1o 1 en la direcci\u00f3n ffff888026670f50 por tarea scsicmd/15032 CPU: 1 PID: 15032 Comm: scsicmd Not tainted 5.15.0 -01d0625 #15 Nombre del hardware: PC est\u00e1ndar QEMU (i440FX + PIIX, 1996), seguimiento de llamadas del BIOS: dump_stack_lvl+0x89/0xb5 lib/dump_stack.c:107 print_address_description.constprop.9+0x28/0x160 mm/kasan/ report.c:257 kasan_report.cold.14+0x7d/0x117 mm/kasan/report.c:443 __asan_report_load1_noabort+0x14/0x20 mm/kasan/report_generic.c:306 resp_mode_select+0xa4c/0xb40 drivers/scsi/scsi_debug.c: 2509 Schedule_resp+0x4af/0x1a10 controladores/scsi/scsi_debug.c:5483 scsi_debug_queuecommand+0x8c9/0x1e70 controladores/scsi/scsi_debug.c:7537 scsi_queue_rq+0x16b4/0x2d10 controladores/scsi/scsi_lib.c:1521 blk_mq_dispatch_rq_list+0xb9b/0x2700 bloque/ blk-mq.c:1640 __blk_mq_sched_dispatch_requests+0x28f/0x590 block/blk-mq-sched.c:325 blk_mq_sched_dispatch_requests+0x105/0x190 block/blk-mq-sched.c:358 __blk_mq_run_hw_queue+0xe5/ 0x150 cuadra/blk-mq. c:1762 __blk_mq_delay_run_hw_queue+0x4f8/0x5c0 block/blk-mq.c:1839 blk_mq_run_hw_queue+0x18d/0x350 block/blk-mq.c:1891 blk_mq_sched_insert_request+0x3db/0x4e0 ched.c:474 blk_execute_rq_nowait+0x16b /0x1c0 block/blk-exec.c:63 sg_common_write.isra.18+0xeb3/0x2000 controladores/scsi/sg.c:837 sg_new_write.isra.19+0x570/0x8c0 controladores/scsi/sg.c:775 sg_ioctl_common+0x14d6 /0x2710 controladores/scsi/sg.c:941 sg_ioctl+0xa2/0x180 controladores/scsi/sg.c:1166 __x64_sys_ioctl+0x19d/0x220 fs/ioctl.c:52 do_syscall_64+0x3a/0x80 arch/x86/entry/common. c:50 entrada_SYSCALL_64_after_hwframe+0x44/0xae arch/x86/entry/entry_64.S:113" } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-475xx/CVE-2021-47577.json b/CVE-2021/CVE-2021-475xx/CVE-2021-47577.json index e8ec38e7339..9f223c76ca1 100644 --- a/CVE-2021/CVE-2021-475xx/CVE-2021-47577.json +++ b/CVE-2021/CVE-2021-475xx/CVE-2021-47577.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47577", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:52.223", - "lastModified": "2024-06-19T15:15:52.223", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nio-wq: check for wq exit after adding new worker task_work\n\nWe check IO_WQ_BIT_EXIT before attempting to create a new worker, and\nwq exit cancels pending work if we have any. But it's possible to have\na race between the two, where creation checks exit finding it not set,\nbut we're in the process of exiting. The exit side will cancel pending\ncreation task_work, but there's a gap where we add task_work after we've\ncanceled existing creations at exit time.\n\nFix this by checking the EXIT bit post adding the creation task_work.\nIf it's set, run the same cancelation that exit does." + }, + { + "lang": "es", + "value": "En el kernel de Linux se ha resuelto la siguiente vulnerabilidad: io-wq: comprueba la salida de wq despu\u00e9s de agregar un nuevo trabajador task_work Comprobamos IO_WQ_BIT_EXIT antes de intentar crear un nuevo trabajador, y wq exit cancela el trabajo pendiente si tenemos alguno. Pero es posible tener una carrera entre los dos, donde las comprobaciones de creaci\u00f3n salen y descubren que no est\u00e1 configurado, pero estamos en el proceso de salir. El lado de salida cancelar\u00e1 la creaci\u00f3n pendiente task_work, pero hay un espacio en el que agregamos task_work despu\u00e9s de haber cancelado las creaciones existentes en el momento de la salida. Solucione este problema marcando la publicaci\u00f3n del bit EXIT agregando la tarea de creaci\u00f3n_trabajo. Si est\u00e1 configurado, ejecute la misma cancelaci\u00f3n que realiza la salida." } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-475xx/CVE-2021-47578.json b/CVE-2021/CVE-2021-475xx/CVE-2021-47578.json index 859a3751ea0..d0674ee2dc1 100644 --- a/CVE-2021/CVE-2021-475xx/CVE-2021-47578.json +++ b/CVE-2021/CVE-2021-475xx/CVE-2021-47578.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47578", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:52.320", - "lastModified": "2024-06-19T15:15:52.320", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: scsi_debug: Don't call kcalloc() if size arg is zero\n\nIf the size arg to kcalloc() is zero, it returns ZERO_SIZE_PTR. Because of\nthat, for a following NULL pointer check to work on the returned pointer,\nkcalloc() must not be called with the size arg equal to zero. Return early\nwithout error before the kcalloc() call if size arg is zero.\n\nBUG: KASAN: null-ptr-deref in memcpy include/linux/fortify-string.h:191 [inline]\nBUG: KASAN: null-ptr-deref in sg_copy_buffer+0x138/0x240 lib/scatterlist.c:974\nWrite of size 4 at addr 0000000000000010 by task syz-executor.1/22789\n\nCPU: 1 PID: 22789 Comm: syz-executor.1 Not tainted 5.15.0-syzk #1\nHardware name: Red Hat KVM, BIOS 1.13.0-2\nCall Trace:\n __dump_stack lib/dump_stack.c:88 [inline]\n dump_stack_lvl+0x89/0xb5 lib/dump_stack.c:106\n __kasan_report mm/kasan/report.c:446 [inline]\n kasan_report.cold.14+0x112/0x117 mm/kasan/report.c:459\n check_region_inline mm/kasan/generic.c:183 [inline]\n kasan_check_range+0x1a3/0x210 mm/kasan/generic.c:189\n memcpy+0x3b/0x60 mm/kasan/shadow.c:66\n memcpy include/linux/fortify-string.h:191 [inline]\n sg_copy_buffer+0x138/0x240 lib/scatterlist.c:974\n do_dout_fetch drivers/scsi/scsi_debug.c:2954 [inline]\n do_dout_fetch drivers/scsi/scsi_debug.c:2946 [inline]\n resp_verify+0x49e/0x930 drivers/scsi/scsi_debug.c:4276\n schedule_resp+0x4d8/0x1a70 drivers/scsi/scsi_debug.c:5478\n scsi_debug_queuecommand+0x8c9/0x1ec0 drivers/scsi/scsi_debug.c:7533\n scsi_dispatch_cmd drivers/scsi/scsi_lib.c:1520 [inline]\n scsi_queue_rq+0x16b0/0x2d40 drivers/scsi/scsi_lib.c:1699\n blk_mq_dispatch_rq_list+0xb9b/0x2700 block/blk-mq.c:1639\n __blk_mq_sched_dispatch_requests+0x28f/0x590 block/blk-mq-sched.c:325\n blk_mq_sched_dispatch_requests+0x105/0x190 block/blk-mq-sched.c:358\n __blk_mq_run_hw_queue+0xe5/0x150 block/blk-mq.c:1761\n __blk_mq_delay_run_hw_queue+0x4f8/0x5c0 block/blk-mq.c:1838\n blk_mq_run_hw_queue+0x18d/0x350 block/blk-mq.c:1891\n blk_mq_sched_insert_request+0x3db/0x4e0 block/blk-mq-sched.c:474\n blk_execute_rq_nowait+0x16b/0x1c0 block/blk-exec.c:62\n blk_execute_rq+0xdb/0x360 block/blk-exec.c:102\n sg_scsi_ioctl drivers/scsi/scsi_ioctl.c:621 [inline]\n scsi_ioctl+0x8bb/0x15c0 drivers/scsi/scsi_ioctl.c:930\n sg_ioctl_common+0x172d/0x2710 drivers/scsi/sg.c:1112\n sg_ioctl+0xa2/0x180 drivers/scsi/sg.c:1165\n vfs_ioctl fs/ioctl.c:51 [inline]\n __do_sys_ioctl fs/ioctl.c:874 [inline]\n __se_sys_ioctl fs/ioctl.c:860 [inline]\n __x64_sys_ioctl+0x19d/0x220 fs/ioctl.c:860\n do_syscall_x64 arch/x86/entry/common.c:50 [inline]\n do_syscall_64+0x3a/0x80 arch/x86/entry/common.c:80\n entry_SYSCALL_64_after_hwframe+0x44/0xae" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: scsi: scsi_debug: no llamar a kcalloc() si el tama\u00f1o arg es cero. Si el tama\u00f1o arg de kcalloc() es cero, devuelve ZERO_SIZE_PTR. Por eso, para que una siguiente verificaci\u00f3n de puntero NULL funcione en el puntero devuelto, no se debe llamar a kcalloc() con el tama\u00f1o arg igual a cero. Regrese temprano sin errores antes de la llamada a kcalloc() si el tama\u00f1o arg es cero. ERROR: KASAN: null-ptr-deref en memcpy include/linux/fortify-string.h:191 [en l\u00ednea] ERROR: KASAN: null-ptr-deref en sg_copy_buffer+0x138/0x240 lib/scatterlist.c:974 Escritura de tama\u00f1o 4 en la direcci\u00f3n 0000000000000010 por tarea syz-executor.1/22789 CPU: 1 PID: 22789 Comm: syz-executor.1 No contaminado 5.15.0-syzk #1 Nombre del hardware: Red Hat KVM, BIOS 1.13.0-2 Seguimiento de llamadas : __dump_stack lib/dump_stack.c:88 [en l\u00ednea] dump_stack_lvl+0x89/0xb5 lib/dump_stack.c:106 __kasan_report mm/kasan/report.c:446 [en l\u00ednea] kasan_report.cold.14+0x112/0x117 mm/kasan/ report.c:459 check_region_inline mm/kasan/generic.c:183 [en l\u00ednea] kasan_check_range+0x1a3/0x210 mm/kasan/generic.c:189 memcpy+0x3b/0x60 mm/kasan/shadow.c:66 memcpy include/linux /fortify-string.h:191 [en l\u00ednea] sg_copy_buffer+0x138/0x240 lib/scatterlist.c:974 controladores do_dout_fetch/scsi/scsi_debug.c:2954 [en l\u00ednea] controladores do_dout_fetch/scsi/scsi_debug.c:2946 [en l\u00ednea] resp_verify +0x49e/0x930 controladores/scsi/scsi_debug.c:4276 Schedule_resp+0x4d8/0x1a70 controladores/scsi/scsi_debug.c:5478 scsi_debug_queuecommand+0x8c9/0x1ec0 controladores/scsi/scsi_debug.c:7533 controladores scsi_dispatch_cmd/scsi /scsi_lib.c: 1520 [en l\u00ednea] scsi_queue_rq+0x16b0/0x2d40 drivers/scsi/scsi_lib.c:1699 blk_mq_dispatch_rq_list+0xb9b/0x2700 block/blk-mq.c:1639 __blk_mq_sched_dispatch_requests+0x28f/0x590 lk-mq-sched.c:325 blk_mq_sched_dispatch_requests+ 0x105/0x190 block/blk-mq-sched.c:358 __blk_mq_run_hw_queue+0xe5/0x150 block/blk-mq.c:1761 __blk_mq_delay_run_hw_queue+0x4f8/0x5c0 block/blk-mq.c:1838 cola+0x18d/0x350 bloque/negro -mq.c:1891 blk_mq_sched_insert_request+0x3db/0x4e0 block/blk-mq-sched.c:474 blk_execute_rq_nowait+0x16b/0x1c0 block/blk-exec.c:62 blk_execute_rq+0xdb/0x360 block/blk-exec.c:102 sg_scsi_ioctl controladores/scsi/scsi_ioctl.c:621 [en l\u00ednea] scsi_ioctl+0x8bb/0x15c0 controladores/scsi/scsi_ioctl.c:930 sg_ioctl_common+0x172d/0x2710 controladores/scsi/sg.c:1112 sg_ioctl+0xa2/0 controladores x180/scsi/ SG.C: 1165 VFS_IOCTL FS/IOCTL.C: 51 [INLINE] __DO_SYS_IOCTL FS/IOCTL.C: 874 [INLINE] __SE_SYS_IOCTL FS/IOCTL.C: 860 [Inline] __X64_SY 60 do_syscall_x64 arch/x86/entry/common.c:50 [en l\u00ednea] do_syscall_64+0x3a/0x80 arch/x86/entry/common.c:80 Entry_SYSCALL_64_after_hwframe+0x44/0xae" } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-475xx/CVE-2021-47579.json b/CVE-2021/CVE-2021-475xx/CVE-2021-47579.json index 9579f516b22..2ff2d5b7fcf 100644 --- a/CVE-2021/CVE-2021-475xx/CVE-2021-47579.json +++ b/CVE-2021/CVE-2021-475xx/CVE-2021-47579.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47579", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:52.427", - "lastModified": "2024-06-19T15:15:52.427", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\novl: fix warning in ovl_create_real()\n\nSyzbot triggered the following warning in ovl_workdir_create() ->\novl_create_real():\n\n\tif (!err && WARN_ON(!newdentry->d_inode)) {\n\nThe reason is that the cgroup2 filesystem returns from mkdir without\ninstantiating the new dentry.\n\nWeird filesystems such as this will be rejected by overlayfs at a later\nstage during setup, but to prevent such a warning, call ovl_mkdir_real()\ndirectly from ovl_workdir_create() and reject this case early." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: ovl: corregir advertencia en ovl_create_real() Syzbot activ\u00f3 la siguiente advertencia en ovl_workdir_create() -> ovl_create_real(): if (!err && WARN_ON(!newdentry->d_inode)) { La raz\u00f3n es que el sistema de archivos cgroup2 regresa desde mkdir sin crear una instancia del nuevo dentry. Los sistemas de archivos extra\u00f1os como este ser\u00e1n rechazados por overlayfs en una etapa posterior durante la instalaci\u00f3n, pero para evitar dicha advertencia, llame a ovl_mkdir_real() directamente desde ovl_workdir_create() y rechace este caso anticipadamente." } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-475xx/CVE-2021-47580.json b/CVE-2021/CVE-2021-475xx/CVE-2021-47580.json index 862ae4522d6..b16f25331b5 100644 --- a/CVE-2021/CVE-2021-475xx/CVE-2021-47580.json +++ b/CVE-2021/CVE-2021-475xx/CVE-2021-47580.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47580", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:52.537", - "lastModified": "2024-06-19T15:15:52.537", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: scsi_debug: Fix type in min_t to avoid stack OOB\n\nChange min_t() to use type \"u32\" instead of type \"int\" to avoid stack out\nof bounds. With min_t() type \"int\" the values get sign extended and the\nlarger value gets used causing stack out of bounds.\n\nBUG: KASAN: stack-out-of-bounds in memcpy include/linux/fortify-string.h:191 [inline]\nBUG: KASAN: stack-out-of-bounds in sg_copy_buffer+0x1de/0x240 lib/scatterlist.c:976\nRead of size 127 at addr ffff888072607128 by task syz-executor.7/18707\n\nCPU: 1 PID: 18707 Comm: syz-executor.7 Not tainted 5.15.0-syzk #1\nHardware name: Red Hat KVM, BIOS 1.13.0-2\nCall Trace:\n __dump_stack lib/dump_stack.c:88 [inline]\n dump_stack_lvl+0x89/0xb5 lib/dump_stack.c:106\n print_address_description.constprop.9+0x28/0x160 mm/kasan/report.c:256\n __kasan_report mm/kasan/report.c:442 [inline]\n kasan_report.cold.14+0x7d/0x117 mm/kasan/report.c:459\n check_region_inline mm/kasan/generic.c:183 [inline]\n kasan_check_range+0x1a3/0x210 mm/kasan/generic.c:189\n memcpy+0x23/0x60 mm/kasan/shadow.c:65\n memcpy include/linux/fortify-string.h:191 [inline]\n sg_copy_buffer+0x1de/0x240 lib/scatterlist.c:976\n sg_copy_from_buffer+0x33/0x40 lib/scatterlist.c:1000\n fill_from_dev_buffer.part.34+0x82/0x130 drivers/scsi/scsi_debug.c:1162\n fill_from_dev_buffer drivers/scsi/scsi_debug.c:1888 [inline]\n resp_readcap16+0x365/0x3b0 drivers/scsi/scsi_debug.c:1887\n schedule_resp+0x4d8/0x1a70 drivers/scsi/scsi_debug.c:5478\n scsi_debug_queuecommand+0x8c9/0x1ec0 drivers/scsi/scsi_debug.c:7533\n scsi_dispatch_cmd drivers/scsi/scsi_lib.c:1520 [inline]\n scsi_queue_rq+0x16b0/0x2d40 drivers/scsi/scsi_lib.c:1699\n blk_mq_dispatch_rq_list+0xb9b/0x2700 block/blk-mq.c:1639\n __blk_mq_sched_dispatch_requests+0x28f/0x590 block/blk-mq-sched.c:325\n blk_mq_sched_dispatch_requests+0x105/0x190 block/blk-mq-sched.c:358\n __blk_mq_run_hw_queue+0xe5/0x150 block/blk-mq.c:1761\n __blk_mq_delay_run_hw_queue+0x4f8/0x5c0 block/blk-mq.c:1838\n blk_mq_run_hw_queue+0x18d/0x350 block/blk-mq.c:1891\n blk_mq_sched_insert_request+0x3db/0x4e0 block/blk-mq-sched.c:474\n blk_execute_rq_nowait+0x16b/0x1c0 block/blk-exec.c:62\n sg_common_write.isra.18+0xeb3/0x2000 drivers/scsi/sg.c:836\n sg_new_write.isra.19+0x570/0x8c0 drivers/scsi/sg.c:774\n sg_ioctl_common+0x14d6/0x2710 drivers/scsi/sg.c:939\n sg_ioctl+0xa2/0x180 drivers/scsi/sg.c:1165\n vfs_ioctl fs/ioctl.c:51 [inline]\n __do_sys_ioctl fs/ioctl.c:874 [inline]\n __se_sys_ioctl fs/ioctl.c:860 [inline]\n __x64_sys_ioctl+0x19d/0x220 fs/ioctl.c:860\n do_syscall_x64 arch/x86/entry/common.c:50 [inline]\n do_syscall_64+0x3a/0x80 arch/x86/entry/common.c:80\n entry_SYSCALL_64_after_hwframe+0x44/0xae" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: scsi: scsi_debug: corrige el tipo min_t para evitar la pila OOB. Cambie min_t() para usar el tipo \"u32\" en lugar de \"int\" para evitar la pila fuera de los l\u00edmites. Con min_t() escriba \"int\", los valores se extienden y el valor mayor se usa provocando que la pila est\u00e9 fuera de los l\u00edmites. ERROR: KASAN: pila fuera de los l\u00edmites en memcpy include/linux/fortify-string.h:191 [en l\u00ednea] ERROR: KASAN: pila fuera de los l\u00edmites en sg_copy_buffer+0x1de/0x240 lib/scatterlist.c: 976 Lectura del tama\u00f1o 127 en la direcci\u00f3n ffff888072607128 mediante la tarea syz-executor.7/18707 CPU: 1 PID: 18707 Comm: syz-executor.7 No contaminado 5.15.0-syzk #1 Nombre del hardware: Red Hat KVM, BIOS 1.13.0 -2 Seguimiento de llamadas: __dump_stack lib/dump_stack.c:88 [en l\u00ednea] dump_stack_lvl+0x89/0xb5 lib/dump_stack.c:106 print_address_description.constprop.9+0x28/0x160 mm/kasan/report.c:256 __kasan_report mm/kasan /report.c:442 [en l\u00ednea] kasan_report.cold.14+0x7d/0x117 mm/kasan/report.c:459 check_region_inline mm/kasan/generic.c:183 [en l\u00ednea] kasan_check_range+0x1a3/0x210 mm/kasan/generic .c:189 memcpy+0x23/0x60 mm/kasan/shadow.c:65 memcpy include/linux/fortify-string.h:191 [en l\u00ednea] sg_copy_buffer+0x1de/0x240 lib/scatterlist.c:976 sg_copy_from_buffer+0x33/0x40 lib/scatterlist.c:1000 fill_from_dev_buffer.part.34+0x82/0x130 controladores/scsi/scsi_debug.c:1162 fill_from_dev_buffer controladores/scsi/scsi_debug.c:1888 [en l\u00ednea] resp_readcap16+0x365/0x3b0 controladores/scsi/scsi_debug.c :1887 Schedule_resp+0x4d8/0x1a70 controladores/scsi/scsi_debug.c:5478 scsi_debug_queuecommand+0x8c9/0x1ec0 controladores/scsi/scsi_debug.c:7533 controladores scsi_dispatch_cmd/scsi/scsi_lib.c:1520 [en l\u00ednea] Controladores 0x16b0/0x2d40/ scsi/scsi_lib.c:1699 blk_mq_dispatch_rq_list+0xb9b/0x2700 block/blk-mq.c:1639 __blk_mq_sched_dispatch_requests+0x28f/0x590 block/blk-mq-sched.c:325 blk_mq_sched_dispatch_requests+0x10 5/0x190 cuadra/blk-mq-programado. c:358 __blk_mq_run_hw_queue+0xe5/0x150 block/blk-mq.c:1761 __blk_mq_delay_run_hw_queue+0x4f8/0x5c0 block/blk-mq.c:1838 blk_mq_run_hw_queue+0x18d/0x350 :1891 blk_mq_sched_insert_request+0x3db/0x4e0 block/blk-mq-sched.c:474 blk_execute_rq_nowait+0x16b/0x1c0 block/blk-exec.c:62 sg_common_write.isra.18+0xeb3/0x2000 drivers/scsi/sg.c:836 sg_new_write.isra.19+0x570 /0x8c0 controladores/scsi/sg.c:774 sg_ioctl_common+0x14d6/0x2710 controladores/scsi/sg.c:939 sg_ioctl+0xa2/0x180 controladores/scsi/sg.c:1165 vfs_ioctl fs/ioctl.c:51 [en l\u00ednea] __do_sys_ioctl fs/ioctl.c:874 [en l\u00ednea] __se_sys_ioctl fs/ioctl.c:860 [en l\u00ednea] __x64_sys_ioctl+0x19d/0x220 fs/ioctl.c:860 do_syscall_x64 arch/x86/entry/common.c:50 [en l\u00ednea] llamada al sistema_64 +0x3a/0x80 arch/x86/entry/common.c:80 Entry_SYSCALL_64_after_hwframe+0x44/0xae" } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-475xx/CVE-2021-47582.json b/CVE-2021/CVE-2021-475xx/CVE-2021-47582.json index 4a846fd4756..261a0b8219c 100644 --- a/CVE-2021/CVE-2021-475xx/CVE-2021-47582.json +++ b/CVE-2021/CVE-2021-475xx/CVE-2021-47582.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47582", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:52.743", - "lastModified": "2024-06-19T15:15:52.743", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nUSB: core: Make do_proc_control() and do_proc_bulk() killable\n\nThe USBDEVFS_CONTROL and USBDEVFS_BULK ioctls invoke\nusb_start_wait_urb(), which contains an uninterruptible wait with a\nuser-specified timeout value. If timeout value is very large and the\ndevice being accessed does not respond in a reasonable amount of time,\nthe kernel will complain about \"Task X blocked for more than N\nseconds\", as found in testing by syzbot:\n\nINFO: task syz-executor.0:8700 blocked for more than 143 seconds.\n Not tainted 5.14.0-rc7-syzkaller #0\n\"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\" disables this message.\ntask:syz-executor.0 state:D stack:23192 pid: 8700 ppid: 8455 flags:0x00004004\nCall Trace:\n context_switch kernel/sched/core.c:4681 [inline]\n __schedule+0xc07/0x11f0 kernel/sched/core.c:5938\n schedule+0x14b/0x210 kernel/sched/core.c:6017\n schedule_timeout+0x98/0x2f0 kernel/time/timer.c:1857\n do_wait_for_common+0x2da/0x480 kernel/sched/completion.c:85\n __wait_for_common kernel/sched/completion.c:106 [inline]\n wait_for_common kernel/sched/completion.c:117 [inline]\n wait_for_completion_timeout+0x46/0x60 kernel/sched/completion.c:157\n usb_start_wait_urb+0x167/0x550 drivers/usb/core/message.c:63\n do_proc_bulk+0x978/0x1080 drivers/usb/core/devio.c:1236\n proc_bulk drivers/usb/core/devio.c:1273 [inline]\n usbdev_do_ioctl drivers/usb/core/devio.c:2547 [inline]\n usbdev_ioctl+0x3441/0x6b10 drivers/usb/core/devio.c:2713\n...\n\nTo fix this problem, this patch replaces usbfs's calls to\nusb_control_msg() and usb_bulk_msg() with special-purpose code that\ndoes essentially the same thing (as recommended in the comment for\nusb_start_wait_urb()), except that it always uses a killable wait and\nit uses GFP_KERNEL rather than GFP_NOIO." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: USB: core: Hacer que do_proc_control() y do_proc_bulk() se puedan eliminar. Los ioctls USBDEVFS_CONTROL y USBDEVFS_BULK invocan usb_start_wait_urb(), que contiene una espera ininterrumpida con un valor de tiempo de espera especificado por el usuario. Si el valor del tiempo de espera es muy grande y el dispositivo al que se accede no responde en un per\u00edodo de tiempo razonable, el kernel se quejar\u00e1 de \"Tarea X bloqueada durante m\u00e1s de N segundos\", como se encontr\u00f3 en las pruebas realizadas por syzbot: INFORMACI\u00d3N: tarea syz-executor .0:8700 bloqueado durante m\u00e1s de 143 segundos. Not tainted 5.14.0-rc7-syzkaller #0 \"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\" desactiva este mensaje. tarea:syz-executor.0 estado:D pila:23192 pid: 8700 ppid: 8455 banderas:0x00004004 Seguimiento de llamadas: context_switch kernel/sched/core.c:4681 [en l\u00ednea] __schedule+0xc07/0x11f0 kernel/sched/core.c :5938 programaci\u00f3n+0x14b/0x210 kernel/sched/core.c:6017 Schedule_timeout+0x98/0x2f0 kernel/time/timer.c:1857 do_wait_for_common+0x2da/0x480 kernel/sched/completion.c:85 __wait_for_common kernel/sched/completion .c:106 [en l\u00ednea] wait_for_common kernel/sched/completion.c:117 [en l\u00ednea] wait_for_completion_timeout+0x46/0x60 kernel/sched/completion.c:157 usb_start_wait_urb+0x167/0x550 drivers/usb/core/message.c:63 do_proc_bulk+0x978/0x1080 controladores/usb/core/devio.c:1236 controladores proc_bulk/usb/core/devio.c:1273 [en l\u00ednea] usbdev_do_ioctl controladores/usb/core/devio.c:2547 [en l\u00ednea] usbdev_ioctl+0x3441/ 0x6b10 drivers/usb/core/devio.c:2713 ... Para solucionar este problema, este parche reemplaza las llamadas de usbfs a usb_control_msg() y usb_bulk_msg() con c\u00f3digo de prop\u00f3sito especial que hace esencialmente lo mismo (como se recomienda en el comentario para usb_start_wait_urb()), excepto que siempre usa una espera eliminable y usa GFP_KERNEL en lugar de GFP_NOIO." } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-475xx/CVE-2021-47583.json b/CVE-2021/CVE-2021-475xx/CVE-2021-47583.json index db059016e67..5405b9550be 100644 --- a/CVE-2021/CVE-2021-475xx/CVE-2021-47583.json +++ b/CVE-2021/CVE-2021-475xx/CVE-2021-47583.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47583", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:52.843", - "lastModified": "2024-06-19T15:15:52.843", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: mxl111sf: change mutex_init() location\n\nSyzbot reported, that mxl111sf_ctrl_msg() uses uninitialized\nmutex. The problem was in wrong mutex_init() location.\n\nPrevious mutex_init(&state->msg_lock) call was in ->init() function, but\ndvb_usbv2_init() has this order of calls:\n\n\tdvb_usbv2_init()\n\t dvb_usbv2_adapter_init()\n\t dvb_usbv2_adapter_frontend_init()\n\t props->frontend_attach()\n\n\t props->init()\n\nSince mxl111sf_* devices call mxl111sf_ctrl_msg() in ->frontend_attach()\ninternally we need to initialize state->msg_lock before\nfrontend_attach(). To achieve it, ->probe() call added to all mxl111sf_*\ndevices, which will simply initiaize mutex." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: medio: mxl111sf: cambiar la ubicaci\u00f3n de mutex_init() Syzbot inform\u00f3 que mxl111sf_ctrl_msg() usa un mutex no inicializado. El problema estaba en la ubicaci\u00f3n mutex_init() incorrecta. La llamada anterior a mutex_init(&state->msg_lock) estaba en la funci\u00f3n ->init(), pero dvb_usbv2_init() tiene este orden de llamadas: dvb_usbv2_init() dvb_usbv2_adapter_init() dvb_usbv2_adapter_frontend_init() props->frontend_attach() props->init() Desde Los dispositivos mxl111sf_* llaman a mxl111sf_ctrl_msg() en ->frontend_attach() internamente, necesitamos inicializar state->msg_lock antes de frontend_attach(). Para lograrlo, se agrega la llamada ->probe() a todos los dispositivos mxl111sf_*, lo que simplemente iniciar\u00e1 el mutex." } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-475xx/CVE-2021-47584.json b/CVE-2021/CVE-2021-475xx/CVE-2021-47584.json index a193b1262e8..79c8132670d 100644 --- a/CVE-2021/CVE-2021-475xx/CVE-2021-47584.json +++ b/CVE-2021/CVE-2021-475xx/CVE-2021-47584.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47584", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:52.947", - "lastModified": "2024-06-19T15:15:52.947", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\niocost: Fix divide-by-zero on donation from low hweight cgroup\n\nThe donation calculation logic assumes that the donor has non-zero\nafter-donation hweight, so the lowest active hweight a donating cgroup can\nhave is 2 so that it can donate 1 while keeping the other 1 for itself.\nEarlier, we only donated from cgroups with sizable surpluses so this\ncondition was always true. However, with the precise donation algorithm\nimplemented, f1de2439ec43 (\"blk-iocost: revamp donation amount\ndetermination\") made the donation amount calculation exact enabling even low\nhweight cgroups to donate.\n\nThis means that in rare occasions, a cgroup with active hweight of 1 can\nenter donation calculation triggering the following warning and then a\ndivide-by-zero oops.\n\n WARNING: CPU: 4 PID: 0 at block/blk-iocost.c:1928 transfer_surpluses.cold+0x0/0x53 [884/94867]\n ...\n RIP: 0010:transfer_surpluses.cold+0x0/0x53\n Code: 92 ff 48 c7 c7 28 d1 ab b5 65 48 8b 34 25 00 ae 01 00 48 81 c6 90 06 00 00 e8 8b 3f fe ff 48 c7 c0 ea ff ff ff e9 95 ff 92 ff <0f> 0b 48 c7 c7 30 da ab b5 e8 71 3f fe ff 4c 89 e8 4d 85 ed 74 0\n4\n ...\n Call Trace:\n \n ioc_timer_fn+0x1043/0x1390\n call_timer_fn+0xa1/0x2c0\n __run_timers.part.0+0x1ec/0x2e0\n run_timer_softirq+0x35/0x70\n ...\n iocg: invalid donation weights in /a/b: active=1 donating=1 after=0\n\nFix it by excluding cgroups w/ active hweight < 2 from donating. Excluding\nthese extreme low hweight donations shouldn't affect work conservation in\nany meaningful way." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: iocost: corrige la divisi\u00f3n por cero en la donaci\u00f3n de un grupo c de bajo peso. La l\u00f3gica de c\u00e1lculo de la donaci\u00f3n supone que el donante tiene un peso posterior a la donaci\u00f3n distinto de cero, por lo que el peso activo m\u00e1s bajo es una donaci\u00f3n. cgroup puede tener 2 para poder donar 1 y conservar el otro para s\u00ed mismo. Anteriormente, solo don\u00e1bamos de grupos comunitarios con excedentes considerables, por lo que esta condici\u00f3n siempre fue cierta. Sin embargo, con el algoritmo de donaci\u00f3n preciso implementado, f1de2439ec43 (\"blk-iocost: renovar la determinaci\u00f3n del monto de la donaci\u00f3n\") hizo que el c\u00e1lculo del monto de la donaci\u00f3n fuera exacto, permitiendo que incluso los grupos de bajo peso donaran. Esto significa que, en raras ocasiones, un grupo con un peso activo de 1 puede ingresar al c\u00e1lculo de la donaci\u00f3n, lo que genera la siguiente advertencia y luego una divisi\u00f3n por cero. ADVERTENCIA: CPU: 4 PID: 0 en block/blk-iocost.c:1928 transfer_surpluses.cold+0x0/0x53 [884/94867] ... RIP: 0010:transfer_surpluses.cold+0x0/0x53 C\u00f3digo: 92 y siguientes 48 c7 c7 28 d1 ab b5 65 48 8b 34 25 00 ae 01 00 48 81 c6 90 06 00 00 e8 8b 3f fe ff 48 c7 c0 ea ff ff ff e9 95 ff 92 ff <0f> 0b 48 c7 c7 30 da ab b5 e8 71 3f fe ff 4c 89 e8 4d 85 ed 74 0 4 ... Seguimiento de llamadas: ioc_timer_fn+0x1043/0x1390 call_timer_fn+0xa1/0x2c0 __run_timers.part.0+0x1ec/0x2e0 run_timer_softirq+0x35/0x70 ... iocg : pesos de donaci\u00f3n no v\u00e1lidos en /a/b: activo=1 donaci\u00f3n=1 despu\u00e9s=0 Corr\u00edjalo excluyendo cgroups con hweight activo < 2 de la donaci\u00f3n. Excluir estas donaciones de peso extremadamente bajo no deber\u00eda afectar la conservaci\u00f3n del trabajo de ninguna manera significativa." } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-475xx/CVE-2021-47585.json b/CVE-2021/CVE-2021-475xx/CVE-2021-47585.json index e7dcae06c17..38039f20050 100644 --- a/CVE-2021/CVE-2021-475xx/CVE-2021-47585.json +++ b/CVE-2021/CVE-2021-475xx/CVE-2021-47585.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47585", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:53.057", - "lastModified": "2024-06-19T15:15:53.057", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: fix memory leak in __add_inode_ref()\n\nLine 1169 (#3) allocates a memory chunk for victim_name by kmalloc(),\nbut when the function returns in line 1184 (#4) victim_name allocated\nby line 1169 (#3) is not freed, which will lead to a memory leak.\nThere is a similar snippet of code in this function as allocating a memory\nchunk for victim_name in line 1104 (#1) as well as releasing the memory\nin line 1116 (#2).\n\nWe should kfree() victim_name when the return value of backref_in_log()\nis less than zero and before the function returns in line 1184 (#4).\n\n1057 static inline int __add_inode_ref(struct btrfs_trans_handle *trans,\n1058 \t\t\t\t struct btrfs_root *root,\n1059 \t\t\t\t struct btrfs_path *path,\n1060 \t\t\t\t struct btrfs_root *log_root,\n1061 \t\t\t\t struct btrfs_inode *dir,\n1062 \t\t\t\t struct btrfs_inode *inode,\n1063 \t\t\t\t u64 inode_objectid, u64 parent_objectid,\n1064 \t\t\t\t u64 ref_index, char *name, int namelen,\n1065 \t\t\t\t int *search_done)\n1066 {\n\n1104 \tvictim_name = kmalloc(victim_name_len, GFP_NOFS);\n\t// #1: kmalloc (victim_name-1)\n1105 \tif (!victim_name)\n1106 \t\treturn -ENOMEM;\n\n1112\tret = backref_in_log(log_root, &search_key,\n1113\t\t\tparent_objectid, victim_name,\n1114\t\t\tvictim_name_len);\n1115\tif (ret < 0) {\n1116\t\tkfree(victim_name); // #2: kfree (victim_name-1)\n1117\t\treturn ret;\n1118\t} else if (!ret) {\n\n1169 \tvictim_name = kmalloc(victim_name_len, GFP_NOFS);\n\t// #3: kmalloc (victim_name-2)\n1170 \tif (!victim_name)\n1171 \t\treturn -ENOMEM;\n\n1180 \tret = backref_in_log(log_root, &search_key,\n1181 \t\t\tparent_objectid, victim_name,\n1182 \t\t\tvictim_name_len);\n1183 \tif (ret < 0) {\n1184 \t\treturn ret; // #4: missing kfree (victim_name-2)\n1185 \t} else if (!ret) {\n\n1241 \treturn 0;\n1242 }" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: btrfs: corrige la p\u00e9rdida de memoria en __add_inode_ref() La l\u00ednea 1169 (#3) asigna un fragmento de memoria para victim_name mediante kmalloc(), pero cuando la funci\u00f3n regresa en la l\u00ednea 1184 (#4) victim_name asignado por la l\u00ednea 1169 (#3) no se libera, lo que provocar\u00e1 una p\u00e9rdida de memoria. Hay un fragmento de c\u00f3digo similar en esta funci\u00f3n para asignar un fragmento de memoria para victim_name en la l\u00ednea 1104 (n.\u00ba 1), as\u00ed como para liberar la memoria en la l\u00ednea 1116 (n.\u00ba 2). Deber\u00edamos kfree() victim_name cuando el valor de retorno de backref_in_log() sea menor que cero y antes de que la funci\u00f3n regrese en la l\u00ednea 1184 (#4). 1057 static inline int __add_inode_ref(struct btrfs_trans_handle *trans, 1058 struct btrfs_root *root, 1059 struct btrfs_path *path, 1060 struct btrfs_root *log_root, 1061 struct btrfs_inode *dir, 1062 struct btrfs_inode *inode, 63 u64 inode_objectid, u64 parent_objectid, 1064 u64 ref_index, char *nombre, int nombrelen, 1065 int *search_done) 1066 { 1104 nombre_v\u00edctima = kmalloc(nombre_v\u00edctima_len, GFP_NOFS); // #1: kmalloc (nombre_v\u00edctima-1) 1105 if (!nombre_v\u00edctima) 1106 return -ENOMEM; 1112 ret = backref_in_log(log_root, &search_key, 1113 parent_objectid, victim_name, 1114 victim_name_len); 1115 if (ret < 0) { 1116 kfree(nombre_v\u00edctima); // #2: kfree (nombre_v\u00edctima-1) 1117 return ret; 1118 } else if (!ret) { 1169 nombre_v\u00edctima = kmalloc(nombre_v\u00edctima_len, GFP_NOFS); // #3: kmalloc (nombre_v\u00edctima-2) 1170 if (!nombre_v\u00edctima) 1171 return -ENOMEM; 1180 ret = backref_in_log(log_root, &search_key, 1181 parent_objectid, victim_name, 1182 victim_name_len); 1183 si (ret < 0) { 1184 retorno ret; // #4: falta kfree (nombre_v\u00edctima-2) 1185 } else if (!ret) { 1241 return 0; 1242 }" } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-475xx/CVE-2021-47586.json b/CVE-2021/CVE-2021-475xx/CVE-2021-47586.json index c3bb872759f..5b63dec7746 100644 --- a/CVE-2021/CVE-2021-475xx/CVE-2021-47586.json +++ b/CVE-2021/CVE-2021-475xx/CVE-2021-47586.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47586", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:53.160", - "lastModified": "2024-06-19T15:15:53.160", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: stmmac: dwmac-rk: fix oob read in rk_gmac_setup\n\nKASAN reports an out-of-bounds read in rk_gmac_setup on the line:\n\n\twhile (ops->regs[i]) {\n\nThis happens for most platforms since the regs flexible array member is\nempty, so the memory after the ops structure is being read here. It\nseems that mostly this happens to contain zero anyway, so we get lucky\nand everything still works.\n\nTo avoid adding redundant data to nearly all the ops structures, add a\nnew flag to indicate whether the regs field is valid and avoid this loop\nwhen it is not." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: net: stmmac: dwmac-rk: fix oob read in rk_gmac_setup KASAN informa una lectura fuera de los l\u00edmites en rk_gmac_setup en la l\u00ednea: while (ops->regs[i]) { Esto sucede en la mayor\u00eda de las plataformas, ya que el miembro de la matriz flexible regs est\u00e1 vac\u00edo, por lo que aqu\u00ed se lee la memoria despu\u00e9s de la estructura de operaciones. Parece que la mayor parte de esto contiene cero de todos modos, as\u00ed que tenemos suerte y todo sigue funcionando. Para evitar agregar datos redundantes a casi todas las estructuras de operaciones, agregue un nuevo indicador para indicar si el campo regs es v\u00e1lido y evite este bucle cuando no lo sea." } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-475xx/CVE-2021-47587.json b/CVE-2021/CVE-2021-475xx/CVE-2021-47587.json index 6bfc76bf612..85f63bf190e 100644 --- a/CVE-2021/CVE-2021-475xx/CVE-2021-47587.json +++ b/CVE-2021/CVE-2021-475xx/CVE-2021-47587.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47587", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:53.260", - "lastModified": "2024-06-19T15:15:53.260", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: systemport: Add global locking for descriptor lifecycle\n\nThe descriptor list is a shared resource across all of the transmit queues, and\nthe locking mechanism used today only protects concurrency across a given\ntransmit queue between the transmit and reclaiming. This creates an opportunity\nfor the SYSTEMPORT hardware to work on corrupted descriptors if we have\nmultiple producers at once which is the case when using multiple transmit\nqueues.\n\nThis was particularly noticeable when using multiple flows/transmit queues and\nit showed up in interesting ways in that UDP packets would get a correct UDP\nheader checksum being calculated over an incorrect packet length. Similarly TCP\npackets would get an equally correct checksum computed by the hardware over an\nincorrect packet length.\n\nThe SYSTEMPORT hardware maintains an internal descriptor list that it re-arranges\nwhen the driver produces a new descriptor anytime it writes to the\nWRITE_PORT_{HI,LO} registers, there is however some delay in the hardware to\nre-organize its descriptors and it is possible that concurrent TX queues\neventually break this internal allocation scheme to the point where the\nlength/status part of the descriptor gets used for an incorrect data buffer.\n\nThe fix is to impose a global serialization for all TX queues in the short\nsection where we are writing to the WRITE_PORT_{HI,LO} registers which solves\nthe corruption even with multiple concurrent TX queues being used." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: net: systemport: agregue bloqueo global para el ciclo de vida del descriptor. La lista de descriptores es un recurso compartido entre todas las colas de transmisi\u00f3n y el mecanismo de bloqueo que se usa hoy solo protege la concurrencia en una cola de transmisi\u00f3n determinada. entre la transmisi\u00f3n y la recuperaci\u00f3n. Esto crea una oportunidad para que el hardware de SYSTEMPORT funcione con descriptores corruptos si tenemos varios productores a la vez, como es el caso cuando utilizamos varias colas de transmisi\u00f3n. Esto fue particularmente notable cuando se usaban m\u00faltiples flujos/colas de transmisi\u00f3n y se mostr\u00f3 de manera interesante en que los paquetes UDP obtendr\u00edan una suma de verificaci\u00f3n de encabezado UDP correcta al calcularse sobre una longitud de paquete incorrecta. De manera similar, los paquetes TCP obtendr\u00edan una suma de verificaci\u00f3n igualmente correcta calculada por el hardware en una longitud de paquete incorrecta. El hardware de SYSTEMPORT mantiene una lista de descriptores internos que reorganiza cuando el controlador produce un nuevo descriptor cada vez que escribe en los registros WRITE_PORT_{HI,LO}. Sin embargo, hay cierto retraso en el hardware para reorganizar sus descriptores y es Es posible que las colas de TX simult\u00e1neas eventualmente rompan este esquema de asignaci\u00f3n interna hasta el punto en que la parte de longitud/estado del descriptor se use para un b\u00fafer de datos incorrecto. La soluci\u00f3n es imponer una serializaci\u00f3n global para todas las colas de TX en la secci\u00f3n corta donde escribimos en los registros WRITE_PORT_{HI,LO}, lo que resuelve la corrupci\u00f3n incluso cuando se utilizan varias colas de TX simult\u00e1neas." } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-475xx/CVE-2021-47588.json b/CVE-2021/CVE-2021-475xx/CVE-2021-47588.json index 19d17476815..9b9cbe7b1b3 100644 --- a/CVE-2021/CVE-2021-475xx/CVE-2021-47588.json +++ b/CVE-2021/CVE-2021-475xx/CVE-2021-47588.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47588", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:53.383", - "lastModified": "2024-06-19T15:15:53.383", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nsit: do not call ipip6_dev_free() from sit_init_net()\n\nipip6_dev_free is sit dev->priv_destructor, already called\nby register_netdevice() if something goes wrong.\n\nAlternative would be to make ipip6_dev_free() robust against\nmultiple invocations, but other drivers do not implement this\nstrategy.\n\nsyzbot reported:\n\ndst_release underflow\nWARNING: CPU: 0 PID: 5059 at net/core/dst.c:173 dst_release+0xd8/0xe0 net/core/dst.c:173\nModules linked in:\nCPU: 1 PID: 5059 Comm: syz-executor.4 Not tainted 5.16.0-rc5-syzkaller #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011\nRIP: 0010:dst_release+0xd8/0xe0 net/core/dst.c:173\nCode: 4c 89 f2 89 d9 31 c0 5b 41 5e 5d e9 da d5 44 f9 e8 1d 90 5f f9 c6 05 87 48 c6 05 01 48 c7 c7 80 44 99 8b 31 c0 e8 e8 67 29 f9 <0f> 0b eb 85 0f 1f 40 00 53 48 89 fb e8 f7 8f 5f f9 48 83 c3 a8 48\nRSP: 0018:ffffc9000aa5faa0 EFLAGS: 00010246\nRAX: d6894a925dd15a00 RBX: 00000000ffffffff RCX: 0000000000040000\nRDX: ffffc90005e19000 RSI: 000000000003ffff RDI: 0000000000040000\nRBP: 0000000000000000 R08: ffffffff816a1f42 R09: ffffed1017344f2c\nR10: ffffed1017344f2c R11: 0000000000000000 R12: 0000607f462b1358\nR13: 1ffffffff1bfd305 R14: ffffe8ffffcb1358 R15: dffffc0000000000\nFS: 00007f66c71a2700(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f88aaed5058 CR3: 0000000023e0f000 CR4: 00000000003506f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \n dst_cache_destroy+0x107/0x1e0 net/core/dst_cache.c:160\n ipip6_dev_free net/ipv6/sit.c:1414 [inline]\n sit_init_net+0x229/0x550 net/ipv6/sit.c:1936\n ops_init+0x313/0x430 net/core/net_namespace.c:140\n setup_net+0x35b/0x9d0 net/core/net_namespace.c:326\n copy_net_ns+0x359/0x5c0 net/core/net_namespace.c:470\n create_new_namespaces+0x4ce/0xa00 kernel/nsproxy.c:110\n unshare_nsproxy_namespaces+0x11e/0x180 kernel/nsproxy.c:226\n ksys_unshare+0x57d/0xb50 kernel/fork.c:3075\n __do_sys_unshare kernel/fork.c:3146 [inline]\n __se_sys_unshare kernel/fork.c:3144 [inline]\n __x64_sys_unshare+0x34/0x40 kernel/fork.c:3144\n do_syscall_x64 arch/x86/entry/common.c:50 [inline]\n do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80\n entry_SYSCALL_64_after_hwframe+0x44/0xae\nRIP: 0033:0x7f66c882ce99\nCode: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48\nRSP: 002b:00007f66c71a2168 EFLAGS: 00000246 ORIG_RAX: 0000000000000110\nRAX: ffffffffffffffda RBX: 00007f66c893ff60 RCX: 00007f66c882ce99\nRDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000048040200\nRBP: 00007f66c8886ff1 R08: 0000000000000000 R09: 0000000000000000\nR10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000\nR13: 00007fff6634832f R14: 00007f66c71a2300 R15: 0000000000022000\n " + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: sit: no llame a ipip6_dev_free() desde sit_init_net() ipip6_dev_free es sit dev->priv_destructor, ya llamado por Register_netdevice() si algo sale mal. La alternativa ser\u00eda hacer que ipip6_dev_free() sea robusto contra m\u00faltiples invocaciones, pero otros controladores no implementan esta estrategia. syzbot inform\u00f3: dst_release underflow ADVERTENCIA: CPU: 0 PID: 5059 en net/core/dst.c:173 dst_release+0xd8/0xe0 net/core/dst.c:173 M\u00f3dulos vinculados en: CPU: 1 PID: 5059 Comm: syz -executor.4 Not tainted 5.16.0-rc5-syzkaller #0 Nombre del hardware: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:dst_release+0xd8/0xe0 net/core/dst.c :173 C\u00f3digo: 4c 89 f2 89 d9 31 c0 5b 41 5e 5d e9 da d5 44 f9 e8 1d 90 5f f9 c6 05 87 48 c6 05 01 48 c7 c7 80 44 99 8b 31 c0 e8 e8 67 29 f9 <0f> 0b eb 85 0f 1f 40 00 53 48 89 fb e8 f7 8f 5f f9 48 83 c3 a8 48 RSP: 0018:ffffc9000aa5faa0 EFLAGS: 00010246 RAX: d6894a925dd15a00 RBX: RCX: 0000000000040000 RDX: ffffc90005e19000 RSI: 000000000003ffff RDI: 0000000000040000 RBP: 0000000000000000 R08 : ffffffff816a1f42 R09: ffffed1017344f2c R10: ffffed1017344f2c R11: 0000000000000000 R12: 0000607f462b1358 R13: 1ffffffff1bfd305 R14: ffffe8ffffcb135 8 R15: dffffc0000000000 FS: 00007f66c71a2700(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 50033 CR2: 00007f88aaed5058 CR3: 0000000023e0f000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 00000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Seguimiento de llamadas: dst_cache_destroy+0x107/0x1e0 net/core/dst_cache.c:160 ipip6_dev_free net/ ipv6/sit.c:1414 [en l\u00ednea] sit_init_net+0x229/0x550 net/ipv6/sit.c:1936 ops_init+0x313/0x430 net/core/net_namespace.c:140 setup_net+0x35b/0x9d0 net/core/net_namespace.c :326 copy_net_ns+0x359/0x5c0 net/core/net_namespace.c:470 create_new_namespaces+0x4ce/0xa00 kernel/nsproxy.c:110 unshare_nsproxy_namespaces+0x11e/0x180 kernel/nsproxy.c:226 ksys_unshare+0x57d/0xb50 .c :3075 __do_sys_unshare kernel/fork.c:3146 [en l\u00ednea] __se_sys_unshare kernel/fork.c:3144 [en l\u00ednea] __x64_sys_unshare+0x34/0x40 kernel/fork.c:3144 do_syscall_x64 arch/x86/entry/common.c:50 [en l\u00ednea ] do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80 Entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f66c882ce99 C\u00f3digo: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48 RSP:00 007f66c71a2168 EFLAGS: 00000246 ORIG_RAX: 0000000000000110 RAX: ffffffffffffffda RBX: 00007f66c893ff60 RCX: 00007f66c882ce99 RDX: 0000000000000000 RSI: 0000000000 000000 RDI: 0000000048040200 RBP: 00007f66c8886ff1 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 00000000000 00246 R12: 0000000000000000 R13: 00007fff6634832f R14: 00007f66c71a2300 R15: 0000000000022000 " } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-475xx/CVE-2021-47589.json b/CVE-2021/CVE-2021-475xx/CVE-2021-47589.json index dee22d85adc..4e7f9e96a38 100644 --- a/CVE-2021/CVE-2021-475xx/CVE-2021-47589.json +++ b/CVE-2021/CVE-2021-475xx/CVE-2021-47589.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47589", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:53.490", - "lastModified": "2024-06-19T15:15:53.490", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nigbvf: fix double free in `igbvf_probe`\n\nIn `igbvf_probe`, if register_netdev() fails, the program will go to\nlabel err_hw_init, and then to label err_ioremap. In free_netdev() which\nis just below label err_ioremap, there is `list_for_each_entry_safe` and\n`netif_napi_del` which aims to delete all entries in `dev->napi_list`.\nThe program has added an entry `adapter->rx_ring->napi` which is added by\n`netif_napi_add` in igbvf_alloc_queues(). However, adapter->rx_ring has\nbeen freed below label err_hw_init. So this a UAF.\n\nIn terms of how to patch the problem, we can refer to igbvf_remove() and\ndelete the entry before `adapter->rx_ring`.\n\nThe KASAN logs are as follows:\n\n[ 35.126075] BUG: KASAN: use-after-free in free_netdev+0x1fd/0x450\n[ 35.127170] Read of size 8 at addr ffff88810126d990 by task modprobe/366\n[ 35.128360]\n[ 35.128643] CPU: 1 PID: 366 Comm: modprobe Not tainted 5.15.0-rc2+ #14\n[ 35.129789] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org 04/01/2014\n[ 35.131749] Call Trace:\n[ 35.132199] dump_stack_lvl+0x59/0x7b\n[ 35.132865] print_address_description+0x7c/0x3b0\n[ 35.133707] ? free_netdev+0x1fd/0x450\n[ 35.134378] __kasan_report+0x160/0x1c0\n[ 35.135063] ? free_netdev+0x1fd/0x450\n[ 35.135738] kasan_report+0x4b/0x70\n[ 35.136367] free_netdev+0x1fd/0x450\n[ 35.137006] igbvf_probe+0x121d/0x1a10 [igbvf]\n[ 35.137808] ? igbvf_vlan_rx_add_vid+0x100/0x100 [igbvf]\n[ 35.138751] local_pci_probe+0x13c/0x1f0\n[ 35.139461] pci_device_probe+0x37e/0x6c0\n[ 35.165526]\n[ 35.165806] Allocated by task 366:\n[ 35.166414] ____kasan_kmalloc+0xc4/0xf0\n[ 35.167117] foo_kmem_cache_alloc_trace+0x3c/0x50 [igbvf]\n[ 35.168078] igbvf_probe+0x9c5/0x1a10 [igbvf]\n[ 35.168866] local_pci_probe+0x13c/0x1f0\n[ 35.169565] pci_device_probe+0x37e/0x6c0\n[ 35.179713]\n[ 35.179993] Freed by task 366:\n[ 35.180539] kasan_set_track+0x4c/0x80\n[ 35.181211] kasan_set_free_info+0x1f/0x40\n[ 35.181942] ____kasan_slab_free+0x103/0x140\n[ 35.182703] kfree+0xe3/0x250\n[ 35.183239] igbvf_probe+0x1173/0x1a10 [igbvf]\n[ 35.184040] local_pci_probe+0x13c/0x1f0" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: igbvf: corrige double free en `igbvf_probe` En `igbvf_probe`, si Register_netdev() falla, el programa ir\u00e1 a la etiqueta err_hw_init y luego a la etiqueta err_ioremap. En free_netdev(), que est\u00e1 justo debajo de la etiqueta err_ioremap, est\u00e1n `list_for_each_entry_safe` y `netif_napi_del` que tienen como objetivo eliminar todas las entradas en `dev->napi_list`. El programa ha agregado una entrada `adapter->rx_ring->napi` que se agrega mediante `netif_napi_add` en igbvf_alloc_queues(). Sin embargo, adaptador->rx_ring se ha liberado debajo de la etiqueta err_hw_init. Entonces esto es una UAF. En t\u00e9rminos de c\u00f3mo solucionar el problema, podemos consultar igbvf_remove() y eliminar la entrada antes de `adapter->rx_ring`. Los registros de KASAN son los siguientes: [35.126075] ERROR: KASAN: use-after-free en free_netdev+0x1fd/0x450 [35.127170] Lectura de tama\u00f1o 8 en la direcci\u00f3n ffff88810126d990 mediante la tarea modprobe/366 [35.128360] [35.128643] CPU: 1 PID : 366 Comm: modprobe Not tainted 5.15.0-rc2+ #14 [ 35.129789] Nombre del hardware: PC est\u00e1ndar QEMU (Q35 + ICH9, 2009), BIOS rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org 04/01 /2014 [35.131749] Seguimiento de llamadas: [35.132199] dump_stack_lvl+0x59/0x7b [35.132865] print_address_description+0x7c/0x3b0 [35.133707] ? free_netdev+0x1fd/0x450 [ 35.134378] __kasan_report+0x160/0x1c0 [ 35.135063] ? free_netdev+0x1fd/0x450 [ 35.135738] kasan_report+0x4b/0x70 [ 35.136367] free_netdev+0x1fd/0x450 [ 35.137006] igbvf_probe+0x121d/0x1a10 [igbvf] [ 35.137808 ] ? igbvf_vlan_rx_add_vid+0x100/0x100 [igbvf] [ 35.138751] local_pci_probe+0x13c/0x1f0 [ 35.139461] pci_device_probe+0x37e/0x6c0 [ 35.165526] [ 35.165806] por tarea 366: [35.166414] ____kasan_kmalloc+0xc4/0xf0 [35.167117] foo_kmem_cache_alloc_trace+0x3c/ 0x50 [igbvf] [ 35.168078] igbvf_probe+0x9c5/0x1a10 [igbvf] [ 35.168866] local_pci_probe+0x13c/0x1f0 [ 35.169565] pci_device_probe+0x37e/0x6c0 [ 35.179713 ] [35.179993] Liberado por la tarea 366: [35.180539] kasan_set_track+0x4c/0x80 [ 35.181211] kasan_set_free_info+0x1f/0x40 [ 35.181942] ____kasan_slab_free+0x103/0x140 [ 35.182703] kfree+0xe3/0x250 [ 35.183239] igbvf_probe+0x1173/0x1a10 vf] [35.184040] local_pci_probe+0x13c/0x1f0" } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-475xx/CVE-2021-47590.json b/CVE-2021/CVE-2021-475xx/CVE-2021-47590.json index 27f55b4911e..df1dd5d4ef5 100644 --- a/CVE-2021/CVE-2021-475xx/CVE-2021-47590.json +++ b/CVE-2021/CVE-2021-475xx/CVE-2021-47590.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47590", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:53.610", - "lastModified": "2024-06-19T15:15:53.610", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: fix deadlock in __mptcp_push_pending()\n\n__mptcp_push_pending() may call mptcp_flush_join_list() with subflow\nsocket lock held. If such call hits mptcp_sockopt_sync_all() then\nsubsequently __mptcp_sockopt_sync() could try to lock the subflow\nsocket for itself, causing a deadlock.\n\nsysrq: Show Blocked State\ntask:ss-server state:D stack: 0 pid: 938 ppid: 1 flags:0x00000000\nCall Trace:\n \n __schedule+0x2d6/0x10c0\n ? __mod_memcg_state+0x4d/0x70\n ? csum_partial+0xd/0x20\n ? _raw_spin_lock_irqsave+0x26/0x50\n schedule+0x4e/0xc0\n __lock_sock+0x69/0x90\n ? do_wait_intr_irq+0xa0/0xa0\n __lock_sock_fast+0x35/0x50\n mptcp_sockopt_sync_all+0x38/0xc0\n __mptcp_push_pending+0x105/0x200\n mptcp_sendmsg+0x466/0x490\n sock_sendmsg+0x57/0x60\n __sys_sendto+0xf0/0x160\n ? do_wait_intr_irq+0xa0/0xa0\n ? fpregs_restore_userregs+0x12/0xd0\n __x64_sys_sendto+0x20/0x30\n do_syscall_64+0x38/0x90\n entry_SYSCALL_64_after_hwframe+0x44/0xae\nRIP: 0033:0x7f9ba546c2d0\nRSP: 002b:00007ffdc3b762d8 EFLAGS: 00000246 ORIG_RAX: 000000000000002c\nRAX: ffffffffffffffda RBX: 00007f9ba56c8060 RCX: 00007f9ba546c2d0\nRDX: 000000000000077a RSI: 0000000000e5e180 RDI: 0000000000000234\nRBP: 0000000000cc57f0 R08: 0000000000000000 R09: 0000000000000000\nR10: 0000000000000000 R11: 0000000000000246 R12: 00007f9ba56c8060\nR13: 0000000000b6ba60 R14: 0000000000cc7840 R15: 41d8685b1d7901b8\n \n\nFix the issue by using __mptcp_flush_join_list() instead of plain\nmptcp_flush_join_list() inside __mptcp_push_pending(), as suggested by\nFlorian. The sockopt sync will be deferred to the workqueue." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: mptcp: corrige el punto muerto en __mptcp_push_pending() __mptcp_push_pending() puede llamar a mptcp_flush_join_list() con el bloqueo del socket de subflujo retenido. Si dicha llamada llega a mptcp_sockopt_sync_all(), posteriormente __mptcp_sockopt_sync() podr\u00eda intentar bloquear el socket de subflujo por s\u00ed mismo, provocando un punto muerto. sysrq: Mostrar estado bloqueado tarea: estado del servidor ss: D pila: 0 pid: 938 ppid: 1 banderas: 0x00000000 Seguimiento de llamadas: __schedule+0x2d6/0x10c0? __mod_memcg_state+0x4d/0x70 ? csum_partial+0xd/0x20? _raw_spin_lock_irqsave+0x26/0x50 horario+0x4e/0xc0 __lock_sock+0x69/0x90 ? do_wait_intr_irq+0xa0/0xa0 __lock_sock_fast+0x35/0x50 mptcp_sockopt_sync_all+0x38/0xc0 __mptcp_push_pending+0x105/0x200 mptcp_sendmsg+0x466/0x490 sock_sendmsg+0x57/0x60 __sys_sendto+0xf0/0x160? do_wait_intr_irq+0xa0/0xa0? fpregs_restore_userregs+0x12/0xd0 __x64_sys_sendto+0x20/0x30 do_syscall_64+0x38/0x90 Entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f9ba546c2d0 RSP: dc3b762d8 EFLAGS: 00000246 ORIG_RAX: 000000000000002c RAX: ffffffffffffffda RBX: 00007f9ba56c8060 RCX: 00007f9ba546c2d0 RDX: 000000000000077a RSI: 0000000000e5e180 RDI: 0000000000000234 RBP: 0000000000cc57f0 R08: 0000000000000000 R09: 00000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00007f9ba56c8060 R13: 0000000000b6ba60 R14: 0000000000cc7840 R15: 41d8685b1d7901b8 Solucione el problema usando __mptcp_flush_join_list() en su lugar de mptcp_flush_join_list() simple dentro __mptcp_push_pending(), como sugiere Florian. La sincronizaci\u00f3n de sockopt se aplazar\u00e1 a la cola de trabajo." } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-475xx/CVE-2021-47591.json b/CVE-2021/CVE-2021-475xx/CVE-2021-47591.json index a8d9ed619b9..16f982b5843 100644 --- a/CVE-2021/CVE-2021-475xx/CVE-2021-47591.json +++ b/CVE-2021/CVE-2021-475xx/CVE-2021-47591.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47591", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:53.700", - "lastModified": "2024-06-19T15:15:53.700", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: remove tcp ulp setsockopt support\n\nTCP_ULP setsockopt cannot be used for mptcp because its already\nused internally to plumb subflow (tcp) sockets to the mptcp layer.\n\nsyzbot managed to trigger a crash for mptcp connections that are\nin fallback mode:\n\nKASAN: null-ptr-deref in range [0x0000000000000020-0x0000000000000027]\nCPU: 1 PID: 1083 Comm: syz-executor.3 Not tainted 5.16.0-rc2-syzkaller #0\nRIP: 0010:tls_build_proto net/tls/tls_main.c:776 [inline]\n[..]\n __tcp_set_ulp net/ipv4/tcp_ulp.c:139 [inline]\n tcp_set_ulp+0x428/0x4c0 net/ipv4/tcp_ulp.c:160\n do_tcp_setsockopt+0x455/0x37c0 net/ipv4/tcp.c:3391\n mptcp_setsockopt+0x1b47/0x2400 net/mptcp/sockopt.c:638\n\nRemove support for TCP_ULP setsockopt." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: mptcp: elimina el soporte de tcp ulp setsockopt TCP_ULP setsockopt no se puede usar para mptcp porque ya se usa internamente para conectar sockets de subflujo (tcp) a la capa mptcp. syzbot logr\u00f3 desencadenar un bloqueo para las conexiones mptcp que est\u00e1n en modo alternativo: KASAN: null-ptr-deref en el rango [0x0000000000000020-0x0000000000000027] CPU: 1 PID: 1083 Comm: syz-executor.3 Not tainted 5.16.0-rc2- syzkaller #0 RIP: 0010:tls_build_proto net/tls/tls_main.c:776 [en l\u00ednea] [..] __tcp_set_ulp net/ipv4/tcp_ulp.c:139 [en l\u00ednea] tcp_set_ulp+0x428/0x4c0 net/ipv4/tcp_ulp.c: 160 do_tcp_setsockopt+0x455/0x37c0 net/ipv4/tcp.c:3391 mptcp_setsockopt+0x1b47/0x2400 net/mptcp/sockopt.c:638 Elimina la compatibilidad con TCP_ULP setsockopt." } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-475xx/CVE-2021-47592.json b/CVE-2021/CVE-2021-475xx/CVE-2021-47592.json index e4d88e6d5fe..93a8933ae3b 100644 --- a/CVE-2021/CVE-2021-475xx/CVE-2021-47592.json +++ b/CVE-2021/CVE-2021-475xx/CVE-2021-47592.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47592", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:53.793", - "lastModified": "2024-06-19T15:15:53.793", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: stmmac: fix tc flower deletion for VLAN priority Rx steering\n\nTo replicate the issue:-\n\n1) Add 1 flower filter for VLAN Priority based frame steering:-\n$ IFDEVNAME=eth0\n$ tc qdisc add dev $IFDEVNAME ingress\n$ tc qdisc add dev $IFDEVNAME root mqprio num_tc 8 \\\n map 0 1 2 3 4 5 6 7 0 0 0 0 0 0 0 0 \\\n queues 1@0 1@1 1@2 1@3 1@4 1@5 1@6 1@7 hw 0\n$ tc filter add dev $IFDEVNAME parent ffff: protocol 802.1Q \\\n flower vlan_prio 0 hw_tc 0\n\n2) Get the 'pref' id\n$ tc filter show dev $IFDEVNAME ingress\n\n3) Delete a specific tc flower record (say pref 49151)\n$ tc filter del dev $IFDEVNAME parent ffff: pref 49151\n\nFrom dmesg, we will observe kernel NULL pointer ooops\n\n[ 197.170464] BUG: kernel NULL pointer dereference, address: 0000000000000000\n[ 197.171367] #PF: supervisor read access in kernel mode\n[ 197.171367] #PF: error_code(0x0000) - not-present page\n[ 197.171367] PGD 0 P4D 0\n[ 197.171367] Oops: 0000 [#1] PREEMPT SMP NOPTI\n\n\n\n[ 197.171367] RIP: 0010:tc_setup_cls+0x20b/0x4a0 [stmmac]\n\n\n\n[ 197.171367] Call Trace:\n[ 197.171367] \n[ 197.171367] ? __stmmac_disable_all_queues+0xa8/0xe0 [stmmac]\n[ 197.171367] stmmac_setup_tc_block_cb+0x70/0x110 [stmmac]\n[ 197.171367] tc_setup_cb_destroy+0xb3/0x180\n[ 197.171367] fl_hw_destroy_filter+0x94/0xc0 [cls_flower]\n\nThe above issue is due to previous incorrect implementation of\ntc_del_vlan_flow(), shown below, that uses flow_cls_offload_flow_rule()\nto get struct flow_rule *rule which is no longer valid for tc filter\ndelete operation.\n\n struct flow_rule *rule = flow_cls_offload_flow_rule(cls);\n struct flow_dissector *dissector = rule->match.dissector;\n\nSo, to ensure tc_del_vlan_flow() deletes the right VLAN cls record for\nearlier configured RX queue (configured by hw_tc) in tc_add_vlan_flow(),\nthis patch introduces stmmac_rfs_entry as driver-side flow_cls_offload\nrecord for 'RX frame steering' tc flower, currently used for VLAN\npriority. The implementation has taken consideration for future extension\nto include other type RX frame steering such as EtherType based.\n\nv2:\n - Clean up overly extensive backtrace and rewrite git message to better\n explain the kernel NULL pointer issue." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: net: stmmac: corrija la eliminaci\u00f3n de flores tc para la direcci\u00f3n Rx con prioridad de VLAN Para replicar el problema: - 1) Agregue 1 filtro de flores para la direcci\u00f3n de cuadros basada en prioridad de VLAN: - $ IFDEVNAME=eth0 $ tc qdisc agregar dev $IFDEVNAME ingreso $ tc qdisc agregar dev $IFDEVNAME ra\u00edz mqprio num_tc 8 \\ map 0 1 2 3 4 5 6 7 0 0 0 0 0 0 0 0 0 \\ colas 1@0 1@1 1@2 1@3 1@4 1@5 1@6 1@7 hw 0 $ tc filter add dev $IFDEVNAME parent ffff: protocolo 802.1Q \\ flower vlan_prio 0 hw_tc 0 2) Obtener el id 'pref' $ tc filter show dev $IFDEVNAME ingress 3 ) Eliminar un registro de flor tc espec\u00edfico (digamos pref 49151) $ tc filter del dev $IFDEVNAME parent ffff: pref 49151 Desde dmesg, observaremos el puntero NULL del kernel ooops [ 197.170464] ERROR: desreferencia del puntero NULL del kernel, direcci\u00f3n: 00000000000000000 [ 197.171367] #PF: acceso de lectura de supervisor en modo kernel [ 197.171367] #PF: error_code(0x0000) - p\u00e1gina no presente [ 197.171367] PGD 0 P4D 0 [ 197.171367] Ups: 0000 [#1] PREEMPT SMP NOPTI [ 197.171367] RIP: 0010:tc_setup_cls+0x20b/0x4a0 [stmmac] [ 197.171367] Seguimiento de llamadas: [ 197.171367] [ 197.171367] ? __stmmac_disable_all_queues+0xa8/0xe0 [stmmac] [ 197.171367] stmmac_setup_tc_block_cb+0x70/0x110 [stmmac] [ 197.171367] tc_setup_cb_destroy+0xb3/0x180 [ 197.171367] destroy_filter+0x94/0xc0 [cls_flower] El problema anterior se debe a una implementaci\u00f3n anterior incorrecta de tc_del_vlan_flow( ), que se muestra a continuaci\u00f3n, que usa flow_cls_offload_flow_rule() para obtener la estructura flow_rule *rule que ya no es v\u00e1lida para la operaci\u00f3n de eliminaci\u00f3n del filtro tc. estructura flow_rule *regla = flow_cls_offload_flow_rule(cls); estructura flow_dissector *dissector = regla->match.dissector; Por lo tanto, para garantizar que tc_del_vlan_flow() elimine el registro VLAN cls correcto para la cola RX configurada anteriormente (configurada por hw_tc) en tc_add_vlan_flow(), este parche introduce stmmac_rfs_entry como registro flow_cls_offload del lado del controlador para la flor tc 'Direcci\u00f3n de trama RX', actualmente utilizada para Prioridad de VLAN. La implementaci\u00f3n ha tenido en cuenta una futura ampliaci\u00f3n para incluir otro tipo de direcci\u00f3n de bastidor RX, como la basada en EtherType. v2: - Limpiar el rastreo demasiado extenso y reescribir el mensaje de git para explicar mejor el problema del puntero NULL del kernel." } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-475xx/CVE-2021-47593.json b/CVE-2021/CVE-2021-475xx/CVE-2021-47593.json index 6d3f8672e1f..f7b7c95f32c 100644 --- a/CVE-2021/CVE-2021-475xx/CVE-2021-47593.json +++ b/CVE-2021/CVE-2021-475xx/CVE-2021-47593.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47593", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:53.890", - "lastModified": "2024-06-19T15:15:53.890", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: clear 'kern' flag from fallback sockets\n\nThe mptcp ULP extension relies on sk->sk_sock_kern being set correctly:\nIt prevents setsockopt(fd, IPPROTO_TCP, TCP_ULP, \"mptcp\", 6); from\nworking for plain tcp sockets (any userspace-exposed socket).\n\nBut in case of fallback, accept() can return a plain tcp sk.\nIn such case, sk is still tagged as 'kernel' and setsockopt will work.\n\nThis will crash the kernel, The subflow extension has a NULL ctx->conn\nmptcp socket:\n\nBUG: KASAN: null-ptr-deref in subflow_data_ready+0x181/0x2b0\nCall Trace:\n tcp_data_ready+0xf8/0x370\n [..]" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: mptcp: borrar el indicador 'kern' de los sockets de reserva La extensi\u00f3n mptcp ULP depende de que sk->sk_sock_kern est\u00e9 configurado correctamente: impide que setsockopt(fd, IPPROTO_TCP, TCP_ULP, \"mptcp\", 6); de funcionar para sockets tcp simples (cualquier socket expuesto al espacio de usuario). Pero en caso de respaldo, aceptar() puede devolver un sk tcp simple. En tal caso, sk todav\u00eda est\u00e1 etiquetado como 'kernel' y setsockopt funcionar\u00e1. Esto bloquear\u00e1 el kernel. La extensi\u00f3n de subflujo tiene un socket NULL ctx->conn mptcp: ERROR: KASAN: null-ptr-deref en subflow_data_ready+0x181/0x2b0 Seguimiento de llamadas: tcp_data_ready+0xf8/0x370 [..]" } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-475xx/CVE-2021-47594.json b/CVE-2021/CVE-2021-475xx/CVE-2021-47594.json index 14ced56fa29..43138375c64 100644 --- a/CVE-2021/CVE-2021-475xx/CVE-2021-47594.json +++ b/CVE-2021/CVE-2021-475xx/CVE-2021-47594.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47594", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:53.983", - "lastModified": "2024-06-19T15:15:53.983", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: never allow the PM to close a listener subflow\n\nCurrently, when deleting an endpoint the netlink PM treverses\nall the local MPTCP sockets, regardless of their status.\n\nIf an MPTCP listener socket is bound to the IP matching the\ndelete endpoint, the listener TCP socket will be closed.\nThat is unexpected, the PM should only affect data subflows.\n\nAdditionally, syzbot was able to trigger a NULL ptr dereference\ndue to the above:\n\ngeneral protection fault, probably for non-canonical address 0xdffffc0000000003: 0000 [#1] PREEMPT SMP KASAN\nKASAN: null-ptr-deref in range [0x0000000000000018-0x000000000000001f]\nCPU: 1 PID: 6550 Comm: syz-executor122 Not tainted 5.16.0-rc4-syzkaller #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011\nRIP: 0010:__lock_acquire+0xd7d/0x54a0 kernel/locking/lockdep.c:4897\nCode: 0f 0e 41 be 01 00 00 00 0f 86 c8 00 00 00 89 05 69 cc 0f 0e e9 bd 00 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 da 48 c1 ea 03 <80> 3c 02 00 0f 85 f3 2f 00 00 48 81 3b 20 75 17 8f 0f 84 52 f3 ff\nRSP: 0018:ffffc90001f2f818 EFLAGS: 00010016\nRAX: dffffc0000000000 RBX: 0000000000000018 RCX: 0000000000000000\nRDX: 0000000000000003 RSI: 0000000000000000 RDI: 0000000000000001\nRBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000001\nR10: 0000000000000000 R11: 000000000000000a R12: 0000000000000000\nR13: ffff88801b98d700 R14: 0000000000000000 R15: 0000000000000001\nFS: 00007f177cd3d700(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f177cd1b268 CR3: 000000001dd55000 CR4: 0000000000350ee0\nCall Trace:\n \n lock_acquire kernel/locking/lockdep.c:5637 [inline]\n lock_acquire+0x1ab/0x510 kernel/locking/lockdep.c:5602\n __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]\n _raw_spin_lock_irqsave+0x39/0x50 kernel/locking/spinlock.c:162\n finish_wait+0xc0/0x270 kernel/sched/wait.c:400\n inet_csk_wait_for_connect net/ipv4/inet_connection_sock.c:464 [inline]\n inet_csk_accept+0x7de/0x9d0 net/ipv4/inet_connection_sock.c:497\n mptcp_accept+0xe5/0x500 net/mptcp/protocol.c:2865\n inet_accept+0xe4/0x7b0 net/ipv4/af_inet.c:739\n mptcp_stream_accept+0x2e7/0x10e0 net/mptcp/protocol.c:3345\n do_accept+0x382/0x510 net/socket.c:1773\n __sys_accept4_file+0x7e/0xe0 net/socket.c:1816\n __sys_accept4+0xb0/0x100 net/socket.c:1846\n __do_sys_accept net/socket.c:1864 [inline]\n __se_sys_accept net/socket.c:1861 [inline]\n __x64_sys_accept+0x71/0xb0 net/socket.c:1861\n do_syscall_x64 arch/x86/entry/common.c:50 [inline]\n do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80\n entry_SYSCALL_64_after_hwframe+0x44/0xae\nRIP: 0033:0x7f177cd8b8e9\nCode: 28 00 00 00 75 05 48 83 c4 28 c3 e8 b1 14 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48\nRSP: 002b:00007f177cd3d308 EFLAGS: 00000246 ORIG_RAX: 000000000000002b\nRAX: ffffffffffffffda RBX: 00007f177ce13408 RCX: 00007f177cd8b8e9\nRDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003\nRBP: 00007f177ce13400 R08: 0000000000000000 R09: 0000000000000000\nR10: 0000000000000000 R11: 0000000000000246 R12: 00007f177ce1340c\nR13: 00007f177cde1004 R14: 6d705f706374706d R15: 0000000000022000\n \n\nFix the issue explicitly skipping MPTCP socket in TCP_LISTEN\nstatus." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: mptcp: nunca permitir que el PM cierre un subflujo de escucha Actualmente, al eliminar un endpoint, el PM de netlink atraviesa todos los sockets MPTCP locales, independientemente de su estado. Si un socket de escucha MPTCP est\u00e1 vinculado a la IP que coincide con el endpoint de eliminaci\u00f3n, el socket TCP de escucha se cerrar\u00e1. Esto es inesperado, el PM solo deber\u00eda afectar los subflujos de datos. Adem\u00e1s, syzbot pudo activar una desreferencia de ptr NULL debido a lo anterior: falla de protecci\u00f3n general, probablemente para la direcci\u00f3n no can\u00f3nica 0xdffffc0000000003: 0000 [#1] PREEMPT SMP KASAN KASAN: null-ptr-deref en el rango [0x0000000000000018-0x0000000000000001f] CPU: 1 PID: 6550 Comm: syz-executor122 No contaminado 5.16.0-rc4-syzkaller #0 Nombre del hardware: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:__lock_acquire+0xd7d/0x54a0 kernel/locking/lockdep.c:4897 C\u00f3digo: 0f 0e 41 be 01 00 00 00 0f 86 c8 00 00 00 89 05 69 cc 0f 0e e9 bd 00 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 da 48 c1 ea 03 <80> 3c 02 00 0f 85 f3 2f 00 00 48 81 3b 20 75 17 8f 0f 84 52 f3 ff RSP: 0018:ffffc90001f2f818 EFLAGS: 00010016 RAX: 00 RBX: 0000000000000018 RCX: 0000000000000000 RDX: 0000000000000003 RSI: 0000000000000000 RDI: 0000000000000001 RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000001 R10: 0000000000000000 R11: 000000000000000 a R12: 0000000000000000 R13: ffff88801b98d700 R14: 0000000000000000 R15: 0000000000000001 FS: 00007f177cd3d700(0000) GS:ffff8880b9d00000 (0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f177cd1b268 CR3: 000000001dd55000 CR4: 0000000000350ee0 Seguimiento de llamadas: lock_acquire kernel/locking/lockdep.c:5637 [en l\u00ednea] +0x1ab/0x510 kernel/locking/lockdep.c:5602 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [en l\u00ednea] _raw_spin_lock_irqsave+0x39/0x50 kernel/locking/spinlock.c:162 Finish_wait+0xc0/0x270 kernel/sched/wait.c:400 inet_csk_wait_for_connect net/ipv4/inet_connection_sock.c:464 [en l\u00ednea] inet_csk_accept+0x7de/0x9d0 net/ipv4/inet_connection_sock.c:497 mptcp_accept+0xe5/0x500 net/mptcp/protocol.c:2865 inet_accept+0xe4/0x7b0 net/ipv4/af_inet.c:739 e7/0x10e0 net/mptcp/protocol.c:3345 do_accept+0x382/0x510 net/socket.c:1773 __sys_accept4_file+0x7e/0xe0 net/socket.c:1816 __sys_accept4+0xb0/0x100 net/socket.c:1846 __do_sys_accept net/socket. c:1864 [en l\u00ednea] __se_sys_accept net/socket.c:1861 [en l\u00ednea] __x64_sys_accept+0x71/0xb0 net/socket.c:1861 do_syscall_x64 arch/x86/entry/common.c:50 [en l\u00ednea] do_syscall_64+0x35/0xb0 arch /x86/entry/common.c:80 Entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f177cd8b8e9 C\u00f3digo: 28 00 00 00 75 05 48 83 c4 28 c3 e8 b1 14 00 00 90 48 89 f8 48 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f177cd3d308 EFLAGS: 00000246 ORIG_RAX: 000000000000002b RAX : ffffffffffffffda RBX: 00007f177ce13408 RCX: 00007f177cd8b8e9 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003 RBP: 00007f177 ce13400 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00007f177ce1340c R13: cde1004 R14: 6d705f706374706d R15: 0000000000022000 Arreglar el problema al omitir expl\u00edcitamente el socket MPTCP en el estado TCP_LISTEN." } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-475xx/CVE-2021-47595.json b/CVE-2021/CVE-2021-475xx/CVE-2021-47595.json index 4aeafa3c451..a000b760105 100644 --- a/CVE-2021/CVE-2021-475xx/CVE-2021-47595.json +++ b/CVE-2021/CVE-2021-475xx/CVE-2021-47595.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47595", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:54.097", - "lastModified": "2024-06-19T15:15:54.097", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: sch_ets: don't remove idle classes from the round-robin list\n\nShuang reported that the following script:\n\n 1) tc qdisc add dev ddd0 handle 10: parent 1: ets bands 8 strict 4 priomap 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7\n 2) mausezahn ddd0 -A 10.10.10.1 -B 10.10.10.2 -c 0 -a own -b 00:c1:a0:c1:a0:00 -t udp &\n 3) tc qdisc change dev ddd0 handle 10: ets bands 4 strict 2 quanta 2500 2500 priomap 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3\n\ncrashes systematically when line 2) is commented:\n\n list_del corruption, ffff8e028404bd30->next is LIST_POISON1 (dead000000000100)\n ------------[ cut here ]------------\n kernel BUG at lib/list_debug.c:47!\n invalid opcode: 0000 [#1] PREEMPT SMP NOPTI\n CPU: 0 PID: 954 Comm: tc Not tainted 5.16.0-rc4+ #478\n Hardware name: Red Hat KVM, BIOS 1.11.1-4.module+el8.1.0+4066+0f1aadab 04/01/2014\n RIP: 0010:__list_del_entry_valid.cold.1+0x12/0x47\n Code: fe ff 0f 0b 48 89 c1 4c 89 c6 48 c7 c7 08 42 1b 87 e8 1d c5 fe ff 0f 0b 48 89 fe 48 89 c2 48 c7 c7 98 42 1b 87 e8 09 c5 fe ff <0f> 0b 48 c7 c7 48 43 1b 87 e8 fb c4 fe ff 0f 0b 48 89 f2 48 89 fe\n RSP: 0018:ffffae46807a3888 EFLAGS: 00010246\n RAX: 000000000000004e RBX: 0000000000000007 RCX: 0000000000000202\n RDX: 0000000000000000 RSI: ffffffff871ac536 RDI: 00000000ffffffff\n RBP: ffffae46807a3a10 R08: 0000000000000000 R09: c0000000ffff7fff\n R10: 0000000000000001 R11: ffffae46807a36a8 R12: ffff8e028404b800\n R13: ffff8e028404bd30 R14: dead000000000100 R15: ffff8e02fafa2400\n FS: 00007efdc92e4480(0000) GS:ffff8e02fb600000(0000) knlGS:0000000000000000\n CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 0000000000682f48 CR3: 00000001058be000 CR4: 0000000000350ef0\n Call Trace:\n \n ets_qdisc_change+0x58b/0xa70 [sch_ets]\n tc_modify_qdisc+0x323/0x880\n rtnetlink_rcv_msg+0x169/0x4a0\n netlink_rcv_skb+0x50/0x100\n netlink_unicast+0x1a5/0x280\n netlink_sendmsg+0x257/0x4d0\n sock_sendmsg+0x5b/0x60\n ____sys_sendmsg+0x1f2/0x260\n ___sys_sendmsg+0x7c/0xc0\n __sys_sendmsg+0x57/0xa0\n do_syscall_64+0x3a/0x80\n entry_SYSCALL_64_after_hwframe+0x44/0xae\n RIP: 0033:0x7efdc8031338\n Code: 89 02 48 c7 c0 ff ff ff ff eb b5 0f 1f 80 00 00 00 00 f3 0f 1e fa 48 8d 05 25 43 2c 00 8b 00 85 c0 75 17 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 58 c3 0f 1f 80 00 00 00 00 41 54 41 89 d4 55\n RSP: 002b:00007ffdf1ce9828 EFLAGS: 00000246 ORIG_RAX: 000000000000002e\n RAX: ffffffffffffffda RBX: 0000000061b37a97 RCX: 00007efdc8031338\n RDX: 0000000000000000 RSI: 00007ffdf1ce9890 RDI: 0000000000000003\n RBP: 0000000000000000 R08: 0000000000000001 R09: 000000000078a940\n R10: 000000000000000c R11: 0000000000000246 R12: 0000000000000001\n R13: 0000000000688880 R14: 0000000000000000 R15: 0000000000000000\n \n Modules linked in: sch_ets sch_tbf dummy rfkill iTCO_wdt iTCO_vendor_support intel_rapl_msr intel_rapl_common joydev pcspkr i2c_i801 virtio_balloon i2c_smbus lpc_ich ip_tables xfs libcrc32c crct10dif_pclmul crc32_pclmul crc32c_intel serio_raw ghash_clmulni_intel ahci libahci libata virtio_blk virtio_console virtio_net net_failover failover sunrpc dm_mirror dm_region_hash dm_log dm_mod [last unloaded: sch_ets]\n ---[ end trace f35878d1912655c2 ]---\n RIP: 0010:__list_del_entry_valid.cold.1+0x12/0x47\n Code: fe ff 0f 0b 48 89 c1 4c 89 c6 48 c7 c7 08 42 1b 87 e8 1d c5 fe ff 0f 0b 48 89 fe 48 89 c2 48 c7 c7 98 42 1b 87 e8 09 c5 fe ff <0f> 0b 48 c7 c7 48 43 1b 87 e8 fb c4 fe ff 0f 0b 48 89 f2 48 89 fe\n RSP: 0018:ffffae46807a3888 EFLAGS: 00010246\n RAX: 000000000000004e RBX: 0000000000000007 RCX: 0000000000000202\n RDX: 0000000000000000 RSI: ffffffff871ac536 RDI: 00000000ffffffff\n RBP: ffffae46807a3a10 R08: 0000000000000000 R09: c0000000ffff7fff\n R10: 0000000000000001 R11: ffffae46807a36a8 R12: ffff8e028404b800\n R13: ffff8e028404bd30 R14: dead000000000100 R15: ffff8e02fafa2400\n FS: 00007efdc92e4480(0000) GS:ffff8e02fb600000(0000) knlGS:0000000000000000\n CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 000000000\n---truncated---" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: net/sched: sch_ets: no elimine las clases inactivas de la lista de turnos Shuang inform\u00f3 que el siguiente script: 1) tc qdisc add dev ddd0 handle 10: parent 1: ets bandas 8 estricto 4 priomap 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 2) mausezahn ddd0 -A 10.10.10.1 -B 10.10.10.2 -c 0 -a propio -b 00:c1:a0: c1:a0:00 -t udp & 3) tc qdisc change dev ddd0 handle 10: ets bands 4 estricto 2 cuantos 2500 2500 priomap 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 falla sistem\u00e1ticamente cuando la l\u00ednea 2) se comenta: corrupci\u00f3n list_del, ffff8e028404bd30->el siguiente es LIST_POISON1 (dead000000000100) ------------[ cortar aqu\u00ed ]------------ ERROR del kernel en lib/list_debug. c:47! c\u00f3digo de operaci\u00f3n no v\u00e1lido: 0000 [#1] PREEMPT SMP NOPTI CPU: 0 PID: 954 Comunicaciones: tc Not tainted 5.16.0-rc4+ #478 Nombre de hardware: Red Hat KVM, BIOS 1.11.1-4.module+el8.1.0+4066 +0f1aadab 01/04/2014 RIP: 0010:__list_del_entry_valid.cold.1+0x12/0x47 C\u00f3digo: fe ff 0f 0b 48 89 c1 4c 89 c6 48 c7 c7 08 42 1b 87 e8 1d c5 fe ff 0f 0b 48 89 fe 4 8 89 c2 48 c7 c7 98 42 1b 87 e8 09 c5 fe ff <0f> 0b 48 c7 c7 48 43 1b 87 e8 fb c4 fe ff 0f 0b 48 89 f2 48 89 fe RSP: 0018:ffffae46807a3888 EFLAGS: 246 RAX: 000000000000004eRBX : 0000000000000007 RCX: 0000000000000202 RDX: 0000000000000000 RSI: ffffffff871ac536 RDI: 00000000ffffffff RBP: ffffae46807a3a10 R08: 00000000000 00000 R09: c0000000ffff7fff R10: 00000000000000001 R11: ffffae46807a36a8 R12: ffff8e028404b800 R13: ffff8e028404bd30 R14: dead000000000100 R15: e02fafa2400 FS: 00007efdc92e4480(0000) GS:ffff8e02fb600000 (0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000682f48 CR3: 00000001058be000 CR4: 000000000035 0ef0 Seguimiento de llamadas: ets_qdisc_change+0x58b/0xa70 [sch_ets] tc_modify_qdisc+0x323/0x880 rtnetlink_rcv_msg+0x169/ 0x4a0 netlink_rcv_skb+0x50/0x100 netlink_unicast+0x1a5/0x280 netlink_sendmsg+0x257/0x4d0 sock_sendmsg+0x5b/0x60 ____sys_sendmsg+0x1f2/0x260 ___sys_sendmsg+0x7c/0xc0 __sys_sendmsg+0x57/0xa0 do_syscall_64+0x3a/0x80 Entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033: 0x7efdc8031338 C\u00f3digo: 89 02 48 c7 c0 ff ff ff ff eb b5 0f 1f 80 00 00 00 00 f3 0f 1e fa 48 8d 05 25 43 2c 00 8b 00 85 c0 75 17 b8 2e 00 00 0f 05 <48> 3d 00 f0 ff ff 77 58 c3 0f 1f 80 00 00 00 00 41 54 41 89 d4 55 RSP: 002b:00007ffdf1ce9828 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: de RBX: 0000000061b37a97 RCX: 00007efdc8031338 RDX: 0000000000000000 RSI: 00007ffdf1ce9890 RDI: 0000000000000003 RBP: 0000000000000000 R08: 0000000000000001 R09: 000000000078a940 R10: 000000000000000c R11: 00000000000000246 R12: 0000000000000001 R 13: 0000000000688880 R14: 0000000000000000 R15: 0000000000000000 M\u00f3dulos vinculados en: sch_ets sch_tbf dummy rfkill iTCO_wdt iTCO_vendor_support intel_rapl_msr intel_rapl_common pcs pkr i2c_i801 virtio_balloon i2c_smbus lpc_ich ip_tables xfs libcrc32c crct10dif_pclmul crc32_pclmul crc32c_intel serio_raw ghash_clmulni_intel ahci libahci libata virtio_blk virtio_console virtio_net net_failover failover sunrpc dm_mirror dm_region_hash dm_log dm_mod [\u00faltima descarga: sch_ets] ---[ fin de seguimiento f35878d191 2655c2 ]--- RIP: 0010:__list_del_entry_valid.cold.1+0x12/0x47 C\u00f3digo: fe ff 0f 0b 48 89 c1 4c 89 c6 48 c7 c7 08 42 1b 87 e8 1d c5 fe ff 0f 0b 48 89 fe 48 89 c2 48 c7 c7 98 42 1b 87 e8 09 c5 fe ff <0f> 0b 48 c7 c7 48 43 1b 87 e8 fb c4 fe ff 0f 0b 48 89 f2 48 89 fe RSP: 0018:ffffae46807a3888 EFLAGS: 00010246 RAX: 000000000000004e RBX: 0000000000000007 RCX 000 0000000000202 RDX: 0000000000000000 RSI: ffffffff871ac536 RDI: 00000000ffffffff RBP: ffffae46807a3a10 R08: 0000000000000000 R09: c0000000ffff7fff R10: 0000000000000001 R11: FFFFFAE46807A36A8 R12: FFFFF8E028404B800 R13: FFFF8E028404BD30 R14: Dead000000000100 R15: FFFFF8E02FAFA2400 FUT: GS: FFFF8E02FB600000 (0000) KNLGS: 000000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000000 - --truncado---" } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-475xx/CVE-2021-47596.json b/CVE-2021/CVE-2021-475xx/CVE-2021-47596.json index b90a9922be6..d6c00e329f0 100644 --- a/CVE-2021/CVE-2021-475xx/CVE-2021-47596.json +++ b/CVE-2021/CVE-2021-475xx/CVE-2021-47596.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47596", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:54.197", - "lastModified": "2024-06-19T15:15:54.197", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: hns3: fix use-after-free bug in hclgevf_send_mbx_msg\n\nCurrently, the hns3_remove function firstly uninstall client instance,\nand then uninstall acceletion engine device. The netdevice is freed in\nclient instance uninstall process, but acceletion engine device uninstall\nprocess still use it to trace runtime information. This causes a use after\nfree problem.\n\nSo fixes it by check the instance register state to avoid use after free." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: net: hns3: corrige el error de use-after-free en hclgevf_send_mbx_msg Actualmente, la funci\u00f3n hns3_remove desinstala primero la instancia del cliente y luego desinstala el dispositivo del motor de aceleraci\u00f3n. El dispositivo de red se libera en el proceso de desinstalaci\u00f3n de la instancia del cliente, pero el proceso de desinstalaci\u00f3n del dispositivo del motor de aceleraci\u00f3n a\u00fan lo utiliza para rastrear la informaci\u00f3n del tiempo de ejecuci\u00f3n. Esto provoca un problema de use-after-free. Entonces lo soluciona verificando el estado del registro de la instancia para evitar use after free." } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-475xx/CVE-2021-47597.json b/CVE-2021/CVE-2021-475xx/CVE-2021-47597.json index 7bee495ce8f..9e0ef74e314 100644 --- a/CVE-2021/CVE-2021-475xx/CVE-2021-47597.json +++ b/CVE-2021/CVE-2021-475xx/CVE-2021-47597.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47597", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:54.290", - "lastModified": "2024-06-19T15:15:54.290", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ninet_diag: fix kernel-infoleak for UDP sockets\n\nKMSAN reported a kernel-infoleak [1], that can exploited\nby unpriv users.\n\nAfter analysis it turned out UDP was not initializing\nr->idiag_expires. Other users of inet_sk_diag_fill()\nmight make the same mistake in the future, so fix this\nin inet_sk_diag_fill().\n\n[1]\nBUG: KMSAN: kernel-infoleak in instrument_copy_to_user include/linux/instrumented.h:121 [inline]\nBUG: KMSAN: kernel-infoleak in copyout lib/iov_iter.c:156 [inline]\nBUG: KMSAN: kernel-infoleak in _copy_to_iter+0x69d/0x25c0 lib/iov_iter.c:670\n instrument_copy_to_user include/linux/instrumented.h:121 [inline]\n copyout lib/iov_iter.c:156 [inline]\n _copy_to_iter+0x69d/0x25c0 lib/iov_iter.c:670\n copy_to_iter include/linux/uio.h:155 [inline]\n simple_copy_to_iter+0xf3/0x140 net/core/datagram.c:519\n __skb_datagram_iter+0x2cb/0x1280 net/core/datagram.c:425\n skb_copy_datagram_iter+0xdc/0x270 net/core/datagram.c:533\n skb_copy_datagram_msg include/linux/skbuff.h:3657 [inline]\n netlink_recvmsg+0x660/0x1c60 net/netlink/af_netlink.c:1974\n sock_recvmsg_nosec net/socket.c:944 [inline]\n sock_recvmsg net/socket.c:962 [inline]\n sock_read_iter+0x5a9/0x630 net/socket.c:1035\n call_read_iter include/linux/fs.h:2156 [inline]\n new_sync_read fs/read_write.c:400 [inline]\n vfs_read+0x1631/0x1980 fs/read_write.c:481\n ksys_read+0x28c/0x520 fs/read_write.c:619\n __do_sys_read fs/read_write.c:629 [inline]\n __se_sys_read fs/read_write.c:627 [inline]\n __x64_sys_read+0xdb/0x120 fs/read_write.c:627\n do_syscall_x64 arch/x86/entry/common.c:51 [inline]\n do_syscall_64+0x54/0xd0 arch/x86/entry/common.c:82\n entry_SYSCALL_64_after_hwframe+0x44/0xae\n\nUninit was created at:\n slab_post_alloc_hook mm/slab.h:524 [inline]\n slab_alloc_node mm/slub.c:3251 [inline]\n __kmalloc_node_track_caller+0xe0c/0x1510 mm/slub.c:4974\n kmalloc_reserve net/core/skbuff.c:354 [inline]\n __alloc_skb+0x545/0xf90 net/core/skbuff.c:426\n alloc_skb include/linux/skbuff.h:1126 [inline]\n netlink_dump+0x3d5/0x16a0 net/netlink/af_netlink.c:2245\n __netlink_dump_start+0xd1c/0xee0 net/netlink/af_netlink.c:2370\n netlink_dump_start include/linux/netlink.h:254 [inline]\n inet_diag_handler_cmd+0x2e7/0x400 net/ipv4/inet_diag.c:1343\n sock_diag_rcv_msg+0x24a/0x620\n netlink_rcv_skb+0x447/0x800 net/netlink/af_netlink.c:2491\n sock_diag_rcv+0x63/0x80 net/core/sock_diag.c:276\n netlink_unicast_kernel net/netlink/af_netlink.c:1319 [inline]\n netlink_unicast+0x1095/0x1360 net/netlink/af_netlink.c:1345\n netlink_sendmsg+0x16f3/0x1870 net/netlink/af_netlink.c:1916\n sock_sendmsg_nosec net/socket.c:704 [inline]\n sock_sendmsg net/socket.c:724 [inline]\n sock_write_iter+0x594/0x690 net/socket.c:1057\n do_iter_readv_writev+0xa7f/0xc70\n do_iter_write+0x52c/0x1500 fs/read_write.c:851\n vfs_writev fs/read_write.c:924 [inline]\n do_writev+0x63f/0xe30 fs/read_write.c:967\n __do_sys_writev fs/read_write.c:1040 [inline]\n __se_sys_writev fs/read_write.c:1037 [inline]\n __x64_sys_writev+0xe5/0x120 fs/read_write.c:1037\n do_syscall_x64 arch/x86/entry/common.c:51 [inline]\n do_syscall_64+0x54/0xd0 arch/x86/entry/common.c:82\n entry_SYSCALL_64_after_hwframe+0x44/0xae\n\nBytes 68-71 of 312 are uninitialized\nMemory access of size 312 starts at ffff88812ab54000\nData copied to user address 0000000020001440\n\nCPU: 1 PID: 6365 Comm: syz-executor801 Not tainted 5.16.0-rc3-syzkaller #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: inet_diag: corrige la fuga de informaci\u00f3n del kernel para sockets UDP KMSAN inform\u00f3 una fuga de informaci\u00f3n del kernel [1], que puede ser explotada por usuarios sin privilegios. Despu\u00e9s del an\u00e1lisis result\u00f3 que UDP no estaba inicializando r->idiag_expires. Otros usuarios de inet_sk_diag_fill() podr\u00edan cometer el mismo error en el futuro, as\u00ed que solucione este problema en inet_sk_diag_fill(). [1] ERROR: KMSAN: kernel-infoleak en instrument_copy_to_user include/linux/instrumented.h:121 [en l\u00ednea] ERROR: KMSAN: kernel-infoleak en copia lib/iov_iter.c:156 [en l\u00ednea] ERROR: KMSAN: kernel-infoleak en _copy_to_iter+0x69d/0x25c0 lib/iov_iter.c:670 instrument_copy_to_user include/linux/instrumented.h:121 [en l\u00ednea] copia lib/iov_iter.c:156 [en l\u00ednea] _copy_to_iter+0x69d/0x25c0 lib/iov_iter.c:670 copy_to_iter include/linux/uio.h:155 [en l\u00ednea] simple_copy_to_iter+0xf3/0x140 net/core/datagram.c:519 __skb_datagram_iter+0x2cb/0x1280 net/core/datagram.c:425 skb_copy_datagram_iter+0xdc/0x270 net/core/datagram .c:533 skb_copy_datagram_msg include/linux/skbuff.h:3657 [en l\u00ednea] netlink_recvmsg+0x660/0x1c60 net/netlink/af_netlink.c:1974 sock_recvmsg_nosec net/socket.c:944 [en l\u00ednea] sock_recvmsg net/socket.c:962 [en l\u00ednea] sock_read_iter+0x5a9/0x630 net/socket.c:1035 call_read_iter include/linux/fs.h:2156 [en l\u00ednea] new_sync_read fs/read_write.c:400 [en l\u00ednea] vfs_read+0x1631/0x1980 fs/read_write.c: 481 ksys_read+0x28c/0x520 fs/read_write.c:619 __do_sys_read fs/read_write.c:629 [en l\u00ednea] __se_sys_read fs/read_write.c:627 [en l\u00ednea] __x64_sys_read+0xdb/0x120 fs/read_write.c:627 _arco x64/ x86/entry/common.c:51 [en l\u00ednea] do_syscall_64+0x54/0xd0 arch/x86/entry/common.c:82 Entry_SYSCALL_64_after_hwframe+0x44/0xae Uninit se cre\u00f3 en: slab_post_alloc_hook mm/slab.h:524 [en l\u00ednea] slab_alloc_node mm/slub.c:3251 [en l\u00ednea] __kmalloc_node_track_caller+0xe0c/0x1510 mm/slub.c:4974 kmalloc_reserve net/core/skbuff.c:354 [en l\u00ednea] __alloc_skb+0x545/0xf90 net/core/skbuff.c:426 alloc_skb include/linux/skbuff.h:1126 [en l\u00ednea] netlink_dump+0x3d5/0x16a0 net/netlink/af_netlink.c:2245 __netlink_dump_start+0xd1c/0xee0 net/netlink/af_netlink.c:2370 netlink_dump_start include/linux/netlink.h:254 [en l\u00ednea] inet_diag_handler_cmd+0x2e7/0x400 net/ipv4/inet_diag.c:1343 sock_diag_rcv_msg+0x24a/0x620 netlink_rcv_skb+0x447/0x800 net/netlink/af_netlink.c:2491 sock_diag_rcv+0x63/0x80 net/core/sock_diag.c:276 netlink_unicast_kernel net/netlink/af_netlink.c: 1319 [en l\u00ednea] netlink_unicast+0x1095/0x1360 netLink/af_netlink.c: 1345 netlink_sendmsg+0x16f3/0x1870 net/netlink/af_etlink.c: 1916 sockm. C: 704 [ en l\u00ednea] sock_sendmsg net/socket.c:724 [en l\u00ednea] sock_write_iter+0x594/0x690 net/socket.c:1057 do_iter_readv_writev+0xa7f/0xc70 do_iter_write+0x52c/0x1500 fs/read_write.c:851 vfs_writev fs/read_write.c:9 24 [en l\u00ednea] do_writev+0x63f/0xe30 fs/read_write.c:967 __do_sys_writev fs/read_write.c:1040 [en l\u00ednea] __se_sys_writev fs/read_write.c:1037 [en l\u00ednea] __x64_sys_writev+0xe5/0x120 fs/read_write.c:1037 _syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x54/0xd0 arch/x86/entry/common.c:82 Entry_SYSCALL_64_after_hwframe+0x44/0xae Los bytes 68-71 de 312 no est\u00e1n inicializados El acceso a la memoria de tama\u00f1o 312 comienza en ffff88812ab54000 Datos copiados a la direcci\u00f3n de usuario 0000000020001440 CPU: 1 PID: 6365 Comm: syz-executor801 Not tainted 5.16.0-rc3-syzkaller #0 Nombre de hardware: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011" } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-475xx/CVE-2021-47598.json b/CVE-2021/CVE-2021-475xx/CVE-2021-47598.json index b39b5b963de..0f422463229 100644 --- a/CVE-2021/CVE-2021-475xx/CVE-2021-47598.json +++ b/CVE-2021/CVE-2021-475xx/CVE-2021-47598.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47598", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:54.383", - "lastModified": "2024-06-19T15:15:54.383", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nsch_cake: do not call cake_destroy() from cake_init()\n\nqdiscs are not supposed to call their own destroy() method\nfrom init(), because core stack already does that.\n\nsyzbot was able to trigger use after free:\n\nDEBUG_LOCKS_WARN_ON(lock->magic != lock)\nWARNING: CPU: 0 PID: 21902 at kernel/locking/mutex.c:586 __mutex_lock_common kernel/locking/mutex.c:586 [inline]\nWARNING: CPU: 0 PID: 21902 at kernel/locking/mutex.c:586 __mutex_lock+0x9ec/0x12f0 kernel/locking/mutex.c:740\nModules linked in:\nCPU: 0 PID: 21902 Comm: syz-executor189 Not tainted 5.16.0-rc4-syzkaller #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011\nRIP: 0010:__mutex_lock_common kernel/locking/mutex.c:586 [inline]\nRIP: 0010:__mutex_lock+0x9ec/0x12f0 kernel/locking/mutex.c:740\nCode: 08 84 d2 0f 85 19 08 00 00 8b 05 97 38 4b 04 85 c0 0f 85 27 f7 ff ff 48 c7 c6 20 00 ac 89 48 c7 c7 a0 fe ab 89 e8 bf 76 ba ff <0f> 0b e9 0d f7 ff ff 48 8b 44 24 40 48 8d b8 c8 08 00 00 48 89 f8\nRSP: 0018:ffffc9000627f290 EFLAGS: 00010282\nRAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000\nRDX: ffff88802315d700 RSI: ffffffff815f1db8 RDI: fffff52000c4fe44\nRBP: ffff88818f28e000 R08: 0000000000000000 R09: 0000000000000000\nR10: ffffffff815ebb5e R11: 0000000000000000 R12: 0000000000000000\nR13: dffffc0000000000 R14: ffffc9000627f458 R15: 0000000093c30000\nFS: 0000555556abc400(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007fda689c3303 CR3: 000000001cfbb000 CR4: 0000000000350ef0\nCall Trace:\n \n tcf_chain0_head_change_cb_del+0x2e/0x3d0 net/sched/cls_api.c:810\n tcf_block_put_ext net/sched/cls_api.c:1381 [inline]\n tcf_block_put_ext net/sched/cls_api.c:1376 [inline]\n tcf_block_put+0xbc/0x130 net/sched/cls_api.c:1394\n cake_destroy+0x3f/0x80 net/sched/sch_cake.c:2695\n qdisc_create.constprop.0+0x9da/0x10f0 net/sched/sch_api.c:1293\n tc_modify_qdisc+0x4c5/0x1980 net/sched/sch_api.c:1660\n rtnetlink_rcv_msg+0x413/0xb80 net/core/rtnetlink.c:5571\n netlink_rcv_skb+0x153/0x420 net/netlink/af_netlink.c:2496\n netlink_unicast_kernel net/netlink/af_netlink.c:1319 [inline]\n netlink_unicast+0x533/0x7d0 net/netlink/af_netlink.c:1345\n netlink_sendmsg+0x904/0xdf0 net/netlink/af_netlink.c:1921\n sock_sendmsg_nosec net/socket.c:704 [inline]\n sock_sendmsg+0xcf/0x120 net/socket.c:724\n ____sys_sendmsg+0x6e8/0x810 net/socket.c:2409\n ___sys_sendmsg+0xf3/0x170 net/socket.c:2463\n __sys_sendmsg+0xe5/0x1b0 net/socket.c:2492\n do_syscall_x64 arch/x86/entry/common.c:50 [inline]\n do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80\n entry_SYSCALL_64_after_hwframe+0x44/0xae\nRIP: 0033:0x7f1bb06badb9\nCode: Unable to access opcode bytes at RIP 0x7f1bb06bad8f.\nRSP: 002b:00007fff3012a658 EFLAGS: 00000246 ORIG_RAX: 000000000000002e\nRAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f1bb06badb9\nRDX: 0000000000000000 RSI: 00000000200007c0 RDI: 0000000000000003\nRBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000003\nR10: 0000000000000003 R11: 0000000000000246 R12: 00007fff3012a688\nR13: 00007fff3012a6a0 R14: 00007fff3012a6e0 R15: 00000000000013c2\n " + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: sch_cake: no llamar a cake_destroy() desde cake_init() Se supone que las qdiscs no deben llamar a su propio m\u00e9todo destroy() desde init(), porque la pila central ya lo hace. syzbot pudo activar el use-after-free: DEBUG_LOCKS_WARN_ON(lock->magic != lock) ADVERTENCIA: CPU: 0 PID: 21902 en kernel/locking/mutex.c:586 __mutex_lock_common kernel/locking/mutex.c:586 [en l\u00ednea] ADVERTENCIA: CPU: 0 PID: 21902 en kernel/locking/mutex.c:586 __mutex_lock+0x9ec/0x12f0 kernel/locking/mutex.c:740 M\u00f3dulos vinculados en: CPU: 0 PID: 21902 Comm: syz-executor189 No contaminado 5.16 .0-rc4-syzkaller #0 Nombre del hardware: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:__mutex_lock_common kernel/locking/mutex.c:586 [en l\u00ednea] RIP: 0010:__mutex_lock+ 0x9ec/0x12f0 kernel/locking/mutex.c:740 C\u00f3digo: 08 84 d2 0f 85 19 08 00 00 8b 05 97 38 4b 04 85 c0 0f 85 27 f7 ff ff 48 c7 c6 20 00 ac 89 48 c7 c7 a0 fe ab 89 e8 bf 76 ba ff <0f> 0b e9 0d f7 ff ff 48 8b 44 24 40 48 8d b8 c8 08 00 00 48 89 f8 RSP: 0018:ffffc9000627f290 EFLAGS: 00010282 RAX: 0000000 RBX: 0000000000000000 RCX: 0000000000000000 RDX: ffff88802315d700 RSI: ffffffff815f1db8 RDI: fffff52000c4fe44 RBP: ffff88818f28e000 R08: 0000000000000000 R09: 0000000000000000 R10: ffffffff815ebb5e R11: 00000 R12: 0000000000000000 R13: dffffc0000000000 R14: ffffc9000627f458 R15: 0000000093c30000 FS: 000055556abc400(0000) GS:ffff8880b9c0000 0(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fda689c3303 CR3: 000000001cfbb000 CR4: 0000000000350ef0 Seguimiento de llamadas: tcf_chain0_head_change_cb_del+0x2e/0 x3d0 net/sched/cls_api.c:810 tcf_block_put_ext net/sched/cls_api.c:1381 [ en l\u00ednea] tcf_block_put_ext net/sched/cls_api.c:1376 [en l\u00ednea] tcf_block_put+0xbc/0x130 net/sched/cls_api.c:1394 cake_destroy+0x3f/0x80 net/sched/sch_cake.c:2695 qdisc_create.constprop.0+0x9da /0x10f0 net/sched/sch_api.c:1293 tc_modify_qdisc+0x4c5/0x1980 net/sched/sch_api.c:1660 rtnetlink_rcv_msg+0x413/0xb80 net/core/rtnetlink.c:5571 netlink_rcv_skb+0x153/0x420 net/netlink/ af_netlink. c:2496 netlink_unicast_kernel net/netlink/af_netlink.c:1319 [en l\u00ednea] netlink_unicast+0x533/0x7d0 net/netlink/af_netlink.c:1345 netlink_sendmsg+0x904/0xdf0 net/netlink/af_netlink.c:1921 sock_sendmsg_nosec net/socket.c :704 [en l\u00ednea] sock_sendmsg+0xcf/0x120 net/socket.c:724 ____sys_sendmsg+0x6e8/0x810 net/socket.c:2409 ___sys_sendmsg+0xf3/0x170 net/socket.c:2463 __sys_sendmsg+0xe5/0x1b 0 red/toma. c:2492 do_syscall_x64 arch/x86/entry/common.c:50 [en l\u00ednea] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 Entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f1bb06badb9 C\u00f3digo: No se puede acceder al c\u00f3digo de operaci\u00f3n bytes en RIP 0x7f1bb06bad8f. RSP: 002b:00007fff3012a658 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 00000000000000003 RCX: 00007f1bb06badb9 RDX: 000000000 RSI: 00000000200007c0 RDI: 0000000000000003 RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000003 R10: 00000003 R11: 0000000000000246 R12: 00007fff3012a688 R13: 00007fff3012a6a0 R14: 00007fff3012a6e0 R15: 00000000000013c2 " } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-475xx/CVE-2021-47599.json b/CVE-2021/CVE-2021-475xx/CVE-2021-47599.json index 6d5418a52d3..4c929338c90 100644 --- a/CVE-2021/CVE-2021-475xx/CVE-2021-47599.json +++ b/CVE-2021/CVE-2021-475xx/CVE-2021-47599.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47599", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:54.483", - "lastModified": "2024-06-19T15:15:54.483", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: use latest_dev in btrfs_show_devname\n\nThe test case btrfs/238 reports the warning below:\n\n WARNING: CPU: 3 PID: 481 at fs/btrfs/super.c:2509 btrfs_show_devname+0x104/0x1e8 [btrfs]\n CPU: 2 PID: 1 Comm: systemd Tainted: G W O 5.14.0-rc1-custom #72\n Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2015\n Call trace:\n btrfs_show_devname+0x108/0x1b4 [btrfs]\n show_mountinfo+0x234/0x2c4\n m_show+0x28/0x34\n seq_read_iter+0x12c/0x3c4\n vfs_read+0x29c/0x2c8\n ksys_read+0x80/0xec\n __arm64_sys_read+0x28/0x34\n invoke_syscall+0x50/0xf8\n do_el0_svc+0x88/0x138\n el0_svc+0x2c/0x8c\n el0t_64_sync_handler+0x84/0xe4\n el0t_64_sync+0x198/0x19c\n\nReason:\nWhile btrfs_prepare_sprout() moves the fs_devices::devices into\nfs_devices::seed_list, the btrfs_show_devname() searches for the devices\nand found none, leading to the warning as in above.\n\nFix:\nlatest_dev is updated according to the changes to the device list.\nThat means we could use the latest_dev->name to show the device name in\n/proc/self/mounts, the pointer will be always valid as it's assigned\nbefore the device is deleted from the list in remove or replace.\nThe RCU protection is sufficient as the device structure is freed after\nsynchronization." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: btrfs: utilice Latest_dev en btrfs_show_devname El caso de prueba btrfs/238 informa la siguiente advertencia: ADVERTENCIA: CPU: 3 PID: 481 en fs/btrfs/super.c:2509 btrfs_show_devname+0x104 /0x1e8 [btrfs] CPU: 2 PID: 1 Comunicaci\u00f3n: systemd Contaminado: GWO 5.14.0-rc1-custom #72 Nombre de hardware: QEMU M\u00e1quina virtual QEMU, BIOS 0.0.0 06/02/2015 Rastreo de llamadas: btrfs_show_devname+0x108/ 0x1b4 [btrfs] show_mountinfo+0x234/0x2c4 m_show+0x28/0x34 seq_read_iter+0x12c/0x3c4 vfs_read+0x29c/0x2c8 ksys_read+0x80/0xec __arm64_sys_read+0x28/0x34 x50/0xf8 do_el0_svc+0x88/0x138 el0_svc+0x2c/0x8c el0t_64_sync_handler +0x84/0xe4 el0t_64_sync+0x198/0x19c Motivo: mientras btrfs_prepare_sprout() mueve fs_devices::devices a fs_devices::seed_list, btrfs_show_devname() busca los dispositivos y no encuentra ninguno, lo que genera la advertencia como se muestra arriba. Soluci\u00f3n: last_dev se actualiza seg\u00fan los cambios en la lista de dispositivos. Eso significa que podr\u00edamos usar el \u00faltimo_dev->name para mostrar el nombre del dispositivo en /proc/self/mounts, el puntero siempre ser\u00e1 v\u00e1lido tal como est\u00e1 asignado antes de que el dispositivo se elimine de la lista en eliminar o reemplazar. La protecci\u00f3n de la RCU es suficiente, ya que la estructura del dispositivo se libera despu\u00e9s de la sincronizaci\u00f3n." } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-476xx/CVE-2021-47600.json b/CVE-2021/CVE-2021-476xx/CVE-2021-47600.json index b22857c9be3..06fbff5812b 100644 --- a/CVE-2021/CVE-2021-476xx/CVE-2021-47600.json +++ b/CVE-2021/CVE-2021-476xx/CVE-2021-47600.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47600", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:54.567", - "lastModified": "2024-06-19T15:15:54.567", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndm btree remove: fix use after free in rebalance_children()\n\nMove dm_tm_unlock() after dm_tm_dec()." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: dm btree remove: corrige el use after free en rebalance_children() Mueve dm_tm_unlock() despu\u00e9s de dm_tm_dec()." } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-476xx/CVE-2021-47601.json b/CVE-2021/CVE-2021-476xx/CVE-2021-47601.json index 0d9af35bae6..29ee8bfff58 100644 --- a/CVE-2021/CVE-2021-476xx/CVE-2021-47601.json +++ b/CVE-2021/CVE-2021-476xx/CVE-2021-47601.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47601", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:54.670", - "lastModified": "2024-06-19T15:15:54.670", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ntee: amdtee: fix an IS_ERR() vs NULL bug\n\nThe __get_free_pages() function does not return error pointers it returns\nNULL so fix this condition to avoid a NULL dereference." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: tee: amdtee: corrige un error IS_ERR() vs NULL La funci\u00f3n __get_free_pages() no devuelve punteros de error, devuelve NULL, as\u00ed que corrija esta condici\u00f3n para evitar una desreferencia a NULL." } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-476xx/CVE-2021-47602.json b/CVE-2021/CVE-2021-476xx/CVE-2021-47602.json index 815dc66548e..8c811feeeb2 100644 --- a/CVE-2021/CVE-2021-476xx/CVE-2021-47602.json +++ b/CVE-2021/CVE-2021-476xx/CVE-2021-47602.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47602", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:54.760", - "lastModified": "2024-06-19T15:15:54.760", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmac80211: track only QoS data frames for admission control\n\nFor admission control, obviously all of that only works for\nQoS data frames, otherwise we cannot even access the QoS\nfield in the header.\n\nSyzbot reported (see below) an uninitialized value here due\nto a status of a non-QoS nullfunc packet, which isn't even\nlong enough to contain the QoS header.\n\nFix this to only do anything for QoS data packets." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: mac80211: rastrea solo frameworks de datos QoS para control de admisi\u00f3n. Para el control de admisi\u00f3n, obviamente todo eso solo funciona para frameworks de datos QoS; de lo contrario, ni siquiera podemos acceder al campo QoS en el encabezado. Syzbot inform\u00f3 (ver m\u00e1s abajo) un valor no inicializado aqu\u00ed debido al estado de un paquete nullfunc sin QoS, que ni siquiera es lo suficientemente largo para contener el encabezado de QoS. Solucione este problema para hacer algo \u00fanicamente con los paquetes de datos QoS." } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-476xx/CVE-2021-47603.json b/CVE-2021/CVE-2021-476xx/CVE-2021-47603.json index a15a302bb48..c2a5325e49a 100644 --- a/CVE-2021/CVE-2021-476xx/CVE-2021-47603.json +++ b/CVE-2021/CVE-2021-476xx/CVE-2021-47603.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47603", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:54.863", - "lastModified": "2024-06-19T15:15:54.863", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\naudit: improve robustness of the audit queue handling\n\nIf the audit daemon were ever to get stuck in a stopped state the\nkernel's kauditd_thread() could get blocked attempting to send audit\nrecords to the userspace audit daemon. With the kernel thread\nblocked it is possible that the audit queue could grow unbounded as\ncertain audit record generating events must be exempt from the queue\nlimits else the system enter a deadlock state.\n\nThis patch resolves this problem by lowering the kernel thread's\nsocket sending timeout from MAX_SCHEDULE_TIMEOUT to HZ/10 and tweaks\nthe kauditd_send_queue() function to better manage the various audit\nqueues when connection problems occur between the kernel and the\naudit daemon. With this patch, the backlog may temporarily grow\nbeyond the defined limits when the audit daemon is stopped and the\nsystem is under heavy audit pressure, but kauditd_thread() will\ncontinue to make progress and drain the queues as it would for other\nconnection problems. For example, with the audit daemon put into a\nstopped state and the system configured to audit every syscall it\nwas still possible to shutdown the system without a kernel panic,\ndeadlock, etc.; granted, the system was slow to shutdown but that is\nto be expected given the extreme pressure of recording every syscall.\n\nThe timeout value of HZ/10 was chosen primarily through\nexperimentation and this developer's \"gut feeling\". There is likely\nno one perfect value, but as this scenario is limited in scope (root\nprivileges would be needed to send SIGSTOP to the audit daemon), it\nis likely not worth exposing this as a tunable at present. This can\nalways be done at a later date if it proves necessary." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: auditor\u00eda: mejora la solidez del manejo de la cola de auditor\u00eda. Si el daemon de auditor\u00eda alguna vez se atascara en un estado detenido, kauditd_thread() del kernel podr\u00eda bloquearse al intentar enviar registros de auditor\u00eda al espacio de usuario. daemon de auditor\u00eda. Con el subproceso del n\u00facleo bloqueado, es posible que la cola de auditor\u00eda crezca sin l\u00edmites, ya que ciertos eventos que generan registros de auditor\u00eda deben estar exentos de los l\u00edmites de la cola, de lo contrario, el sistema entrar\u00e1 en un estado de bloqueo. Este parche resuelve este problema reduciendo el tiempo de espera de env\u00edo del socket del subproceso del n\u00facleo de MAX_SCHEDULE_TIMEOUT a HZ/10 y modifica la funci\u00f3n kauditd_send_queue() para gestionar mejor las distintas colas de auditor\u00eda cuando se producen problemas de conexi\u00f3n entre el n\u00facleo y el daemon de auditor\u00eda. Con este parche, el trabajo pendiente puede crecer temporalmente m\u00e1s all\u00e1 de los l\u00edmites definidos cuando se detiene el daemon de auditor\u00eda y el sistema est\u00e1 bajo una fuerte presi\u00f3n de auditor\u00eda, pero kauditd_thread() continuar\u00e1 progresando y drenando las colas como lo har\u00eda con otros problemas de conexi\u00f3n. Por ejemplo, con el daemon de auditor\u00eda en estado detenido y el sistema configurado para auditar cada llamada al sistema, a\u00fan era posible apagar el sistema sin p\u00e1nico en el kernel, interbloqueo, etc.; Por supuesto, el sistema tard\u00f3 en cerrarse, pero eso es de esperarse dada la presi\u00f3n extrema de registrar cada llamada al sistema. El valor de tiempo de espera de HZ/10 se eligi\u00f3 principalmente a trav\u00e9s de la experimentaci\u00f3n y el \"instinto\" de este desarrollador. Probablemente no exista un valor perfecto, pero como este escenario tiene un alcance limitado (se necesitar\u00edan privilegios de root para enviar SIGSTOP al daemon de auditor\u00eda), probablemente no valga la pena exponerlo como un ajuste ajustable en este momento. Esto siempre se puede hacer en una fecha posterior si resulta necesario." } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-476xx/CVE-2021-47604.json b/CVE-2021/CVE-2021-476xx/CVE-2021-47604.json index 3f3af3c289b..5a853e7845f 100644 --- a/CVE-2021/CVE-2021-476xx/CVE-2021-47604.json +++ b/CVE-2021/CVE-2021-476xx/CVE-2021-47604.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47604", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:54.973", - "lastModified": "2024-06-19T15:15:54.973", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nvduse: check that offset is within bounds in get_config()\n\nThis condition checks \"len\" but it does not check \"offset\" and that\ncould result in an out of bounds read if \"offset > dev->config_size\".\nThe problem is that since both variables are unsigned the\n\"dev->config_size - offset\" subtraction would result in a very high\nunsigned value.\n\nI think these checks might not be necessary because \"len\" and \"offset\"\nare supposed to already have been validated using the\nvhost_vdpa_config_validate() function. But I do not know the code\nperfectly, and I like to be safe." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: vduse: verifique que el desplazamiento est\u00e9 dentro de los l\u00edmites en get_config() Esta condici\u00f3n verifica \"len\" pero no verifica \"desplazamiento\" y eso podr\u00eda resultar en una lectura fuera de los l\u00edmites si \" desplazamiento > dev->config_size\". El problema es que, dado que ambas variables no est\u00e1n firmadas, la resta \"dev->config_size - offset\" dar\u00eda como resultado un valor sin firmar muy alto. Creo que estas comprobaciones podr\u00edan no ser necesarias porque se supone que \"len\" y \"offset\" ya se han validado mediante la funci\u00f3n vhost_vdpa_config_validate(). Pero no conozco el c\u00f3digo a la perfecci\u00f3n y me gusta estar seguro." } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-476xx/CVE-2021-47605.json b/CVE-2021/CVE-2021-476xx/CVE-2021-47605.json index f9c75f7f8dd..65360c6a1ed 100644 --- a/CVE-2021/CVE-2021-476xx/CVE-2021-47605.json +++ b/CVE-2021/CVE-2021-476xx/CVE-2021-47605.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47605", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:55.067", - "lastModified": "2024-06-19T15:15:55.067", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nvduse: fix memory corruption in vduse_dev_ioctl()\n\nThe \"config.offset\" comes from the user. There needs to a check to\nprevent it being out of bounds. The \"config.offset\" and\n\"dev->config_size\" variables are both type u32. So if the offset if\nout of bounds then the \"dev->config_size - config.offset\" subtraction\nresults in a very high u32 value. The out of bounds offset can result\nin memory corruption." + }, + { + "lang": "es", + "value": "En el kernel de Linux se ha resuelto la siguiente vulnerabilidad: vduse: corrige corrupci\u00f3n de memoria en vduse_dev_ioctl() El \"config.offset\" proviene del usuario. Es necesario realizar un control para evitar que est\u00e9 fuera de los l\u00edmites. Las variables \"config.offset\" y \"dev->config_size\" son ambas del tipo u32. Entonces, si el desplazamiento est\u00e1 fuera de los l\u00edmites, entonces la resta \"dev->config_size - config.offset\" da como resultado un valor u32 muy alto. El desplazamiento fuera de los l\u00edmites puede provocar da\u00f1os en la memoria." } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-476xx/CVE-2021-47606.json b/CVE-2021/CVE-2021-476xx/CVE-2021-47606.json index f48edeb1fa8..89111e4ac24 100644 --- a/CVE-2021/CVE-2021-476xx/CVE-2021-47606.json +++ b/CVE-2021/CVE-2021-476xx/CVE-2021-47606.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47606", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:55.153", - "lastModified": "2024-06-19T15:15:55.153", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: netlink: af_netlink: Prevent empty skb by adding a check on len.\n\nAdding a check on len parameter to avoid empty skb. This prevents a\ndivision error in netem_enqueue function which is caused when skb->len=0\nand skb->data_len=0 in the randomized corruption step as shown below.\n\nskb->data[prandom_u32() % skb_headlen(skb)] ^= 1<<(prandom_u32() % 8);\n\nCrash Report:\n[ 343.170349] netdevsim netdevsim0 netdevsim3: set [1, 0] type 2 family\n0 port 6081 - 0\n[ 343.216110] netem: version 1.3\n[ 343.235841] divide error: 0000 [#1] PREEMPT SMP KASAN NOPTI\n[ 343.236680] CPU: 3 PID: 4288 Comm: reproducer Not tainted 5.16.0-rc1+\n[ 343.237569] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),\nBIOS 1.11.0-2.el7 04/01/2014\n[ 343.238707] RIP: 0010:netem_enqueue+0x1590/0x33c0 [sch_netem]\n[ 343.239499] Code: 89 85 58 ff ff ff e8 5f 5d e9 d3 48 8b b5 48 ff ff\nff 8b 8d 50 ff ff ff 8b 85 58 ff ff ff 48 8b bd 70 ff ff ff 31 d2 2b 4f\n74 f1 48 b8 00 00 00 00 00 fc ff df 49 01 d5 4c 89 e9 48 c1 e9 03\n[ 343.241883] RSP: 0018:ffff88800bcd7368 EFLAGS: 00010246\n[ 343.242589] RAX: 00000000ba7c0a9c RBX: 0000000000000001 RCX:\n0000000000000000\n[ 343.243542] RDX: 0000000000000000 RSI: ffff88800f8edb10 RDI:\nffff88800f8eda40\n[ 343.244474] RBP: ffff88800bcd7458 R08: 0000000000000000 R09:\nffffffff94fb8445\n[ 343.245403] R10: ffffffff94fb8336 R11: ffffffff94fb8445 R12:\n0000000000000000\n[ 343.246355] R13: ffff88800a5a7000 R14: ffff88800a5b5800 R15:\n0000000000000020\n[ 343.247291] FS: 00007fdde2bd7700(0000) GS:ffff888109780000(0000)\nknlGS:0000000000000000\n[ 343.248350] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 343.249120] CR2: 00000000200000c0 CR3: 000000000ef4c000 CR4:\n00000000000006e0\n[ 343.250076] Call Trace:\n[ 343.250423] \n[ 343.250713] ? memcpy+0x4d/0x60\n[ 343.251162] ? netem_init+0xa0/0xa0 [sch_netem]\n[ 343.251795] ? __sanitizer_cov_trace_pc+0x21/0x60\n[ 343.252443] netem_enqueue+0xe28/0x33c0 [sch_netem]\n[ 343.253102] ? stack_trace_save+0x87/0xb0\n[ 343.253655] ? filter_irq_stacks+0xb0/0xb0\n[ 343.254220] ? netem_init+0xa0/0xa0 [sch_netem]\n[ 343.254837] ? __kasan_check_write+0x14/0x20\n[ 343.255418] ? _raw_spin_lock+0x88/0xd6\n[ 343.255953] dev_qdisc_enqueue+0x50/0x180\n[ 343.256508] __dev_queue_xmit+0x1a7e/0x3090\n[ 343.257083] ? netdev_core_pick_tx+0x300/0x300\n[ 343.257690] ? check_kcov_mode+0x10/0x40\n[ 343.258219] ? _raw_spin_unlock_irqrestore+0x29/0x40\n[ 343.258899] ? __kasan_init_slab_obj+0x24/0x30\n[ 343.259529] ? setup_object.isra.71+0x23/0x90\n[ 343.260121] ? new_slab+0x26e/0x4b0\n[ 343.260609] ? kasan_poison+0x3a/0x50\n[ 343.261118] ? kasan_unpoison+0x28/0x50\n[ 343.261637] ? __kasan_slab_alloc+0x71/0x90\n[ 343.262214] ? memcpy+0x4d/0x60\n[ 343.262674] ? write_comp_data+0x2f/0x90\n[ 343.263209] ? __kasan_check_write+0x14/0x20\n[ 343.263802] ? __skb_clone+0x5d6/0x840\n[ 343.264329] ? __sanitizer_cov_trace_pc+0x21/0x60\n[ 343.264958] dev_queue_xmit+0x1c/0x20\n[ 343.265470] netlink_deliver_tap+0x652/0x9c0\n[ 343.266067] netlink_unicast+0x5a0/0x7f0\n[ 343.266608] ? netlink_attachskb+0x860/0x860\n[ 343.267183] ? __sanitizer_cov_trace_pc+0x21/0x60\n[ 343.267820] ? write_comp_data+0x2f/0x90\n[ 343.268367] netlink_sendmsg+0x922/0xe80\n[ 343.268899] ? netlink_unicast+0x7f0/0x7f0\n[ 343.269472] ? __sanitizer_cov_trace_pc+0x21/0x60\n[ 343.270099] ? write_comp_data+0x2f/0x90\n[ 343.270644] ? netlink_unicast+0x7f0/0x7f0\n[ 343.271210] sock_sendmsg+0x155/0x190\n[ 343.271721] ____sys_sendmsg+0x75f/0x8f0\n[ 343.272262] ? kernel_sendmsg+0x60/0x60\n[ 343.272788] ? write_comp_data+0x2f/0x90\n[ 343.273332] ? write_comp_data+0x2f/0x90\n[ 343.273869] ___sys_sendmsg+0x10f/0x190\n[ 343.274405] ? sendmsg_copy_msghdr+0x80/0x80\n[ 343.274984] ? slab_post_alloc_hook+0x70/0x230\n[ 343.275597] ? futex_wait_setup+0x240/0x240\n[ 343.276175] ? security_file_alloc+0x3e/0x170\n[ 343.276779] ? write_comp_d\n---truncated---" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: net: netlink: af_netlink: Evite el skb vac\u00edo agregando una marca en len. Agregar una verificaci\u00f3n en el par\u00e1metro len para evitar skb vac\u00edo. Esto evita un error de divisi\u00f3n en la funci\u00f3n netem_enqueue que se produce cuando skb->len=0 y skb->data_len=0 en el paso de corrupci\u00f3n aleatoria como se muestra a continuaci\u00f3n. skb->datos[prandom_u32() % skb_headlen(skb)] ^= 1<<(prandom_u32() % 8); Informe de fallo: [343.170349] netdevsim netdevsim0 netdevsim3: establecer [1, 0] tipo 2 familia 0 puerto 6081 - 0 [343.216110] netem: versi\u00f3n 1.3 [343.235841] error de divisi\u00f3n: 0000 [#1] PREEMPT SMP KASAN NOPTI [ 80] CPU : 3 PID: 4288 Comm: reproductor No contaminado 5.16.0-rc1+ [ 343.237569] Nombre del hardware: PC est\u00e1ndar QEMU (i440FX + PIIX, 1996), BIOS 1.11.0-2.el7 01/04/2014 [ 343.238707] RIP: 0010:netem_enqueue+0x1590/0x33c0 [sch_netem] [ 343.239499] C\u00f3digo: 89 85 58 ff ff ff e8 5f 5d e9 d3 48 8b b5 48 ff ff ff 8b 8d 50 ff ff 8b 85 58 ff ff 4 8 8b bd 70 y sigs. ff ff 31 d2 2b 4f 74 f1 48 b8 00 00 00 00 00 fc ff df 49 01 d5 4c 89 e9 48 c1 e9 03 [ 343.241883] RSP: 0018:ffff88800bcd7368 EFLAGS: 46 [343.242589] RAX: 00000000ba7c0a9c RBX: 0000000000000001 RCX: 0000000000000000 [ 343.243542] RDX: 0000000000000000 RSI: ffff88800f8edb10 RDI: ffff88800f8eda40 [ 343.244474] RBP: ff88800bcd7458 R08: 0000000000000000 R09: ffffffff94fb8445 [ 343.245403] R10: ffffffff94fb8336 R11: ffffffff94fb8445 R12: 0000000000000000 [ 343. 246355] R13: ffff88800a5a7000 R14: ffff88800a5b5800 R15 : 0000000000000020 [ 343.247291] FS: 00007fdde2bd7700(0000) GS:ffff888109780000(0000) knlGS:0000000000000000 [ 343.248350] CS: 0010 DS: 000 ES: 0000 CR0: 0000000080050033 [ 343.249120] CR2: 00000000200000c0 CR3: 000000000ef4c000 CR4: 00000000000006e0 [ 343.250076] Seguimiento de llamadas: [ 343.250423] [ 343.250713] ? memcpy+0x4d/0x60 [343.251162]? netem_init+0xa0/0xa0 [sch_netem] [ 343.251795] ? __sanitizer_cov_trace_pc+0x21/0x60 [ 343.252443] netem_enqueue+0xe28/0x33c0 [sch_netem] [ 343.253102] ? stack_trace_save+0x87/0xb0 [343.253655]? filter_irq_stacks+0xb0/0xb0 [343.254220]? netem_init+0xa0/0xa0 [sch_netem] [ 343.254837] ? __kasan_check_write+0x14/0x20 [343.255418]? _raw_spin_lock+0x88/0xd6 [ 343.255953] dev_qdisc_enqueue+0x50/0x180 [ 343.256508] __dev_queue_xmit+0x1a7e/0x3090 [ 343.257083] ? netdev_core_pick_tx+0x300/0x300 [343.257690]? check_kcov_mode+0x10/0x40 [343.258219]? _raw_spin_unlock_irqrestore+0x29/0x40 [343.258899]? __kasan_init_slab_obj+0x24/0x30 [343.259529] ? setup_object.isra.71+0x23/0x90 [343.260121]? nueva_losa+0x26e/0x4b0 [ 343.260609] ? kasan_poison+0x3a/0x50 [ 343.261118] ? kasan_unpoison+0x28/0x50 [343.261637]? __kasan_slab_alloc+0x71/0x90 [343.262214]? memcpy+0x4d/0x60 [343.262674]? write_comp_data+0x2f/0x90 [343.263209]? __kasan_check_write+0x14/0x20 [343.263802]? __skb_clone+0x5d6/0x840 [343.264329]? __sanitizer_cov_trace_pc+0x21/0x60 [ 343.264958] dev_queue_xmit+0x1c/0x20 [ 343.265470] netlink_deliver_tap+0x652/0x9c0 [ 343.266067] netlink_unicast+0x5a0/0x7f0 [ 343. 266608] ? netlink_attachskb+0x860/0x860 [343.267183]? __sanitizer_cov_trace_pc+0x21/0x60 [ 343.267820] ? write_comp_data+0x2f/0x90 [343.268367] netlink_sendmsg+0x922/0xe80 [343.268899]? netlink_unicast+0x7f0/0x7f0 [343.269472]? __sanitizer_cov_trace_pc+0x21/0x60 [343.270099] ? write_comp_data+0x2f/0x90 [343.270644]? netlink_unicast+0x7f0/0x7f0 [343.271210] sock_sendmsg+0x155/0x190 [343.271721] ____sys_sendmsg+0x75f/0x8f0 [343.272262] ? kernel_sendmsg+0x60/0x60 [343.272788]? write_comp_data+0x2f/0x90 [343.273332]? write_comp_data+0x2f/0x90 [ 343.273869] ___sys_sendmsg+0x10f/0x190 [ 343.274405] ? sendmsg_copy_msghdr+0x80/0x80 [343.274984]? slab_post_alloc_hook+0x70/0x230 [343.275597]? futex_wait_setup+0x240/0x240 [343.276175]? security_file_alloc+0x3e/0x170 [343.276779]? write_comp_d ---truncado---" } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-476xx/CVE-2021-47607.json b/CVE-2021/CVE-2021-476xx/CVE-2021-47607.json index 52a56508f54..e69da2ee736 100644 --- a/CVE-2021/CVE-2021-476xx/CVE-2021-47607.json +++ b/CVE-2021/CVE-2021-476xx/CVE-2021-47607.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47607", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:55.263", - "lastModified": "2024-06-19T15:15:55.263", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix kernel address leakage in atomic cmpxchg's r0 aux reg\n\nThe implementation of BPF_CMPXCHG on a high level has the following parameters:\n\n .-[old-val] .-[new-val]\n BPF_R0 = cmpxchg{32,64}(DST_REG + insn->off, BPF_R0, SRC_REG)\n `-[mem-loc] `-[old-val]\n\nGiven a BPF insn can only have two registers (dst, src), the R0 is fixed and\nused as an auxilliary register for input (old value) as well as output (returning\nold value from memory location). While the verifier performs a number of safety\nchecks, it misses to reject unprivileged programs where R0 contains a pointer as\nold value.\n\nThrough brute-forcing it takes about ~16sec on my machine to leak a kernel pointer\nwith BPF_CMPXCHG. The PoC is basically probing for kernel addresses by storing the\nguessed address into the map slot as a scalar, and using the map value pointer as\nR0 while SRC_REG has a canary value to detect a matching address.\n\nFix it by checking R0 for pointers, and reject if that's the case for unprivileged\nprograms." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: bpf: corrige la fuga de direcci\u00f3n del kernel en el registro auxiliar r0 de atomic cmpxchg. La implementaci\u00f3n de BPF_CMPXCHG en un nivel alto tiene los siguientes par\u00e1metros: .-[old-val] .-[new-val ] BPF_R0 = cmpxchg{32,64}(DST_REG + insn->off, BPF_R0, SRC_REG) `-[mem-loc] `-[old-val] Dado un BPF insn solo puede tener dos registros (dst, src), el R0 es fijo y se utiliza como registro auxiliar para la entrada (valor anterior), as\u00ed como para la salida (devolver el valor anterior desde la ubicaci\u00f3n de la memoria). Si bien el verificador realiza una serie de comprobaciones de seguridad, no rechaza los programas sin privilegios donde R0 contiene un puntero como valor antiguo. A trav\u00e9s de la fuerza bruta, en mi m\u00e1quina se necesitan aproximadamente 16 segundos para filtrar un puntero del kernel con BPF_CMPXCHG. B\u00e1sicamente, PoC busca direcciones del kernel almacenando la direcci\u00f3n adivinada en la ranura del mapa como un escalar y usando el puntero del valor del mapa como R0, mientras que SRC_REG tiene un valor canario para detectar una direcci\u00f3n coincidente. Solucionelo comprobando R0 en busca de punteros y rech\u00e1celo si ese es el caso de los programas sin privilegios." } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-476xx/CVE-2021-47608.json b/CVE-2021/CVE-2021-476xx/CVE-2021-47608.json index 45a93b22e61..d2b2a2743f6 100644 --- a/CVE-2021/CVE-2021-476xx/CVE-2021-47608.json +++ b/CVE-2021/CVE-2021-476xx/CVE-2021-47608.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47608", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:55.360", - "lastModified": "2024-06-19T15:15:55.360", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix kernel address leakage in atomic fetch\n\nThe change in commit 37086bfdc737 (\"bpf: Propagate stack bounds to registers\nin atomics w/ BPF_FETCH\") around check_mem_access() handling is buggy since\nthis would allow for unprivileged users to leak kernel pointers. For example,\nan atomic fetch/and with -1 on a stack destination which holds a spilled\npointer will migrate the spilled register type into a scalar, which can then\nbe exported out of the program (since scalar != pointer) by dumping it into\na map value.\n\nThe original implementation of XADD was preventing this situation by using\na double call to check_mem_access() one with BPF_READ and a subsequent one\nwith BPF_WRITE, in both cases passing -1 as a placeholder value instead of\nregister as per XADD semantics since it didn't contain a value fetch. The\nBPF_READ also included a check in check_stack_read_fixed_off() which rejects\nthe program if the stack slot is of __is_pointer_value() if dst_regno < 0.\nThe latter is to distinguish whether we're dealing with a regular stack spill/\nfill or some arithmetical operation which is disallowed on non-scalars, see\nalso 6e7e63cbb023 (\"bpf: Forbid XADD on spilled pointers for unprivileged\nusers\") for more context on check_mem_access() and its handling of placeholder\nvalue -1.\n\nOne minimally intrusive option to fix the leak is for the BPF_FETCH case to\ninitially check the BPF_READ case via check_mem_access() with -1 as register,\nfollowed by the actual load case with non-negative load_reg to propagate\nstack bounds to registers." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: bpf: corrige la fuga de la direcci\u00f3n del kernel en la recuperaci\u00f3n at\u00f3mica. El cambio en el commit 37086bfdc737 (\"bpf: propaga los l\u00edmites de la pila a los registros en at\u00f3micos con BPF_FETCH\") alrededor del manejo de check_mem_access() tiene errores ya que esto permitir\u00eda a usuarios sin privilegios filtrar punteros del kernel. Por ejemplo, una recuperaci\u00f3n at\u00f3mica/y con -1 en un destino de pila que contiene un puntero derramado migrar\u00e1 el tipo de registro derramado a un escalar, que luego se puede exportar fuera del programa (ya que escalar! = puntero) volc\u00e1ndolo en un valor de mapa. La implementaci\u00f3n original de XADD evitaba esta situaci\u00f3n mediante el uso de una llamada doble a check_mem_access(), una con BPF_READ y otra posterior con BPF_WRITE, en ambos casos pasando -1 como valor de marcador de posici\u00f3n en lugar de registrarse seg\u00fan la sem\u00e1ntica de XADD, ya que no lo hac\u00eda contener una recuperaci\u00f3n de valor. BPF_READ tambi\u00e9n incluy\u00f3 una verificaci\u00f3n en check_stack_read_fixed_off() que rechaza el programa si la ranura de la pila es de __is_pointer_value() si dst_regno < 0. Esto \u00faltimo es para distinguir si estamos tratando con un derrame/llenado de pila regular o alguna operaci\u00f3n aritm\u00e9tica que no est\u00e1 permitido en valores no escalares, consulte tambi\u00e9n 6e7e63cbb023 (\"bpf: Prohibir XADD en punteros dispersos para usuarios sin privilegios\") para obtener m\u00e1s contexto sobre check_mem_access() y su manejo del valor del marcador de posici\u00f3n -1. Una opci\u00f3n m\u00ednimamente intrusiva para solucionar la fuga es que el caso BPF_FETCH verifique inicialmente el caso BPF_READ mediante check_mem_access() con -1 como registro, seguido del caso de carga real con load_reg no negativo para propagar los l\u00edmites de la pila a los registros." } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-476xx/CVE-2021-47609.json b/CVE-2021/CVE-2021-476xx/CVE-2021-47609.json index cd217d10cb3..8a14673971e 100644 --- a/CVE-2021/CVE-2021-476xx/CVE-2021-47609.json +++ b/CVE-2021/CVE-2021-476xx/CVE-2021-47609.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47609", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:55.457", - "lastModified": "2024-06-19T15:15:55.457", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nfirmware: arm_scpi: Fix string overflow in SCPI genpd driver\n\nWithout the bound checks for scpi_pd->name, it could result in the buffer\noverflow when copying the SCPI device name from the corresponding device\ntree node as the name string is set at maximum size of 30.\n\nLet us fix it by using devm_kasprintf so that the string buffer is\nallocated dynamically." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: firmware: arm_scpi: corrige el desbordamiento de cadena en el controlador SCPI genpd. Sin las comprobaciones vinculadas para scpi_pd->name, podr\u00eda provocar un desbordamiento del b\u00fafer al copiar el nombre del dispositivo SCPI del dispositivo correspondiente. El nodo del \u00e1rbol como cadena de nombre se establece en un tama\u00f1o m\u00e1ximo de 30. Arreglemoslo usando devm_kasprintf para que el b\u00fafer de cadena se asigne din\u00e1micamente." } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-476xx/CVE-2021-47610.json b/CVE-2021/CVE-2021-476xx/CVE-2021-47610.json index 48a9e8e5fc3..898545be50f 100644 --- a/CVE-2021/CVE-2021-476xx/CVE-2021-47610.json +++ b/CVE-2021/CVE-2021-476xx/CVE-2021-47610.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47610", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:55.557", - "lastModified": "2024-06-19T15:15:55.557", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/msm: Fix null ptr access msm_ioctl_gem_submit()\n\nFix the below null pointer dereference in msm_ioctl_gem_submit():\n\n 26545.260705: Call trace:\n 26545.263223: kref_put+0x1c/0x60\n 26545.266452: msm_ioctl_gem_submit+0x254/0x744\n 26545.270937: drm_ioctl_kernel+0xa8/0x124\n 26545.274976: drm_ioctl+0x21c/0x33c\n 26545.278478: drm_compat_ioctl+0xdc/0xf0\n 26545.282428: __arm64_compat_sys_ioctl+0xc8/0x100\n 26545.287169: el0_svc_common+0xf8/0x250\n 26545.291025: do_el0_svc_compat+0x28/0x54\n 26545.295066: el0_svc_compat+0x10/0x1c\n 26545.298838: el0_sync_compat_handler+0xa8/0xcc\n 26545.303403: el0_sync_compat+0x188/0x1c0\n 26545.307445: Code: d503201f d503201f 52800028 4b0803e8 (b8680008)\n 26545.318799: Kernel panic - not syncing: Oops: Fatal exception" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: drm/msm: corrige el acceso ptr nulo msm_ioctl_gem_submit() Corrige la siguiente desreferencia del puntero nulo en msm_ioctl_gem_submit(): 26545.260705: Rastreo de llamadas: 26545.263223: kref_put+0x1c/0x60 26545.266452 msm: _ioctl_gem_submit+ 0x254/0x744 26545.270937: drm_ioctl_kernel+0xa8/0x124 26545.274976: drm_ioctl+0x21c/0x33c 26545.278478: drm_compat_ioctl+0xdc/0xf0 : __arm64_compat_sys_ioctl+0xc8/0x100 26545.287169: el0_svc_common+0xf8/0x250 26545.291025: do_el0_svc_compat+0x28/0x54 26545.295066: 0 /0x1c 26545.298838: el0_sync_compat_handler+0xa8/0xcc 26545.303403: el0_sync_compat+0x188/0x1c0 26545.307445: C\u00f3digo: d503201f d503201f 52800028 4b0803e8 680008) 26545.318799: P\u00e1nico del kernel: no se sincroniza: Ups: excepci\u00f3n fatal" } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-476xx/CVE-2021-47611.json b/CVE-2021/CVE-2021-476xx/CVE-2021-47611.json index 3a3f0be9a48..ff974b75733 100644 --- a/CVE-2021/CVE-2021-476xx/CVE-2021-47611.json +++ b/CVE-2021/CVE-2021-476xx/CVE-2021-47611.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47611", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:55.650", - "lastModified": "2024-06-19T15:15:55.650", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmac80211: validate extended element ID is present\n\nBefore attempting to parse an extended element, verify that\nthe extended element ID is present." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: mac80211: validar que el ID del elemento extendido est\u00e9 presente Antes de intentar analizar un elemento extendido, verifique que el ID del elemento extendido est\u00e9 presente." } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-476xx/CVE-2021-47612.json b/CVE-2021/CVE-2021-476xx/CVE-2021-47612.json index 984ee2a3910..22acd445171 100644 --- a/CVE-2021/CVE-2021-476xx/CVE-2021-47612.json +++ b/CVE-2021/CVE-2021-476xx/CVE-2021-47612.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47612", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:55.750", - "lastModified": "2024-06-19T15:15:55.750", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnfc: fix segfault in nfc_genl_dump_devices_done\n\nWhen kmalloc in nfc_genl_dump_devices() fails then\nnfc_genl_dump_devices_done() segfaults as below\n\nKASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f]\nCPU: 0 PID: 25 Comm: kworker/0:1 Not tainted 5.16.0-rc4-01180-g2a987e65025e-dirty #5\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-6.fc35 04/01/2014\nWorkqueue: events netlink_sock_destruct_work\nRIP: 0010:klist_iter_exit+0x26/0x80\nCall Trace:\n\nclass_dev_iter_exit+0x15/0x20\nnfc_genl_dump_devices_done+0x3b/0x50\ngenl_lock_done+0x84/0xd0\nnetlink_sock_destruct+0x8f/0x270\n__sk_destruct+0x64/0x3b0\nsk_destruct+0xa8/0xd0\n__sk_free+0x2e8/0x3d0\nsk_free+0x51/0x90\nnetlink_sock_destruct_work+0x1c/0x20\nprocess_one_work+0x411/0x710\nworker_thread+0x6fd/0xa80" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: nfc: corrige el error de segmentaci\u00f3n en nfc_genl_dump_devices_done Cuando falla kmalloc en nfc_genl_dump_devices(), entonces el error de segmentaci\u00f3n de nfc_genl_dump_devices_done() se muestra a continuaci\u00f3n KASAN: null-ptr-deref en el rango [0x0000000000000008-0x00 0000000000000f] CPU: 0 PID : 25 Comm: kworker/0:1 Not tainted 5.16.0-rc4-01180-g2a987e65025e-dirty #5 Nombre del hardware: PC est\u00e1ndar QEMU (i440FX + PIIX, 1996), BIOS 1.14.0-6.fc35 04/01/ 2014 Cola de trabajo: eventos netlink_sock_destruct_work RIP: 0010:klist_iter_exit+0x26/0x80 Seguimiento de llamadas: class_dev_iter_exit+0x15/0x20 nfc_genl_dump_devices_done+0x3b/0x50 genl_lock_done+0x84/0xd0 estructura+0x8f/0x270 __sk_destruct+0x64/0x3b0 sk_destruct+0xa8/0xd0 __sk_free+0x2e8/0x3d0 sk_free+0x51/0x90 netlink_sock_destruct_work+0x1c/0x20 Process_one_work+0x411/0x710 trabajador_thread+0x6fd/0xa80" } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-476xx/CVE-2021-47613.json b/CVE-2021/CVE-2021-476xx/CVE-2021-47613.json index 4b0ddf42dda..8e975638d55 100644 --- a/CVE-2021/CVE-2021-476xx/CVE-2021-47613.json +++ b/CVE-2021/CVE-2021-476xx/CVE-2021-47613.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47613", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:55.850", - "lastModified": "2024-06-19T15:15:55.850", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ni2c: virtio: fix completion handling\n\nThe driver currently assumes that the notify callback is only received\nwhen the device is done with all the queued buffers.\n\nHowever, this is not true, since the notify callback could be called\nwithout any of the queued buffers being completed (for example, with\nvirtio-pci and shared interrupts) or with only some of the buffers being\ncompleted (since the driver makes them available to the device in\nmultiple separate virtqueue_add_sgs() calls).\n\nThis can lead to incorrect data on the I2C bus or memory corruption in\nthe guest if the device operates on buffers which are have been freed by\nthe driver. (The WARN_ON in the driver is also triggered.)\n\n BUG kmalloc-128 (Tainted: G W ): Poison overwritten\n First byte 0x0 instead of 0x6b\n Allocated in i2cdev_ioctl_rdwr+0x9d/0x1de age=243 cpu=0 pid=28\n \tmemdup_user+0x2e/0xbd\n \ti2cdev_ioctl_rdwr+0x9d/0x1de\n \ti2cdev_ioctl+0x247/0x2ed\n \tvfs_ioctl+0x21/0x30\n \tsys_ioctl+0xb18/0xb41\n Freed in i2cdev_ioctl_rdwr+0x1bb/0x1de age=68 cpu=0 pid=28\n \tkfree+0x1bd/0x1cc\n \ti2cdev_ioctl_rdwr+0x1bb/0x1de\n \ti2cdev_ioctl+0x247/0x2ed\n \tvfs_ioctl+0x21/0x30\n \tsys_ioctl+0xb18/0xb41\n\nFix this by calling virtio_get_buf() from the notify handler like other\nvirtio drivers and by actually waiting for all the buffers to be\ncompleted." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: i2c: virtio: manejo de finalizaci\u00f3n de reparaci\u00f3n El controlador actualmente supone que la devoluci\u00f3n de llamada de notificaci\u00f3n solo se recibe cuando el dispositivo termina con todos los b\u00faferes en cola. Sin embargo, esto no es cierto, ya que la devoluci\u00f3n de llamada de notificaci\u00f3n podr\u00eda llamarse sin que se complete ninguno de los b\u00faferes en cola (por ejemplo, con virtio-pci e interrupciones compartidas) o con solo algunos de los b\u00faferes completados (ya que el controlador los pone a disposici\u00f3n). al dispositivo en m\u00faltiples llamadas virtqueue_add_sgs() separadas). Esto puede provocar datos incorrectos en el bus I2C o da\u00f1os en la memoria del hu\u00e9sped si el dispositivo funciona con b\u00faferes que han sido liberados por el controlador. (El WARN_ON en el controlador tambi\u00e9n se activa). ERROR kmalloc-128 (Contaminado: GW): Veneno sobrescrito Primer byte 0x0 en lugar de 0x6b Asignado en i2cdev_ioctl_rdwr+0x9d/0x1de age=243 cpu=0 pid=28 memdup_user+0x2e/0xbd i2cdev_ioctl_rdwr+0x9d/0x1de i2cdev_ioctl+0x247/0x2ed vfs_ioctl+0x21/0x30 sys_ioctl+0xb18/0xb41 Liberado en i2cdev_ioctl_rdwr+0x1bb/0x1de age=68 cpu=0 pid=28 0x1cc i2cdev_ioctl_rdwr+0x1bb/0x1de i2cdev_ioctl+0x247/ 0x2ed vfs_ioctl+0x21/0x30 sys_ioctl+0xb18/0xb41 Solucione este problema llamando a virtio_get_buf() desde el controlador de notificaci\u00f3n como otros controladores virtio y esperando a que se completen todos los b\u00faferes." } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-476xx/CVE-2021-47614.json b/CVE-2021/CVE-2021-476xx/CVE-2021-47614.json index 22ce191d834..cf93da9b6e6 100644 --- a/CVE-2021/CVE-2021-476xx/CVE-2021-47614.json +++ b/CVE-2021/CVE-2021-476xx/CVE-2021-47614.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47614", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:55.943", - "lastModified": "2024-06-19T15:15:55.943", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/irdma: Fix a user-after-free in add_pble_prm\n\nWhen irdma_hmc_sd_one fails, 'chunk' is freed while its still on the PBLE\ninfo list.\n\nAdd the chunk entry to the PBLE info list only after successful setting of\nthe SD in irdma_hmc_sd_one." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: RDMA/irdma: corrige un user-after-free en add_pble_prm Cuando falla irdma_hmc_sd_one, el 'fragmento' se libera mientras todav\u00eda est\u00e1 en la lista de informaci\u00f3n de PBLE. Agregue la entrada del fragmento a la lista de informaci\u00f3n de PBLE solo despu\u00e9s de configurar correctamente la SD en irdma_hmc_sd_one." } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-476xx/CVE-2021-47615.json b/CVE-2021/CVE-2021-476xx/CVE-2021-47615.json index af66841a88d..b01dbf108f5 100644 --- a/CVE-2021/CVE-2021-476xx/CVE-2021-47615.json +++ b/CVE-2021/CVE-2021-476xx/CVE-2021-47615.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47615", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:56.030", - "lastModified": "2024-06-19T15:15:56.030", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/mlx5: Fix releasing unallocated memory in dereg MR flow\n\nFor the case of IB_MR_TYPE_DM the mr does doesn't have a umem, even though\nit is a user MR. This causes function mlx5_free_priv_descs() to think that\nit is a kernel MR, leading to wrongly accessing mr->descs that will get\nwrong values in the union which leads to attempt to release resources that\nwere not allocated in the first place.\n\nFor example:\n DMA-API: mlx5_core 0000:08:00.1: device driver tries to free DMA memory it has not allocated [device address=0x0000000000000000] [size=0 bytes]\n WARNING: CPU: 8 PID: 1021 at kernel/dma/debug.c:961 check_unmap+0x54f/0x8b0\n RIP: 0010:check_unmap+0x54f/0x8b0\n Call Trace:\n debug_dma_unmap_page+0x57/0x60\n mlx5_free_priv_descs+0x57/0x70 [mlx5_ib]\n mlx5_ib_dereg_mr+0x1fb/0x3d0 [mlx5_ib]\n ib_dereg_mr_user+0x60/0x140 [ib_core]\n uverbs_destroy_uobject+0x59/0x210 [ib_uverbs]\n uobj_destroy+0x3f/0x80 [ib_uverbs]\n ib_uverbs_cmd_verbs+0x435/0xd10 [ib_uverbs]\n ? uverbs_finalize_object+0x50/0x50 [ib_uverbs]\n ? lock_acquire+0xc4/0x2e0\n ? lock_acquired+0x12/0x380\n ? lock_acquire+0xc4/0x2e0\n ? lock_acquire+0xc4/0x2e0\n ? ib_uverbs_ioctl+0x7c/0x140 [ib_uverbs]\n ? lock_release+0x28a/0x400\n ib_uverbs_ioctl+0xc0/0x140 [ib_uverbs]\n ? ib_uverbs_ioctl+0x7c/0x140 [ib_uverbs]\n __x64_sys_ioctl+0x7f/0xb0\n do_syscall_64+0x38/0x90\n\nFix it by reorganizing the dereg flow and mlx5_ib_mr structure:\n - Move the ib_umem field into the user MRs structure in the union as it's\n applicable only there.\n - Function mlx5_ib_dereg_mr() will now call mlx5_free_priv_descs() only\n in case there isn't udata, which indicates that this isn't a user MR." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: RDMA/mlx5: Se corrigi\u00f3 la liberaci\u00f3n de memoria no asignada en el flujo de MR dereg. Para el caso de IB_MR_TYPE_DM, mr no tiene un umem, aunque sea un usuario MR. Esto hace que la funci\u00f3n mlx5_free_priv_descs() piense que es un MR del kernel, lo que lleva a un acceso incorrecto a mr->descs que obtendr\u00e1 valores incorrectos en la uni\u00f3n, lo que lleva a intentar liberar recursos que no fueron asignados en primer lugar. Por ejemplo: DMA-API: mlx5_core 0000:08:00.1: el controlador de dispositivo intenta liberar la memoria DMA que no ha asignado [direcci\u00f3n del dispositivo=0x0000000000000000] [tama\u00f1o=0 bytes] ADVERTENCIA: CPU: 8 PID: 1021 en kernel/dma/ debug.c:961 check_unmap+0x54f/0x8b0 RIP: 0010:check_unmap+0x54f/0x8b0 Seguimiento de llamadas: debug_dma_unmap_page+0x57/0x60 mlx5_free_priv_descs+0x57/0x70 [mlx5_ib] [mlx5_ib] ib_dereg_mr_user+0x60/0x140 [ib_core ] uverbs_destroy_uobject+0x59/0x210 [ib_uverbs] uobj_destroy+0x3f/0x80 [ib_uverbs] ib_uverbs_cmd_verbs+0x435/0xd10 [ib_uverbs] ? uverbs_finalize_object+0x50/0x50 [ib_uverbs] ? lock_acquire+0xc4/0x2e0? lock_adquirido+0x12/0x380? lock_acquire+0xc4/0x2e0? lock_acquire+0xc4/0x2e0? ib_uverbs_ioctl+0x7c/0x140 [ib_uverbs] ? lock_release+0x28a/0x400 ib_uverbs_ioctl+0xc0/0x140 [ib_uverbs]? ib_uverbs_ioctl+0x7c/0x140 [ib_uverbs] __x64_sys_ioctl+0x7f/0xb0 do_syscall_64+0x38/0x90 Soluci\u00f3nelo reorganizando el flujo de dereg y la estructura mlx5_ib_mr: - Mueva el campo ib_umem a la estructura MRs del usuario en la uni\u00f3n, ya que solo se aplica all\u00ed. - La funci\u00f3n mlx5_ib_dereg_mr() ahora llamar\u00e1 a mlx5_free_priv_descs() solo en caso de que no haya udata, lo que indica que no se trata de un usuario MR." } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-476xx/CVE-2021-47616.json b/CVE-2021/CVE-2021-476xx/CVE-2021-47616.json index eccb6aa1eb5..bf57b0be000 100644 --- a/CVE-2021/CVE-2021-476xx/CVE-2021-47616.json +++ b/CVE-2021/CVE-2021-476xx/CVE-2021-47616.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47616", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T15:15:56.130", - "lastModified": "2024-06-19T15:15:56.130", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA: Fix use-after-free in rxe_queue_cleanup\n\nOn error handling path in rxe_qp_from_init() qp->sq.queue is freed and\nthen rxe_create_qp() will drop last reference to this object. qp clean up\nfunction will try to free this queue one time and it causes UAF bug.\n\nFix it by zeroing queue pointer after freeing queue in rxe_qp_from_init()." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: RDMA: corrige el use-after-free en rxe_queue_cleanup En la ruta de manejo de errores en rxe_qp_from_init() qp->sq.queue se libera y luego rxe_create_qp() eliminar\u00e1 la \u00faltima referencia a este objeto. La funci\u00f3n de limpieza qp intentar\u00e1 liberar esta cola una vez y provocar\u00e1 un error UAF. Solucionarlo poniendo a cero el puntero de la cola despu\u00e9s de liberar la cola en rxe_qp_from_init()." } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-476xx/CVE-2021-47617.json b/CVE-2021/CVE-2021-476xx/CVE-2021-47617.json index 7ab92f4930b..3fc344b4db2 100644 --- a/CVE-2021/CVE-2021-476xx/CVE-2021-47617.json +++ b/CVE-2021/CVE-2021-476xx/CVE-2021-47617.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47617", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-20T11:15:54.317", - "lastModified": "2024-06-20T11:15:54.317", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nPCI: pciehp: Fix infinite loop in IRQ handler upon power fault\n\nThe Power Fault Detected bit in the Slot Status register differs from\nall other hotplug events in that it is sticky: It can only be cleared\nafter turning off slot power. Per PCIe r5.0, sec. 6.7.1.8:\n\n If a power controller detects a main power fault on the hot-plug slot,\n it must automatically set its internal main power fault latch [...].\n The main power fault latch is cleared when software turns off power to\n the hot-plug slot.\n\nThe stickiness used to cause interrupt storms and infinite loops which\nwere fixed in 2009 by commits 5651c48cfafe (\"PCI pciehp: fix power fault\ninterrupt storm problem\") and 99f0169c17f3 (\"PCI: pciehp: enable\nsoftware notification on empty slots\").\n\nUnfortunately in 2020 the infinite loop issue was inadvertently\nreintroduced by commit 8edf5332c393 (\"PCI: pciehp: Fix MSI interrupt\nrace\"): The hardirq handler pciehp_isr() clears the PFD bit until\npciehp's power_fault_detected flag is set. That happens in the IRQ\nthread pciehp_ist(), which never learns of the event because the hardirq\nhandler is stuck in an infinite loop. Fix by setting the\npower_fault_detected flag already in the hardirq handler." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: PCI: pciehp: soluciona el bucle infinito en el controlador IRQ ante un fallo de alimentaci\u00f3n. El bit de fallo de alimentaci\u00f3n detectado en el registro de estado de la ranura se diferencia de todos los dem\u00e1s eventos de conexi\u00f3n en caliente en que es fijo: solo puede borrarse despu\u00e9s de apagar la alimentaci\u00f3n de la ranura. Por PCIe r5.0, seg. 6.7.1.8: Si un controlador de energ\u00eda detecta una falla de energ\u00eda principal en la ranura de conexi\u00f3n en caliente, debe configurar autom\u00e1ticamente su pestillo interno de falla de energ\u00eda principal [...]. El bloqueo de fallo de alimentaci\u00f3n principal se borra cuando el software corta la alimentaci\u00f3n a la ranura de conexi\u00f3n en caliente. La rigidez sol\u00eda causar tormentas de interrupci\u00f3n y bucles infinitos que se solucionaron en 2009 mediante los commits 5651c48cfafe (\"PCI pciehp: solucionar el problema de la tormenta de interrupci\u00f3n por falla de energ\u00eda\") y 99f0169c17f3 (\"PCI: pciehp: habilitar la notificaci\u00f3n de software en ranuras vac\u00edas\"). Desafortunadamente, en 2020, el problema del bucle infinito se reintrodujo inadvertidamente mediante el commit 8edf5332c393 (\"PCI: pciehp: arreglar carrera de interrupci\u00f3n MSI\"): el controlador hardirq pciehp_isr() borra el bit PFD hasta que se establece el indicador power_fault_detected de pciehp. Eso sucede en el hilo IRQ pciehp_ist(), que nunca se entera del evento porque el controlador hardirq est\u00e1 atrapado en un bucle infinito. Para solucionarlo, configure el indicador power_fault_detected que ya est\u00e1 en el controlador hardirq." } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-476xx/CVE-2021-47618.json b/CVE-2021/CVE-2021-476xx/CVE-2021-47618.json index cfb0adb3a6a..c0303fc138e 100644 --- a/CVE-2021/CVE-2021-476xx/CVE-2021-47618.json +++ b/CVE-2021/CVE-2021-476xx/CVE-2021-47618.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47618", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-20T11:15:54.477", - "lastModified": "2024-06-20T11:15:54.477", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nARM: 9170/1: fix panic when kasan and kprobe are enabled\n\narm32 uses software to simulate the instruction replaced\nby kprobe. some instructions may be simulated by constructing\nassembly functions. therefore, before executing instruction\nsimulation, it is necessary to construct assembly function\nexecution environment in C language through binding registers.\nafter kasan is enabled, the register binding relationship will\nbe destroyed, resulting in instruction simulation errors and\ncausing kernel panic.\n\nthe kprobe emulate instruction function is distributed in three\nfiles: actions-common.c actions-arm.c actions-thumb.c, so disable\nKASAN when compiling these files.\n\nfor example, use kprobe insert on cap_capable+20 after kasan\nenabled, the cap_capable assembly code is as follows:\n:\ne92d47f0\tpush\t{r4, r5, r6, r7, r8, r9, sl, lr}\ne1a05000\tmov\tr5, r0\ne280006c\tadd\tr0, r0, #108 ; 0x6c\ne1a04001\tmov\tr4, r1\ne1a06002\tmov\tr6, r2\ne59fa090\tldr\tsl, [pc, #144] ;\nebfc7bf8\tbl\tc03aa4b4 <__asan_load4>\ne595706c\tldr\tr7, [r5, #108] ; 0x6c\ne2859014\tadd\tr9, r5, #20\n......\nThe emulate_ldr assembly code after enabling kasan is as follows:\nc06f1384 :\ne92d47f0\tpush\t{r4, r5, r6, r7, r8, r9, sl, lr}\ne282803c\tadd\tr8, r2, #60 ; 0x3c\ne1a05000\tmov\tr5, r0\ne7e37855\tubfx\tr7, r5, #16, #4\ne1a00008\tmov\tr0, r8\ne1a09001\tmov\tr9, r1\ne1a04002\tmov\tr4, r2\nebf35462\tbl\tc03c6530 <__asan_load4>\ne357000f\tcmp\tr7, #15\ne7e36655\tubfx\tr6, r5, #12, #4\ne205a00f\tand\tsl, r5, #15\n0a000001\tbeq\tc06f13bc \ne0840107\tadd\tr0, r4, r7, lsl #2\nebf3545c\tbl\tc03c6530 <__asan_load4>\ne084010a\tadd\tr0, r4, sl, lsl #2\nebf3545a\tbl\tc03c6530 <__asan_load4>\ne2890010\tadd\tr0, r9, #16\nebf35458\tbl\tc03c6530 <__asan_load4>\ne5990010\tldr\tr0, [r9, #16]\ne12fff30\tblx\tr0\ne356000f\tcm\tr6, #15\n1a000014\tbne\tc06f1430 \ne1a06000\tmov\tr6, r0\ne2840040\tadd\tr0, r4, #64 ; 0x40\n......\n\nwhen running in emulate_ldr to simulate the ldr instruction, panic\noccurred, and the log is as follows:\nUnable to handle kernel NULL pointer dereference at virtual address\n00000090\npgd = ecb46400\n[00000090] *pgd=2e0fa003, *pmd=00000000\nInternal error: Oops: 206 [#1] SMP ARM\nPC is at cap_capable+0x14/0xb0\nLR is at emulate_ldr+0x50/0xc0\npsr: 600d0293 sp : ecd63af8 ip : 00000004 fp : c0a7c30c\nr10: 00000000 r9 : c30897f4 r8 : ecd63cd4\nr7 : 0000000f r6 : 0000000a r5 : e59fa090 r4 : ecd63c98\nr3 : c06ae294 r2 : 00000000 r1 : b7611300 r0 : bf4ec008\nFlags: nZCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment user\nControl: 32c5387d Table: 2d546400 DAC: 55555555\nProcess bash (pid: 1643, stack limit = 0xecd60190)\n(cap_capable) from (kprobe_handler+0x218/0x340)\n(kprobe_handler) from (kprobe_trap_handler+0x24/0x48)\n(kprobe_trap_handler) from (do_undefinstr+0x13c/0x364)\n(do_undefinstr) from (__und_svc_finish+0x0/0x30)\n(__und_svc_finish) from (cap_capable+0x18/0xb0)\n(cap_capable) from (cap_vm_enough_memory+0x38/0x48)\n(cap_vm_enough_memory) from\n(security_vm_enough_memory_mm+0x48/0x6c)\n(security_vm_enough_memory_mm) from\n(copy_process.constprop.5+0x16b4/0x25c8)\n(copy_process.constprop.5) from (_do_fork+0xe8/0x55c)\n(_do_fork) from (SyS_clone+0x1c/0x24)\n(SyS_clone) from (__sys_trace_return+0x0/0x10)\nCode: 0050a0e1 6c0080e2 0140a0e1 0260a0e1 (f801f0e7)" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: ARM: 9170/1: soluciona el p\u00e1nico cuando kasan y kprobe est\u00e1n habilitados arm32 usa software para simular la instrucci\u00f3n reemplazada por kprobe. Algunas instrucciones pueden simularse mediante la construcci\u00f3n de funciones de ensamblaje. por lo tanto, antes de ejecutar la simulaci\u00f3n de instrucciones, es necesario construir un entorno de ejecuci\u00f3n de funciones de ensamblaje en lenguaje C mediante registros vinculantes. despu\u00e9s de habilitar kasan, la relaci\u00f3n de enlace de registros se destruir\u00e1, lo que provocar\u00e1 errores de simulaci\u00f3n de instrucciones y provocar\u00e1 p\u00e1nico en el kernel. La funci\u00f3n de emulaci\u00f3n de instrucciones de kprobe se distribuye en tres archivos: acciones-common.c acciones-arm.c acciones-thumb.c, por lo tanto, desactive KASAN al compilar estos archivos. por ejemplo, use kprobe insert en cap_capable+20 despu\u00e9s de habilitar kasan, el c\u00f3digo ensamblador de cap_capable es el siguiente: : e92d47f0 push {r4, r5, r6, r7, r8, r9, sl, lr} e1a05000 mov r5, r0 e280006c agregue r0, r0, #108; 0x6c e1a04001 mov r4, r1 e1a06002 mov r6, r2 e59fa090 ldr sl, [ordenador personal, #144]; ebfc7bf8 bl c03aa4b4 <__asan_load4> e595706c ldr r7, [r5, #108]; 0x6c e2859014 add r9, r5, #20 ...... El c\u00f3digo ensamblador emulate_ldr despu\u00e9s de habilitar kasan es el siguiente: c06f1384 : e92d47f0 push {r4, r5, r6, r7, r8, r9, sl, lr} e282803c agregue r8, r2, #60; 0x3c e1a05000 mov r5, r0 e7e37855 ubfx r7, r5, #16, #4 e1a00008 mov r0, r8 e1a09001 mov r9, r1 e1a04002 mov r4, r2 ebf35462 bl c03c6530 <__asan_load 4> e357000f cmp r7, #15 e7e36655 ubfx r6, r5, #12, #4 e205a00f y sl, r5, #15 0a000001 beq c06f13bc e0840107 add r0, r4, r7, lsl #2 ebf3545c bl c03c6530 <__asan_load4> e084010a add r0, 4, sl, lsl #2 ebf3545a bl c03c6530 <__asan_load4> e2890010 agregar r0, r9, #16 ebf35458 bl c03c6530 <__asan_load4> e5990010 ldr r0, [r9, #16] e12fff30 blx r0 e356000f cm r6, #15 14 bne c06f1430 e1a06000 mov r6, r0 e2840040 agregar r0, r4, #64; 0x40 ...... cuando se ejecuta emulate_ldr para simular la instrucci\u00f3n ldr, se produce p\u00e1nico y el registro es el siguiente: No se puede manejar la desreferencia del puntero NULL del kernel en la direcci\u00f3n virtual 00000090 pgd = ecb46400 [00000090] *pgd=2e0fa003, * pmd=00000000 Error interno: Ups: 206 [#1] La PC SMP ARM est\u00e1 en cap_capable+0x14/0xb0 LR est\u00e1 en emulate_ldr+0x50/0xc0 psr: 600d0293 sp: ecd63af8 ip: 00000004 fp: c0a7c30c r10: r9: c30897f4 r8 : ecd63cd4 r7 : 0000000f r6 : 0000000a r5 : e59fa090 r4 : ecd63c98 r3 : c06ae294 r2 : 00000000 r1 : b7611300 r0 : bf4ec008 Banderas: nZCv IRQ desactivadas FIQ activadas Modo SVC_3 2 Usuario de segmento ISA ARM Control: 32c5387d Tabla: 2d546400 DAC: 55555555 Proceso bash (pid: 1643, l\u00edmite de pila = 0xecd60190) (cap_capable) de (kprobe_handler+0x218/0x340) (kprobe_handler) de (kprobe_trap_handler+0x24/0x48) (kprobe_trap_handler) de (do_undefinstr+0x13c/0x364) (do_undefinstr) de (__ und_svc_finish+ 0x0/0x30) (__und_svc_finish) de (cap_capable+0x18/0xb0) (cap_capable) de (cap_vm_enough_memory+0x38/0x48) (cap_vm_enough_memory) de (security_vm_enough_memory_mm+0x48/0x6c) (security_vm_enough_memory_mm) de (copy_process .constprop.5+0x16b4/ 0x25c8) (copy_process.constprop.5) de (_do_fork+0xe8/0x55c) (_do_fork) de (SyS_clone+0x1c/0x24) (SyS_clone) de (__sys_trace_return+0x0/0x10) C\u00f3digo: 0050a0e1 6c0080e2 0260a0e1 (f801f0e7)" } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-476xx/CVE-2021-47619.json b/CVE-2021/CVE-2021-476xx/CVE-2021-47619.json index d0de37ff523..ccb43309800 100644 --- a/CVE-2021/CVE-2021-476xx/CVE-2021-47619.json +++ b/CVE-2021/CVE-2021-476xx/CVE-2021-47619.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47619", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-20T11:15:54.560", - "lastModified": "2024-06-20T11:15:54.560", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ni40e: Fix queues reservation for XDP\n\nWhen XDP was configured on a system with large number of CPUs\nand X722 NIC there was a call trace with NULL pointer dereference.\n\ni40e 0000:87:00.0: failed to get tracking for 256 queues for VSI 0 err -12\ni40e 0000:87:00.0: setup of MAIN VSI failed\n\nBUG: kernel NULL pointer dereference, address: 0000000000000000\nRIP: 0010:i40e_xdp+0xea/0x1b0 [i40e]\nCall Trace:\n? i40e_reconfig_rss_queues+0x130/0x130 [i40e]\ndev_xdp_install+0x61/0xe0\ndev_xdp_attach+0x18a/0x4c0\ndev_change_xdp_fd+0x1e6/0x220\ndo_setlink+0x616/0x1030\n? ahci_port_stop+0x80/0x80\n? ata_qc_issue+0x107/0x1e0\n? lock_timer_base+0x61/0x80\n? __mod_timer+0x202/0x380\nrtnl_setlink+0xe5/0x170\n? bpf_lsm_binder_transaction+0x10/0x10\n? security_capable+0x36/0x50\nrtnetlink_rcv_msg+0x121/0x350\n? rtnl_calcit.isra.0+0x100/0x100\nnetlink_rcv_skb+0x50/0xf0\nnetlink_unicast+0x1d3/0x2a0\nnetlink_sendmsg+0x22a/0x440\nsock_sendmsg+0x5e/0x60\n__sys_sendto+0xf0/0x160\n? __sys_getsockname+0x7e/0xc0\n? _copy_from_user+0x3c/0x80\n? __sys_setsockopt+0xc8/0x1a0\n__x64_sys_sendto+0x20/0x30\ndo_syscall_64+0x33/0x40\nentry_SYSCALL_64_after_hwframe+0x44/0xae\nRIP: 0033:0x7f83fa7a39e0\n\nThis was caused by PF queue pile fragmentation due to\nflow director VSI queue being placed right after main VSI.\nBecause of this main VSI was not able to resize its\nqueue allocation for XDP resulting in no queues allocated\nfor main VSI when XDP was turned on.\n\nFix this by always allocating last queue in PF queue pile\nfor a flow director VSI." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: i40e: Arreglar la reserva de colas para XDP Cuando se configur\u00f3 XDP en un sistema con una gran cantidad de CPU y NIC X722, hubo un seguimiento de llamada con desreferencia de puntero NULL. i40e 0000:87:00.0: no se pudo obtener el seguimiento de 256 colas para VSI 0 err -12 i40e 0000:87:00.0: fall\u00f3 la configuraci\u00f3n de VSI PRINCIPAL ERROR: desreferencia del puntero NULL del kernel, direcci\u00f3n: 00000000000000000 RIP: 0010:i40e_xdp+0xea/ 0x1b0 [i40e] Seguimiento de llamadas:? i40e_reconfig_rss_queues+0x130/0x130 [i40e] dev_xdp_install+0x61/0xe0 dev_xdp_attach+0x18a/0x4c0 dev_change_xdp_fd+0x1e6/0x220 do_setlink+0x616/0x1030 ? ahci_port_stop+0x80/0x80? ata_qc_issue+0x107/0x1e0? lock_timer_base+0x61/0x80? __mod_timer+0x202/0x380 rtnl_setlink+0xe5/0x170 ? bpf_lsm_binder_transaction+0x10/0x10? capacidad_seguridad+0x36/0x50 rtnetlink_rcv_msg+0x121/0x350 ? rtnl_calcit.isra.0+0x100/0x100 netlink_rcv_skb+0x50/0xf0 netlink_unicast+0x1d3/0x2a0 netlink_sendmsg+0x22a/0x440 sock_sendmsg+0x5e/0x60 __sys_sendto+0xf0/0x160 ? __sys_getsockname+0x7e/0xc0 ? _copia_de_usuario+0x3c/0x80 ? __sys_setsockopt+0xc8/0x1a0 __x64_sys_sendto+0x20/0x30 do_syscall_64+0x33/0x40 Entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f83fa7a39e0 Esto fue causado por la fragmentaci\u00f3n de la pila de cola PF debido al flujo La cola VSI del director se coloca justo despu\u00e9s de la VSI principal. Debido a esto, la VSI principal no pudo cambiar el tama\u00f1o de su asignaci\u00f3n de cola para XDP, lo que provoc\u00f3 que no se asignaran colas para la VSI principal cuando se activ\u00f3 XDP. Solucione este problema asignando siempre la \u00faltima cola en la pila de colas PF para una VSI de director de flujo." } ], "metrics": {}, diff --git a/CVE-2021/CVE-2021-476xx/CVE-2021-47620.json b/CVE-2021/CVE-2021-476xx/CVE-2021-47620.json index 846bf6f26b8..0317114fe1f 100644 --- a/CVE-2021/CVE-2021-476xx/CVE-2021-47620.json +++ b/CVE-2021/CVE-2021-476xx/CVE-2021-47620.json @@ -2,12 +2,16 @@ "id": "CVE-2021-47620", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-20T11:15:54.653", - "lastModified": "2024-06-20T11:15:54.653", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: refactor malicious adv data check\n\nCheck for out-of-bound read was being performed at the end of while\nnum_reports loop, and would fill journal with false positives. Added\ncheck to beginning of loop processing so that it doesn't get checked\nafter ptr has been advanced." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: Bluetooth: refactorizaci\u00f3n de verificaci\u00f3n de datos publicitarios maliciosos. Se estaba realizando una verificaci\u00f3n de lectura fuera de los l\u00edmites al final del bucle while num_reports y llenar\u00eda el diario con falsos positivos. Se agreg\u00f3 una verificaci\u00f3n al comienzo del procesamiento del bucle para que no se verifique despu\u00e9s de que se haya avanzado ptr." } ], "metrics": {}, diff --git a/CVE-2022/CVE-2022-238xx/CVE-2022-23829.json b/CVE-2022/CVE-2022-238xx/CVE-2022-23829.json index ad943a4e74a..a02b6188d68 100644 --- a/CVE-2022/CVE-2022-238xx/CVE-2022-23829.json +++ b/CVE-2022/CVE-2022-238xx/CVE-2022-23829.json @@ -2,12 +2,16 @@ "id": "CVE-2022-23829", "sourceIdentifier": "psirt@amd.com", "published": "2024-06-18T19:15:56.957", - "lastModified": "2024-06-18T19:15:56.957", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A potential weakness in AMD SPI protection features may allow a malicious attacker with Ring0 (kernel mode) access to bypass the native System Management Mode (SMM) ROM protections." + }, + { + "lang": "es", + "value": "Una posible debilidad en las funciones de protecci\u00f3n AMD SPI puede permitir que un atacante malicioso con acceso Ring0 (modo kernel) evite las protecciones ROM nativas del modo de administraci\u00f3n del sistema (SMM)." } ], "metrics": { diff --git a/CVE-2022/CVE-2022-458xx/CVE-2022-45832.json b/CVE-2022/CVE-2022-458xx/CVE-2022-45832.json index 77487237570..c35aaf42596 100644 --- a/CVE-2022/CVE-2022-458xx/CVE-2022-45832.json +++ b/CVE-2022/CVE-2022-458xx/CVE-2022-45832.json @@ -2,12 +2,16 @@ "id": "CVE-2022-45832", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T15:15:56.223", - "lastModified": "2024-06-19T15:15:56.223", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in Hennessey Digital Attorney.This issue affects Attorney: from n/a through 3." + }, + { + "lang": "es", + "value": "Vulnerabilidad de falta de autorizaci\u00f3n en Hennessey Digital Attorney. Este problema afecta a Attorney: desde n/a hasta 3." } ], "metrics": { diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48711.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48711.json index ca0d2ffc685..874f5279024 100644 --- a/CVE-2022/CVE-2022-487xx/CVE-2022-48711.json +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48711.json @@ -2,12 +2,16 @@ "id": "CVE-2022-48711", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-20T11:15:54.793", - "lastModified": "2024-06-20T11:15:54.793", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ntipc: improve size validations for received domain records\n\nThe function tipc_mon_rcv() allows a node to receive and process\ndomain_record structs from peer nodes to track their views of the\nnetwork topology.\n\nThis patch verifies that the number of members in a received domain\nrecord does not exceed the limit defined by MAX_MON_DOMAIN, something\nthat may otherwise lead to a stack overflow.\n\ntipc_mon_rcv() is called from the function tipc_link_proto_rcv(), where\nwe are reading a 32 bit message data length field into a uint16. To\navert any risk of bit overflow, we add an extra sanity check for this in\nthat function. We cannot see that happen with the current code, but\nfuture designers being unaware of this risk, may introduce it by\nallowing delivery of very large (> 64k) sk buffers from the bearer\nlayer. This potential problem was identified by Eric Dumazet.\n\nThis fixes CVE-2022-0435" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: tipc: mejorar las validaciones de tama\u00f1o para los registros de dominio recibidos. La funci\u00f3n tipc_mon_rcv() permite que un nodo reciba y procese estructuras domain_record de nodos pares para rastrear sus vistas de la topolog\u00eda de la red. Este parche verifica que la cantidad de miembros en un registro de dominio recibido no exceda el l\u00edmite definido por MAX_MON_DOMAIN, algo que de otro modo podr\u00eda provocar un desbordamiento de pila. tipc_mon_rcv() se llama desde la funci\u00f3n tipc_link_proto_rcv(), donde leemos un campo de longitud de datos de mensaje de 32 bits en un uint16. Para evitar cualquier riesgo de desbordamiento de bits, agregamos una verificaci\u00f3n de cordura adicional en esa funci\u00f3n. No podemos ver que eso suceda con el c\u00f3digo actual, pero los futuros dise\u00f1adores, al desconocer este riesgo, pueden introducirlo permitiendo la entrega de b\u00faferes sk muy grandes (> 64k) desde la capa portadora. Este problema potencial fue identificado por Eric Dumazet. Esto corrige CVE-2022-0435" } ], "metrics": {}, diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48712.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48712.json index bf53b79def7..1efc4b72dea 100644 --- a/CVE-2022/CVE-2022-487xx/CVE-2022-48712.json +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48712.json @@ -2,12 +2,16 @@ "id": "CVE-2022-48712", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-20T11:15:54.880", - "lastModified": "2024-06-20T11:15:54.880", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\next4: fix error handling in ext4_fc_record_modified_inode()\n\nCurrent code does not fully takes care of krealloc() error case, which\ncould lead to silent memory corruption or a kernel bug. This patch\nfixes that.\n\nAlso it cleans up some duplicated error handling logic from various\nfunctions in fast_commit.c file." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: ext4: corrige el manejo de errores en ext4_fc_record_modified_inode() El c\u00f3digo actual no soluciona completamente el caso de error de krealloc(), lo que podr\u00eda provocar una corrupci\u00f3n silenciosa de la memoria o un error del kernel. Este parche soluciona eso. Tambi\u00e9n limpia alguna l\u00f3gica de manejo de errores duplicada de varias funciones en el archivo fast_commit.c." } ], "metrics": {}, diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48713.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48713.json index 77a5338a475..83aea570e2b 100644 --- a/CVE-2022/CVE-2022-487xx/CVE-2022-48713.json +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48713.json @@ -2,12 +2,16 @@ "id": "CVE-2022-48713", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-20T11:15:54.960", - "lastModified": "2024-06-20T11:15:54.960", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nperf/x86/intel/pt: Fix crash with stop filters in single-range mode\n\nAdd a check for !buf->single before calling pt_buffer_region_size in a\nplace where a missing check can cause a kernel crash.\n\nFixes a bug introduced by commit 670638477aed (\"perf/x86/intel/pt:\nOpportunistically use single range output mode\"), which added a\nsupport for PT single-range output mode. Since that commit if a PT\nstop filter range is hit while tracing, the kernel will crash because\nof a null pointer dereference in pt_handle_status due to calling\npt_buffer_region_size without a ToPA configured.\n\nThe commit which introduced single-range mode guarded almost all uses of\nthe ToPA buffer variables with checks of the buf->single variable, but\nmissed the case where tracing was stopped by the PT hardware, which\nhappens when execution hits a configured stop filter.\n\nTested that hitting a stop filter while PT recording successfully\nrecords a trace with this patch but crashes without this patch." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: perf/x86/intel/pt: soluciona el fallo con filtros de parada en modo de rango \u00fanico. A\u00f1ade una marca para !buf->single antes de llamar a pt_buffer_region_size en un lugar donde una marca faltante puede provocar un fallo del kernel. Corrige un error introducido por el commit 670638477aed (\"perf/x86/intel/pt: utilizar de manera oportunista el modo de salida de rango \u00fanico\"), que agreg\u00f3 soporte para el modo de salida de rango \u00fanico PT. Desde esa confirmaci\u00f3n, si se alcanza un rango de filtro de parada PT durante el seguimiento, el kernel fallar\u00e1 debido a una desreferencia de puntero nulo en pt_handle_status debido a la llamada a pt_buffer_region_size sin un ToPA configurado. La confirmaci\u00f3n que introdujo el modo de rango \u00fanico protegi\u00f3 casi todos los usos de las variables del b\u00fafer ToPA con comprobaciones de la variable buf->single, pero omiti\u00f3 el caso en el que el hardware PT detuvo el seguimiento, lo que ocurre cuando la ejecuci\u00f3n llega a un filtro de parada configurado. Se prob\u00f3 que al presionar un filtro de detenci\u00f3n mientras se graba PT se registra exitosamente un seguimiento con este parche, pero falla sin este parche." } ], "metrics": {}, diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48714.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48714.json index fc976185984..632e03d1b42 100644 --- a/CVE-2022/CVE-2022-487xx/CVE-2022-48714.json +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48714.json @@ -2,12 +2,16 @@ "id": "CVE-2022-48714", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-20T11:15:55.033", - "lastModified": "2024-06-20T11:15:55.033", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Use VM_MAP instead of VM_ALLOC for ringbuf\n\nAfter commit 2fd3fb0be1d1 (\"kasan, vmalloc: unpoison VM_ALLOC pages\nafter mapping\"), non-VM_ALLOC mappings will be marked as accessible\nin __get_vm_area_node() when KASAN is enabled. But now the flag for\nringbuf area is VM_ALLOC, so KASAN will complain out-of-bound access\nafter vmap() returns. Because the ringbuf area is created by mapping\nallocated pages, so use VM_MAP instead.\n\nAfter the change, info in /proc/vmallocinfo also changes from\n [start]-[end] 24576 ringbuf_map_alloc+0x171/0x290 vmalloc user\nto\n [start]-[end] 24576 ringbuf_map_alloc+0x171/0x290 vmap user" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: bpf: use VM_MAP en lugar de VM_ALLOC para ringbuf Despu\u00e9s del commit 2fd3fb0be1d1 (\"kasan, vmalloc: despoisone las p\u00e1ginas VM_ALLOC despu\u00e9s del mapeo\"), los mapeos que no sean VM_ALLOC se marcar\u00e1n como accesibles en __get_vm_area_node( ) cuando KASAN est\u00e1 habilitado. Pero ahora el indicador para el \u00e1rea ringbuf es VM_ALLOC, por lo que KASAN se quejar\u00e1 del acceso fuera de los l\u00edmites despu\u00e9s de que regrese vmap(). Debido a que el \u00e1rea ringbuf se crea asignando p\u00e1ginas asignadas, use VM_MAP en su lugar. Despu\u00e9s del cambio, la informaci\u00f3n en /proc/vmallocinfo tambi\u00e9n cambia de [inicio]-[fin] 24576 ringbuf_map_alloc+0x171/0x290 usuario vmalloc a [inicio]-[fin] 24576 ringbuf_map_alloc+0x171/0x290 usuario vmap" } ], "metrics": {}, diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48715.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48715.json index fd2b54571b9..d1a987b8e6f 100644 --- a/CVE-2022/CVE-2022-487xx/CVE-2022-48715.json +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48715.json @@ -2,12 +2,16 @@ "id": "CVE-2022-48715", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-20T11:15:55.110", - "lastModified": "2024-06-20T11:15:55.110", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: bnx2fc: Make bnx2fc_recv_frame() mp safe\n\nRunning tests with a debug kernel shows that bnx2fc_recv_frame() is\nmodifying the per_cpu lport stats counters in a non-mpsafe way. Just boot\na debug kernel and run the bnx2fc driver with the hardware enabled.\n\n[ 1391.699147] BUG: using smp_processor_id() in preemptible [00000000] code: bnx2fc_\n[ 1391.699160] caller is bnx2fc_recv_frame+0xbf9/0x1760 [bnx2fc]\n[ 1391.699174] CPU: 2 PID: 4355 Comm: bnx2fc_l2_threa Kdump: loaded Tainted: G B\n[ 1391.699180] Hardware name: HP ProLiant DL120 G7, BIOS J01 07/01/2013\n[ 1391.699183] Call Trace:\n[ 1391.699188] dump_stack_lvl+0x57/0x7d\n[ 1391.699198] check_preemption_disabled+0xc8/0xd0\n[ 1391.699205] bnx2fc_recv_frame+0xbf9/0x1760 [bnx2fc]\n[ 1391.699215] ? do_raw_spin_trylock+0xb5/0x180\n[ 1391.699221] ? bnx2fc_npiv_create_vports.isra.0+0x4e0/0x4e0 [bnx2fc]\n[ 1391.699229] ? bnx2fc_l2_rcv_thread+0xb7/0x3a0 [bnx2fc]\n[ 1391.699240] bnx2fc_l2_rcv_thread+0x1af/0x3a0 [bnx2fc]\n[ 1391.699250] ? bnx2fc_ulp_init+0xc0/0xc0 [bnx2fc]\n[ 1391.699258] kthread+0x364/0x420\n[ 1391.699263] ? _raw_spin_unlock_irq+0x24/0x50\n[ 1391.699268] ? set_kthread_struct+0x100/0x100\n[ 1391.699273] ret_from_fork+0x22/0x30\n\nRestore the old get_cpu/put_cpu code with some modifications to reduce the\nsize of the critical section." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: scsi: bnx2fc: Hacer que bnx2fc_recv_frame() mp sea seguro La ejecuci\u00f3n de pruebas con un kernel de depuraci\u00f3n muestra que bnx2fc_recv_frame() est\u00e1 modificando los contadores de estad\u00edsticas de puerto por CPU de una manera no segura para mp. Simplemente inicie un kernel de depuraci\u00f3n y ejecute el controlador bnx2fc con el hardware habilitado. [1391.699147] ERROR: uso de smp_processor_id() en c\u00f3digo interrumpible [00000000]: bnx2fc_ [1391.699160] la persona que llama es bnx2fc_recv_frame+0xbf9/0x1760 [bnx2fc] [1391.699174] CPU: 2 PID: 4355 Comm: bnx2fc_l2_threa Kdump: cargado Contaminado: GB [ 1391.699180 ] Nombre del hardware: HP ProLiant DL120 G7, BIOS J01 01/07/2013 [ 1391.699183] Seguimiento de llamadas: [ 1391.699188] dump_stack_lvl+0x57/0x7d [ 1391.699198] check_preemption_disabled+0xc8/0xd0 [ 1391.69 9205] bnx2fc_recv_frame+0xbf9/0x1760 [bnx2fc] [ 1391.699215] ? do_raw_spin_trylock+0xb5/0x180 [1391.699221]? bnx2fc_npiv_create_vports.isra.0+0x4e0/0x4e0 [bnx2fc] [1391.699229]? bnx2fc_l2_rcv_thread+0xb7/0x3a0 [bnx2fc] [ 1391.699240] bnx2fc_l2_rcv_thread+0x1af/0x3a0 [bnx2fc] [ 1391.699250] ? bnx2fc_ulp_init+0xc0/0xc0 [bnx2fc] [ 1391.699258] kthread+0x364/0x420 [ 1391.699263] ? _raw_spin_unlock_irq+0x24/0x50 [1391.699268]? set_kthread_struct+0x100/0x100 [ 1391.699273] ret_from_fork+0x22/0x30 Restaura el antiguo c\u00f3digo get_cpu/put_cpu con algunas modificaciones para reducir el tama\u00f1o de la secci\u00f3n cr\u00edtica." } ], "metrics": {}, diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48716.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48716.json index a8624084305..32b7595da28 100644 --- a/CVE-2022/CVE-2022-487xx/CVE-2022-48716.json +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48716.json @@ -2,12 +2,16 @@ "id": "CVE-2022-48716", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-20T11:15:55.207", - "lastModified": "2024-06-20T11:15:55.207", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nASoC: codecs: wcd938x: fix incorrect used of portid\n\nMixer controls have the channel id in mixer->reg, which is not same\nas port id. port id should be derived from chan_info array.\nSo fix this. Without this, its possible that we could corrupt\nstruct wcd938x_sdw_priv by accessing port_map array out of range\nwith channel id instead of port id." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: ASoC: c\u00f3decs: wcd938x: corrige el uso incorrecto del puerto Los controles del mezclador tienen la identificaci\u00f3n del canal en mezclador->reg, que no es la misma que la identificaci\u00f3n del puerto. La identificaci\u00f3n del puerto debe derivarse de la matriz chan_info. Entonces arregla esto. Sin esto, es posible que podamos da\u00f1ar la estructura wcd938x_sdw_priv accediendo a la matriz port_map fuera del rango con la identificaci\u00f3n del canal en lugar de la identificaci\u00f3n del puerto." } ], "metrics": {}, diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48717.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48717.json index 84d056c60a8..c29de08b4ae 100644 --- a/CVE-2022/CVE-2022-487xx/CVE-2022-48717.json +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48717.json @@ -2,12 +2,16 @@ "id": "CVE-2022-48717", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-20T11:15:55.287", - "lastModified": "2024-06-20T11:15:55.287", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nASoC: max9759: fix underflow in speaker_gain_control_put()\n\nCheck for negative values of \"priv->gain\" to prevent an out of bounds\naccess. The concern is that these might come from the user via:\n -> snd_ctl_elem_write_user()\n -> snd_ctl_elem_write()\n -> kctl->put()" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: ASoC: max9759: corrige el desbordamiento en altavoz_gain_control_put() Compruebe si hay valores negativos de \"priv->gain\" para evitar un acceso fuera de los l\u00edmites. La preocupaci\u00f3n es que estos puedan provenir del usuario a trav\u00e9s de: -> snd_ctl_elem_write_user() -> snd_ctl_elem_write() -> kctl->put()" } ], "metrics": {}, diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48718.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48718.json index 6a2c2d60269..72f2726704c 100644 --- a/CVE-2022/CVE-2022-487xx/CVE-2022-48718.json +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48718.json @@ -2,12 +2,16 @@ "id": "CVE-2022-48718", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-20T11:15:55.373", - "lastModified": "2024-06-20T11:15:55.373", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm: mxsfb: Fix NULL pointer dereference\n\nmxsfb should not ever dereference the NULL pointer which\ndrm_atomic_get_new_bridge_state is allowed to return.\nAssume a fixed format instead." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: drm: mxsfb: corrige la desreferencia del puntero NULL. mxsfb nunca deber\u00eda desreferenciar el puntero NULL que drm_atomic_get_new_bridge_state puede devolver. En su lugar, asuma un formato fijo." } ], "metrics": {}, diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48719.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48719.json index e4b6062bb95..73c6e5f0dc8 100644 --- a/CVE-2022/CVE-2022-487xx/CVE-2022-48719.json +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48719.json @@ -2,12 +2,16 @@ "id": "CVE-2022-48719", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-20T11:15:55.470", - "lastModified": "2024-06-20T11:15:55.470", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet, neigh: Do not trigger immediate probes on NUD_FAILED from neigh_managed_work\n\nsyzkaller was able to trigger a deadlock for NTF_MANAGED entries [0]:\n\n kworker/0:16/14617 is trying to acquire lock:\n ffffffff8d4dd370 (&tbl->lock){++-.}-{2:2}, at: ___neigh_create+0x9e1/0x2990 net/core/neighbour.c:652\n [...]\n but task is already holding lock:\n ffffffff8d4dd370 (&tbl->lock){++-.}-{2:2}, at: neigh_managed_work+0x35/0x250 net/core/neighbour.c:1572\n\nThe neighbor entry turned to NUD_FAILED state, where __neigh_event_send()\ntriggered an immediate probe as per commit cd28ca0a3dd1 (\"neigh: reduce\narp latency\") via neigh_probe() given table lock was held.\n\nOne option to fix this situation is to defer the neigh_probe() back to\nthe neigh_timer_handler() similarly as pre cd28ca0a3dd1. For the case\nof NTF_MANAGED, this deferral is acceptable given this only happens on\nactual failure state and regular / expected state is NUD_VALID with the\nentry already present.\n\nThe fix adds a parameter to __neigh_event_send() in order to communicate\nwhether immediate probe is allowed or disallowed. Existing call-sites\nof neigh_event_send() default as-is to immediate probe. However, the\nneigh_managed_work() disables it via use of neigh_event_send_probe().\n\n[0] \n __dump_stack lib/dump_stack.c:88 [inline]\n dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106\n print_deadlock_bug kernel/locking/lockdep.c:2956 [inline]\n check_deadlock kernel/locking/lockdep.c:2999 [inline]\n validate_chain kernel/locking/lockdep.c:3788 [inline]\n __lock_acquire.cold+0x149/0x3ab kernel/locking/lockdep.c:5027\n lock_acquire kernel/locking/lockdep.c:5639 [inline]\n lock_acquire+0x1ab/0x510 kernel/locking/lockdep.c:5604\n __raw_write_lock_bh include/linux/rwlock_api_smp.h:202 [inline]\n _raw_write_lock_bh+0x2f/0x40 kernel/locking/spinlock.c:334\n ___neigh_create+0x9e1/0x2990 net/core/neighbour.c:652\n ip6_finish_output2+0x1070/0x14f0 net/ipv6/ip6_output.c:123\n __ip6_finish_output net/ipv6/ip6_output.c:191 [inline]\n __ip6_finish_output+0x61e/0xe90 net/ipv6/ip6_output.c:170\n ip6_finish_output+0x32/0x200 net/ipv6/ip6_output.c:201\n NF_HOOK_COND include/linux/netfilter.h:296 [inline]\n ip6_output+0x1e4/0x530 net/ipv6/ip6_output.c:224\n dst_output include/net/dst.h:451 [inline]\n NF_HOOK include/linux/netfilter.h:307 [inline]\n ndisc_send_skb+0xa99/0x17f0 net/ipv6/ndisc.c:508\n ndisc_send_ns+0x3a9/0x840 net/ipv6/ndisc.c:650\n ndisc_solicit+0x2cd/0x4f0 net/ipv6/ndisc.c:742\n neigh_probe+0xc2/0x110 net/core/neighbour.c:1040\n __neigh_event_send+0x37d/0x1570 net/core/neighbour.c:1201\n neigh_event_send include/net/neighbour.h:470 [inline]\n neigh_managed_work+0x162/0x250 net/core/neighbour.c:1574\n process_one_work+0x9ac/0x1650 kernel/workqueue.c:2307\n worker_thread+0x657/0x1110 kernel/workqueue.c:2454\n kthread+0x2e9/0x3a0 kernel/kthread.c:377\n ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295\n " + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: net, neigh: no activar sondas inmediatas en NUD_FAILED desde neigh_managed_work syzkaller pudo activar un punto muerto para las entradas NTF_MANAGED [0]: kworker/0:16/14617 est\u00e1 intentando adquirir bloqueo: ffffffff8d4dd370 (&tbl->lock){++-.}-{2:2}, en: ___neigh_create+0x9e1/0x2990 net/core/neighbour.c:652 [...] pero la tarea ya mantiene el bloqueo: ffffffff8d4dd370 (&tbl->lock){++-.}-{2:2}, en: neigh_managed_work+0x35/0x250 net/core/neighbour.c:1572 La entrada del vecino pas\u00f3 al estado NUD_FAILED, donde __neigh_event_send() desencaden\u00f3 una Sondeo inmediato seg\u00fan el commit cd28ca0a3dd1 (\"relincho: reducir la latencia de arp\") a trav\u00e9s de neigh_probe() dado que se mantuvo el bloqueo de la tabla. Una opci\u00f3n para solucionar esta situaci\u00f3n es posponer neigh_probe() nuevamente a neigh_timer_handler() de manera similar a como se hac\u00eda antes de cd28ca0a3dd1. Para el caso de NTF_MANAGED, este aplazamiento es aceptable dado que esto solo ocurre en el estado de falla real y el estado normal/esperado es NUD_VALID con la entrada ya presente. La soluci\u00f3n agrega un par\u00e1metro a __neigh_event_send() para comunicar si se permite o no la sonda inmediata. Los sitios de llamadas existentes de neigh_event_send() est\u00e1n predeterminados tal cual para la investigaci\u00f3n inmediata. Sin embargo, neigh_managed_work() lo desactiva mediante el uso de neigh_event_send_probe(). [0] __dump_stack lib/dump_stack.c:88 [en l\u00ednea] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 print_deadlock_bug kernel/locking/lockdep.c:2956 [en l\u00ednea] check_deadlock kernel/locking/lockdep.c :2999 [en l\u00ednea] validar_chain kernel/locking/lockdep.c:3788 [en l\u00ednea] __lock_acquire.cold+0x149/0x3ab kernel/locking/lockdep.c:5027 lock_acquire kernel/locking/lockdep.c:5639 [en l\u00ednea] lock_acquire+0x1ab /0x510 kernel/locking/lockdep.c:5604 __raw_write_lock_bh include/linux/rwlock_api_smp.h:202 [en l\u00ednea] _raw_write_lock_bh+0x2f/0x40 kernel/locking/spinlock.c:334 ___neigh_create+0x9e1/0x2990 net/core/neighbour.c :652 ip6_finish_output2+0x1070/0x14f0 net/ipv6/ip6_output.c:123 __ip6_finish_output net/ipv6/ip6_output.c:191 [en l\u00ednea] __ip6_finish_output+0x61e/0xe90 net/ipv6/ip6_output.c:170 poner+0x32/0x200 neto/ ipv6/ip6_output.c:201 NF_HOOK_COND include/linux/netfilter.h:296 [en l\u00ednea] ip6_output+0x1e4/0x530 net/ipv6/ip6_output.c:224 dst_output include/net/dst.h:451 [en l\u00ednea] NF_HOOK include/ linux/netfilter.h:307 [en l\u00ednea] ndisc_send_skb+0xa99/0x17f0 net/ipv6/ndisc.c:508 ndisc_send_ns+0x3a9/0x840 net/ipv6/ndisc.c:650 ndisc_solicit+0x2cd/0x4f0 net/ipv6/ndisc.c :742 neigh_probe+0xc2/0x110 net/core/neighbour.c:1040 __neigh_event_send+0x37d/0x1570 net/core/neighbour.c:1201 neigh_event_send include/net/neighbour.h:470 [en l\u00ednea] neigh_managed_work+0x162/0x250 net/ core/neighbour.c:1574 Process_one_work+0x9ac/0x1650 kernel/workqueue.c:2307 trabajador_thread+0x657/0x1110 kernel/workqueue.c:2454 kthread+0x2e9/0x3a0 kernel/kthread.c:377 ret_from_fork+0x1f/0x30 arch/ x86/entry/entry_64.S:295 " } ], "metrics": {}, diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48720.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48720.json index c70e5b8b26a..63d2b41bb68 100644 --- a/CVE-2022/CVE-2022-487xx/CVE-2022-48720.json +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48720.json @@ -2,12 +2,16 @@ "id": "CVE-2022-48720", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-20T11:15:55.547", - "lastModified": "2024-06-20T11:15:55.547", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: macsec: Fix offload support for NETDEV_UNREGISTER event\n\nCurrent macsec netdev notify handler handles NETDEV_UNREGISTER event by\nreleasing relevant SW resources only, this causes resources leak in case\nof macsec HW offload, as the underlay driver was not notified to clean\nit's macsec offload resources.\n\nFix by calling the underlay driver to clean it's relevant resources\nby moving offload handling from macsec_dellink() to macsec_common_dellink()\nwhen handling NETDEV_UNREGISTER event." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: net: macsec: se corrigi\u00f3 el soporte de descarga para el evento NETDEV_UNREGISTER. El controlador de notificaci\u00f3n netdev de macsec actual maneja el evento NETDEV_UNREGISTER liberando solo recursos SW relevantes, lo que provoca una p\u00e9rdida de recursos en caso de descarga de HW de macsec, ya que No se notific\u00f3 al controlador subyacente que limpiara sus recursos de descarga de macsec. Para solucionarlo, llame al controlador subyacente para limpiar sus recursos relevantes moviendo el manejo de descarga de macsec_dellink() a macsec_common_dellink() cuando se maneja el evento NETDEV_UNREGISTER." } ], "metrics": {}, diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48721.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48721.json index 6f780c554f1..18363c159f7 100644 --- a/CVE-2022/CVE-2022-487xx/CVE-2022-48721.json +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48721.json @@ -2,12 +2,16 @@ "id": "CVE-2022-48721", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-20T11:15:55.620", - "lastModified": "2024-06-20T11:15:55.620", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/smc: Forward wakeup to smc socket waitqueue after fallback\n\nWhen we replace TCP with SMC and a fallback occurs, there may be\nsome socket waitqueue entries remaining in smc socket->wq, such\nas eppoll_entries inserted by userspace applications.\n\nAfter the fallback, data flows over TCP/IP and only clcsocket->wq\nwill be woken up. Applications can't be notified by the entries\nwhich were inserted in smc socket->wq before fallback. So we need\na mechanism to wake up smc socket->wq at the same time if some\nentries remaining in it.\n\nThe current workaround is to transfer the entries from smc socket->wq\nto clcsock->wq during the fallback. But this may cause a crash\nlike this:\n\n general protection fault, probably for non-canonical address 0xdead000000000100: 0000 [#1] PREEMPT SMP PTI\n CPU: 3 PID: 0 Comm: swapper/3 Kdump: loaded Tainted: G E 5.16.0+ #107\n RIP: 0010:__wake_up_common+0x65/0x170\n Call Trace:\n \n __wake_up_common_lock+0x7a/0xc0\n sock_def_readable+0x3c/0x70\n tcp_data_queue+0x4a7/0xc40\n tcp_rcv_established+0x32f/0x660\n ? sk_filter_trim_cap+0xcb/0x2e0\n tcp_v4_do_rcv+0x10b/0x260\n tcp_v4_rcv+0xd2a/0xde0\n ip_protocol_deliver_rcu+0x3b/0x1d0\n ip_local_deliver_finish+0x54/0x60\n ip_local_deliver+0x6a/0x110\n ? tcp_v4_early_demux+0xa2/0x140\n ? tcp_v4_early_demux+0x10d/0x140\n ip_sublist_rcv_finish+0x49/0x60\n ip_sublist_rcv+0x19d/0x230\n ip_list_rcv+0x13e/0x170\n __netif_receive_skb_list_core+0x1c2/0x240\n netif_receive_skb_list_internal+0x1e6/0x320\n napi_complete_done+0x11d/0x190\n mlx5e_napi_poll+0x163/0x6b0 [mlx5_core]\n __napi_poll+0x3c/0x1b0\n net_rx_action+0x27c/0x300\n __do_softirq+0x114/0x2d2\n irq_exit_rcu+0xb4/0xe0\n common_interrupt+0xba/0xe0\n \n \n\nThe crash is caused by privately transferring waitqueue entries from\nsmc socket->wq to clcsock->wq. The owners of these entries, such as\nepoll, have no idea that the entries have been transferred to a\ndifferent socket wait queue and still use original waitqueue spinlock\n(smc socket->wq.wait.lock) to make the entries operation exclusive,\nbut it doesn't work. The operations to the entries, such as removing\nfrom the waitqueue (now is clcsock->wq after fallback), may cause a\ncrash when clcsock waitqueue is being iterated over at the moment.\n\nThis patch tries to fix this by no longer transferring wait queue\nentries privately, but introducing own implementations of clcsock's\ncallback functions in fallback situation. The callback functions will\nforward the wakeup to smc socket->wq if clcsock->wq is actually woken\nup and smc socket->wq has remaining entries." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: net/smc: Reenviar activaci\u00f3n a la cola de espera del socket smc despu\u00e9s del respaldo Cuando reemplazamos TCP con SMC y se produce un respaldo, es posible que queden algunas entradas de la cola de espera del socket en el socket smc->wq. como eppoll_entries insertados por aplicaciones de espacio de usuario. Despu\u00e9s del respaldo, los datos fluyen a trav\u00e9s de TCP/IP y solo se activar\u00e1 clcsocket->wq. Las aplicaciones no pueden ser notificadas por las entradas que se insertaron en smc socket->wq antes del respaldo. Entonces necesitamos un mecanismo para activar smc socket->wq al mismo tiempo si quedan algunas entradas en \u00e9l. La soluci\u00f3n actual es transferir las entradas de smc socket->wq a clcsock->wq durante el respaldo. Pero esto puede causar un fallo como este: fallo de protecci\u00f3n general, probablemente para la direcci\u00f3n no can\u00f3nica 0xdead000000000100: 0000 [#1] PREEMPT SMP PTI CPU: 3 PID: 0 Comm: swapper/3 Kdump: cargado Contaminado: GE 5.16.0+ #107 RIP: 0010:__wake_up_common+0x65/0x170 Seguimiento de llamadas: __wake_up_common_lock+0x7a/0xc0 sock_def_readable+0x3c/0x70 tcp_data_queue+0x4a7/0xc40 tcp_rcv_establecido+0x32f/0x660 ? sk_filter_trim_cap+0xcb/0x2e0 tcp_v4_do_rcv+0x10b/0x260 tcp_v4_rcv+0xd2a/0xde0 ip_protocol_deliver_rcu+0x3b/0x1d0 ip_local_deliver_finish+0x54/0x60 0 ? tcp_v4_early_demux+0xa2/0x140? tcp_v4_early_demux+0x10d/0x140 ip_sublist_rcv_finish+0x49/0x60 ip_sublist_rcv+0x19d/0x230 ip_list_rcv+0x13e/0x170 __netif_receive_skb_list_core+0x1c2/0x240 netif_receive_skb_list_ interno+0x1e6/0x320 napi_complete_done+0x11d/0x190 mlx5e_napi_poll+0x163/0x6b0 [mlx5_core] __napi_poll+0x3c/0x1b0 net_rx_action+ 0x27c/0x300 __do_softirq+0x114/0x2d2 irq_exit_rcu+0xb4/0xe0 common_interrupt+0xba/0xe0 El bloqueo se debe a la transferencia privada de entradas de la cola de espera desde smc socket->wq a clcsock->wq. Los propietarios de estas entradas, como epoll, no tienen idea de que las entradas se han transferido a una cola de espera de socket diferente y a\u00fan usan el spinlock de cola de espera original (smc socket->wq.wait.lock) para que la operaci\u00f3n de entradas sea exclusiva, pero no funciona. Las operaciones realizadas en las entradas, como la eliminaci\u00f3n de la cola de espera (ahora es clcsock->wq despu\u00e9s del respaldo), pueden causar un bloqueo cuando se est\u00e1 iterando sobre la cola de espera de clcsock en este momento. Este parche intenta solucionar este problema al no transferir las entradas de la cola de espera de forma privada, sino al introducir implementaciones propias de las funciones de devoluci\u00f3n de llamada de clcsock en situaciones de reserva. Las funciones de devoluci\u00f3n de llamada reenviar\u00e1n la activaci\u00f3n a smc socket->wq si clcsock->wq realmente se activa y smc socket->wq tiene entradas restantes." } ], "metrics": {}, diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48722.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48722.json index e6ec0fba645..8b52503b212 100644 --- a/CVE-2022/CVE-2022-487xx/CVE-2022-48722.json +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48722.json @@ -2,12 +2,16 @@ "id": "CVE-2022-48722", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-20T11:15:55.733", - "lastModified": "2024-06-20T11:15:55.733", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: ieee802154: ca8210: Stop leaking skb's\n\nUpon error the ieee802154_xmit_complete() helper is not called. Only\nieee802154_wake_queue() is called manually. We then leak the skb\nstructure.\n\nFree the skb structure upon error before returning." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: net: ieee802154: ca8210: Detener la fuga de skb. En caso de error, no se llama al asistente ieee802154_xmit_complete(). S\u00f3lo se llama manualmente a ieee802154_wake_queue(). Luego filtramos la estructura skb. Libere la estructura skb en caso de error antes de regresar." } ], "metrics": {}, diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48723.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48723.json index c4c9e829082..9d00374c5ff 100644 --- a/CVE-2022/CVE-2022-487xx/CVE-2022-48723.json +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48723.json @@ -2,12 +2,16 @@ "id": "CVE-2022-48723", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-20T11:15:55.820", - "lastModified": "2024-06-20T11:15:55.820", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nspi: uniphier: fix reference count leak in uniphier_spi_probe()\n\nThe issue happens in several error paths in uniphier_spi_probe().\nWhen either dma_get_slave_caps() or devm_spi_register_master() returns\nan error code, the function forgets to decrease the refcount of both\n`dma_rx` and `dma_tx` objects, which may lead to refcount leaks.\n\nFix it by decrementing the reference count of specific objects in\nthose error paths." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: spi: uniphier: corrige la fuga del recuento de referencias en uniphier_spi_probe() El problema ocurre en varias rutas de error en uniphier_spi_probe(). Cuando dma_get_slave_caps() o devm_spi_register_master() devuelven un c\u00f3digo de error, la funci\u00f3n se olvida de disminuir el recuento de los objetos `dma_rx` y `dma_tx`, lo que puede provocar fugas de recuento. Corr\u00edjalo disminuyendo el recuento de referencias de objetos espec\u00edficos en esas rutas de error." } ], "metrics": {}, diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48724.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48724.json new file mode 100644 index 00000000000..ced1cd0aebe --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48724.json @@ -0,0 +1,44 @@ +{ + "id": "CVE-2022-48724", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:10.900", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\niommu/vt-d: Fix potential memory leak in intel_setup_irq_remapping()\n\nAfter commit e3beca48a45b (\"irqdomain/treewide: Keep firmware node\nunconditionally allocated\"). For tear down scenario, fn is only freed\nafter fail to allocate ir_domain, though it also should be freed in case\ndmar_enable_qi returns error.\n\nBesides free fn, irq_domain and ir_msi_domain need to be removed as well\nif intel_setup_irq_remapping fails to enable queued invalidation.\n\nImprove the rewinding path by add out_free_ir_domain and out_free_fwnode\nlables per Baolu's suggestion." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/336d096b62bdc673e852b6b80d5072d7888ce85d", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/5c43d46daa0d2928234dd2792ebebc35d29ee2d1", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/99e675d473eb8cf2deac1376a0f840222fc1adcf", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/9d9995b0371e4e8c18d4f955479e5d47efe7b2d4", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/a0c685ba99961b1dd894b2e470e692a539770f6d", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/a31cb1f0fb6caf46ffe88c41252b6b7a4ee062d9", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/b62eceb5f8f08815fe3f945fc55bbf997c344ecd", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48725.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48725.json new file mode 100644 index 00000000000..fdfd7c9615c --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48725.json @@ -0,0 +1,28 @@ +{ + "id": "CVE-2022-48725", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:10.997", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/siw: Fix refcounting leak in siw_create_qp()\n\nThe atomic_inc() needs to be paired with an atomic_dec() on the error\npath." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/2989ba9532babac66e79997ccff73c015b69700c", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/a75badebfdc0b3823054bedf112edb54d6357c75", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/fa3b844a50845c817660146c27c0fc29b08d3116", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48726.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48726.json new file mode 100644 index 00000000000..818b38b6608 --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48726.json @@ -0,0 +1,32 @@ +{ + "id": "CVE-2022-48726", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:11.077", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/ucma: Protect mc during concurrent multicast leaves\n\nPartially revert the commit mentioned in the Fixes line to make sure that\nallocation and erasing multicast struct are locked.\n\n BUG: KASAN: use-after-free in ucma_cleanup_multicast drivers/infiniband/core/ucma.c:491 [inline]\n BUG: KASAN: use-after-free in ucma_destroy_private_ctx+0x914/0xb70 drivers/infiniband/core/ucma.c:579\n Read of size 8 at addr ffff88801bb74b00 by task syz-executor.1/25529\n CPU: 0 PID: 25529 Comm: syz-executor.1 Not tainted 5.16.0-rc7-syzkaller #0\n Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011\n Call Trace:\n __dump_stack lib/dump_stack.c:88 [inline]\n dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106\n print_address_description.constprop.0.cold+0x8d/0x320 mm/kasan/report.c:247\n __kasan_report mm/kasan/report.c:433 [inline]\n kasan_report.cold+0x83/0xdf mm/kasan/report.c:450\n ucma_cleanup_multicast drivers/infiniband/core/ucma.c:491 [inline]\n ucma_destroy_private_ctx+0x914/0xb70 drivers/infiniband/core/ucma.c:579\n ucma_destroy_id+0x1e6/0x280 drivers/infiniband/core/ucma.c:614\n ucma_write+0x25c/0x350 drivers/infiniband/core/ucma.c:1732\n vfs_write+0x28e/0xae0 fs/read_write.c:588\n ksys_write+0x1ee/0x250 fs/read_write.c:643\n do_syscall_x64 arch/x86/entry/common.c:50 [inline]\n do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80\n entry_SYSCALL_64_after_hwframe+0x44/0xae\n\nCurrently the xarray search can touch a concurrently freeing mc as the\nxa_for_each() is not surrounded by any lock. Rather than hold the lock for\na full scan hold it only for the effected items, which is usually an empty\nlist." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/2923948ffe0835f7114e948b35bcc42bc9b3baa1", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/36e8169ec973359f671f9ec7213547059cae972e", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/75c610212b9f1756b9384911d3a2c347eee8031c", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/ee2477e8ccd3d978eeac0dc5a981b286d9bb7b0a", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48727.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48727.json new file mode 100644 index 00000000000..7ef91599659 --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48727.json @@ -0,0 +1,28 @@ +{ + "id": "CVE-2022-48727", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:11.167", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: arm64: Avoid consuming a stale esr value when SError occur\n\nWhen any exception other than an IRQ occurs, the CPU updates the ESR_EL2\nregister with the exception syndrome. An SError may also become pending,\nand will be synchronised by KVM. KVM notes the exception type, and whether\nan SError was synchronised in exit_code.\n\nWhen an exception other than an IRQ occurs, fixup_guest_exit() updates\nvcpu->arch.fault.esr_el2 from the hardware register. When an SError was\nsynchronised, the vcpu esr value is used to determine if the exception\nwas due to an HVC. If so, ELR_EL2 is moved back one instruction. This\nis so that KVM can process the SError first, and re-execute the HVC if\nthe guest survives the SError.\n\nBut if an IRQ synchronises an SError, the vcpu's esr value is stale.\nIf the previous non-IRQ exception was an HVC, KVM will corrupt ELR_EL2,\ncausing an unrelated guest instruction to be executed twice.\n\nCheck ARM_EXCEPTION_CODE() before messing with ELR_EL2, IRQs don't\nupdate this register so don't need to check." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/1c71dbc8a179d99dd9bb7e7fc1888db613cf85de", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/57e2986c3b25092691a6e3d6ee9168caf8978932", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/e1e852746997500f1873f60b954da5f02cc2dba3", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48728.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48728.json new file mode 100644 index 00000000000..a3d5ec51065 --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48728.json @@ -0,0 +1,32 @@ +{ + "id": "CVE-2022-48728", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:11.253", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nIB/hfi1: Fix AIP early init panic\n\nAn early failure in hfi1_ipoib_setup_rn() can lead to the following panic:\n\n BUG: unable to handle kernel NULL pointer dereference at 00000000000001b0\n PGD 0 P4D 0\n Oops: 0002 [#1] SMP NOPTI\n Workqueue: events work_for_cpu_fn\n RIP: 0010:try_to_grab_pending+0x2b/0x140\n Code: 1f 44 00 00 41 55 41 54 55 48 89 d5 53 48 89 fb 9c 58 0f 1f 44 00 00 48 89 c2 fa 66 0f 1f 44 00 00 48 89 55 00 40 84 f6 75 77 48 0f ba 2b 00 72 09 31 c0 5b 5d 41 5c 41 5d c3 48 89 df e8 6c\n RSP: 0018:ffffb6b3cf7cfa48 EFLAGS: 00010046\n RAX: 0000000000000246 RBX: 00000000000001b0 RCX: 0000000000000000\n RDX: 0000000000000246 RSI: 0000000000000000 RDI: 00000000000001b0\n RBP: ffffb6b3cf7cfa70 R08: 0000000000000f09 R09: 0000000000000001\n R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000000\n R13: ffffb6b3cf7cfa90 R14: ffffffff9b2fbfc0 R15: ffff8a4fdf244690\n FS: 0000000000000000(0000) GS:ffff8a527f400000(0000) knlGS:0000000000000000\n CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 00000000000001b0 CR3: 00000017e2410003 CR4: 00000000007706f0\n DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n PKRU: 55555554\n Call Trace:\n __cancel_work_timer+0x42/0x190\n ? dev_printk_emit+0x4e/0x70\n iowait_cancel_work+0x15/0x30 [hfi1]\n hfi1_ipoib_txreq_deinit+0x5a/0x220 [hfi1]\n ? dev_err+0x6c/0x90\n hfi1_ipoib_netdev_dtor+0x15/0x30 [hfi1]\n hfi1_ipoib_setup_rn+0x10e/0x150 [hfi1]\n rdma_init_netdev+0x5a/0x80 [ib_core]\n ? hfi1_ipoib_free_rdma_netdev+0x20/0x20 [hfi1]\n ipoib_intf_init+0x6c/0x350 [ib_ipoib]\n ipoib_intf_alloc+0x5c/0xc0 [ib_ipoib]\n ipoib_add_one+0xbe/0x300 [ib_ipoib]\n add_client_context+0x12c/0x1a0 [ib_core]\n enable_device_and_get+0xdc/0x1d0 [ib_core]\n ib_register_device+0x572/0x6b0 [ib_core]\n rvt_register_device+0x11b/0x220 [rdmavt]\n hfi1_register_ib_device+0x6b4/0x770 [hfi1]\n do_init_one.isra.20+0x3e3/0x680 [hfi1]\n local_pci_probe+0x41/0x90\n work_for_cpu_fn+0x16/0x20\n process_one_work+0x1a7/0x360\n ? create_worker+0x1a0/0x1a0\n worker_thread+0x1cf/0x390\n ? create_worker+0x1a0/0x1a0\n kthread+0x116/0x130\n ? kthread_flush_work_fn+0x10/0x10\n ret_from_fork+0x1f/0x40\n\nThe panic happens in hfi1_ipoib_txreq_deinit() because there is a NULL\nderef when hfi1_ipoib_netdev_dtor() is called in this error case.\n\nhfi1_ipoib_txreq_init() and hfi1_ipoib_rxq_init() are self unwinding so\nfix by adjusting the error paths accordingly.\n\nOther changes:\n- hfi1_ipoib_free_rdma_netdev() is deleted including the free_netdev()\n since the netdev core code deletes calls free_netdev()\n- The switch to the accelerated entrances is moved to the success path." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/1899c3cad265c4583658aed5293d02e8af84276b", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/4a9bd1e6780fc59f81466ec3489d5ad535a37190", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/5f8f55b92edd621f056bdf09e572092849fabd83", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/a3dd4d2682f2a796121609e5f3bbeb1243198c53", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48729.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48729.json new file mode 100644 index 00000000000..1e71c5adc85 --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48729.json @@ -0,0 +1,24 @@ +{ + "id": "CVE-2022-48729", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:11.343", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nIB/hfi1: Fix panic with larger ipoib send_queue_size\n\nWhen the ipoib send_queue_size is increased from the default the following\npanic happens:\n\n RIP: 0010:hfi1_ipoib_drain_tx_ring+0x45/0xf0 [hfi1]\n Code: 31 e4 eb 0f 8b 85 c8 02 00 00 41 83 c4 01 44 39 e0 76 60 8b 8d cc 02 00 00 44 89 e3 be 01 00 00 00 d3 e3 48 03 9d c0 02 00 00 83 18 01 00 00 00 00 00 00 48 8b bb 30 01 00 00 e8 25 af a7 e0\n RSP: 0018:ffffc9000798f4a0 EFLAGS: 00010286\n RAX: 0000000000008000 RBX: ffffc9000aa0f000 RCX: 000000000000000f\n RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000\n RBP: ffff88810ff08000 R08: ffff88889476d900 R09: 0000000000000101\n R10: 0000000000000000 R11: ffffc90006590ff8 R12: 0000000000000200\n R13: ffffc9000798fba8 R14: 0000000000000000 R15: 0000000000000001\n FS: 00007fd0f79cc3c0(0000) GS:ffff88885fb00000(0000) knlGS:0000000000000000\n CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: ffffc9000aa0f118 CR3: 0000000889c84001 CR4: 00000000001706e0\n Call Trace:\n \n hfi1_ipoib_napi_tx_disable+0x45/0x60 [hfi1]\n hfi1_ipoib_dev_stop+0x18/0x80 [hfi1]\n ipoib_ib_dev_stop+0x1d/0x40 [ib_ipoib]\n ipoib_stop+0x48/0xc0 [ib_ipoib]\n __dev_close_many+0x9e/0x110\n __dev_change_flags+0xd9/0x210\n dev_change_flags+0x21/0x60\n do_setlink+0x31c/0x10f0\n ? __nla_validate_parse+0x12d/0x1a0\n ? __nla_parse+0x21/0x30\n ? inet6_validate_link_af+0x5e/0xf0\n ? cpumask_next+0x1f/0x20\n ? __snmp6_fill_stats64.isra.53+0xbb/0x140\n ? __nla_validate_parse+0x47/0x1a0\n __rtnl_newlink+0x530/0x910\n ? pskb_expand_head+0x73/0x300\n ? __kmalloc_node_track_caller+0x109/0x280\n ? __nla_put+0xc/0x20\n ? cpumask_next_and+0x20/0x30\n ? update_sd_lb_stats.constprop.144+0xd3/0x820\n ? _raw_spin_unlock_irqrestore+0x25/0x37\n ? __wake_up_common_lock+0x87/0xc0\n ? kmem_cache_alloc_trace+0x3d/0x3d0\n rtnl_newlink+0x43/0x60\n\nThe issue happens when the shift that should have been a function of the\ntxq item size mistakenly used the ring size.\n\nFix by using the item size." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/1530d84fba1e459ba55f46aa42649b88773210e7", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/8c83d39cc730378bbac64d67a551897b203a606e", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48730.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48730.json new file mode 100644 index 00000000000..b1bd019c8a2 --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48730.json @@ -0,0 +1,32 @@ +{ + "id": "CVE-2022-48730", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:11.430", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndma-buf: heaps: Fix potential spectre v1 gadget\n\nIt appears like nr could be a Spectre v1 gadget as it's supplied by a\nuser and used as an array index. Prevent the contents\nof kernel memory from being leaked to userspace via speculative\nexecution by using array_index_nospec.\n\n [sumits: added fixes and cc: stable tags]" + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/24f8e12d965b24f8aea762589e0e9fe2025c005e", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/5d40f1bdad3dd1a177f21a90ad4353c1ed40ba3a", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/92c4cfaee6872038563c5b6f2e8e613f9d84d47d", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/cc8f7940d9c2d45f67b3d1a2f2b7a829ca561bed", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48731.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48731.json new file mode 100644 index 00000000000..f5772e124b7 --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48731.json @@ -0,0 +1,36 @@ +{ + "id": "CVE-2022-48731", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:11.517", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/kmemleak: avoid scanning potential huge holes\n\nWhen using devm_request_free_mem_region() and devm_memremap_pages() to\nadd ZONE_DEVICE memory, if requested free mem region's end pfn were\nhuge(e.g., 0x400000000), the node_end_pfn() will be also huge (see\nmove_pfn_range_to_zone()). Thus it creates a huge hole between\nnode_start_pfn() and node_end_pfn().\n\nWe found on some AMD APUs, amdkfd requested such a free mem region and\ncreated a huge hole. In such a case, following code snippet was just\ndoing busy test_bit() looping on the huge hole.\n\n for (pfn = start_pfn; pfn < end_pfn; pfn++) {\n\tstruct page *page = pfn_to_online_page(pfn);\n\t\tif (!page)\n\t\t\tcontinue;\n\t...\n }\n\nSo we got a soft lockup:\n\n watchdog: BUG: soft lockup - CPU#6 stuck for 26s! [bash:1221]\n CPU: 6 PID: 1221 Comm: bash Not tainted 5.15.0-custom #1\n RIP: 0010:pfn_to_online_page+0x5/0xd0\n Call Trace:\n ? kmemleak_scan+0x16a/0x440\n kmemleak_write+0x306/0x3a0\n ? common_file_perm+0x72/0x170\n full_proxy_write+0x5c/0x90\n vfs_write+0xb9/0x260\n ksys_write+0x67/0xe0\n __x64_sys_write+0x1a/0x20\n do_syscall_64+0x3b/0xc0\n entry_SYSCALL_64_after_hwframe+0x44/0xae\n\nI did some tests with the patch.\n\n(1) amdgpu module unloaded\n\nbefore the patch:\n\n real 0m0.976s\n user 0m0.000s\n sys 0m0.968s\n\nafter the patch:\n\n real 0m0.981s\n user 0m0.000s\n sys 0m0.973s\n\n(2) amdgpu module loaded\n\nbefore the patch:\n\n real 0m35.365s\n user 0m0.000s\n sys 0m35.354s\n\nafter the patch:\n\n real 0m1.049s\n user 0m0.000s\n sys 0m1.042s" + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/352715593e81b917ce1b321e794549815b850134", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/a5389c80992f0001ee505838fe6a8b20897ce96e", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/c10a0f877fe007021d70f9cada240f42adc2b5db", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/cebb0aceb21ad91429617a40e3a17444fabf1529", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/d3533ee20e9a0e2e8f60384da7450d43d1c63d1a", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48732.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48732.json new file mode 100644 index 00000000000..10e0fa9e150 --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48732.json @@ -0,0 +1,48 @@ +{ + "id": "CVE-2022-48732", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:11.607", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/nouveau: fix off by one in BIOS boundary checking\n\nBounds checking when parsing init scripts embedded in the BIOS reject\naccess to the last byte. This causes driver initialization to fail on\nApple eMac's with GeForce 2 MX GPUs, leaving the system with no working\nconsole.\n\nThis is probably only seen on OpenFirmware machines like PowerPC Macs\nbecause the BIOS image provided by OF is only the used parts of the ROM,\nnot a power-of-two blocks read from PCI directly so PCs always have\nempty bytes at the end that are never accessed." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/1b777d4d9e383d2744fc9b3a09af6ec1893c8b1a", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/909d3ec1bf9f0ec534bfc081b77c0836fea7b0e2", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/acc887ba88333f5fec49631f12d8cc7ebd95781c", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/b2a21669ee98aafc41c6d42ef15af4dab9e6e882", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/d4b746e60fd8eaa8016e144223abe91158edcdad", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/d877e814a62b7de9069aeff8bc1d979dfc996e06", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/e7c36fa8a1e63b08312162179c78a0c7795ea369", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/f071d9fa857582d7bd77f4906691f73d3edeab73", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48733.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48733.json new file mode 100644 index 00000000000..692f51fc5a3 --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48733.json @@ -0,0 +1,28 @@ +{ + "id": "CVE-2022-48733", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:11.700", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: fix use-after-free after failure to create a snapshot\n\nAt ioctl.c:create_snapshot(), we allocate a pending snapshot structure and\nthen attach it to the transaction's list of pending snapshots. After that\nwe call btrfs_commit_transaction(), and if that returns an error we jump\nto 'fail' label, where we kfree() the pending snapshot structure. This can\nresult in a later use-after-free of the pending snapshot:\n\n1) We allocated the pending snapshot and added it to the transaction's\n list of pending snapshots;\n\n2) We call btrfs_commit_transaction(), and it fails either at the first\n call to btrfs_run_delayed_refs() or btrfs_start_dirty_block_groups().\n In both cases, we don't abort the transaction and we release our\n transaction handle. We jump to the 'fail' label and free the pending\n snapshot structure. We return with the pending snapshot still in the\n transaction's list;\n\n3) Another task commits the transaction. This time there's no error at\n all, and then during the transaction commit it accesses a pointer\n to the pending snapshot structure that the snapshot creation task\n has already freed, resulting in a user-after-free.\n\nThis issue could actually be detected by smatch, which produced the\nfollowing warning:\n\n fs/btrfs/ioctl.c:843 create_snapshot() warn: '&pending_snapshot->list' not removed from list\n\nSo fix this by not having the snapshot creation ioctl directly add the\npending snapshot to the transaction's list. Instead add the pending\nsnapshot to the transaction handle, and then at btrfs_commit_transaction()\nwe add the snapshot to the list only when we can guarantee that any error\nreturned after that point will result in a transaction abort, in which\ncase the ioctl code can safely free the pending snapshot and no one can\naccess it anymore." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/28b21c558a3753171097193b6f6602a94169093a", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/9372fa1d73da5f1673921e365d0cd2c27ec7adc2", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/a7b717fa15165d3d9245614680bebc48a52ac05d", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48734.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48734.json new file mode 100644 index 00000000000..63d8eef5520 --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48734.json @@ -0,0 +1,36 @@ +{ + "id": "CVE-2022-48734", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:11.797", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: fix deadlock between quota disable and qgroup rescan worker\n\nQuota disable ioctl starts a transaction before waiting for the qgroup\nrescan worker completes. However, this wait can be infinite and results\nin deadlock because of circular dependency among the quota disable\nioctl, the qgroup rescan worker and the other task with transaction such\nas block group relocation task.\n\nThe deadlock happens with the steps following:\n\n1) Task A calls ioctl to disable quota. It starts a transaction and\n waits for qgroup rescan worker completes.\n2) Task B such as block group relocation task starts a transaction and\n joins to the transaction that task A started. Then task B commits to\n the transaction. In this commit, task B waits for a commit by task A.\n3) Task C as the qgroup rescan worker starts its job and starts a\n transaction. In this transaction start, task C waits for completion\n of the transaction that task A started and task B committed.\n\nThis deadlock was found with fstests test case btrfs/115 and a zoned\nnull_blk device. The test case enables and disables quota, and the\nblock group reclaim was triggered during the quota disable by chance.\nThe deadlock was also observed by running quota enable and disable in\nparallel with 'btrfs balance' command on regular null_blk devices.\n\nAn example report of the deadlock:\n\n [372.469894] INFO: task kworker/u16:6:103 blocked for more than 122 seconds.\n [372.479944] Not tainted 5.16.0-rc8 #7\n [372.485067] \"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\" disables this message.\n [372.493898] task:kworker/u16:6 state:D stack: 0 pid: 103 ppid: 2 flags:0x00004000\n [372.503285] Workqueue: btrfs-qgroup-rescan btrfs_work_helper [btrfs]\n [372.510782] Call Trace:\n [372.514092] \n [372.521684] __schedule+0xb56/0x4850\n [372.530104] ? io_schedule_timeout+0x190/0x190\n [372.538842] ? lockdep_hardirqs_on+0x7e/0x100\n [372.547092] ? _raw_spin_unlock_irqrestore+0x3e/0x60\n [372.555591] schedule+0xe0/0x270\n [372.561894] btrfs_commit_transaction+0x18bb/0x2610 [btrfs]\n [372.570506] ? btrfs_apply_pending_changes+0x50/0x50 [btrfs]\n [372.578875] ? free_unref_page+0x3f2/0x650\n [372.585484] ? finish_wait+0x270/0x270\n [372.591594] ? release_extent_buffer+0x224/0x420 [btrfs]\n [372.599264] btrfs_qgroup_rescan_worker+0xc13/0x10c0 [btrfs]\n [372.607157] ? lock_release+0x3a9/0x6d0\n [372.613054] ? btrfs_qgroup_account_extent+0xda0/0xda0 [btrfs]\n [372.620960] ? do_raw_spin_lock+0x11e/0x250\n [372.627137] ? rwlock_bug.part.0+0x90/0x90\n [372.633215] ? lock_is_held_type+0xe4/0x140\n [372.639404] btrfs_work_helper+0x1ae/0xa90 [btrfs]\n [372.646268] process_one_work+0x7e9/0x1320\n [372.652321] ? lock_release+0x6d0/0x6d0\n [372.658081] ? pwq_dec_nr_in_flight+0x230/0x230\n [372.664513] ? rwlock_bug.part.0+0x90/0x90\n [372.670529] worker_thread+0x59e/0xf90\n [372.676172] ? process_one_work+0x1320/0x1320\n [372.682440] kthread+0x3b9/0x490\n [372.687550] ? _raw_spin_unlock_irq+0x24/0x50\n [372.693811] ? set_kthread_struct+0x100/0x100\n [372.700052] ret_from_fork+0x22/0x30\n [372.705517] \n [372.709747] INFO: task btrfs-transacti:2347 blocked for more than 123 seconds.\n [372.729827] Not tainted 5.16.0-rc8 #7\n [372.745907] \"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\" disables this message.\n [372.767106] task:btrfs-transacti state:D stack: 0 pid: 2347 ppid: 2 flags:0x00004000\n [372.787776] Call Trace:\n [372.801652] \n [372.812961] __schedule+0xb56/0x4850\n [372.830011] ? io_schedule_timeout+0x190/0x190\n [372.852547] ? lockdep_hardirqs_on+0x7e/0x100\n [372.871761] ? _raw_spin_unlock_irqrestore+0x3e/0x60\n [372.886792] schedule+0xe0/0x270\n [372.901685] wait_current_trans+0x22c/0x310 [btrfs]\n [372.919743] ? btrfs_put_transaction+0x3d0/0x3d0 [btrfs]\n [372.938923] ? finish_wait+0x270/0x270\n [372.959085] ? join_transaction+0xc7\n---truncated---" + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/26b3901d20bf9da2c6a00cb1fb48932166f80a45", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/31198e58c09e21d4f65c49d2361f76b87aca4c3f", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/32747e01436aac8ef93fe85b5b523b4f3b52f040", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/89d4cca583fc9594ee7d1a0bc986886d6fb587e6", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/e804861bd4e69cc5fe1053eedcb024982dde8e48", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48735.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48735.json new file mode 100644 index 00000000000..89883b99864 --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48735.json @@ -0,0 +1,32 @@ +{ + "id": "CVE-2022-48735", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:11.890", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nALSA: hda: Fix UAF of leds class devs at unbinding\n\nThe LED class devices that are created by HD-audio codec drivers are\nregistered via devm_led_classdev_register() and associated with the\nHD-audio codec device. Unfortunately, it turned out that the devres\nrelease doesn't work for this case; namely, since the codec resource\nrelease happens before the devm call chain, it triggers a NULL\ndereference or a UAF for a stale set_brightness_delay callback.\n\nFor fixing the bug, this patch changes the LED class device register\nand unregister in a manual manner without devres, keeping the\ninstances in hda_gen_spec." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/0e629052f013eeb61494d4df2f1f647c2a9aef47", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/549f8ffc7b2f7561bea7f90930b6c5104318e87b", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/813e9f3e06d22e29872d4fd51b54992d89cf66c8", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/a7de1002135cf94367748ffc695a29812d7633b5", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48736.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48736.json new file mode 100644 index 00000000000..d394bd121e7 --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48736.json @@ -0,0 +1,48 @@ +{ + "id": "CVE-2022-48736", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:11.973", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nASoC: ops: Reject out of bounds values in snd_soc_put_xr_sx()\n\nWe don't currently validate that the values being set are within the range\nwe advertised to userspace as being valid, do so and reject any values\nthat are out of range." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/17e16a66b4f9a310713d8599e6e1ca4a0c9fd28c", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/4cf28e9ae6e2e11a044be1bcbcfa1b0d8675fe4d", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/54abca038e287d3746dd40016514670a7f654c5c", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/6877f87579ed830f9ff6d478539074f035d04bfb", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/7659f25a80e6affb784b690df8994b79b4212fd4", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/b0a7836ecf1345814a7d8ef748fb797c520dad18", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/e09cf398e8c6db69c620b6d8073abc4377a07af5", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/fd9a23319f16e7031f0d8c98eed6e093c2927229", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48737.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48737.json new file mode 100644 index 00000000000..b10031637ab --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48737.json @@ -0,0 +1,48 @@ +{ + "id": "CVE-2022-48737", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:12.060", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nASoC: ops: Reject out of bounds values in snd_soc_put_volsw_sx()\n\nWe don't currently validate that the values being set are within the range\nwe advertised to userspace as being valid, do so and reject any values\nthat are out of range." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/038f8b7caa74d29e020949a43ca368c93f6b29b9", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/4977491e4b3aad8567f57e2a9992d251410c1db3", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/4f1e50d6a9cf9c1b8c859d449b5031cacfa8404e", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/9a12fcbf3c622f9bf6b110a873d62b0cba93972e", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/9e5c40b5706d8aae2cf70bd7e01f0b4575a642d0", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/c33402b056de61104b6146dedbe138ca8d7ec62b", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/e8e07c5e25a29e2a6f119fd947f55d7a55eb8a13", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/ef6cd9eeb38062a145802b7b56be7ae1090e165e", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48738.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48738.json new file mode 100644 index 00000000000..f44544517fb --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48738.json @@ -0,0 +1,48 @@ +{ + "id": "CVE-2022-48738", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:12.150", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nASoC: ops: Reject out of bounds values in snd_soc_put_volsw()\n\nWe don't currently validate that the values being set are within the range\nwe advertised to userspace as being valid, do so and reject any values\nthat are out of range." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/40f598698129b5ceaf31012f9501b775c7b6e57d", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/586ef863c94354a7e00e5ae5ef01443d1dc99bc7", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/65a61b1f56f5386486757930069fbdce94af08bf", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/68fd718724284788fc5f379e0b7cac541429ece7", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/817f7c9335ec01e0f5e8caffc4f1dcd5e458a4c0", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/9e8895f1b3d4433f6d78aa6578e9db61ca6e6830", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/a9394f21fba027147bf275b083c77955864c366a", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/bb72d2dda85564c66d909108ea6903937a41679d", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48739.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48739.json new file mode 100644 index 00000000000..50935c68a01 --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48739.json @@ -0,0 +1,28 @@ +{ + "id": "CVE-2022-48739", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:12.243", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nASoC: hdmi-codec: Fix OOB memory accesses\n\nCorrect size of iec_status array by changing it to the size of status\narray of the struct snd_aes_iec958. This fixes out-of-bounds slab\nread accesses made by memcpy() of the hdmi-codec driver. This problem\nis reported by KASAN." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/06feec6005c9d9500cd286ec440aabf8b2ddd94d", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/10007bd96b6c4c3cfaea9e76c311b06a07a5e260", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/1552e66be325a21d7eff49f46013fb402165a0ac", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48740.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48740.json new file mode 100644 index 00000000000..f7296ca5f42 --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48740.json @@ -0,0 +1,32 @@ +{ + "id": "CVE-2022-48740", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:12.330", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nselinux: fix double free of cond_list on error paths\n\nOn error path from cond_read_list() and duplicate_policydb_cond_list()\nthe cond_list_destroy() gets called a second time in caller functions,\nresulting in NULL pointer deref. Fix this by resetting the\ncond_list_len to 0 in cond_list_destroy(), making subsequent calls a\nnoop.\n\nAlso consistently reset the cond_list pointer to NULL after freeing.\n\n[PM: fix line lengths in the description]" + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/186edf7e368c40d06cf727a1ad14698ea67b74ad", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/70caa32e6d81f45f0702070c0e4dfe945e92fbd7", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/7ed9cbf7ac0d4ed86b356e1b944304ae9ee450d4", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/f446089a268c8fc6908488e991d28a9b936293db", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48741.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48741.json new file mode 100644 index 00000000000..400993c9749 --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48741.json @@ -0,0 +1,28 @@ +{ + "id": "CVE-2022-48741", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:12.430", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\novl: fix NULL pointer dereference in copy up warning\n\nThis patch is fixing a NULL pointer dereference to get a recently\nintroduced warning message working." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/4ee7e4a6c9b298da44029ed9ec8ed23ae49cc209", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/9c7f8a35c5a83740c0e3ea540b6ad145c50d79aa", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/e6b678c1a3673de6a5d2f4e22bb725a086a0701a", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48742.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48742.json new file mode 100644 index 00000000000..d88c8a650f0 --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48742.json @@ -0,0 +1,48 @@ +{ + "id": "CVE-2022-48742", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:12.517", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nrtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink()\n\nWhile looking at one unrelated syzbot bug, I found the replay logic\nin __rtnl_newlink() to potentially trigger use-after-free.\n\nIt is better to clear master_dev and m_ops inside the loop,\nin case we have to replay it." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/2cf180360d66bd657e606c1217e0e668e6faa303", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/36a9a0aee881940476b254e0352581401b23f210", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/3bbe2019dd12b8d13671ee6cda055d49637b4c39", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/7d9211678c0f0624f74cdff36117ab8316697bb8", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/a01e60a1ec6bef9be471fb7182a33c6d6f124e93", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/bd43771ee9759dd9dfae946bff190e2c5a120de5", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/c6f6f2444bdbe0079e41914a35081530d0409963", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/def5e7070079b2a214b3b1a2fbec623e6fbfe34a", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48743.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48743.json new file mode 100644 index 00000000000..580e4cf5af3 --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48743.json @@ -0,0 +1,48 @@ +{ + "id": "CVE-2022-48743", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:12.610", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: amd-xgbe: Fix skb data length underflow\n\nThere will be BUG_ON() triggered in include/linux/skbuff.h leading to\nintermittent kernel panic, when the skb length underflow is detected.\n\nFix this by dropping the packet if such length underflows are seen\nbecause of inconsistencies in the hardware descriptors." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/34aeb4da20f93ac80a6291a2dbe7b9c6460e9b26", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/4d3fcfe8464838b3920bc2b939d888e0b792934e", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/5aac9108a180fc06e28d4e7fb00247ce603b72ee", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/617f9934bb37993b9813832516f318ba874bcb7d", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/9892742f035f7aa7dcd2bb0750effa486db89576", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/9924c80bd484340191e586110ca22bff23a49f2e", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/db6fd92316a254be2097556f01bccecf560e53ce", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/e8f73f620fee5f52653ed2da360121e4446575c5", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48744.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48744.json new file mode 100644 index 00000000000..9901b4d686c --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48744.json @@ -0,0 +1,24 @@ +{ + "id": "CVE-2022-48744", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:12.700", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Avoid field-overflowing memcpy()\n\nIn preparation for FORTIFY_SOURCE performing compile-time and run-time\nfield bounds checking for memcpy(), memmove(), and memset(), avoid\nintentionally writing across neighboring fields.\n\nUse flexible arrays instead of zero-element arrays (which look like they\nare always overflowing) and split the cross-field memcpy() into two halves\nthat can be appropriately bounds-checked by the compiler.\n\nWe were doing:\n\n\t#define ETH_HLEN 14\n\t#define VLAN_HLEN 4\n\t...\n\t#define MLX5E_XDP_MIN_INLINE (ETH_HLEN + VLAN_HLEN)\n\t...\n struct mlx5e_tx_wqe *wqe = mlx5_wq_cyc_get_wqe(wq, pi);\n\t...\n struct mlx5_wqe_eth_seg *eseg = &wqe->eth;\n struct mlx5_wqe_data_seg *dseg = wqe->data;\n\t...\n\tmemcpy(eseg->inline_hdr.start, xdptxd->data, MLX5E_XDP_MIN_INLINE);\n\ntarget is wqe->eth.inline_hdr.start (which the compiler sees as being\n2 bytes in size), but copying 18, intending to write across start\n(really vlan_tci, 2 bytes). The remaining 16 bytes get written into\nwqe->data[0], covering byte_count (4 bytes), lkey (4 bytes), and addr\n(8 bytes).\n\nstruct mlx5e_tx_wqe {\n struct mlx5_wqe_ctrl_seg ctrl; /* 0 16 */\n struct mlx5_wqe_eth_seg eth; /* 16 16 */\n struct mlx5_wqe_data_seg data[]; /* 32 0 */\n\n /* size: 32, cachelines: 1, members: 3 */\n /* last cacheline: 32 bytes */\n};\n\nstruct mlx5_wqe_eth_seg {\n u8 swp_outer_l4_offset; /* 0 1 */\n u8 swp_outer_l3_offset; /* 1 1 */\n u8 swp_inner_l4_offset; /* 2 1 */\n u8 swp_inner_l3_offset; /* 3 1 */\n u8 cs_flags; /* 4 1 */\n u8 swp_flags; /* 5 1 */\n __be16 mss; /* 6 2 */\n __be32 flow_table_metadata; /* 8 4 */\n union {\n struct {\n __be16 sz; /* 12 2 */\n u8 start[2]; /* 14 2 */\n } inline_hdr; /* 12 4 */\n struct {\n __be16 type; /* 12 2 */\n __be16 vlan_tci; /* 14 2 */\n } insert; /* 12 4 */\n __be32 trailer; /* 12 4 */\n }; /* 12 4 */\n\n /* size: 16, cachelines: 1, members: 9 */\n /* last cacheline: 16 bytes */\n};\n\nstruct mlx5_wqe_data_seg {\n __be32 byte_count; /* 0 4 */\n __be32 lkey; /* 4 4 */\n __be64 addr; /* 8 8 */\n\n /* size: 16, cachelines: 1, members: 3 */\n /* last cacheline: 16 bytes */\n};\n\nSo, split the memcpy() so the compiler can reason about the buffer\nsizes.\n\n\"pahole\" shows no size nor member offset changes to struct mlx5e_tx_wqe\nnor struct mlx5e_umr_wqe. \"objdump -d\" shows no meaningful object\ncode changes (i.e. only source line number induced differences and\noptimizations)." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/8fbdf8c8b8ab82beab882175157650452c46493e", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/ad5185735f7dab342fdd0dd41044da4c9ccfef67", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48745.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48745.json new file mode 100644 index 00000000000..e48120fb8dd --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48745.json @@ -0,0 +1,32 @@ +{ + "id": "CVE-2022-48745", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:12.783", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: Use del_timer_sync in fw reset flow of halting poll\n\nSubstitute del_timer() with del_timer_sync() in fw reset polling\ndeactivation flow, in order to prevent a race condition which occurs\nwhen del_timer() is called and timer is deactivated while another\nprocess is handling the timer interrupt. A situation that led to\nthe following call trace:\n\tRIP: 0010:run_timer_softirq+0x137/0x420\n\t\n\trecalibrate_cpu_khz+0x10/0x10\n\tktime_get+0x3e/0xa0\n\t? sched_clock_cpu+0xb/0xc0\n\t__do_softirq+0xf5/0x2ea\n\tirq_exit_rcu+0xc1/0xf0\n\tsysvec_apic_timer_interrupt+0x9e/0xc0\n\tasm_sysvec_apic_timer_interrupt+0x12/0x20\n\t" + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/2a038dd1d942f8fbc495c58fa592ff24af05f1c2", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/3c5193a87b0fea090aa3f769d020337662d87b5e", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/502c37b033fab7cde3e95a570af4f073306be45e", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/f895ebeb44d09d02674cfdd0cfc2bf687603918c", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48746.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48746.json new file mode 100644 index 00000000000..067b5b9736c --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48746.json @@ -0,0 +1,32 @@ +{ + "id": "CVE-2022-48746", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:12.870", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Fix handling of wrong devices during bond netevent\n\nCurrent implementation of bond netevent handler only check if\nthe handled netdev is VF representor and it missing a check if\nthe VF representor is on the same phys device of the bond handling\nthe netevent.\n\nFix by adding the missing check and optimizing the check if\nthe netdev is VF representor so it will not access uninitialized\nprivate data and crashes.\n\nBUG: kernel NULL pointer dereference, address: 000000000000036c\nPGD 0 P4D 0\nOops: 0000 [#1] SMP NOPTI\nWorkqueue: eth3bond0 bond_mii_monitor [bonding]\nRIP: 0010:mlx5e_is_uplink_rep+0xc/0x50 [mlx5_core]\nRSP: 0018:ffff88812d69fd60 EFLAGS: 00010282\nRAX: 0000000000000000 RBX: ffff8881cf800000 RCX: 0000000000000000\nRDX: ffff88812d69fe10 RSI: 000000000000001b RDI: ffff8881cf800880\nRBP: ffff8881cf800000 R08: 00000445cabccf2b R09: 0000000000000008\nR10: 0000000000000004 R11: 0000000000000008 R12: ffff88812d69fe10\nR13: 00000000fffffffe R14: ffff88820c0f9000 R15: 0000000000000000\nFS: 0000000000000000(0000) GS:ffff88846fb00000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 000000000000036c CR3: 0000000103d80006 CR4: 0000000000370ea0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n mlx5e_eswitch_uplink_rep+0x31/0x40 [mlx5_core]\n mlx5e_rep_is_lag_netdev+0x94/0xc0 [mlx5_core]\n mlx5e_rep_esw_bond_netevent+0xeb/0x3d0 [mlx5_core]\n raw_notifier_call_chain+0x41/0x60\n call_netdevice_notifiers_info+0x34/0x80\n netdev_lower_state_changed+0x4e/0xa0\n bond_mii_monitor+0x56b/0x640 [bonding]\n process_one_work+0x1b9/0x390\n worker_thread+0x4d/0x3d0\n ? rescuer_thread+0x350/0x350\n kthread+0x124/0x150\n ? set_kthread_struct+0x40/0x40\n ret_from_fork+0x1f/0x30" + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/4fad499d7fece448e7230d5e5b92f6d8a073e0bb", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/a01ee1b8165f4161459b5ec4e728bc7130fe8cd4", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/ec41332e02bd0acf1f24206867bb6a02f5877a62", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/fe70126da6063c29ca161cdec7ad1dae9af836b3", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48747.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48747.json new file mode 100644 index 00000000000..ea6099153eb --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48747.json @@ -0,0 +1,36 @@ +{ + "id": "CVE-2022-48747", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:12.960", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nblock: Fix wrong offset in bio_truncate()\n\nbio_truncate() clears the buffer outside of last block of bdev, however\ncurrent bio_truncate() is using the wrong offset of page. So it can\nreturn the uninitialized data.\n\nThis happened when both of truncated/corrupted FS and userspace (via\nbdev) are trying to read the last of bdev." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/3ee859e384d453d6ac68bfd5971f630d9fa46ad3", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/4633a79ff8bc82770486a063a08b55e5162521d8", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/6cbf4c731d7812518cd857c2cfc3da9fd120f6ae", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/941d5180c430ce5b0f7a3622ef9b76077bfa3d82", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/b63e120189fd92aff00096d11e2fc5253f60248b", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48748.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48748.json new file mode 100644 index 00000000000..9d4f2dc78c7 --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48748.json @@ -0,0 +1,32 @@ +{ + "id": "CVE-2022-48748", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:13.047", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: bridge: vlan: fix memory leak in __allowed_ingress\n\nWhen using per-vlan state, if vlan snooping and stats are disabled,\nuntagged or priority-tagged ingress frame will go to check pvid state.\nIf the port state is forwarding and the pvid state is not\nlearning/forwarding, untagged or priority-tagged frame will be dropped\nbut skb memory is not freed.\nShould free skb when __allowed_ingress returns false." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/14be8d448fca6fe7b2a413831eedd55aef6c6511", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/446ff1fc37c74093e81db40811a07b5a19f1d797", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/c5e216e880fa6f2cd9d4a6541269377657163098", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/fd20d9738395cf8e27d0a17eba34169699fccdff", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48749.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48749.json new file mode 100644 index 00000000000..ac6701efa02 --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48749.json @@ -0,0 +1,32 @@ +{ + "id": "CVE-2022-48749", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:13.143", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/msm/dpu: invalid parameter check in dpu_setup_dspp_pcc\n\nThe function performs a check on the \"ctx\" input parameter, however, it\nis used before the check.\n\nInitialize the \"base\" variable after the sanity check to avoid a\npossible NULL pointer dereference.\n\nAddresses-Coverity-ID: 1493866 (\"Null pointer dereference\")" + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/170b22234d5495f5e0844246e23f004639ee89ba", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/1ebc18836d5df09061657f8c548e594cbb519476", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/8f069f6dde518dfebe86e848508c07e497bd9298", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/93a6e920d8ccb4df846c03b6e72f7e08843d294c", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48750.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48750.json new file mode 100644 index 00000000000..1cd4353c46f --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48750.json @@ -0,0 +1,24 @@ +{ + "id": "CVE-2022-48750", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:13.223", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nhwmon: (nct6775) Fix crash in clear_caseopen\n\nPawe? Marciniak reports the following crash, observed when clearing\nthe chassis intrusion alarm.\n\nBUG: kernel NULL pointer dereference, address: 0000000000000028\nPGD 0 P4D 0\nOops: 0000 [#1] PREEMPT SMP PTI\nCPU: 3 PID: 4815 Comm: bash Tainted: G S 5.16.2-200.fc35.x86_64 #1\nHardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z97 Extreme4, BIOS P2.60A 05/03/2018\nRIP: 0010:clear_caseopen+0x5a/0x120 [nct6775]\nCode: 68 70 e8 e9 32 b1 e3 85 c0 0f 85 d2 00 00 00 48 83 7c 24 ...\nRSP: 0018:ffffabcb02803dd8 EFLAGS: 00010246\nRAX: 0000000000000000 RBX: 0000000000000002 RCX: 0000000000000000\nRDX: ffff8e8808192880 RSI: 0000000000000000 RDI: ffff8e87c7509a68\nRBP: 0000000000000000 R08: 0000000000000001 R09: 000000000000000a\nR10: 000000000000000a R11: f000000000000000 R12: 000000000000001f\nR13: ffff8e87c7509828 R14: ffff8e87c7509a68 R15: ffff8e88494527a0\nFS: 00007f4db9151740(0000) GS:ffff8e8ebfec0000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000028 CR3: 0000000166b66001 CR4: 00000000001706e0\nCall Trace:\n \n kernfs_fop_write_iter+0x11c/0x1b0\n new_sync_write+0x10b/0x180\n vfs_write+0x209/0x2a0\n ksys_write+0x4f/0xc0\n do_syscall_64+0x3b/0x90\n entry_SYSCALL_64_after_hwframe+0x44/0xae\n\nThe problem is that the device passed to clear_caseopen() is the hwmon\ndevice, not the platform device, and the platform data is not set in the\nhwmon device. Store the pointer to sio_data in struct nct6775_data and\nget if from there if needed." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/79da533d3cc717ccc05ddbd3190da8a72bc2408b", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/cfb7d12f2e4a4d694f49e9b4ebb352f7b67cdfbb", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48751.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48751.json new file mode 100644 index 00000000000..3abfc98971d --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48751.json @@ -0,0 +1,28 @@ +{ + "id": "CVE-2022-48751", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:13.310", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/smc: Transitional solution for clcsock race issue\n\nWe encountered a crash in smc_setsockopt() and it is caused by\naccessing smc->clcsock after clcsock was released.\n\n BUG: kernel NULL pointer dereference, address: 0000000000000020\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\n PGD 0 P4D 0\n Oops: 0000 [#1] PREEMPT SMP PTI\n CPU: 1 PID: 50309 Comm: nginx Kdump: loaded Tainted: G E 5.16.0-rc4+ #53\n RIP: 0010:smc_setsockopt+0x59/0x280 [smc]\n Call Trace:\n \n __sys_setsockopt+0xfc/0x190\n __x64_sys_setsockopt+0x20/0x30\n do_syscall_64+0x34/0x90\n entry_SYSCALL_64_after_hwframe+0x44/0xae\n RIP: 0033:0x7f16ba83918e\n \n\nThis patch tries to fix it by holding clcsock_release_lock and\nchecking whether clcsock has already been released before access.\n\nIn case that a crash of the same reason happens in smc_getsockopt()\nor smc_switch_to_fallback(), this patch also checkes smc->clcsock\nin them too. And the caller of smc_switch_to_fallback() will identify\nwhether fallback succeeds according to the return value." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/38f0bdd548fd2ef5d481b88d8a2bfef968452e34", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/4284225cd8001e134f5cf533a7cd244bbb654d0f", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/c0bf3d8a943b6f2e912b7c1de03e2ef28e76f760", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48752.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48752.json new file mode 100644 index 00000000000..a0f1f4303ad --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48752.json @@ -0,0 +1,32 @@ +{ + "id": "CVE-2022-48752", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:13.397", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\npowerpc/perf: Fix power_pmu_disable to call clear_pmi_irq_pending only if PMI is pending\n\nRunning selftest with CONFIG_PPC_IRQ_SOFT_MASK_DEBUG enabled in kernel\ntriggered below warning:\n\n[ 172.851380] ------------[ cut here ]------------\n[ 172.851391] WARNING: CPU: 8 PID: 2901 at arch/powerpc/include/asm/hw_irq.h:246 power_pmu_disable+0x270/0x280\n[ 172.851402] Modules linked in: dm_mod bonding nft_ct nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables rfkill nfnetlink sunrpc xfs libcrc32c pseries_rng xts vmx_crypto uio_pdrv_genirq uio sch_fq_codel ip_tables ext4 mbcache jbd2 sd_mod t10_pi sg ibmvscsi ibmveth scsi_transport_srp fuse\n[ 172.851442] CPU: 8 PID: 2901 Comm: lost_exception_ Not tainted 5.16.0-rc5-03218-g798527287598 #2\n[ 172.851451] NIP: c00000000013d600 LR: c00000000013d5a4 CTR: c00000000013b180\n[ 172.851458] REGS: c000000017687860 TRAP: 0700 Not tainted (5.16.0-rc5-03218-g798527287598)\n[ 172.851465] MSR: 8000000000029033 CR: 48004884 XER: 20040000\n[ 172.851482] CFAR: c00000000013d5b4 IRQMASK: 1\n[ 172.851482] GPR00: c00000000013d5a4 c000000017687b00 c000000002a10600 0000000000000004\n[ 172.851482] GPR04: 0000000082004000 c0000008ba08f0a8 0000000000000000 00000008b7ed0000\n[ 172.851482] GPR08: 00000000446194f6 0000000000008000 c00000000013b118 c000000000d58e68\n[ 172.851482] GPR12: c00000000013d390 c00000001ec54a80 0000000000000000 0000000000000000\n[ 172.851482] GPR16: 0000000000000000 0000000000000000 c000000015d5c708 c0000000025396d0\n[ 172.851482] GPR20: 0000000000000000 0000000000000000 c00000000a3bbf40 0000000000000003\n[ 172.851482] GPR24: 0000000000000000 c0000008ba097400 c0000000161e0d00 c00000000a3bb600\n[ 172.851482] GPR28: c000000015d5c700 0000000000000001 0000000082384090 c0000008ba0020d8\n[ 172.851549] NIP [c00000000013d600] power_pmu_disable+0x270/0x280\n[ 172.851557] LR [c00000000013d5a4] power_pmu_disable+0x214/0x280\n[ 172.851565] Call Trace:\n[ 172.851568] [c000000017687b00] [c00000000013d5a4] power_pmu_disable+0x214/0x280 (unreliable)\n[ 172.851579] [c000000017687b40] [c0000000003403ac] perf_pmu_disable+0x4c/0x60\n[ 172.851588] [c000000017687b60] [c0000000003445e4] __perf_event_task_sched_out+0x1d4/0x660\n[ 172.851596] [c000000017687c50] [c000000000d1175c] __schedule+0xbcc/0x12a0\n[ 172.851602] [c000000017687d60] [c000000000d11ea8] schedule+0x78/0x140\n[ 172.851608] [c000000017687d90] [c0000000001a8080] sys_sched_yield+0x20/0x40\n[ 172.851615] [c000000017687db0] [c0000000000334dc] system_call_exception+0x18c/0x380\n[ 172.851622] [c000000017687e10] [c00000000000c74c] system_call_common+0xec/0x268\n\nThe warning indicates that MSR_EE being set(interrupt enabled) when\nthere was an overflown PMC detected. This could happen in\npower_pmu_disable since it runs under interrupt soft disable\ncondition ( local_irq_save ) and not with interrupts hard disabled.\ncommit 2c9ac51b850d (\"powerpc/perf: Fix PMU callbacks to clear\npending PMI before resetting an overflown PMC\") intended to clear\nPMI pending bit in Paca when disabling the PMU. It could happen\nthat PMC gets overflown while code is in power_pmu_disable\ncallback function. Hence add a check to see if PMI pending bit\nis set in Paca before clearing it via clear_pmi_pending." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/28aaed966e76807a71de79dd40a8eee9042374dd", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/55402a4618721f350a9ab660bb42717d8aa18e7c", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/fa4ad064a6bd49208221df5e62adf27b426d1720", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/fb6433b48a178d4672cb26632454ee0b21056eaa", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48753.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48753.json new file mode 100644 index 00000000000..b9fea1d467e --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48753.json @@ -0,0 +1,24 @@ +{ + "id": "CVE-2022-48753", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:13.480", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nblock: fix memory leak in disk_register_independent_access_ranges\n\nkobject_init_and_add() takes reference even when it fails.\nAccording to the doc of kobject_init_and_add()\n\n If this function returns an error, kobject_put() must be called to\n properly clean up the memory associated with the object.\n\nFix this issue by adding kobject_put().\nCallback function blk_ia_ranges_sysfs_release() in kobject_put()\ncan handle the pointer \"iars\" properly." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/83114df32ae779df57e0af99a8ba6c3968b2ba3d", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/fe4214a07e0b53d2af711f57519e33739c5df23f", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48754.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48754.json new file mode 100644 index 00000000000..bbea47c64c6 --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48754.json @@ -0,0 +1,40 @@ +{ + "id": "CVE-2022-48754", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:13.563", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nphylib: fix potential use-after-free\n\nCommit bafbdd527d56 (\"phylib: Add device reset GPIO support\") added call\nto phy_device_reset(phydev) after the put_device() call in phy_detach().\n\nThe comment before the put_device() call says that the phydev might go\naway with put_device().\n\nFix potential use-after-free by calling phy_device_reset() before\nput_device()." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/67d271760b037ce0806d687ee6057edc8afd4205", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/aefaccd19379d6c4620269a162bfb88ff687f289", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/bd024e36f68174b1793906c39ca16cee0c9295c2", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/cb2fab10fc5e7a3aa1bb0a68a3abdcf3e37852af", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/cbda1b16687580d5beee38273f6241ae3725960c", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/f39027cbada43b33566c312e6be3db654ca3ad17", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48755.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48755.json new file mode 100644 index 00000000000..83ce2031294 --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48755.json @@ -0,0 +1,32 @@ +{ + "id": "CVE-2022-48755", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:13.653", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\npowerpc64/bpf: Limit 'ldbrx' to processors compliant with ISA v2.06\n\nJohan reported the below crash with test_bpf on ppc64 e5500:\n\n test_bpf: #296 ALU_END_FROM_LE 64: 0x0123456789abcdef -> 0x67452301 jited:1\n Oops: Exception in kernel mode, sig: 4 [#1]\n BE PAGE_SIZE=4K SMP NR_CPUS=24 QEMU e500\n Modules linked in: test_bpf(+)\n CPU: 0 PID: 76 Comm: insmod Not tainted 5.14.0-03771-g98c2059e008a-dirty #1\n NIP: 8000000000061c3c LR: 80000000006dea64 CTR: 8000000000061c18\n REGS: c0000000032d3420 TRAP: 0700 Not tainted (5.14.0-03771-g98c2059e008a-dirty)\n MSR: 0000000080089000 CR: 88002822 XER: 20000000 IRQMASK: 0\n <...>\n NIP [8000000000061c3c] 0x8000000000061c3c\n LR [80000000006dea64] .__run_one+0x104/0x17c [test_bpf]\n Call Trace:\n .__run_one+0x60/0x17c [test_bpf] (unreliable)\n .test_bpf_init+0x6a8/0xdc8 [test_bpf]\n .do_one_initcall+0x6c/0x28c\n .do_init_module+0x68/0x28c\n .load_module+0x2460/0x2abc\n .__do_sys_init_module+0x120/0x18c\n .system_call_exception+0x110/0x1b8\n system_call_common+0xf0/0x210\n --- interrupt: c00 at 0x101d0acc\n <...>\n ---[ end trace 47b2bf19090bb3d0 ]---\n\n Illegal instruction\n\nThe illegal instruction turned out to be 'ldbrx' emitted for\nBPF_FROM_[L|B]E, which was only introduced in ISA v2.06. Guard use of\nthe same and implement an alternative approach for older processors." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/129c71829d7f46423d95c19e8d87ce956d4c6e1c", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/3bfbc00587dc883eaed383558ae512a351c2cd09", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/3f5f766d5f7f95a69a630da3544a1a0cee1cdddf", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/aaccfeeee1630b155e8ff0d6c449d3de1ef86e73", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48756.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48756.json new file mode 100644 index 00000000000..c60e66f4849 --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48756.json @@ -0,0 +1,44 @@ +{ + "id": "CVE-2022-48756", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:13.740", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/msm/dsi: invalid parameter check in msm_dsi_phy_enable\n\nThe function performs a check on the \"phy\" input parameter, however, it\nis used before the check.\n\nInitialize the \"dev\" variable after the sanity check to avoid a possible\nNULL pointer dereference.\n\nAddresses-Coverity-ID: 1493860 (\"Null pointer dereference\")" + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/2b7e7df1eacd280e561ede3e977853606871c951", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/56480fb10b976581a363fd168dc2e4fbee87a1a7", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/581317b1f001b7509041544d7019b75571daa100", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/5e761a2287234bc402ba7ef07129f5103bcd775c", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/6d9f8ba28f3747ca0f910a363e46f1114856dbbe", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/79c0b5287ded74f4eacde4dfd8aa0a76cbd853b5", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/ca63eeb70fcb53c42e1fe54e1735a54d8e7759fd", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48757.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48757.json new file mode 100644 index 00000000000..d56d0acf6be --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48757.json @@ -0,0 +1,52 @@ +{ + "id": "CVE-2022-48757", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:13.823", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: fix information leakage in /proc/net/ptype\n\nIn one net namespace, after creating a packet socket without binding\nit to a device, users in other net namespaces can observe the new\n`packet_type` added by this packet socket by reading `/proc/net/ptype`\nfile. This is minor information leakage as packet socket is\nnamespace aware.\n\nAdd a net pointer in `packet_type` to keep the net namespace of\nof corresponding packet socket. In `ptype_seq_show`, this net pointer\nmust be checked when it is not NULL." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/47934e06b65637c88a762d9c98329ae6e3238888", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/839ec7039513a4f84bfbaff953a9393471176bee", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/8f88c78d24f6f346919007cd459fd7e51a8c7779", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/b67ad6170c0ea87391bb253f35d1f78857736e54", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/be1ca30331c7923c6f376610c1bd6059be9b1908", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/c38023032a598ec6263e008d62c7f02def72d5c7", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/db044d97460ea792110eb8b971e82569ded536c6", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/e372ecd455b6ebc7720f52bf4b5f5d44d02f2092", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/e43669c77cb3a742b7d84ecdc7c68c4167a7709b", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48758.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48758.json new file mode 100644 index 00000000000..a923addd0fd --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48758.json @@ -0,0 +1,52 @@ +{ + "id": "CVE-2022-48758", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:13.927", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: bnx2fc: Flush destroy_work queue before calling bnx2fc_interface_put()\n\nThe bnx2fc_destroy() functions are removing the interface before calling\ndestroy_work. This results multiple WARNings from sysfs_remove_group() as\nthe controller rport device attributes are removed too early.\n\nReplace the fcoe_port's destroy_work queue. It's not needed.\n\nThe problem is easily reproducible with the following steps.\n\nExample:\n\n $ dmesg -w &\n $ systemctl enable --now fcoe\n $ fipvlan -s -c ens2f1\n $ fcoeadm -d ens2f1.802\n [ 583.464488] host2: libfc: Link down on port (7500a1)\n [ 583.472651] bnx2fc: 7500a1 - rport not created Yet!!\n [ 583.490468] ------------[ cut here ]------------\n [ 583.538725] sysfs group 'power' not found for kobject 'rport-2:0-0'\n [ 583.568814] WARNING: CPU: 3 PID: 192 at fs/sysfs/group.c:279 sysfs_remove_group+0x6f/0x80\n [ 583.607130] Modules linked in: dm_service_time 8021q garp mrp stp llc bnx2fc cnic uio rpcsec_gss_krb5 auth_rpcgss nfsv4 ...\n [ 583.942994] CPU: 3 PID: 192 Comm: kworker/3:2 Kdump: loaded Not tainted 5.14.0-39.el9.x86_64 #1\n [ 583.984105] Hardware name: HP ProLiant DL120 G7, BIOS J01 07/01/2013\n [ 584.016535] Workqueue: fc_wq_2 fc_rport_final_delete [scsi_transport_fc]\n [ 584.050691] RIP: 0010:sysfs_remove_group+0x6f/0x80\n [ 584.074725] Code: ff 5b 48 89 ef 5d 41 5c e9 ee c0 ff ff 48 89 ef e8 f6 b8 ff ff eb d1 49 8b 14 24 48 8b 33 48 c7 c7 ...\n [ 584.162586] RSP: 0018:ffffb567c15afdc0 EFLAGS: 00010282\n [ 584.188225] RAX: 0000000000000000 RBX: ffffffff8eec4220 RCX: 0000000000000000\n [ 584.221053] RDX: ffff8c1586ce84c0 RSI: ffff8c1586cd7cc0 RDI: ffff8c1586cd7cc0\n [ 584.255089] RBP: 0000000000000000 R08: 0000000000000000 R09: ffffb567c15afc00\n [ 584.287954] R10: ffffb567c15afbf8 R11: ffffffff8fbe7f28 R12: ffff8c1486326400\n [ 584.322356] R13: ffff8c1486326480 R14: ffff8c1483a4a000 R15: 0000000000000004\n [ 584.355379] FS: 0000000000000000(0000) GS:ffff8c1586cc0000(0000) knlGS:0000000000000000\n [ 584.394419] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n [ 584.421123] CR2: 00007fe95a6f7840 CR3: 0000000107674002 CR4: 00000000000606e0\n [ 584.454888] Call Trace:\n [ 584.466108] device_del+0xb2/0x3e0\n [ 584.481701] device_unregister+0x13/0x60\n [ 584.501306] bsg_unregister_queue+0x5b/0x80\n [ 584.522029] bsg_remove_queue+0x1c/0x40\n [ 584.541884] fc_rport_final_delete+0xf3/0x1d0 [scsi_transport_fc]\n [ 584.573823] process_one_work+0x1e3/0x3b0\n [ 584.592396] worker_thread+0x50/0x3b0\n [ 584.609256] ? rescuer_thread+0x370/0x370\n [ 584.628877] kthread+0x149/0x170\n [ 584.643673] ? set_kthread_struct+0x40/0x40\n [ 584.662909] ret_from_fork+0x22/0x30\n [ 584.680002] ---[ end trace 53575ecefa942ece ]---" + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/00849de10f798a9538242824a51b1756e7110754", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/262550f29c750f7876b6ed1244281e72b64ebffb", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/2a12fe8248a38437b95b942bbe85aced72e6e2eb", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/847f9ea4c5186fdb7b84297e3eeed9e340e83fce", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/ace7b6ef41251c5fe47f629a9a922382fb7b0a6b", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/b11e34f7bab21df36f02a5e54fb69e858c09a65d", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/bf2bd892a0cb14dd2d21f2c658f4b747813be311", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/c93a290c862ccfa404e42d7420565730d67cbff9", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/de6336b17a1376db1c0f7a528cce8783db0881c0", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48759.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48759.json new file mode 100644 index 00000000000..e6b0526d199 --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48759.json @@ -0,0 +1,44 @@ +{ + "id": "CVE-2022-48759", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:14.023", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nrpmsg: char: Fix race between the release of rpmsg_ctrldev and cdev\n\nstruct rpmsg_ctrldev contains a struct cdev. The current code frees\nthe rpmsg_ctrldev struct in rpmsg_ctrldev_release_device(), but the\ncdev is a managed object, therefore its release is not predictable\nand the rpmsg_ctrldev could be freed before the cdev is entirely\nreleased, as in the backtrace below.\n\n[ 93.625603] ODEBUG: free active (active state 0) object type: timer_list hint: delayed_work_timer_fn+0x0/0x7c\n[ 93.636115] WARNING: CPU: 0 PID: 12 at lib/debugobjects.c:488 debug_print_object+0x13c/0x1b0\n[ 93.644799] Modules linked in: veth xt_cgroup xt_MASQUERADE rfcomm algif_hash algif_skcipher af_alg uinput ip6table_nat fuse uvcvideo videobuf2_vmalloc venus_enc venus_dec videobuf2_dma_contig hci_uart btandroid btqca snd_soc_rt5682_i2c bluetooth qcom_spmi_temp_alarm snd_soc_rt5682v\n[ 93.715175] CPU: 0 PID: 12 Comm: kworker/0:1 Tainted: G B 5.4.163-lockdep #26\n[ 93.723855] Hardware name: Google Lazor (rev3 - 8) with LTE (DT)\n[ 93.730055] Workqueue: events kobject_delayed_cleanup\n[ 93.735271] pstate: 60c00009 (nZCv daif +PAN +UAO)\n[ 93.740216] pc : debug_print_object+0x13c/0x1b0\n[ 93.744890] lr : debug_print_object+0x13c/0x1b0\n[ 93.749555] sp : ffffffacf5bc7940\n[ 93.752978] x29: ffffffacf5bc7940 x28: dfffffd000000000\n[ 93.758448] x27: ffffffacdb11a800 x26: dfffffd000000000\n[ 93.763916] x25: ffffffd0734f856c x24: dfffffd000000000\n[ 93.769389] x23: 0000000000000000 x22: ffffffd0733c35b0\n[ 93.774860] x21: ffffffd0751994a0 x20: ffffffd075ec27c0\n[ 93.780338] x19: ffffffd075199100 x18: 00000000000276e0\n[ 93.785814] x17: 0000000000000000 x16: dfffffd000000000\n[ 93.791291] x15: ffffffffffffffff x14: 6e6968207473696c\n[ 93.796768] x13: 0000000000000000 x12: ffffffd075e2b000\n[ 93.802244] x11: 0000000000000001 x10: 0000000000000000\n[ 93.807723] x9 : d13400dff1921900 x8 : d13400dff1921900\n[ 93.813200] x7 : 0000000000000000 x6 : 0000000000000000\n[ 93.818676] x5 : 0000000000000080 x4 : 0000000000000000\n[ 93.824152] x3 : ffffffd0732a0fa4 x2 : 0000000000000001\n[ 93.829628] x1 : ffffffacf5bc7580 x0 : 0000000000000061\n[ 93.835104] Call trace:\n[ 93.837644] debug_print_object+0x13c/0x1b0\n[ 93.841963] __debug_check_no_obj_freed+0x25c/0x3c0\n[ 93.846987] debug_check_no_obj_freed+0x18/0x20\n[ 93.851669] slab_free_freelist_hook+0xbc/0x1e4\n[ 93.856346] kfree+0xfc/0x2f4\n[ 93.859416] rpmsg_ctrldev_release_device+0x78/0xb8\n[ 93.864445] device_release+0x84/0x168\n[ 93.868310] kobject_cleanup+0x12c/0x298\n[ 93.872356] kobject_delayed_cleanup+0x10/0x18\n[ 93.876948] process_one_work+0x578/0x92c\n[ 93.881086] worker_thread+0x804/0xcf8\n[ 93.884963] kthread+0x2a8/0x314\n[ 93.888303] ret_from_fork+0x10/0x18\n\nThe cdev_device_add/del() API was created to address this issue (see\ncommit '233ed09d7fda (\"chardev: add helper function to register char\ndevs with a struct device\")'), use it instead of cdev add/del()." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/1dbb206730f3e5ce90014ad569ddf8167ec4124a", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/70cb4295ec806b663665e1d2ed15caab6159880e", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/74d85e9fbc7022a4011102c7474a9c7aeb704a35", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/85aba11a8ea92a8eef2de95ebbe063086fd62d9c", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/b7fb2dad571d1e21173c06cef0bced77b323990a", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/d6cdc6ae542845d4d0ac8b6d99362bde7042a3c7", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/da27b834c1e0222e149e06caddf7718478086d1b", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48760.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48760.json new file mode 100644 index 00000000000..d40183abb46 --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48760.json @@ -0,0 +1,52 @@ +{ + "id": "CVE-2022-48760", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:14.110", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nUSB: core: Fix hang in usb_kill_urb by adding memory barriers\n\nThe syzbot fuzzer has identified a bug in which processes hang waiting\nfor usb_kill_urb() to return. It turns out the issue is not unlinking\nthe URB; that works just fine. Rather, the problem arises when the\nwakeup notification that the URB has completed is not received.\n\nThe reason is memory-access ordering on SMP systems. In outline form,\nusb_kill_urb() and __usb_hcd_giveback_urb() operating concurrently on\ndifferent CPUs perform the following actions:\n\nCPU 0\t\t\t\t\tCPU 1\n----------------------------\t\t---------------------------------\nusb_kill_urb():\t\t\t\t__usb_hcd_giveback_urb():\n ...\t\t\t\t\t ...\n atomic_inc(&urb->reject);\t\t atomic_dec(&urb->use_count);\n ...\t\t\t\t\t ...\n wait_event(usb_kill_urb_queue,\n\tatomic_read(&urb->use_count) == 0);\n\t\t\t\t\t if (atomic_read(&urb->reject))\n\t\t\t\t\t\twake_up(&usb_kill_urb_queue);\n\nConfining your attention to urb->reject and urb->use_count, you can\nsee that the overall pattern of accesses on CPU 0 is:\n\n\twrite urb->reject, then read urb->use_count;\n\nwhereas the overall pattern of accesses on CPU 1 is:\n\n\twrite urb->use_count, then read urb->reject.\n\nThis pattern is referred to in memory-model circles as SB (for \"Store\nBuffering\"), and it is well known that without suitable enforcement of\nthe desired order of accesses -- in the form of memory barriers -- it\nis entirely possible for one or both CPUs to execute their reads ahead\nof their writes. The end result will be that sometimes CPU 0 sees the\nold un-decremented value of urb->use_count while CPU 1 sees the old\nun-incremented value of urb->reject. Consequently CPU 0 ends up on\nthe wait queue and never gets woken up, leading to the observed hang\nin usb_kill_urb().\n\nThe same pattern of accesses occurs in usb_poison_urb() and the\nfailure pathway of usb_hcd_submit_urb().\n\nThe problem is fixed by adding suitable memory barriers. To provide\nproper memory-access ordering in the SB pattern, a full barrier is\nrequired on both CPUs. The atomic_inc() and atomic_dec() accesses\nthemselves don't provide any memory ordering, but since they are\npresent, we can use the optimized smp_mb__after_atomic() memory\nbarrier in the various routines to obtain the desired effect.\n\nThis patch adds the necessary memory barriers." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/26fbe9772b8c459687930511444ce443011f86bf", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/546ba238535d925254e0b3f12012a5c55801e2f3", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/5904dfd3ddaff3bf4a41c3baf0a8e8f31ed4599b", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/5f138ef224dffd15d5e5c5b095859719e0038427", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/9340226388c66a7e090ebb00e91ed64a753b6c26", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/9c61fce322ac2ef7fecf025285353570d60e41d6", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/b50f5ca60475710bbc9a3af32fbfc17b1e69c2f0", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/c9a18f7c5b071dce5e6939568829d40994866ab0", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/e3b131e30e612ff0e32de6c1cb4f69f89db29193", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48761.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48761.json new file mode 100644 index 00000000000..f161849382f --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48761.json @@ -0,0 +1,32 @@ +{ + "id": "CVE-2022-48761", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:14.203", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nusb: xhci-plat: fix crash when suspend if remote wake enable\n\nCrashed at i.mx8qm platform when suspend if enable remote wakeup\n\nInternal error: synchronous external abort: 96000210 [#1] PREEMPT SMP\nModules linked in:\nCPU: 2 PID: 244 Comm: kworker/u12:6 Not tainted 5.15.5-dirty #12\nHardware name: Freescale i.MX8QM MEK (DT)\nWorkqueue: events_unbound async_run_entry_fn\npstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\npc : xhci_disable_hub_port_wake.isra.62+0x60/0xf8\nlr : xhci_disable_hub_port_wake.isra.62+0x34/0xf8\nsp : ffff80001394bbf0\nx29: ffff80001394bbf0 x28: 0000000000000000 x27: ffff00081193b578\nx26: ffff00081193b570 x25: 0000000000000000 x24: 0000000000000000\nx23: ffff00081193a29c x22: 0000000000020001 x21: 0000000000000001\nx20: 0000000000000000 x19: ffff800014e90490 x18: 0000000000000000\nx17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000\nx14: 0000000000000000 x13: 0000000000000002 x12: 0000000000000000\nx11: 0000000000000000 x10: 0000000000000960 x9 : ffff80001394baa0\nx8 : ffff0008145d1780 x7 : ffff0008f95b8e80 x6 : 000000001853b453\nx5 : 0000000000000496 x4 : 0000000000000000 x3 : ffff00081193a29c\nx2 : 0000000000000001 x1 : 0000000000000000 x0 : ffff000814591620\nCall trace:\n xhci_disable_hub_port_wake.isra.62+0x60/0xf8\n xhci_suspend+0x58/0x510\n xhci_plat_suspend+0x50/0x78\n platform_pm_suspend+0x2c/0x78\n dpm_run_callback.isra.25+0x50/0xe8\n __device_suspend+0x108/0x3c0\n\nThe basic flow:\n\t1. run time suspend call xhci_suspend, xhci parent devices gate the clock.\n 2. echo mem >/sys/power/state, system _device_suspend call xhci_suspend\n 3. xhci_suspend call xhci_disable_hub_port_wake, which access register,\n\t but clock already gated by run time suspend.\n\nThis problem was hidden by power domain driver, which call run time resume before it.\n\nBut the below commit remove it and make this issue happen.\n\tcommit c1df456d0f06e (\"PM: domains: Don't runtime resume devices at genpd_prepare()\")\n\nThis patch call run time resume before suspend to make sure clock is on\nbefore access register.\n\nTesteb-by: Abel Vesa " + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/20c51a4c52208f98e27308c456a1951778f41fa5", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/8b05ad29acb972850ad795fa850e814b2e758b83", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/9df478463d9feb90dae24f183383961cf123a0ec", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/d5755832a1e47f5d8773f0776e211ecd4e02da72", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48762.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48762.json new file mode 100644 index 00000000000..7833b31061e --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48762.json @@ -0,0 +1,24 @@ +{ + "id": "CVE-2022-48762", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:14.287", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\narm64: extable: fix load_unaligned_zeropad() reg indices\n\nIn ex_handler_load_unaligned_zeropad() we erroneously extract the data and\naddr register indices from ex->type rather than ex->data. As ex->type will\ncontain EX_TYPE_LOAD_UNALIGNED_ZEROPAD (i.e. 4):\n * We'll always treat X0 as the address register, since EX_DATA_REG_ADDR is\n extracted from bits [9:5]. Thus, we may attempt to dereference an\n arbitrary address as X0 may hold an arbitrary value.\n * We'll always treat X4 as the data register, since EX_DATA_REG_DATA is\n extracted from bits [4:0]. Thus we will corrupt X4 and cause arbitrary\n behaviour within load_unaligned_zeropad() and its caller.\n\nFix this by extracting both values from ex->data as originally intended.\n\nOn an MTE-enabled QEMU image we are hitting the following crash:\n Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000\n Call trace:\n fixup_exception+0xc4/0x108\n __do_kernel_fault+0x3c/0x268\n do_tag_check_fault+0x3c/0x104\n do_mem_abort+0x44/0xf4\n el1_abort+0x40/0x64\n el1h_64_sync_handler+0x60/0xa0\n el1h_64_sync+0x7c/0x80\n link_path_walk+0x150/0x344\n path_openat+0xa0/0x7dc\n do_filp_open+0xb8/0x168\n do_sys_openat2+0x88/0x17c\n __arm64_sys_openat+0x74/0xa0\n invoke_syscall+0x48/0x148\n el0_svc_common+0xb8/0xf8\n do_el0_svc+0x28/0x88\n el0_svc+0x24/0x84\n el0t_64_sync_handler+0x88/0xec\n el0t_64_sync+0x1b4/0x1b8\n Code: f8695a69 71007d1f 540000e0 927df12a (f940014a)" + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/3758a6c74e08bdc15ccccd6872a6ad37d165239a", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/47fe7a1c5e3e011eeb4ab79f2d54a794fdd1c3eb", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48763.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48763.json new file mode 100644 index 00000000000..301a0d05340 --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48763.json @@ -0,0 +1,32 @@ +{ + "id": "CVE-2022-48763", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:14.363", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86: Forcibly leave nested virt when SMM state is toggled\n\nForcibly leave nested virtualization operation if userspace toggles SMM\nstate via KVM_SET_VCPU_EVENTS or KVM_SYNC_X86_EVENTS. If userspace\nforces the vCPU out of SMM while it's post-VMXON and then injects an SMI,\nvmx_enter_smm() will overwrite vmx->nested.smm.vmxon and end up with both\nvmxon=false and smm.vmxon=false, but all other nVMX state allocated.\n\nDon't attempt to gracefully handle the transition as (a) most transitions\nare nonsencial, e.g. forcing SMM while L2 is running, (b) there isn't\nsufficient information to handle all transitions, e.g. SVM wants access\nto the SMRAM save state, and (c) KVM_SET_VCPU_EVENTS must precede\nKVM_SET_NESTED_STATE during state restore as the latter disallows putting\nthe vCPU into L2 if SMM is active, and disallows tagging the vCPU as\nbeing post-VMXON in SMM if SMM is not active.\n\nAbuse of KVM_SET_VCPU_EVENTS manifests as a WARN and memory leak in nVMX\ndue to failure to free vmcs01's shadow VMCS, but the bug goes far beyond\njust a memory leak, e.g. toggling SMM on while L2 is active puts the vCPU\nin an architecturally impossible state.\n\n WARNING: CPU: 0 PID: 3606 at free_loaded_vmcs arch/x86/kvm/vmx/vmx.c:2665 [inline]\n WARNING: CPU: 0 PID: 3606 at free_loaded_vmcs+0x158/0x1a0 arch/x86/kvm/vmx/vmx.c:2656\n Modules linked in:\n CPU: 1 PID: 3606 Comm: syz-executor725 Not tainted 5.17.0-rc1-syzkaller #0\n Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011\n RIP: 0010:free_loaded_vmcs arch/x86/kvm/vmx/vmx.c:2665 [inline]\n RIP: 0010:free_loaded_vmcs+0x158/0x1a0 arch/x86/kvm/vmx/vmx.c:2656\n Code: <0f> 0b eb b3 e8 8f 4d 9f 00 e9 f7 fe ff ff 48 89 df e8 92 4d 9f 00\n Call Trace:\n \n kvm_arch_vcpu_destroy+0x72/0x2f0 arch/x86/kvm/x86.c:11123\n kvm_vcpu_destroy arch/x86/kvm/../../../virt/kvm/kvm_main.c:441 [inline]\n kvm_destroy_vcpus+0x11f/0x290 arch/x86/kvm/../../../virt/kvm/kvm_main.c:460\n kvm_free_vcpus arch/x86/kvm/x86.c:11564 [inline]\n kvm_arch_destroy_vm+0x2e8/0x470 arch/x86/kvm/x86.c:11676\n kvm_destroy_vm arch/x86/kvm/../../../virt/kvm/kvm_main.c:1217 [inline]\n kvm_put_kvm+0x4fa/0xb00 arch/x86/kvm/../../../virt/kvm/kvm_main.c:1250\n kvm_vm_release+0x3f/0x50 arch/x86/kvm/../../../virt/kvm/kvm_main.c:1273\n __fput+0x286/0x9f0 fs/file_table.c:311\n task_work_run+0xdd/0x1a0 kernel/task_work.c:164\n exit_task_work include/linux/task_work.h:32 [inline]\n do_exit+0xb29/0x2a30 kernel/exit.c:806\n do_group_exit+0xd2/0x2f0 kernel/exit.c:935\n get_signal+0x4b0/0x28c0 kernel/signal.c:2862\n arch_do_signal_or_restart+0x2a9/0x1c40 arch/x86/kernel/signal.c:868\n handle_signal_work kernel/entry/common.c:148 [inline]\n exit_to_user_mode_loop kernel/entry/common.c:172 [inline]\n exit_to_user_mode_prepare+0x17d/0x290 kernel/entry/common.c:207\n __syscall_exit_to_user_mode_work kernel/entry/common.c:289 [inline]\n syscall_exit_to_user_mode+0x19/0x60 kernel/entry/common.c:300\n do_syscall_64+0x42/0xb0 arch/x86/entry/common.c:86\n entry_SYSCALL_64_after_hwframe+0x44/0xae\n " + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/080dbe7e9b86a0392d8dffc00d9971792afc121f", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/b4c0d89c92e957ecccce12e66b63875d0cc7af7e", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/e302786233e6bc512986d007c96458ccf5ca21c7", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/f7e570780efc5cec9b2ed1e0472a7da14e864fdb", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48764.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48764.json new file mode 100644 index 00000000000..cf2a7337624 --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48764.json @@ -0,0 +1,24 @@ +{ + "id": "CVE-2022-48764", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:14.450", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86: Free kvm_cpuid_entry2 array on post-KVM_RUN KVM_SET_CPUID{,2}\n\nFree the \"struct kvm_cpuid_entry2\" array on successful post-KVM_RUN\nKVM_SET_CPUID{,2} to fix a memory leak, the callers of kvm_set_cpuid()\nfree the array only on failure.\n\n BUG: memory leak\n unreferenced object 0xffff88810963a800 (size 2048):\n comm \"syz-executor025\", pid 3610, jiffies 4294944928 (age 8.080s)\n hex dump (first 32 bytes):\n 00 00 00 00 00 00 00 00 00 00 00 00 0d 00 00 00 ................\n 47 65 6e 75 6e 74 65 6c 69 6e 65 49 00 00 00 00 GenuntelineI....\n backtrace:\n [] kmalloc_node include/linux/slab.h:604 [inline]\n [] kvmalloc_node+0x3e/0x100 mm/util.c:580\n [] kvmalloc include/linux/slab.h:732 [inline]\n [] vmemdup_user+0x22/0x100 mm/util.c:199\n [] kvm_vcpu_ioctl_set_cpuid2+0x8f/0xf0 arch/x86/kvm/cpuid.c:423\n [] kvm_arch_vcpu_ioctl+0xb99/0x1e60 arch/x86/kvm/x86.c:5251\n [] kvm_vcpu_ioctl+0x4ad/0x950 arch/x86/kvm/../../../virt/kvm/kvm_main.c:4066\n [] vfs_ioctl fs/ioctl.c:51 [inline]\n [] __do_sys_ioctl fs/ioctl.c:874 [inline]\n [] __se_sys_ioctl fs/ioctl.c:860 [inline]\n [] __x64_sys_ioctl+0xfc/0x140 fs/ioctl.c:860\n [] do_syscall_x64 arch/x86/entry/common.c:50 [inline]\n [] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80\n [] entry_SYSCALL_64_after_hwframe+0x44/0xae" + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/811f95ff95270e6048197821434d9301e3d7f07c", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/b9ee734a14bb685b2088f2176d82b34cb4e30dbc", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48765.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48765.json new file mode 100644 index 00000000000..4e6160ef1b8 --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48765.json @@ -0,0 +1,28 @@ +{ + "id": "CVE-2022-48765", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:14.530", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: LAPIC: Also cancel preemption timer during SET_LAPIC\n\nThe below warning is splatting during guest reboot.\n\n ------------[ cut here ]------------\n WARNING: CPU: 0 PID: 1931 at arch/x86/kvm/x86.c:10322 kvm_arch_vcpu_ioctl_run+0x874/0x880 [kvm]\n CPU: 0 PID: 1931 Comm: qemu-system-x86 Tainted: G I 5.17.0-rc1+ #5\n RIP: 0010:kvm_arch_vcpu_ioctl_run+0x874/0x880 [kvm]\n Call Trace:\n \n kvm_vcpu_ioctl+0x279/0x710 [kvm]\n __x64_sys_ioctl+0x83/0xb0\n do_syscall_64+0x3b/0xc0\n entry_SYSCALL_64_after_hwframe+0x44/0xae\n RIP: 0033:0x7fd39797350b\n\nThis can be triggered by not exposing tsc-deadline mode and doing a reboot in\nthe guest. The lapic_shutdown() function which is called in sys_reboot path\nwill not disarm the flying timer, it just masks LVTT. lapic_shutdown() clears\nAPIC state w/ LVT_MASKED and timer-mode bit is 0, this can trigger timer-mode\nswitch between tsc-deadline and oneshot/periodic, which can result in preemption\ntimer be cancelled in apic_update_lvtt(). However, We can't depend on this when\nnot exposing tsc-deadline mode and oneshot/periodic modes emulated by preemption\ntimer. Qemu will synchronise states around reset, let's cancel preemption timer\nunder KVM_SET_LAPIC." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/35fe7cfbab2e81f1afb23fc4212210b1de6d9633", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/54b3439c8e70e0bcfea59aeef9dd98908cbbf655", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/ce55f63f6cea4cab8ae9212f73285648a5baa30d", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48766.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48766.json new file mode 100644 index 00000000000..841b5698bef --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48766.json @@ -0,0 +1,24 @@ +{ + "id": "CVE-2022-48766", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:14.617", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/display: Wrap dcn301_calculate_wm_and_dlg for FPU.\n\nMirrors the logic for dcn30. Cue lots of WARNs and some\nkernel panics without this fix." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/25f1488bdbba63415239ff301fe61a8546140d9f", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/456ba2433844a6483cc4c933aa8f43d24575e341", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48767.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48767.json new file mode 100644 index 00000000000..c9ab2074c18 --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48767.json @@ -0,0 +1,32 @@ +{ + "id": "CVE-2022-48767", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:14.703", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nceph: properly put ceph_string reference after async create attempt\n\nThe reference acquired by try_prep_async_create is currently leaked.\nEnsure we put it." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/36d433ae3242aa714176378850e6d1a5a3e78f18", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/932a9b5870d38b87ba0a9923c804b1af7d3605b9", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/a0c22e970cd78b81c94691e6cb09713e8074d580", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/e7be12ca7d3947765b0d7c1c7e0537e748da993a", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48768.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48768.json new file mode 100644 index 00000000000..4ef6f9c7e5f --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48768.json @@ -0,0 +1,36 @@ +{ + "id": "CVE-2022-48768", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:14.783", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ntracing/histogram: Fix a potential memory leak for kstrdup()\n\nkfree() is missing on an error path to free the memory allocated by\nkstrdup():\n\n p = param = kstrdup(data->params[i], GFP_KERNEL);\n\nSo it is better to free it via kfree(p)." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/8a8878ebb596281f50fc0b9a6e1f23f0d7f154e8", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/d71b06aa995007eafd247626d0669b9364c42ad7", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/df86e2fe808c3536a9dba353cc2bebdfea00d0cf", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/e33fa4a46ee22de88a700e2e3d033da8214a5175", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/e629e7b525a179e29d53463d992bdee759c950fb", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48769.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48769.json new file mode 100644 index 00000000000..85240c5b4f0 --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48769.json @@ -0,0 +1,32 @@ +{ + "id": "CVE-2022-48769", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:14.870", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nefi: runtime: avoid EFIv2 runtime services on Apple x86 machines\n\nAditya reports [0] that his recent MacbookPro crashes in the firmware\nwhen using the variable services at runtime. The culprit appears to be a\ncall to QueryVariableInfo(), which we did not use to call on Apple x86\nmachines in the past as they only upgraded from EFI v1.10 to EFI v2.40\nfirmware fairly recently, and QueryVariableInfo() (along with\nUpdateCapsule() et al) was added in EFI v2.00.\n\nThe only runtime service introduced in EFI v2.00 that we actually use in\nLinux is QueryVariableInfo(), as the capsule based ones are optional,\ngenerally not used at runtime (all the LVFS/fwupd firmware update\ninfrastructure uses helper EFI programs that invoke capsule update at\nboot time, not runtime), and not implemented by Apple machines in the\nfirst place. QueryVariableInfo() is used to 'safely' set variables,\ni.e., only when there is enough space. This prevents machines with buggy\nfirmwares from corrupting their NVRAMs when they run out of space.\n\nGiven that Apple machines have been using EFI v1.10 services only for\nthe longest time (the EFI v2.0 spec was released in 2006, and Linux\nsupport for the newly introduced runtime services was added in 2011, but\nthe MacbookPro12,1 released in 2015 still claims to be EFI v1.10 only),\nlet's avoid the EFI v2.0 ones on all Apple x86 machines.\n\n[0] https://lore.kernel.org/all/6D757C75-65B1-468B-842D-10410081A8E4@live.com/" + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/3df52448978802ae15dcebf66beba1029df957b4", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/a4085859411c825c321c9b55b8a9dc5a128a6684", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/b0f1cc093bc2493ac259c53766fd2b800e085807", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/f5390cd0b43c2e54c7cf5506c7da4a37c5cef746", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48770.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48770.json new file mode 100644 index 00000000000..7ac70535ac3 --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48770.json @@ -0,0 +1,32 @@ +{ + "id": "CVE-2022-48770", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:14.953", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Guard against accessing NULL pt_regs in bpf_get_task_stack()\n\ntask_pt_regs() can return NULL on powerpc for kernel threads. This is\nthen used in __bpf_get_stack() to check for user mode, resulting in a\nkernel oops. Guard against this by checking return value of\ntask_pt_regs() before trying to obtain the call chain." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/0bcd484587b3b3092e448d27dc369e347e1810c3", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/b82ef4985a6d05e80f604624332430351df7b79a", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/b992f01e66150fc5e90be4a96f5eb8e634c8249e", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/ff6bdc205fd0a83bd365405d4e31fb5905826996", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2022/CVE-2022-487xx/CVE-2022-48771.json b/CVE-2022/CVE-2022-487xx/CVE-2022-48771.json new file mode 100644 index 00000000000..64f082c3fd4 --- /dev/null +++ b/CVE-2022/CVE-2022-487xx/CVE-2022-48771.json @@ -0,0 +1,44 @@ +{ + "id": "CVE-2022-48771", + "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", + "published": "2024-06-20T12:15:15.043", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Fix stale file descriptors on failed usercopy\n\nA failing usercopy of the fence_rep object will lead to a stale entry in\nthe file descriptor table as put_unused_fd() won't release it. This\nenables userland to refer to a dangling 'file' object through that still\nvalid file descriptor, leading to all kinds of use-after-free\nexploitation scenarios.\n\nFix this by deferring the call to fd_install() until after the usercopy\nhas succeeded." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/0008a0c78fc33a84e2212a7c04e6b21a36ca6f4d", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/1d833b27fb708d6fdf5de9f6b3a8be4bd4321565", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/6066977961fc6f437bc064f628cf9b0e4571c56c", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/84b1259fe36ae0915f3d6ddcea6377779de48b82", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/a0f90c8815706981c483a652a6aefca51a5e191c", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/ae2b20f27732fe92055d9e7b350abc5cdf3e2414", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/e8d092a62449dcfc73517ca43963d2b8f44d0516", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2023/CVE-2023-256xx/CVE-2023-25646.json b/CVE-2023/CVE-2023-256xx/CVE-2023-25646.json index c5f4a09bb4f..4fc29b1ae62 100644 --- a/CVE-2023/CVE-2023-256xx/CVE-2023-25646.json +++ b/CVE-2023/CVE-2023-256xx/CVE-2023-25646.json @@ -2,12 +2,16 @@ "id": "CVE-2023-25646", "sourceIdentifier": "psirt@zte.com.cn", "published": "2024-06-20T07:15:41.340", - "lastModified": "2024-06-20T07:15:41.340", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "There is an unauthorized access vulnerability in ZTE H388X. If H388X is caused by brute-force serial port cracking,attackers with common user permissions can use this vulnerability to obtain elevated permissions on the affected device by performing specific operations." + }, + { + "lang": "es", + "value": "Existe una vulnerabilidad de acceso no autorizado en ZTE H388X. Si H388X es causado por un craqueo del puerto serie por fuerza bruta, los atacantes con permisos de usuario comunes pueden usar esta vulnerabilidad para obtener permisos elevados en el dispositivo afectado mediante la realizaci\u00f3n de operaciones espec\u00edficas." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-256xx/CVE-2023-25697.json b/CVE-2023/CVE-2023-256xx/CVE-2023-25697.json index d4c321ddb63..f204529776b 100644 --- a/CVE-2023/CVE-2023-256xx/CVE-2023-25697.json +++ b/CVE-2023/CVE-2023-256xx/CVE-2023-25697.json @@ -2,12 +2,16 @@ "id": "CVE-2023-25697", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T15:15:56.513", - "lastModified": "2024-06-19T15:15:56.513", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Cross-Site Request Forgery (CSRF) vulnerability in GamiPress.This issue affects GamiPress: from n/a through 2.5.6." + }, + { + "lang": "es", + "value": "Vulnerabilidad de Cross-Site Request Forgery (CSRF) en GamiPress. Este problema afecta a GamiPress: desde n/a hasta 2.5.6." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-32xx/CVE-2023-3204.json b/CVE-2023/CVE-2023-32xx/CVE-2023-3204.json index a1630b9c06e..7b5f0ffe2f3 100644 --- a/CVE-2023/CVE-2023-32xx/CVE-2023-3204.json +++ b/CVE-2023/CVE-2023-32xx/CVE-2023-3204.json @@ -2,12 +2,16 @@ "id": "CVE-2023-3204", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-20T02:15:09.147", - "lastModified": "2024-06-20T02:15:09.147", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "The Materialis theme for WordPress is vulnerable to limited arbitrary options updates in versions up to, and including, 1.1.24. This is due to missing authorization checks on the companion_disable_popup() function called via an AJAX action. This makes it possible for authenticated attackers, with minimal permissions such as subscribers, to modify any option on the site to a numerical value." + }, + { + "lang": "es", + "value": "El tema Materialis para WordPress es vulnerable a actualizaciones limitadas de opciones arbitrarias en versiones hasta la 1.1.24 incluida. Esto se debe a que faltan comprobaciones de autorizaci\u00f3n en la funci\u00f3n complementario_disable_popup() llamada mediante una acci\u00f3n AJAX. Esto hace posible que atacantes autenticados, con permisos m\u00ednimos, como suscriptores, modifiquen cualquier opci\u00f3n en el sitio a un valor num\u00e9rico." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-350xx/CVE-2023-35049.json b/CVE-2023/CVE-2023-350xx/CVE-2023-35049.json index 54641132fa5..b371195a638 100644 --- a/CVE-2023/CVE-2023-350xx/CVE-2023-35049.json +++ b/CVE-2023/CVE-2023-350xx/CVE-2023-35049.json @@ -2,12 +2,16 @@ "id": "CVE-2023-35049", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T13:15:52.287", - "lastModified": "2024-06-19T13:15:52.287", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in WooCommerce WooCommerce Stripe Payment Gateway.This issue affects WooCommerce Stripe Payment Gateway: from n/a through 7.4.0." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en WooCommerce WooCommerce Stripe Payment Gateway. Este problema afecta a WooCommerce Stripe Payment Gateway: desde n/a hasta 7.4.0." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-350xx/CVE-2023-35050.json b/CVE-2023/CVE-2023-350xx/CVE-2023-35050.json index 7b6b72380dc..0e757ac9b82 100644 --- a/CVE-2023/CVE-2023-350xx/CVE-2023-35050.json +++ b/CVE-2023/CVE-2023-350xx/CVE-2023-35050.json @@ -2,12 +2,16 @@ "id": "CVE-2023-35050", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T13:15:52.600", - "lastModified": "2024-06-19T13:15:52.600", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in Elementor Elementor Pro.This issue affects Elementor Pro: from n/a through 3.13.0." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en Elementor Elementor Pro. Este problema afecta a Elementor Pro: desde n/a hasta 3.13.0." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-365xx/CVE-2023-36512.json b/CVE-2023/CVE-2023-365xx/CVE-2023-36512.json index 25d3780f5b6..d752bcd6762 100644 --- a/CVE-2023/CVE-2023-365xx/CVE-2023-36512.json +++ b/CVE-2023/CVE-2023-365xx/CVE-2023-36512.json @@ -2,12 +2,16 @@ "id": "CVE-2023-36512", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T13:15:52.893", - "lastModified": "2024-06-19T13:15:52.893", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in Woo AutomateWoo.This issue affects AutomateWoo: from n/a through 5.7.5." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en Woo AutomateWoo. Este problema afecta a AutomateWoo: desde n/a hasta 5.7.5." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-365xx/CVE-2023-36515.json b/CVE-2023/CVE-2023-365xx/CVE-2023-36515.json index 96e24ab3397..170b1c54fff 100644 --- a/CVE-2023/CVE-2023-365xx/CVE-2023-36515.json +++ b/CVE-2023/CVE-2023-365xx/CVE-2023-36515.json @@ -2,12 +2,16 @@ "id": "CVE-2023-36515", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T15:15:56.847", - "lastModified": "2024-06-19T15:15:56.847", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in ThimPress LearnPress.This issue affects LearnPress: from n/a through 4.2.3." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en ThimPress LearnPress. Este problema afecta a LearnPress: desde n/a hasta 4.2.3." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-365xx/CVE-2023-36516.json b/CVE-2023/CVE-2023-365xx/CVE-2023-36516.json index 8efbe27231f..a4beb377f5e 100644 --- a/CVE-2023/CVE-2023-365xx/CVE-2023-36516.json +++ b/CVE-2023/CVE-2023-365xx/CVE-2023-36516.json @@ -2,12 +2,16 @@ "id": "CVE-2023-36516", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T15:15:57.133", - "lastModified": "2024-06-19T15:15:57.133", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in ThimPress LearnPress.This issue affects LearnPress: from n/a through 4.2.3." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en ThimPress LearnPress. Este problema afecta a LearnPress: desde n/a hasta 4.2.3." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-366xx/CVE-2023-36676.json b/CVE-2023/CVE-2023-366xx/CVE-2023-36676.json index 6e19b5679db..a0123f5c486 100644 --- a/CVE-2023/CVE-2023-366xx/CVE-2023-36676.json +++ b/CVE-2023/CVE-2023-366xx/CVE-2023-36676.json @@ -2,12 +2,16 @@ "id": "CVE-2023-36676", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T14:15:11.867", - "lastModified": "2024-06-19T14:15:11.867", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in Brainstorm Force Spectra.This issue affects Spectra: from n/a through 2.6.6." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en Brainstorm Force Spectra. Este problema afecta a Spectra: desde n/a hasta 2.6.6." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-366xx/CVE-2023-36683.json b/CVE-2023/CVE-2023-366xx/CVE-2023-36683.json index 39d399f2874..aa04e289f16 100644 --- a/CVE-2023/CVE-2023-366xx/CVE-2023-36683.json +++ b/CVE-2023/CVE-2023-366xx/CVE-2023-36683.json @@ -2,12 +2,16 @@ "id": "CVE-2023-36683", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T14:15:12.137", - "lastModified": "2024-06-19T14:15:12.137", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in WP SCHEMA PRO Schema Pro.This issue affects Schema Pro: from n/a through 2.7.8." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en WP SCHEMA PRO Schema Pro. Este problema afecta a Schema Pro: desde n/a hasta 2.7.8." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-366xx/CVE-2023-36684.json b/CVE-2023/CVE-2023-366xx/CVE-2023-36684.json index a0dc526380f..e085b3039f6 100644 --- a/CVE-2023/CVE-2023-366xx/CVE-2023-36684.json +++ b/CVE-2023/CVE-2023-366xx/CVE-2023-36684.json @@ -2,12 +2,16 @@ "id": "CVE-2023-36684", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T14:15:12.380", - "lastModified": "2024-06-19T14:15:12.380", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in Brainstorm Force Convert Pro.This issue affects Convert Pro: from n/a through 1.7.5." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en Brainstorm Force Convert Pro. Este problema afecta a Convert Pro: desde n/a hasta 1.7.5." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-370xx/CVE-2023-37057.json b/CVE-2023/CVE-2023-370xx/CVE-2023-37057.json index f06fa74c874..a5ef97a56f7 100644 --- a/CVE-2023/CVE-2023-370xx/CVE-2023-37057.json +++ b/CVE-2023/CVE-2023-370xx/CVE-2023-37057.json @@ -2,12 +2,16 @@ "id": "CVE-2023-37057", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T21:15:50.380", - "lastModified": "2024-06-17T21:15:50.380", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "An issue in JLINK Unionman Technology Co. Ltd Jlink AX1800 v.1.0 allows a remote attacker to execute arbitrary code via the router's authentication mechanism." + }, + { + "lang": "es", + "value": "Un problema en JLINK Unionman Technology Co. Ltd. Jlink AX1800 v.1.0 permite a un atacante remoto ejecutar c\u00f3digo arbitrario a trav\u00e9s del mecanismo de autenticaci\u00f3n del enrutador." } ], "metrics": {}, diff --git a/CVE-2023/CVE-2023-370xx/CVE-2023-37058.json b/CVE-2023/CVE-2023-370xx/CVE-2023-37058.json index ac9a3f1b2ec..3e8c0d88115 100644 --- a/CVE-2023/CVE-2023-370xx/CVE-2023-37058.json +++ b/CVE-2023/CVE-2023-370xx/CVE-2023-37058.json @@ -2,12 +2,16 @@ "id": "CVE-2023-37058", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T21:15:50.503", - "lastModified": "2024-06-17T21:15:50.503", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Insecure Permissions vulnerability in JLINK Unionman Technology Co. Ltd Jlink AX1800 v.1.0 allows a remote attacker to escalate privileges via a crafted command." + }, + { + "lang": "es", + "value": "Vulnerabilidad de permisos inseguros en JLINK Unionman Technology Co. Ltd. Jlink AX1800 v.1.0 permite a un atacante remoto escalar privilegios mediante un comando manipulado." } ], "metrics": {}, diff --git a/CVE-2023/CVE-2023-378xx/CVE-2023-37869.json b/CVE-2023/CVE-2023-378xx/CVE-2023-37869.json index 51d65f69b10..8748b14152e 100644 --- a/CVE-2023/CVE-2023-378xx/CVE-2023-37869.json +++ b/CVE-2023/CVE-2023-378xx/CVE-2023-37869.json @@ -2,12 +2,16 @@ "id": "CVE-2023-37869", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T14:15:12.617", - "lastModified": "2024-06-19T14:15:12.617", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in Premium Addons Premium Addons PRO.This issue affects Premium Addons PRO: from n/a through 2.9.0." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en Premium Addons Premium Addons PRO. Este problema afecta a Premium Addons PRO: desde n/a hasta 2.9.0." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-378xx/CVE-2023-37870.json b/CVE-2023/CVE-2023-378xx/CVE-2023-37870.json index 7dcb33dbef6..4303a13b08e 100644 --- a/CVE-2023/CVE-2023-378xx/CVE-2023-37870.json +++ b/CVE-2023/CVE-2023-378xx/CVE-2023-37870.json @@ -2,12 +2,16 @@ "id": "CVE-2023-37870", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T13:15:53.163", - "lastModified": "2024-06-19T13:15:53.163", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in Woo WooCommerce Warranty Requests.This issue affects WooCommerce Warranty Requests: from n/a through 2.1.9." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en Woo WooCommerce Warranty Requests. Este problema afecta a WooCommerce Warranty Requests: desde n/a hasta 2.1.9." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-378xx/CVE-2023-37872.json b/CVE-2023/CVE-2023-378xx/CVE-2023-37872.json index cb37037075e..9ee02b63cdf 100644 --- a/CVE-2023/CVE-2023-378xx/CVE-2023-37872.json +++ b/CVE-2023/CVE-2023-378xx/CVE-2023-37872.json @@ -2,12 +2,16 @@ "id": "CVE-2023-37872", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T14:15:12.853", - "lastModified": "2024-06-19T14:15:12.853", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in Woo WooCommerce Ship to Multiple Addresses.This issue affects WooCommerce Ship to Multiple Addresses: from n/a through 3.8.5." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en Woo WooCommerce Ship to Multiple Addresses. Este problema afecta a WooCommerce Ship to Multiple Addresses: desde n/a hasta 3.8.5." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-383xx/CVE-2023-38386.json b/CVE-2023/CVE-2023-383xx/CVE-2023-38386.json index ed669fcd979..50c737eb247 100644 --- a/CVE-2023/CVE-2023-383xx/CVE-2023-38386.json +++ b/CVE-2023/CVE-2023-383xx/CVE-2023-38386.json @@ -2,12 +2,16 @@ "id": "CVE-2023-38386", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T13:15:53.440", - "lastModified": "2024-06-19T13:15:53.440", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in Saturday Drive Ninja Forms.This issue affects Ninja Forms: from n/a through 3.6.25." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en Saturday Drive Ninja Forms. Este problema afecta a Ninja Forms: desde n/a hasta 3.6.25." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-383xx/CVE-2023-38393.json b/CVE-2023/CVE-2023-383xx/CVE-2023-38393.json index 37e0451706f..a0e204020c7 100644 --- a/CVE-2023/CVE-2023-383xx/CVE-2023-38393.json +++ b/CVE-2023/CVE-2023-383xx/CVE-2023-38393.json @@ -2,12 +2,16 @@ "id": "CVE-2023-38393", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T15:15:57.420", - "lastModified": "2024-06-19T15:15:57.420", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in Saturday Drive Ninja Forms.This issue affects Ninja Forms: from n/a through 3.6.25." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en Saturday Drive Ninja Forms. Este problema afecta a Ninja Forms: desde n/a hasta 3.6.25." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-383xx/CVE-2023-38394.json b/CVE-2023/CVE-2023-383xx/CVE-2023-38394.json index 9156d00eeef..d98352af748 100644 --- a/CVE-2023/CVE-2023-383xx/CVE-2023-38394.json +++ b/CVE-2023/CVE-2023-383xx/CVE-2023-38394.json @@ -2,12 +2,16 @@ "id": "CVE-2023-38394", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T15:15:57.710", - "lastModified": "2024-06-19T15:15:57.710", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in Artbees JupiterX Core.This issue affects JupiterX Core: from 3.0.0 through 3.3.0." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en Artbees JupiterX Core. Este problema afecta a JupiterX Core: desde 3.0.0 hasta 3.3.0." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-393xx/CVE-2023-39310.json b/CVE-2023/CVE-2023-393xx/CVE-2023-39310.json index c9762fe58c1..f3420d64900 100644 --- a/CVE-2023/CVE-2023-393xx/CVE-2023-39310.json +++ b/CVE-2023/CVE-2023-393xx/CVE-2023-39310.json @@ -2,12 +2,16 @@ "id": "CVE-2023-39310", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T14:15:13.100", - "lastModified": "2024-06-19T14:15:13.100", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in ThemeFusion Fusion Builder.This issue affects Fusion Builder: from n/a through 3.11.1." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en ThemeFusion Fusion Builder. Este problema afecta a Fusion Builder: desde n/a hasta 3.11.1." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-393xx/CVE-2023-39312.json b/CVE-2023/CVE-2023-393xx/CVE-2023-39312.json index 1bd1ad21c03..3506af0e6a3 100644 --- a/CVE-2023/CVE-2023-393xx/CVE-2023-39312.json +++ b/CVE-2023/CVE-2023-393xx/CVE-2023-39312.json @@ -2,12 +2,16 @@ "id": "CVE-2023-39312", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T15:15:58.020", - "lastModified": "2024-06-19T15:15:58.020", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in ThemeFusion Avada.This issue affects Avada: from n/a through 7.11.1." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en ThemeFusion Avada. Este problema afecta a Avada: desde n/a hasta 7.11.1." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-399xx/CVE-2023-39922.json b/CVE-2023/CVE-2023-399xx/CVE-2023-39922.json index 5f63a121cf5..9f9cd5dd5f6 100644 --- a/CVE-2023/CVE-2023-399xx/CVE-2023-39922.json +++ b/CVE-2023/CVE-2023-399xx/CVE-2023-39922.json @@ -2,12 +2,16 @@ "id": "CVE-2023-39922", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T13:15:53.700", - "lastModified": "2024-06-19T13:15:53.700", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in ThemeFusion Avada.This issue affects Avada: from n/a through 7.11.1." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en ThemeFusion Avada. Este problema afecta a Avada: desde n/a hasta 7.11.1." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-399xx/CVE-2023-39990.json b/CVE-2023/CVE-2023-399xx/CVE-2023-39990.json index 8e2a8cf9f4e..bdbd4b9f64b 100644 --- a/CVE-2023/CVE-2023-399xx/CVE-2023-39990.json +++ b/CVE-2023/CVE-2023-399xx/CVE-2023-39990.json @@ -2,12 +2,16 @@ "id": "CVE-2023-39990", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T13:15:54.157", - "lastModified": "2024-06-19T13:15:54.157", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in Paid Memberships Pro.This issue affects Paid Memberships Pro: from n/a through 1.2.3." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en Paid Memberships Pro. Este problema afecta a Paid Memberships Pro: desde n/a hasta 1.2.3." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-399xx/CVE-2023-39993.json b/CVE-2023/CVE-2023-399xx/CVE-2023-39993.json index e1aa7725999..e61f4b0859e 100644 --- a/CVE-2023/CVE-2023-399xx/CVE-2023-39993.json +++ b/CVE-2023/CVE-2023-399xx/CVE-2023-39993.json @@ -2,12 +2,16 @@ "id": "CVE-2023-39993", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T13:15:54.400", - "lastModified": "2024-06-19T13:15:54.400", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in Wpmet Elements kit Elementor addons.This issue affects Elements kit Elementor addons: from n/a through 2.9.0." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en Wpmet Elements kit Elementor addons. Este problema afecta a Elements kit Elementor addons: desde n/a hasta 2.9.0." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-399xx/CVE-2023-39998.json b/CVE-2023/CVE-2023-399xx/CVE-2023-39998.json index 3b90150fb79..2463ed9009a 100644 --- a/CVE-2023/CVE-2023-399xx/CVE-2023-39998.json +++ b/CVE-2023/CVE-2023-399xx/CVE-2023-39998.json @@ -2,12 +2,16 @@ "id": "CVE-2023-39998", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T13:15:54.633", - "lastModified": "2024-06-19T13:15:54.633", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in Muffingroup Betheme.This issue affects Betheme: from n/a through 27.1.1." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en Muffingroup Betheme. Este problema afecta a Betheme: desde n/a hasta 27.1.1." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-400xx/CVE-2023-40004.json b/CVE-2023/CVE-2023-400xx/CVE-2023-40004.json index 91a0fdb63bd..c8eee684230 100644 --- a/CVE-2023/CVE-2023-400xx/CVE-2023-40004.json +++ b/CVE-2023/CVE-2023-400xx/CVE-2023-40004.json @@ -2,12 +2,16 @@ "id": "CVE-2023-40004", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T12:15:09.687", - "lastModified": "2024-06-19T12:15:09.687", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in ServMask All-in-One WP Migration Box Extension, ServMask All-in-One WP Migration OneDrive Extension, ServMask All-in-One WP Migration Dropbox Extension, ServMask All-in-One WP Migration Google Drive Extension.This issue affects All-in-One WP Migration Box Extension: from n/a through 1.53; All-in-One WP Migration OneDrive Extension: from n/a through 1.66; All-in-One WP Migration Dropbox Extension: from n/a through 3.75; All-in-One WP Migration Google Drive Extension: from n/a through 2.79." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en ServMask All-in-One WP Migration Box Extension, ServMask All-in-One WP Migration OneDrive Extension, ServMask All-in-One WP Migration Dropbox Extension, ServMask All-in-One WP Migration Google Drive Extension. El problema afecta a la extensi\u00f3n All-in-One WP Migration Box: desde n/a hasta 1.53; Extension OneDrive de migraci\u00f3n de WP todo en uno: desde n/a hasta 1.66; Extension de Dropbox de migraci\u00f3n de WP todo en uno: desde n/a hasta 3.75; Extension de Google Drive de migraci\u00f3n de WP todo en uno: desde n/a hasta 2.79." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-406xx/CVE-2023-40608.json b/CVE-2023/CVE-2023-406xx/CVE-2023-40608.json index ca3cf84635e..b47f9be40ec 100644 --- a/CVE-2023/CVE-2023-406xx/CVE-2023-40608.json +++ b/CVE-2023/CVE-2023-406xx/CVE-2023-40608.json @@ -2,12 +2,16 @@ "id": "CVE-2023-40608", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T12:15:09.960", - "lastModified": "2024-06-19T12:15:09.960", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in Paid Memberships Pro Paid Memberships Pro CCBill Gateway.This issue affects Paid Memberships Pro CCBill Gateway: from n/a through 0.3." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en Paid Memberships Pro Paid Memberships Pro CCBill Gateway. Este problema afecta a Paid Memberships Pro CCBill Gateway: desde n/a hasta 0.3." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-418xx/CVE-2023-41805.json b/CVE-2023/CVE-2023-418xx/CVE-2023-41805.json index 23634f681a6..2bdc76a4978 100644 --- a/CVE-2023/CVE-2023-418xx/CVE-2023-41805.json +++ b/CVE-2023/CVE-2023-418xx/CVE-2023-41805.json @@ -2,12 +2,16 @@ "id": "CVE-2023-41805", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T13:15:55.360", - "lastModified": "2024-06-19T13:15:55.360", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in Brainstorm Force Premium Starter Templates, Brainstorm Force Starter Templates astra-sites.This issue affects Premium Starter Templates: from n/a through 3.2.5; Starter Templates: from n/a through 3.2.5." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en Brainstorm Force Premium Starter Templates, Brainstorm Force Starter Templates astra-sites. Este problema afecta a Premium Starter Templates: desde n/a hasta 3.2.5; Starter Templates: desde n/a hasta 3.2.5." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-441xx/CVE-2023-44148.json b/CVE-2023/CVE-2023-441xx/CVE-2023-44148.json index be75f48db1d..624be4a1f11 100644 --- a/CVE-2023/CVE-2023-441xx/CVE-2023-44148.json +++ b/CVE-2023/CVE-2023-441xx/CVE-2023-44148.json @@ -2,12 +2,16 @@ "id": "CVE-2023-44148", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T12:15:10.200", - "lastModified": "2024-06-19T12:15:10.200", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in Brainstorm Force Astra Bulk Edit.This issue affects Astra Bulk Edit: from n/a through 1.2.7." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en Brainstorm Force Astra Bulk Edit. Este problema afecta a Astra Bulk Edit: desde n/a hasta 1.2.7." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-441xx/CVE-2023-44151.json b/CVE-2023/CVE-2023-441xx/CVE-2023-44151.json index 926a5571d54..41c916ea922 100644 --- a/CVE-2023/CVE-2023-441xx/CVE-2023-44151.json +++ b/CVE-2023/CVE-2023-441xx/CVE-2023-44151.json @@ -2,12 +2,16 @@ "id": "CVE-2023-44151", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T12:15:10.437", - "lastModified": "2024-06-19T12:15:10.437", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in Brainstorm Force Pre-Publish Checklist.This issue affects Pre-Publish Checklist: from n/a through 1.1.1." + }, + { + "lang": "es", + "value": "Vulnerabilidad de falta de autorizaci\u00f3n en Brainstorm Force Pre-Publish Checklist. Este problema afecta a Pre-Publish Checklist: desde n/a hasta 1.1.1." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-456xx/CVE-2023-45658.json b/CVE-2023/CVE-2023-456xx/CVE-2023-45658.json index d95e41738a9..c9a96541c25 100644 --- a/CVE-2023/CVE-2023-456xx/CVE-2023-45658.json +++ b/CVE-2023/CVE-2023-456xx/CVE-2023-45658.json @@ -2,12 +2,16 @@ "id": "CVE-2023-45658", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T12:15:10.677", - "lastModified": "2024-06-19T12:15:10.677", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in POSIMYTH Nexter.This issue affects Nexter: from n/a through 2.0.3." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en POSIMYTH Nexter. Este problema afecta a Nexter: desde n/a hasta 2.0.3." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-461xx/CVE-2023-46146.json b/CVE-2023/CVE-2023-461xx/CVE-2023-46146.json index 7409cad34a8..2921d121026 100644 --- a/CVE-2023/CVE-2023-461xx/CVE-2023-46146.json +++ b/CVE-2023/CVE-2023-461xx/CVE-2023-46146.json @@ -2,12 +2,16 @@ "id": "CVE-2023-46146", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T12:15:10.930", - "lastModified": "2024-06-19T12:15:10.930", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in Themify Themify Ultra.This issue affects Themify Ultra: from n/a through 7.3.5." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en Themify Themify Ultra. Este problema afecta a Themify Ultra: desde n/a hasta 7.3.5." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-461xx/CVE-2023-46148.json b/CVE-2023/CVE-2023-461xx/CVE-2023-46148.json index 65ad3a55f17..c82f7aa8132 100644 --- a/CVE-2023/CVE-2023-461xx/CVE-2023-46148.json +++ b/CVE-2023/CVE-2023-461xx/CVE-2023-46148.json @@ -2,12 +2,16 @@ "id": "CVE-2023-46148", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T12:15:11.160", - "lastModified": "2024-06-19T12:15:11.160", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in Themify Themify Ultra.This issue affects Themify Ultra: from n/a through 7.3.5." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en Themify Themify Ultra. Este problema afecta a Themify Ultra: desde n/a hasta 7.3.5." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-476xx/CVE-2023-47681.json b/CVE-2023/CVE-2023-476xx/CVE-2023-47681.json index b4abeecf511..a5e008b8c2f 100644 --- a/CVE-2023/CVE-2023-476xx/CVE-2023-47681.json +++ b/CVE-2023/CVE-2023-476xx/CVE-2023-47681.json @@ -2,12 +2,16 @@ "id": "CVE-2023-47681", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T12:15:11.393", - "lastModified": "2024-06-19T12:15:11.393", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in QuadLayers WooCommerce Checkout Manager.This issue affects WooCommerce Checkout Manager: from n/a through 7.3.0." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en QuadLayers WooCommerce Checkout Manager. Este problema afecta a WooCommerce Checkout Manager: desde n/a hasta 7.3.0." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-477xx/CVE-2023-47726.json b/CVE-2023/CVE-2023-477xx/CVE-2023-47726.json index 9183be7e758..ab802be8215 100644 --- a/CVE-2023/CVE-2023-477xx/CVE-2023-47726.json +++ b/CVE-2023/CVE-2023-477xx/CVE-2023-47726.json @@ -2,12 +2,16 @@ "id": "CVE-2023-47726", "sourceIdentifier": "psirt@us.ibm.com", "published": "2024-06-18T14:15:10.317", - "lastModified": "2024-06-18T14:15:10.317", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "IBM QRadar Suite Software 1.10.12.0 through 1.10.21.0 and IBM Cloud Pak for Security 1.10.12.0 through 1.10.21.0 could allow an authenticated user to execute certain arbitrary commands due to improper input validation. IBM X-Force ID: 272087." + }, + { + "lang": "es", + "value": "IBM QRadar Suite Software 1.10.12.0 a 1.10.21.0 e IBM Cloud Pak for Security 1.10.12.0 a 1.10.21.0 podr\u00edan permitir que un usuario autenticado ejecute ciertos comandos arbitrarios debido a una validaci\u00f3n de entrada incorrecta. ID de IBM X-Force: 272087." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-477xx/CVE-2023-47770.json b/CVE-2023/CVE-2023-477xx/CVE-2023-47770.json index 101c0b2f07e..837447bd5c7 100644 --- a/CVE-2023/CVE-2023-477xx/CVE-2023-47770.json +++ b/CVE-2023/CVE-2023-477xx/CVE-2023-47770.json @@ -2,12 +2,16 @@ "id": "CVE-2023-47770", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T12:15:11.630", - "lastModified": "2024-06-19T12:15:11.630", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in Muffin Group Betheme.This issue affects Betheme: from n/a through 27.1.1." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en Muffin Group Betheme. Este problema afecta a Betheme: desde n/a hasta 27.1.1." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-477xx/CVE-2023-47771.json b/CVE-2023/CVE-2023-477xx/CVE-2023-47771.json index eb5be461918..ea90f13ba48 100644 --- a/CVE-2023/CVE-2023-477xx/CVE-2023-47771.json +++ b/CVE-2023/CVE-2023-477xx/CVE-2023-47771.json @@ -2,12 +2,16 @@ "id": "CVE-2023-47771", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T11:15:49.640", - "lastModified": "2024-06-19T11:15:49.640", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in ThemePunch OHG Essential Grid.This issue affects Essential Grid: from n/a through 3.0.18." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en ThemePunch OHG Essential Grid. Este problema afecta a Essential Grid: desde n/a hasta 3.0.18." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-477xx/CVE-2023-47783.json b/CVE-2023/CVE-2023-477xx/CVE-2023-47783.json index 09626d48347..4b7cec89618 100644 --- a/CVE-2023/CVE-2023-477xx/CVE-2023-47783.json +++ b/CVE-2023/CVE-2023-477xx/CVE-2023-47783.json @@ -2,12 +2,16 @@ "id": "CVE-2023-47783", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T11:15:49.933", - "lastModified": "2024-06-19T11:15:49.933", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in Thrive Themes Thrive Theme Builder.This issue affects Thrive Theme Builder: from n/a before 3.24.0." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en Thrive Themes Thrive Theme Builder. Este problema afecta a Thrive Theme Builder: desde n/a antes de 3.24.0." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-477xx/CVE-2023-47788.json b/CVE-2023/CVE-2023-477xx/CVE-2023-47788.json index a08ad849614..3ad18476df9 100644 --- a/CVE-2023/CVE-2023-477xx/CVE-2023-47788.json +++ b/CVE-2023/CVE-2023-477xx/CVE-2023-47788.json @@ -2,12 +2,16 @@ "id": "CVE-2023-47788", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T11:15:50.177", - "lastModified": "2024-06-19T11:15:50.177", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in Automattic Jetpack.This issue affects Jetpack: from n/a before 12.7." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en Automattic Jetpack. Este problema afecta a Jetpack: desde n/a antes de 12.7." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-487xx/CVE-2023-48759.json b/CVE-2023/CVE-2023-487xx/CVE-2023-48759.json index 7e208955ff4..272f9bcab1f 100644 --- a/CVE-2023/CVE-2023-487xx/CVE-2023-48759.json +++ b/CVE-2023/CVE-2023-487xx/CVE-2023-48759.json @@ -2,12 +2,16 @@ "id": "CVE-2023-48759", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T11:15:50.407", - "lastModified": "2024-06-19T11:15:50.407", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in Crocoblock JetElements For Elementor.This issue affects JetElements For Elementor: from n/a through 2.6.13." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en Crocoblock JetElements para Elementor. Este problema afecta a JetElements para Elementor: desde n/a hasta 2.6.13." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-487xx/CVE-2023-48760.json b/CVE-2023/CVE-2023-487xx/CVE-2023-48760.json index 5d27495db75..1251ea78dfb 100644 --- a/CVE-2023/CVE-2023-487xx/CVE-2023-48760.json +++ b/CVE-2023/CVE-2023-487xx/CVE-2023-48760.json @@ -2,12 +2,16 @@ "id": "CVE-2023-48760", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T11:15:50.647", - "lastModified": "2024-06-19T11:15:50.647", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in Crocoblock JetElements For Elementor.This issue affects JetElements For Elementor: from n/a through 2.6.13." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en Crocoblock JetElements para Elementor. Este problema afecta a JetElements para Elementor: desde n/a hasta 2.6.13." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-487xx/CVE-2023-48761.json b/CVE-2023/CVE-2023-487xx/CVE-2023-48761.json index c80b3de098a..d271abe64e7 100644 --- a/CVE-2023/CVE-2023-487xx/CVE-2023-48761.json +++ b/CVE-2023/CVE-2023-487xx/CVE-2023-48761.json @@ -2,12 +2,16 @@ "id": "CVE-2023-48761", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T11:15:50.877", - "lastModified": "2024-06-19T11:15:50.877", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in Crocoblock JetElements For Elementor.This issue affects JetElements For Elementor: from n/a through 2.6.13." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en Crocoblock JetElements para Elementor. Este problema afecta a JetElements para Elementor: desde n/a hasta 2.6.13." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-491xx/CVE-2023-49110.json b/CVE-2023/CVE-2023-491xx/CVE-2023-49110.json new file mode 100644 index 00000000000..e0385343934 --- /dev/null +++ b/CVE-2023/CVE-2023-491xx/CVE-2023-49110.json @@ -0,0 +1,36 @@ +{ + "id": "CVE-2023-49110", + "sourceIdentifier": "551230f0-3615-47bd-b7cc-93e92e730bbf", + "published": "2024-06-20T13:15:49.250", + "lastModified": "2024-06-20T13:15:49.250", + "vulnStatus": "Received", + "descriptions": [ + { + "lang": "en", + "value": "When the Kiuwan Local Analyzer uploads the scan results to the Kiuwan SAST web \napplication (either on-premises or cloud/SaaS solution), the transmitted data \nconsists of a ZIP archive containing several files, some of them in the \nXML file format. During Kiuwan's server-side processing of these XML \nfiles, it resolves external XML entities, resulting in a XML external \nentity injection attack.\u00a0An attacker with privileges to scan \nsource code within the \"Code Security\" module is able to extract any \nfiles of the operating system with the rights of the application server \nuser and is potentially able to gain sensitive files, such as \nconfiguration and passwords. Furthermore, this vulnerability also allows\n an attacker to initiate connections to internal systems, e.g. for port \nscans or accessing other internal functions / applications such as the \nWildfly admin console of Kiuwan.\n\nThis issue affects Kiuwan SAST: tbo.resource may be NULL in amdgpu_vm_bo_update." + } + ], + "metrics": {}, + "references": [ + { + "url": "https://git.kernel.org/stable/c/51b79f33817544e3b4df838d86e8e8e4388ff684", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + }, + { + "url": "https://git.kernel.org/stable/c/fefac8c4686fd81fde6830c6dae32f9001d2ac28", + "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67" + } + ] +} \ No newline at end of file diff --git a/CVE-2023/CVE-2023-55xx/CVE-2023-5527.json b/CVE-2023/CVE-2023-55xx/CVE-2023-5527.json index ea66e618d69..85e1cad636e 100644 --- a/CVE-2023/CVE-2023-55xx/CVE-2023-5527.json +++ b/CVE-2023/CVE-2023-55xx/CVE-2023-5527.json @@ -2,12 +2,16 @@ "id": "CVE-2023-5527", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-18T06:15:10.243", - "lastModified": "2024-06-18T06:15:10.243", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "The Business Directory Plugin plugin for WordPress is vulnerable to CSV Injection in versions up to, and including, 6.4.3 via the class-csv-exporter.php file. This allows authenticated attackers, with author-level permissions and above, to embed untrusted input into CSV files exported by administrators, which can result in code execution when these files are downloaded and opened on a local system with a vulnerable configuration." + }, + { + "lang": "es", + "value": "El complemento Business Directory Plugin para WordPress es vulnerable a la inyecci\u00f3n CSV en versiones hasta la 6.4.3 incluida a trav\u00e9s del archivo class-csv-exporter.php. Esto permite a atacantes autenticados, con permisos de nivel de autor y superiores, incrustar entradas no confiables en archivos CSV exportados por administradores, lo que puede resultar en la ejecuci\u00f3n de c\u00f3digo cuando estos archivos se descargan y abren en un sistema local con una configuraci\u00f3n vulnerable." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-64xx/CVE-2023-6495.json b/CVE-2023/CVE-2023-64xx/CVE-2023-6495.json index ff3ae23c9e1..f4dd2fb626a 100644 --- a/CVE-2023/CVE-2023-64xx/CVE-2023-6495.json +++ b/CVE-2023/CVE-2023-64xx/CVE-2023-6495.json @@ -2,12 +2,16 @@ "id": "CVE-2023-6495", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-19T09:15:10.433", - "lastModified": "2024-06-19T09:15:10.433", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The YARPP \u2013 Yet Another Related Posts Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to and including 5.30.9 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled." + }, + { + "lang": "es", + "value": "El complemento YARPP \u2013 Yet Another Related Posts Plugin para WordPress, es vulnerable a cross-site scripting almacenado a trav\u00e9s de la configuraci\u00f3n de administrador en todas las versiones hasta la 5.30.9 incluida debido a una sanitizaci\u00f3n de entrada y un escape de salida insuficientes. Esto hace posible que atacantes autenticados, con permisos de nivel de administrador y superiores, inyecten scripts web arbitrarios en p\u00e1ginas que se ejecutar\u00e1n cada vez que un usuario acceda a una p\u00e1gina inyectada. Esto solo afecta a las instalaciones multisitio y a las instalaciones en las que se ha deshabilitado unfiltered_html." } ], "metrics": { diff --git a/CVE-2023/CVE-2023-66xx/CVE-2023-6692.json b/CVE-2023/CVE-2023-66xx/CVE-2023-6692.json index 2974f5f99d2..c9bff947d01 100644 --- a/CVE-2023/CVE-2023-66xx/CVE-2023-6692.json +++ b/CVE-2023/CVE-2023-66xx/CVE-2023-6692.json @@ -2,12 +2,16 @@ "id": "CVE-2023-6692", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-19T06:15:10.873", - "lastModified": "2024-06-19T06:15:10.873", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The Ultimate Blocks \u2013 WordPress Blocks Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's tab anchor metabox in all versions up to, and including, 3.0.8 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page." + }, + { + "lang": "es", + "value": "El complemento Ultimate Blocks \u2013 WordPress Blocks Plugin para WordPress es vulnerable a cross-site scripting almacenado a trav\u00e9s del metabox de anclaje de pesta\u00f1a del complemento en todas las versiones hasta la 3.0.8 incluida debido a una sanitizaci\u00f3n de entrada insuficiente y a un escape de salida en los atributos proporcionados por el usuario. Esto hace posible que atacantes autenticados con permisos de nivel de colaborador y superiores inyecten scripts web arbitrarios en p\u00e1ginas que se ejecutar\u00e1n cada vez que un usuario acceda a una p\u00e1gina inyectada." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-00xx/CVE-2024-0066.json b/CVE-2024/CVE-2024-00xx/CVE-2024-0066.json index 049b6c9efb2..4a2a04a2491 100644 --- a/CVE-2024/CVE-2024-00xx/CVE-2024-0066.json +++ b/CVE-2024/CVE-2024-00xx/CVE-2024-0066.json @@ -2,12 +2,16 @@ "id": "CVE-2024-0066", "sourceIdentifier": "product-security@axis.com", "published": "2024-06-18T06:15:10.723", - "lastModified": "2024-06-18T06:15:10.723", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Johan Fagerstr\u00f6m, member of the AXIS OS Bug Bounty Program, has found that a O3C feature may expose sensitive traffic between the client (Axis device) and (O3C) server. If O3C is not being used this flaw does not apply. \nAxis has released patched AXIS OS versions for the highlighted flaw. Please refer to the Axis security advisory for more information and solution." + }, + { + "lang": "es", + "value": "Johan Fagerstr\u00f6m, miembro del programa AXIS OS Bug Bounty, descubri\u00f3 que una caracter\u00edstica de O3C puede exponer el tr\u00e1fico confidencial entre el cliente (dispositivo Axis) y el servidor (O3C). Si no se utiliza O3C, este defecto no se aplica. Axis ha lanzado versiones parcheadas del sistema operativo AXIS para la falla resaltada. Consulte el aviso de seguridad de Axis para obtener m\u00e1s informaci\u00f3n y soluciones." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-03xx/CVE-2024-0383.json b/CVE-2024/CVE-2024-03xx/CVE-2024-0383.json index fb80f56b221..a7db5befb3d 100644 --- a/CVE-2024/CVE-2024-03xx/CVE-2024-0383.json +++ b/CVE-2024/CVE-2024-03xx/CVE-2024-0383.json @@ -2,12 +2,16 @@ "id": "CVE-2024-0383", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-19T09:15:10.807", - "lastModified": "2024-06-19T09:15:10.807", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The WP Recipe Maker plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's [wprm-recipe-instructions] and [wprm-recipe-ingredients] shortcodes in all versions up to, and including, 9.1.0 due to insufficient restrictions on the 'group_tag' attribute . This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page." + }, + { + "lang": "es", + "value": "El complemento WP Recipe Maker para WordPress es vulnerable a Cross-Site Scripting Almacenado a trav\u00e9s de los c\u00f3digos cortos [wprm-recipe-instructions] y [wprm-recipe-ingredients] del complemento en todas las versiones hasta la 9.1.0 incluida debido a restricciones insuficientes. en el atributo 'group_tag'. Esto hace posible que atacantes autenticados con permisos de nivel de colaborador y superiores inyecten scripts web arbitrarios en p\u00e1ginas que se ejecutar\u00e1n cada vez que un usuario acceda a una p\u00e1gina inyectada." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-03xx/CVE-2024-0397.json b/CVE-2024/CVE-2024-03xx/CVE-2024-0397.json index e2175b7b53d..5257f561923 100644 --- a/CVE-2024/CVE-2024-03xx/CVE-2024-0397.json +++ b/CVE-2024/CVE-2024-03xx/CVE-2024-0397.json @@ -2,12 +2,16 @@ "id": "CVE-2024-0397", "sourceIdentifier": "cna@python.org", "published": "2024-06-17T16:15:10.217", - "lastModified": "2024-06-17T18:15:14.767", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A defect was discovered in the Python \u201cssl\u201d module where there is a memory\nrace condition with the ssl.SSLContext methods \u201ccert_store_stats()\u201d and\n\u201cget_ca_certs()\u201d. The race condition can be triggered if the methods are\ncalled at the same time as certificates are loaded into the SSLContext,\nsuch as during the TLS handshake with a certificate directory configured.\nThis issue is fixed in CPython 3.10.14, 3.11.9, 3.12.3, and 3.13.0a5." + }, + { + "lang": "es", + "value": "Se descubri\u00f3 un defecto en el m\u00f3dulo \u201cssl\u201d de Python donde existe una condici\u00f3n de ejecuci\u00f3n de memoria con los m\u00e9todos ssl.SSLContext \u201ccert_store_stats()\u201d y \u201cget_ca_certs()\u201d. La condici\u00f3n de ejecuci\u00f3n se puede desencadenar si los m\u00e9todos se llaman al mismo tiempo que se cargan los certificados en SSLContext, como durante el protocolo de enlace TLS con un directorio de certificados configurado. Este problema se solucion\u00f3 en CPython 3.10.14, 3.11.9, 3.12.3 y 3.13.0a5." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-07xx/CVE-2024-0789.json b/CVE-2024/CVE-2024-07xx/CVE-2024-0789.json index f8bb150dcfa..fe9eb2c6d52 100644 --- a/CVE-2024/CVE-2024-07xx/CVE-2024-0789.json +++ b/CVE-2024/CVE-2024-07xx/CVE-2024-0789.json @@ -2,12 +2,16 @@ "id": "CVE-2024-0789", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-19T08:15:48.873", - "lastModified": "2024-06-19T08:15:48.873", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The WP Maintenance plugin for WordPress is vulnerable to IP Address Spoofing in all versions up to, and including, 6.1.9.2 due to insufficient IP address validation and use of user-supplied HTTP headers as a primary method for IP retrieval. This makes it possible for unauthenticated attackers to bypass maintenance mode." + }, + { + "lang": "es", + "value": "El complemento WP Maintenance para WordPress es vulnerable a la suplantaci\u00f3n de direcciones IP en todas las versiones hasta la 6.1.9.2 incluida debido a una validaci\u00f3n insuficiente de la direcci\u00f3n IP y al uso de encabezados HTTP proporcionados por el usuario como m\u00e9todo principal para la recuperaci\u00f3n de IP. Esto hace posible que atacantes no autenticados eviten el modo de mantenimiento." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-08xx/CVE-2024-0845.json b/CVE-2024/CVE-2024-08xx/CVE-2024-0845.json index 852dd801299..2e2dc0bebdc 100644 --- a/CVE-2024/CVE-2024-08xx/CVE-2024-0845.json +++ b/CVE-2024/CVE-2024-08xx/CVE-2024-0845.json @@ -2,12 +2,16 @@ "id": "CVE-2024-0845", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-18T03:15:09.330", - "lastModified": "2024-06-18T03:15:09.330", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "The PDF Viewer for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the render function in all versions up to, and including, 2.9.3 due to insufficient input sanitization and output escaping. 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." + }, + { + "lang": "es", + "value": "El complemento PDF Viewer para Elementor para WordPress es vulnerable a Cross-Site Scripting Almacenado a trav\u00e9s de la funci\u00f3n de renderizado en todas las versiones hasta la 2.9.3 incluida debido a una sanitizaci\u00f3n de entrada y un escape de salida insuficientes. Esto hace posible que atacantes autenticados, con acceso de nivel de colaborador y superior, inyecten scripts web arbitrarios en p\u00e1ginas que se ejecutar\u00e1n cada vez que un usuario acceda a una p\u00e1gina inyectada." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-11xx/CVE-2024-1168.json b/CVE-2024/CVE-2024-11xx/CVE-2024-1168.json index 238f98d0141..0f99364efed 100644 --- a/CVE-2024/CVE-2024-11xx/CVE-2024-1168.json +++ b/CVE-2024/CVE-2024-11xx/CVE-2024-1168.json @@ -2,12 +2,16 @@ "id": "CVE-2024-1168", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-20T02:15:09.420", - "lastModified": "2024-06-20T02:15:09.420", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "The SEOPress \u2013 On-site SEO plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's social image URL in all versions up to, and including, 7.9 due to insufficient input sanitization and output escaping on user supplied image URLs. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page." + }, + { + "lang": "es", + "value": "El complemento SEOPress \u2013 On-site SEO para WordPress es vulnerable a Cross-Site Scripting Almacenado a trav\u00e9s de la URL de la imagen social del complemento en todas las versiones hasta la 7.9 incluida debido a una sanitizaci\u00f3n de entrada insuficiente y a un escape de salida en las URL de im\u00e1genes proporcionadas por el usuario. Esto hace posible que atacantes autenticados con permisos de nivel de colaborador y superiores inyecten scripts web arbitrarios en p\u00e1ginas que se ejecutar\u00e1n cada vez que un usuario acceda a una p\u00e1gina inyectada." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-14xx/CVE-2024-1407.json b/CVE-2024/CVE-2024-14xx/CVE-2024-1407.json index 1d68a2cfe4c..a32a2af55d4 100644 --- a/CVE-2024/CVE-2024-14xx/CVE-2024-1407.json +++ b/CVE-2024/CVE-2024-14xx/CVE-2024-1407.json @@ -2,12 +2,16 @@ "id": "CVE-2024-1407", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-19T07:15:45.730", - "lastModified": "2024-06-19T07:15:45.730", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The Paid Memberships Pro \u2013 Content Restriction, User Registration, & Paid Subscriptions plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.12.10. This is due to missing or incorrect nonce validation on multiple functions. This makes it possible for unauthenticated attackers to subscribe to, modify, or cancel membership for a user via a forged request granted they can trick a user into performing an action such as clicking on a link." + }, + { + "lang": "es", + "value": "El complemento Paid Memberships Pro \u2013 Content Restriction, User Registration, & Paid Subscriptions para WordPress es vulnerable a Cross-Site Request Forgery en todas las versiones hasta la 2.12.10 incluida. Esto se debe a una validaci\u00f3n nonce faltante o incorrecta en m\u00faltiples funciones. Esto hace posible que atacantes no autenticados se suscriban, modifiquen o cancelen la membres\u00eda de un usuario a trav\u00e9s de una solicitud falsificada, siempre que puedan enga\u00f1ar a un usuario para que realice una acci\u00f3n como hacer clic en un enlace." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-16xx/CVE-2024-1634.json b/CVE-2024/CVE-2024-16xx/CVE-2024-1634.json index 17de9fe534e..64d7fdfbfe8 100644 --- a/CVE-2024/CVE-2024-16xx/CVE-2024-1634.json +++ b/CVE-2024/CVE-2024-16xx/CVE-2024-1634.json @@ -2,12 +2,16 @@ "id": "CVE-2024-1634", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-18T03:15:09.580", - "lastModified": "2024-06-18T03:15:09.580", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "The Scheduling Plugin \u2013 Online Booking for WordPress plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the 'cbsb_disconnect_settings' function in all versions up to, and including, 3.5.10. This makes it possible for unauthenticated attackers to disconnect the plugin from the startbooking service and remove connection data." + }, + { + "lang": "es", + "value": "El complemento Scheduling Plugin \u2013 Online Booking for WordPress para WordPress es vulnerable a la p\u00e9rdida no autorizada de datos debido a una falta de verificaci\u00f3n de capacidad en la funci\u00f3n 'cbsb_disconnect_settings' en todas las versiones hasta la 3.5.10 incluida. Esto hace posible que atacantes no autenticados desconecten el complemento del servicio de inicio de reservas y eliminen los datos de conexi\u00f3n." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-216xx/CVE-2024-21685.json b/CVE-2024/CVE-2024-216xx/CVE-2024-21685.json index 84f02a5097a..8a51d3a2666 100644 --- a/CVE-2024/CVE-2024-216xx/CVE-2024-21685.json +++ b/CVE-2024/CVE-2024-216xx/CVE-2024-21685.json @@ -2,12 +2,16 @@ "id": "CVE-2024-21685", "sourceIdentifier": "security@atlassian.com", "published": "2024-06-18T17:15:51.243", - "lastModified": "2024-06-18T17:15:51.243", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "This High severity Information Disclosure vulnerability was introduced in versions 9.4.0, 9.12.0, and 9.15.0 of Jira Core Data Center. \r\n\t\r\n\tThis Information Disclosure vulnerability, with a CVSS Score of 7.4, allows an unauthenticated attacker to view sensitive information via an Information Disclosure vulnerability which has high impact to confidentiality, no impact to integrity, no impact to availability, and requires user interaction. \r\n\t\r\n\tAtlassian recommends that Jira Core Data Center customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions:\r\n\t\t\r\n\t\tJira Core Data Center 9.4: Upgrade to a release greater than or equal to 9.4.21\r\n\t\t\r\n\t\tJira Core Data Center 9.12: Upgrade to a release greater than or equal to 9.12.8\r\n\t\t\r\n\t\tJira Core Data Center 9.16: Upgrade to a release greater than or equal to 9.16.0\r\n\t\t\r\n\t\t\r\n\t\r\n\tSee the release notes. You can download the latest version of Jira Core Data Center from the download center. \r\n\t\r\n\tThis vulnerability was found internally." + }, + { + "lang": "es", + "value": "Esta vulnerabilidad de divulgaci\u00f3n de informaci\u00f3n de alta gravedad se introdujo en las versiones 9.4.0, 9.12.0 y 9.15.0 de Jira Core Data Center. Esta vulnerabilidad de divulgaci\u00f3n de informaci\u00f3n, con una puntuaci\u00f3n CVSS de 7,4, permite a un atacante no autenticado ver informaci\u00f3n confidencial a trav\u00e9s de una vulnerabilidad de divulgaci\u00f3n de informaci\u00f3n que tiene un alto impacto en la confidencialidad, ning\u00fan impacto en la integridad, ning\u00fan impacto en la disponibilidad y requiere la interacci\u00f3n del usuario. Atlassian recomienda que los clientes de Jira Core Data Center actualicen a la \u00faltima versi\u00f3n; si no pueden hacerlo, actualicen su instancia a una de las versiones fijas admitidas especificadas: Jira Core Data Center 9.4: actualice a una versi\u00f3n superior o igual a 9.4. 21 Jira Core Data Center 9.12: actualice a una versi\u00f3n superior o igual a 9.12.8 Jira Core Data Center 9.16: actualice a una versi\u00f3n superior o igual a 9.16.0 Consulte las notas de la versi\u00f3n. Puede descargar la \u00faltima versi\u00f3n de Jira Core Data Center desde el centro de descargas. Esta vulnerabilidad se encontr\u00f3 internamente." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-220xx/CVE-2024-22002.json b/CVE-2024/CVE-2024-220xx/CVE-2024-22002.json index 7b6f457e4ac..29ea6574198 100644 --- a/CVE-2024/CVE-2024-220xx/CVE-2024-22002.json +++ b/CVE-2024/CVE-2024-220xx/CVE-2024-22002.json @@ -2,12 +2,16 @@ "id": "CVE-2024-22002", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-18T19:15:59.397", - "lastModified": "2024-06-18T19:15:59.397", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "CORSAIR iCUE 5.9.105 with iCUE Murals on Windows allows unprivileged users to insert DLL files in the cuepkg-1.2.6 subdirectory of the installation directory." + }, + { + "lang": "es", + "value": "CORSAIR iCUE 5.9.105 con iCUE Murals en Windows permite a usuarios sin privilegios insertar archivos DLL en el subdirectorio cuepkg-1.2.6 del directorio de instalaci\u00f3n." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-222xx/CVE-2024-22263.json b/CVE-2024/CVE-2024-222xx/CVE-2024-22263.json index 02ceac0fe49..2fde484d11f 100644 --- a/CVE-2024/CVE-2024-222xx/CVE-2024-22263.json +++ b/CVE-2024/CVE-2024-222xx/CVE-2024-22263.json @@ -2,12 +2,16 @@ "id": "CVE-2024-22263", "sourceIdentifier": "security@vmware.com", "published": "2024-06-19T15:15:58.327", - "lastModified": "2024-06-19T15:15:58.327", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Spring Cloud Data Flow is a microservices-based Streaming and Batch data processing in Cloud Foundry and Kubernetes. The Skipper server has the ability to receive upload package requests. However, due to improper sanitization for upload path, a malicious user who has access to skipper server api can use a crafted upload request to write arbitrary file to any location on file system, may even compromises the server." + }, + { + "lang": "es", + "value": "Spring Cloud Data Flow es un procesamiento de datos por lotes y streaming basado en microservicios en Cloud Foundry y Kubernetes. El servidor Skipper tiene la capacidad de recibir solicitudes de carga de paquetes. Sin embargo, debido a una sanitizaci\u00f3n inadecuada de la ruta de carga, un usuario malintencionado que tenga acceso a la API del servidor skipper puede utilizar una solicitud de carga manipulada para escribir un archivo arbitrario en cualquier ubicaci\u00f3n del sistema de archivos e incluso puede comprometer el servidor." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-234xx/CVE-2024-23443.json b/CVE-2024/CVE-2024-234xx/CVE-2024-23443.json index f7afc1ae255..751ca6d5c7e 100644 --- a/CVE-2024/CVE-2024-234xx/CVE-2024-23443.json +++ b/CVE-2024/CVE-2024-234xx/CVE-2024-23443.json @@ -2,12 +2,16 @@ "id": "CVE-2024-23443", "sourceIdentifier": "bressers@elastic.co", "published": "2024-06-19T14:15:13.360", - "lastModified": "2024-06-19T14:15:13.360", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A high-privileged user, allowed to create custom osquery packs 17 could affect the availability of Kibana by uploading a maliciously crafted osquery pack." + }, + { + "lang": "es", + "value": "Un usuario con altos privilegios, al que se le permite crear paquetes de osquery personalizados 17, podr\u00eda afectar la disponibilidad de Kibana al cargar un paquete de osquery creado con fines malintencionados." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-23xx/CVE-2024-2381.json b/CVE-2024/CVE-2024-23xx/CVE-2024-2381.json index b2dffac1c84..741a3b0cdbe 100644 --- a/CVE-2024/CVE-2024-23xx/CVE-2024-2381.json +++ b/CVE-2024/CVE-2024-23xx/CVE-2024-2381.json @@ -2,12 +2,16 @@ "id": "CVE-2024-2381", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-19T04:15:10.753", - "lastModified": "2024-06-19T04:15:10.753", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The AliExpress Dropshipping with AliNext Lite plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the ajax_save_image function in all versions up to, and including, 3.3.5. This makes it possible for authenticated attackers, with subscriber-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible." + }, + { + "lang": "es", + "value": "El complemento AliExpress Dropshipping con AliNext Lite para WordPress es vulnerable a la carga de archivos arbitrarios debido a la falta de validaci\u00f3n del tipo de archivo en la funci\u00f3n ajax_save_image en todas las versiones hasta la 3.3.5 incluida. Esto hace posible que atacantes autenticados, con acceso de nivel de suscriptor y superior, carguen archivos arbitrarios en el servidor del sitio afectado, lo que puede hacer posible la ejecuci\u00f3n remota de c\u00f3digo." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-281xx/CVE-2024-28147.json b/CVE-2024/CVE-2024-281xx/CVE-2024-28147.json index d6417992137..54f96bb02ed 100644 --- a/CVE-2024/CVE-2024-281xx/CVE-2024-28147.json +++ b/CVE-2024/CVE-2024-281xx/CVE-2024-28147.json @@ -2,12 +2,16 @@ "id": "CVE-2024-28147", "sourceIdentifier": "551230f0-3615-47bd-b7cc-93e92e730bbf", "published": "2024-06-20T11:15:55.913", - "lastModified": "2024-06-20T11:15:55.913", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "An authenticated user can upload arbitrary files in the upload \nfunction for collection preview images. An attacker may upload an HTML \nfile that includes malicious JavaScript code which will be executed if a\n user visits the direct URL of the collection preview image (Stored \nCross Site Scripting). It is also possible to upload SVG files that \ninclude nested XML entities. Those are parsed when a user visits the \ndirect URL of the collection preview image, which may be utilized for a \nDenial of Service attack.\n\nThis issue affects edu-sharing: <8.0.8-RC2, <8.1.4-RC0, <9.0.0-RC19." + }, + { + "lang": "es", + "value": "Un usuario autenticado puede cargar archivos arbitrarios en la funci\u00f3n de carga para im\u00e1genes de vista previa de la colecci\u00f3n. Un atacante puede cargar un archivo HTML que incluya c\u00f3digo JavaScript malicioso que se ejecutar\u00e1 si un usuario visita la URL directa de la imagen de vista previa de la colecci\u00f3n (Stored Cross Site Scripting). Tambi\u00e9n es posible cargar archivos SVG que incluyan entidades XML anidadas. Estos se analizan cuando un usuario visita la URL directa de la imagen de vista previa de la colecci\u00f3n, que puede utilizarse para un ataque de denegaci\u00f3n de servicio. Este problema afecta a edu-sharing: <8.0.8-RC2, <8.1.4-RC0, <9.0.0-RC19." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-290xx/CVE-2024-29012.json b/CVE-2024/CVE-2024-290xx/CVE-2024-29012.json index e0c0479b0a2..333780c88d3 100644 --- a/CVE-2024/CVE-2024-290xx/CVE-2024-29012.json +++ b/CVE-2024/CVE-2024-290xx/CVE-2024-29012.json @@ -2,12 +2,16 @@ "id": "CVE-2024-29012", "sourceIdentifier": "PSIRT@sonicwall.com", "published": "2024-06-20T09:15:11.347", - "lastModified": "2024-06-20T09:15:11.347", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Stack-based buffer overflow vulnerability in the SonicOS HTTP server allows an authenticated remote attacker to cause Denial of Service (DoS) via sscanf function." + }, + { + "lang": "es", + "value": "Una vulnerabilidad de desbordamiento de b\u00fafer basada en pila en el servidor HTTP de SonicOS permite que un atacante remoto autenticado provoque una denegaci\u00f3n de servicio (DoS) a trav\u00e9s de la funci\u00f3n sscanf." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-290xx/CVE-2024-29013.json b/CVE-2024/CVE-2024-290xx/CVE-2024-29013.json index eff485bb37a..1f42b3ed1b0 100644 --- a/CVE-2024/CVE-2024-290xx/CVE-2024-29013.json +++ b/CVE-2024/CVE-2024-290xx/CVE-2024-29013.json @@ -2,12 +2,16 @@ "id": "CVE-2024-29013", "sourceIdentifier": "PSIRT@sonicwall.com", "published": "2024-06-20T09:15:11.543", - "lastModified": "2024-06-20T09:15:11.543", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Heap-based buffer overflow vulnerability in the SonicOS SSL-VPN allows an authenticated remote attacker to cause Denial of Service (DoS) via memcpy function." + }, + { + "lang": "es", + "value": "Una vulnerabilidad de desbordamiento de b\u00fafer basada en mont\u00f3n en SonicOS SSL-VPN permite que un atacante remoto autenticado provoque una denegaci\u00f3n de servicio (DoS) a trav\u00e9s de la funci\u00f3n memcpy." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-320xx/CVE-2024-32030.json b/CVE-2024/CVE-2024-320xx/CVE-2024-32030.json index 1eca4d64110..a405cdcb6af 100644 --- a/CVE-2024/CVE-2024-320xx/CVE-2024-32030.json +++ b/CVE-2024/CVE-2024-320xx/CVE-2024-32030.json @@ -2,12 +2,16 @@ "id": "CVE-2024-32030", "sourceIdentifier": "security-advisories@github.com", "published": "2024-06-19T17:15:57.863", - "lastModified": "2024-06-19T17:15:57.863", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Kafka UI is an Open-Source Web UI for Apache Kafka Management. Kafka UI API allows users to connect to different Kafka brokers by specifying their network address and port. As a separate feature, it also provides the ability to monitor the performance of Kafka brokers by connecting to their JMX ports. JMX is based on the RMI protocol, so it is inherently susceptible to deserialization attacks. A potential attacker can exploit this feature by connecting Kafka UI backend to its own malicious broker. This vulnerability affects the deployments where one of the following occurs: 1. dynamic.config.enabled property is set in settings. It's not enabled by default, but it's suggested to be enabled in many tutorials for Kafka UI, including its own README.md. OR 2. an attacker has access to the Kafka cluster that is being connected to Kafka UI. In this scenario the attacker can exploit this vulnerability to expand their access and execute code on Kafka UI as well. Instead of setting up a legitimate JMX port, an attacker can create an RMI listener that returns a malicious serialized object for any RMI call. In the worst case it could lead to remote code execution as Kafka UI has the required gadget chains in its classpath. This issue may lead to post-auth remote code execution. This is particularly dangerous as Kafka-UI does not have authentication enabled by default. This issue has been addressed in version 0.7.2. All users are advised to upgrade. There are no known workarounds for this vulnerability. These issues were discovered and reported by the GitHub Security lab and is also tracked as GHSL-2023-230." + }, + { + "lang": "es", + "value": "Kafka UI es una interfaz de usuario web de c\u00f3digo abierto para la administraci\u00f3n de Apache Kafka. La API de Kafka UI permite a los usuarios conectarse a diferentes corredores de Kafka especificando su direcci\u00f3n de red y puerto. Como caracter\u00edstica independiente, tambi\u00e9n brinda la capacidad de monitorear el desempe\u00f1o de los corredores de Kafka conect\u00e1ndose a sus puertos JMX. JMX se basa en el protocolo RMI, por lo que es inherentemente susceptible a ataques de deserializaci\u00f3n. Un atacante potencial puede aprovechar esta caracter\u00edstica conectando el backend de la interfaz de usuario de Kafka a su propio agente malicioso. Esta vulnerabilidad afecta las implementaciones donde ocurre una de las siguientes situaciones: 1. La propiedad dynamic.config.enabled est\u00e1 configurada en la configuraci\u00f3n. No est\u00e1 habilitado de forma predeterminada, pero se sugiere habilitarlo en muchos tutoriales para Kafka UI, incluido su propio README.md. O 2. un atacante tiene acceso al cl\u00faster de Kafka que se est\u00e1 conectando a la interfaz de usuario de Kafka. En este escenario, el atacante puede aprovechar esta vulnerabilidad para ampliar su acceso y ejecutar c\u00f3digo tambi\u00e9n en la interfaz de usuario de Kafka. En lugar de configurar un puerto JMX leg\u00edtimo, un atacante puede crear un detector RMI que devuelva un objeto serializado malicioso para cualquier llamada RMI. En el peor de los casos, podr\u00eda conducir a la ejecuci\u00f3n remota de c\u00f3digo, ya que Kafka UI tiene las cadenas de dispositivos necesarias en su classpath. Este problema puede provocar la ejecuci\u00f3n remota de c\u00f3digo posterior a la autenticaci\u00f3n. Esto es particularmente peligroso ya que Kafka-UI no tiene la autenticaci\u00f3n habilitada de forma predeterminada. Este problema se solucion\u00f3 en la versi\u00f3n 0.7.2. Se recomienda a todos los usuarios que actualicen. No se conocen workarounds para esta vulnerabilidad. Estos problemas fueron descubiertos e informados por el laboratorio de seguridad de GitHub y tambi\u00e9n se rastrean como GHSL-2023-230." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-32xx/CVE-2024-3229.json b/CVE-2024/CVE-2024-32xx/CVE-2024-3229.json index 6cd14825c65..e96f3e11961 100644 --- a/CVE-2024/CVE-2024-32xx/CVE-2024-3229.json +++ b/CVE-2024/CVE-2024-32xx/CVE-2024-3229.json @@ -2,12 +2,16 @@ "id": "CVE-2024-3229", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-19T05:15:52.067", - "lastModified": "2024-06-19T05:15:52.067", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The Salon booking system plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the SLN_Action_Ajax_ImportAssistants function along with missing authorization checks in all versions up to, and including, 10.2. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible." + }, + { + "lang": "es", + "value": "El complemento Salon booking system para WordPress es vulnerable a cargas arbitrarias de archivos debido a la falta de validaci\u00f3n del tipo de archivo en la funci\u00f3n SLN_Action_Ajax_ImportAssistants junto con la falta de comprobaciones de autorizaci\u00f3n en todas las versiones hasta la 10.2 incluida. Esto hace posible que atacantes no autenticados carguen archivos arbitrarios en el servidor del sitio afectado, lo que puede hacer posible la ejecuci\u00f3n remota de c\u00f3digo." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-32xx/CVE-2024-3276.json b/CVE-2024/CVE-2024-32xx/CVE-2024-3276.json index 93c40279fc8..d0b6b09bc0e 100644 --- a/CVE-2024/CVE-2024-32xx/CVE-2024-3276.json +++ b/CVE-2024/CVE-2024-32xx/CVE-2024-3276.json @@ -2,12 +2,16 @@ "id": "CVE-2024-3276", "sourceIdentifier": "contact@wpscan.com", "published": "2024-06-18T06:15:12.270", - "lastModified": "2024-06-18T06:15:12.270", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "The Lightbox & Modal Popup WordPress Plugin WordPress plugin before 2.7.28, foobox-image-lightbox-premium WordPress plugin before 2.7.28 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup)." + }, + { + "lang": "es", + "value": "El complemento Lightbox & Modal Popup WordPress Plugin de WordPress anterior a 2.7.28, el complemento foobox-image-lightbox-premium de WordPress anterior a 2.7.28 no sanitiza ni escapa a algunas de sus configuraciones, lo que podr\u00eda permitir a usuarios con privilegios elevados, como el administrador, realizar ataques de Cross-Site Scripting Almacenado incluso cuando la capacidad unfiltered_html no est\u00e1 permitida (por ejemplo, en configuraci\u00f3n multisitio)." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-336xx/CVE-2024-33620.json b/CVE-2024/CVE-2024-336xx/CVE-2024-33620.json index 415caf5d100..9749c82a1ab 100644 --- a/CVE-2024/CVE-2024-336xx/CVE-2024-33620.json +++ b/CVE-2024/CVE-2024-336xx/CVE-2024-33620.json @@ -2,12 +2,16 @@ "id": "CVE-2024-33620", "sourceIdentifier": "vultures@jpcert.or.jp", "published": "2024-06-18T06:15:11.053", - "lastModified": "2024-06-18T06:15:11.053", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Absolute path traversal vulnerability exists in ID Link Manager and FUJITSU Software TIME CREATOR. If this vulnerability is exploited, the file contents including sensitive information on the server may be retrieved by an unauthenticated remote attacker." + }, + { + "lang": "es", + "value": "Existe una vulnerabilidad de path traversal absoluta en ID Link Manager y FUJITSU Software TIME CREATOR. Si se explota esta vulnerabilidad, un atacante remoto no autenticado puede recuperar el contenido del archivo, incluida la informaci\u00f3n confidencial del servidor." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-336xx/CVE-2024-33622.json b/CVE-2024/CVE-2024-336xx/CVE-2024-33622.json index 4d2cc1b9ba6..a8aae3404b4 100644 --- a/CVE-2024/CVE-2024-336xx/CVE-2024-33622.json +++ b/CVE-2024/CVE-2024-336xx/CVE-2024-33622.json @@ -2,12 +2,16 @@ "id": "CVE-2024-33622", "sourceIdentifier": "vultures@jpcert.or.jp", "published": "2024-06-18T06:15:11.163", - "lastModified": "2024-06-18T06:15:11.163", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing authentication for critical function vulnerability exists in ID Link Manager and FUJITSU Software TIME CREATOR. If this vulnerability is exploited, sensitive information may be obtained and/or the information stored in the database may be altered by a remote authenticated attacker." + }, + { + "lang": "es", + "value": "Falta autenticaci\u00f3n para una vulnerabilidad de funci\u00f3n cr\u00edtica en ID Link Manager y FUJITSU Software TIME CREATOR. Si se explota esta vulnerabilidad, un atacante remoto autenticado puede obtener informaci\u00f3n confidencial y/o la informaci\u00f3n almacenada en la base de datos puede ser alterada." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-338xx/CVE-2024-33836.json b/CVE-2024/CVE-2024-338xx/CVE-2024-33836.json index 0b733c63f73..5094bac3cae 100644 --- a/CVE-2024/CVE-2024-338xx/CVE-2024-33836.json +++ b/CVE-2024/CVE-2024-338xx/CVE-2024-33836.json @@ -2,12 +2,16 @@ "id": "CVE-2024-33836", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-19T21:15:56.920", - "lastModified": "2024-06-19T21:15:56.920", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the module \"JA Marketplace\" (jamarketplace) up to version 9.0.1 from JA Module for PrestaShop, a guest can upload files with extensions .php. In version 6.X, the method `JmarketplaceproductModuleFrontController::init()` and in version 8.X, the method `JmarketplaceSellerproductModuleFrontController::init()` allow upload of .php files, which will lead to a critical vulnerability." + }, + { + "lang": "es", + "value": "En el m\u00f3dulo \"JA Marketplace\" (jamarketplace) hasta la versi\u00f3n 9.0.1 del M\u00f3dulo JA para PrestaShop, un invitado puede cargar archivos con extensiones .php. En la versi\u00f3n 6.X, el m\u00e9todo `JmarketplaceproductModuleFrontController::init()` y en la versi\u00f3n 8.X, el m\u00e9todo `JmarketplaceSellerproductModuleFrontController::init()` permiten cargar archivos .php, lo que conducir\u00e1 a una vulnerabilidad cr\u00edtica." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-340xx/CVE-2024-34024.json b/CVE-2024/CVE-2024-340xx/CVE-2024-34024.json index c6a73e495fa..7bf172d6bfe 100644 --- a/CVE-2024/CVE-2024-340xx/CVE-2024-34024.json +++ b/CVE-2024/CVE-2024-340xx/CVE-2024-34024.json @@ -2,12 +2,16 @@ "id": "CVE-2024-34024", "sourceIdentifier": "vultures@jpcert.or.jp", "published": "2024-06-18T06:15:11.257", - "lastModified": "2024-06-18T06:15:11.257", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Observable response discrepancy issue exists in ID Link Manager and FUJITSU Software TIME CREATOR. If this vulnerability is exploited, an unauthenticated remote attacker may determine if a username is valid or not." + }, + { + "lang": "es", + "value": "Existe un problema de discrepancia de respuesta observable en ID Link Manager y FUJITSU Software TIME CREATOR. Si se explota esta vulnerabilidad, un atacante remoto no autenticado puede determinar si un nombre de usuario es v\u00e1lido o no." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-344xx/CVE-2024-34443.json b/CVE-2024/CVE-2024-344xx/CVE-2024-34443.json index 066ab521933..491e8438571 100644 --- a/CVE-2024/CVE-2024-344xx/CVE-2024-34443.json +++ b/CVE-2024/CVE-2024-344xx/CVE-2024-34443.json @@ -2,12 +2,16 @@ "id": "CVE-2024-34443", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T15:15:59.230", - "lastModified": "2024-06-19T15:15:59.230", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in ThemePunch OHG Slider Revolution allows Stored XSS.This issue affects Slider Revolution: from n/a before 6.7.11." + }, + { + "lang": "es", + "value": "La vulnerabilidad de neutralizaci\u00f3n inadecuada de la entrada durante la generaci\u00f3n de p\u00e1ginas web (XSS o 'Cross-site Scripting') en ThemePunch OHG Slider Revolution permite XSS Almacenado. Este problema afecta a Slider Revolution: desde n/a antes de 6.7.11." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-344xx/CVE-2024-34444.json b/CVE-2024/CVE-2024-344xx/CVE-2024-34444.json index b76b51684a2..d8f65298166 100644 --- a/CVE-2024/CVE-2024-344xx/CVE-2024-34444.json +++ b/CVE-2024/CVE-2024-344xx/CVE-2024-34444.json @@ -2,12 +2,16 @@ "id": "CVE-2024-34444", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T15:15:59.530", - "lastModified": "2024-06-19T15:15:59.530", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Missing Authorization vulnerability in ThemePunch OHG Slider Revolution.This issue affects Slider Revolution: from n/a before 6.7.0." + }, + { + "lang": "es", + "value": "Vulnerabilidad de autorizaci\u00f3n faltante en ThemePunch OHG Slider Revolution. Este problema afecta a Slider Revolution: desde n/a antes de 6.7.0." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-346xx/CVE-2024-34693.json b/CVE-2024/CVE-2024-346xx/CVE-2024-34693.json index 9013eac72b9..f3a0ca28fe9 100644 --- a/CVE-2024/CVE-2024-346xx/CVE-2024-34693.json +++ b/CVE-2024/CVE-2024-346xx/CVE-2024-34693.json @@ -2,12 +2,16 @@ "id": "CVE-2024-34693", "sourceIdentifier": "security@apache.org", "published": "2024-06-20T09:15:11.683", - "lastModified": "2024-06-20T11:15:56.090", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Improper Input Validation vulnerability in Apache Superset, allows for an authenticated attacker to create a MariaDB connection with local_infile enabled. If both the MariaDB server (off by default) and the local mysql client on the web server are set to allow for local infile, it's possible for the attacker to execute a specific MySQL/MariaDB SQL command that is able to read files from the server and insert their content on a MariaDB database table.This issue affects Apache Superset: before 3.1.3 and version 4.0.0\n\nUsers are recommended to upgrade to version 4.0.1 or 3.1.3, which fixes the issue.\n\n" + }, + { + "lang": "es", + "value": "Vulnerabilidad de validaci\u00f3n de entrada incorrecta en Apache Superset, permite que un atacante autenticado cree una conexi\u00f3n MariaDB con local_infile habilitado. Si tanto el servidor MariaDB (desactivado de forma predeterminada) como el cliente MySQL local en el servidor web est\u00e1n configurados para permitir el archivo local, es posible que el atacante ejecute un comando SQL MySQL/MariaDB espec\u00edfico que pueda leer archivos del servidor e inserte su contenido en una tabla de base de datos MariaDB. Este problema afecta a Apache Superset: antes de 3.1.3 y versi\u00f3n 4.0.0. Se recomienda a los usuarios actualizar a la versi\u00f3n 4.0.1 o 3.1.3, que soluciona el problema." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-348xx/CVE-2024-34833.json b/CVE-2024/CVE-2024-348xx/CVE-2024-34833.json index 0d0bb984211..b01379105dc 100644 --- a/CVE-2024/CVE-2024-348xx/CVE-2024-34833.json +++ b/CVE-2024/CVE-2024-348xx/CVE-2024-34833.json @@ -2,12 +2,16 @@ "id": "CVE-2024-34833", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T21:15:50.783", - "lastModified": "2024-06-17T21:15:50.783", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Sourcecodester Payroll Management System v1.0 is vulnerable to File Upload. Users can upload images via the \"save_settings\" page. An unauthenticated attacker can leverage this functionality to upload a malicious PHP file instead. Successful exploitation of this vulnerability results in the ability to execute arbitrary code as the user running the web server." + }, + { + "lang": "es", + "value": "Sourcecodester Payroll Management System v1.0 es vulnerable a la carga de archivos. Los usuarios pueden cargar im\u00e1genes a trav\u00e9s de la p\u00e1gina \"save_settings\". Un atacante no autenticado puede aprovechar esta funcionalidad para cargar un archivo PHP malicioso. La explotaci\u00f3n exitosa de esta vulnerabilidad da como resultado la capacidad de ejecutar c\u00f3digo arbitrario como usuario que ejecuta el servidor web." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-349xx/CVE-2024-34990.json b/CVE-2024/CVE-2024-349xx/CVE-2024-34990.json index 65cf7db6e44..04908dbc88d 100644 --- a/CVE-2024/CVE-2024-349xx/CVE-2024-34990.json +++ b/CVE-2024/CVE-2024-349xx/CVE-2024-34990.json @@ -2,12 +2,16 @@ "id": "CVE-2024-34990", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-19T21:15:57.023", - "lastModified": "2024-06-19T21:15:57.023", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the module \"Help Desk - Customer Support Management System\" (helpdesk) up to version 2.4.0 from FME Modules for PrestaShop, a customer can upload .php files. Methods `HelpdeskHelpdeskModuleFrontController::submitTicket()` and `HelpdeskHelpdeskModuleFrontController::replyTicket()` allow upload of .php files on a predictable path for connected customers." + }, + { + "lang": "es", + "value": "En el m\u00f3dulo \"Help Desk - Sistema de gesti\u00f3n de atenci\u00f3n al cliente\" (helpdesk) hasta la versi\u00f3n 2.4.0 de los M\u00f3dulos FME para PrestaShop, un cliente puede cargar archivos .php. Los m\u00e9todos `HelpdeskHelpdeskModuleFrontController::submitTicket()` y `HelpdeskHelpdeskModuleFrontController::replyTicket()` permiten cargar archivos .php en una ruta predecible para los clientes conectados." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-349xx/CVE-2024-34993.json b/CVE-2024/CVE-2024-349xx/CVE-2024-34993.json index 402225e2b46..6bfaebb05f6 100644 --- a/CVE-2024/CVE-2024-349xx/CVE-2024-34993.json +++ b/CVE-2024/CVE-2024-349xx/CVE-2024-34993.json @@ -2,12 +2,16 @@ "id": "CVE-2024-34993", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-19T20:15:11.053", - "lastModified": "2024-06-19T20:15:11.053", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the module \"Bulk Export products to Google Merchant-Google Shopping\" (bagoogleshopping) up to version 1.0.26 from Buy Addons for PrestaShop, a guest can perform SQL injection via`GenerateCategories::renderCategories()." + }, + { + "lang": "es", + "value": "En el m\u00f3dulo \"Exportaci\u00f3n masiva de productos a Google Merchant-Google Shopping\" (bagoogleshopping) hasta la versi\u00f3n 1.0.26 de Buy Addons for PrestaShop, un invitado puede realizar una inyecci\u00f3n SQL a trav\u00e9s de `GenerateCategories::renderCategories()." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-349xx/CVE-2024-34994.json b/CVE-2024/CVE-2024-349xx/CVE-2024-34994.json index 97d8d13caa5..6711b80d0e4 100644 --- a/CVE-2024/CVE-2024-349xx/CVE-2024-34994.json +++ b/CVE-2024/CVE-2024-349xx/CVE-2024-34994.json @@ -2,12 +2,16 @@ "id": "CVE-2024-34994", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-19T21:15:57.130", - "lastModified": "2024-06-19T21:15:57.130", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the module \"Channable\" (channable) up to version 3.2.1 from Channable for PrestaShop, a guest can perform SQL injection via `ChannableFeedModuleFrontController::postProcess()`." + }, + { + "lang": "es", + "value": "En el m\u00f3dulo \"Channable\" (channable) hasta la versi\u00f3n 3.2.1 de Channable para PrestaShop, un invitado puede realizar una inyecci\u00f3n SQL a trav\u00e9s de `ChannableFeedModuleFrontController::postProcess()`." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-352xx/CVE-2024-35298.json b/CVE-2024/CVE-2024-352xx/CVE-2024-35298.json index 7d06063d316..dd8f636e8cd 100644 --- a/CVE-2024/CVE-2024-352xx/CVE-2024-35298.json +++ b/CVE-2024/CVE-2024-352xx/CVE-2024-35298.json @@ -2,12 +2,16 @@ "id": "CVE-2024-35298", "sourceIdentifier": "vultures@jpcert.or.jp", "published": "2024-06-19T05:15:51.907", - "lastModified": "2024-06-19T05:15:51.907", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Improper authorization in handler for custom URL scheme issue in 'ZOZOTOWN' App for Android versions prior to 7.39.6 allows an attacker to lead a user to access an arbitrary website via another application installed on the user's device. As a result, the user may become a victim of a phishing attack." + }, + { + "lang": "es", + "value": "La autorizaci\u00f3n inadecuada en el controlador para un problema de esquema de URL personalizado en la aplicaci\u00f3n 'ZOZOTOWN' para versiones de Android anteriores a 7.39.6 permite a un atacante llevar a un usuario a acceder a un sitio web arbitrario a trav\u00e9s de otra aplicaci\u00f3n instalada en el dispositivo del usuario. Como resultado, el usuario puede convertirse en v\u00edctima de un ataque de phishing." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-357xx/CVE-2024-35765.json b/CVE-2024/CVE-2024-357xx/CVE-2024-35765.json index a37d17d970c..66a03106978 100644 --- a/CVE-2024/CVE-2024-357xx/CVE-2024-35765.json +++ b/CVE-2024/CVE-2024-357xx/CVE-2024-35765.json @@ -2,12 +2,16 @@ "id": "CVE-2024-35765", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T11:15:51.117", - "lastModified": "2024-06-19T11:15:51.117", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Wpsoul Greenshift \u2013 animation and page builder blocks allows Stored XSS.This issue affects Greenshift \u2013 animation and page builder blocks: from n/a through 8.8.9.1." + }, + { + "lang": "es", + "value": "Vulnerabilidad de neutralizaci\u00f3n inadecuada de la entrada durante la generaci\u00f3n de p\u00e1ginas web (XSS o 'Cross-site Scripting') en Wpsoul Greenshift \u2013 animation and page builder blocks permiten XSS Almacenado. Este problema afecta a Greenshift \u2013 animation and page builder blocks: desde n/a hasta 8.8. 9.1." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-357xx/CVE-2024-35780.json b/CVE-2024/CVE-2024-357xx/CVE-2024-35780.json index 8697c06801e..d1ab345dee9 100644 --- a/CVE-2024/CVE-2024-357xx/CVE-2024-35780.json +++ b/CVE-2024/CVE-2024-357xx/CVE-2024-35780.json @@ -2,12 +2,16 @@ "id": "CVE-2024-35780", "sourceIdentifier": "audit@patchstack.com", "published": "2024-06-19T11:15:51.370", - "lastModified": "2024-06-19T11:15:51.370", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Deserialization of Untrusted Data vulnerability in Live Composer Team Page Builder: Live Composer.This issue affects Page Builder: Live Composer: from n/a through 1.5.42." + }, + { + "lang": "es", + "value": "Vulnerabilidad de deserializaci\u00f3n de datos no confiables en Live Composer Team Page Builder: Live Composer. Este problema afecta a Page Builder: Live Composer: desde n/a hasta 1.5.42." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-35xx/CVE-2024-3558.json b/CVE-2024/CVE-2024-35xx/CVE-2024-3558.json index 867f67951de..effc9c8d231 100644 --- a/CVE-2024/CVE-2024-35xx/CVE-2024-3558.json +++ b/CVE-2024/CVE-2024-35xx/CVE-2024-3558.json @@ -2,12 +2,16 @@ "id": "CVE-2024-3558", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-20T02:15:09.663", - "lastModified": "2024-06-20T02:15:09.663", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "The Custom Field Suite plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the the 'cfs[post_title]' parameter versions up to, and including, 2.6.7 due to insufficient input sanitization and output escaping. 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." + }, + { + "lang": "es", + "value": "El complemento Custom Field Suite para WordPress es vulnerable a Cross-Site Scripting Almacenado a trav\u00e9s de las versiones del par\u00e1metro 'cfs[post_title]' hasta la 2.6.7 incluida debido a una sanitizaci\u00f3n de entrada y un escape de salida insuficientes. Esto hace posible que atacantes autenticados, con acceso de nivel de colaborador y superior, inyecten scripts web arbitrarios en p\u00e1ginas que se ejecutar\u00e1n cada vez que un usuario acceda a una p\u00e1gina inyectada." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-35xx/CVE-2024-3561.json b/CVE-2024/CVE-2024-35xx/CVE-2024-3561.json index ccd1f3640dc..fe7422e1c55 100644 --- a/CVE-2024/CVE-2024-35xx/CVE-2024-3561.json +++ b/CVE-2024/CVE-2024-35xx/CVE-2024-3561.json @@ -2,12 +2,16 @@ "id": "CVE-2024-3561", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-20T02:15:09.920", - "lastModified": "2024-06-20T02:15:09.920", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "The Custom Field Suite plugin for WordPress is vulnerable to SQL Injection via the the 'Term' custom field in all versions up to, and including, 2.6.7 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database." + }, + { + "lang": "es", + "value": "El complemento Custom Field Suite para WordPress es vulnerable a la inyecci\u00f3n SQL a trav\u00e9s del campo personalizado 'T\u00e9rmino' en todas las versiones hasta la 2.6.7 incluida debido a un escape insuficiente en el par\u00e1metro proporcionado por el usuario y a la falta de preparaci\u00f3n suficiente en la consulta SQL existente. Esto hace posible que los atacantes autenticados, con acceso de nivel de colaborador y superior, agreguen consultas SQL adicionales a consultas ya existentes que pueden usarse para extraer informaci\u00f3n confidencial de la base de datos." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-35xx/CVE-2024-3562.json b/CVE-2024/CVE-2024-35xx/CVE-2024-3562.json index 0a585aa350d..937f16d67dd 100644 --- a/CVE-2024/CVE-2024-35xx/CVE-2024-3562.json +++ b/CVE-2024/CVE-2024-35xx/CVE-2024-3562.json @@ -2,12 +2,16 @@ "id": "CVE-2024-3562", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-20T02:15:10.140", - "lastModified": "2024-06-20T02:15:10.140", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "The Custom Field Suite plugin for WordPress is vulnerable to PHP Code Injection in all versions up to, and including, 2.6.7 via the Loop custom field. This is due to insufficient sanitization of input prior to being used in a call to the eval() function. This makes it possible for authenticated attackers, with contributor-level access and above, to execute arbitrary PHP code on the server." + }, + { + "lang": "es", + "value": "El complemento Custom Field Suite para WordPress es vulnerable a la inyecci\u00f3n de c\u00f3digo PHP en todas las versiones hasta la 2.6.7 incluida a trav\u00e9s del campo personalizado Loop. Esto se debe a una limpieza insuficiente de la entrada antes de usarla en una llamada a la funci\u00f3n eval(). Esto hace posible que atacantes autenticados, con acceso de nivel de colaborador y superior, ejecuten c\u00f3digo PHP arbitrario en el servidor." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-35xx/CVE-2024-3597.json b/CVE-2024/CVE-2024-35xx/CVE-2024-3597.json index e0cf09e1b64..e944e3915d1 100644 --- a/CVE-2024/CVE-2024-35xx/CVE-2024-3597.json +++ b/CVE-2024/CVE-2024-35xx/CVE-2024-3597.json @@ -2,12 +2,16 @@ "id": "CVE-2024-3597", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-20T02:15:10.363", - "lastModified": "2024-06-20T02:15:10.363", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "The Export WP Page to Static HTML/CSS plugin for WordPress is vulnerable to Open Redirect in all versions up to, and including, 2.2.2. This is due to insufficient validation on the redirect url supplied via the rc_exported_zip_file parameter. This makes it possible for unauthenticated attackers to redirect users to potentially malicious sites if they can successfully trick them into performing an action." + }, + { + "lang": "es", + "value": "El complemento Export WP Page to Static HTML/CSS para WordPress es vulnerable a Open Redirect en todas las versiones hasta la 2.2.2 incluida. Esto se debe a una validaci\u00f3n insuficiente de la URL de redireccionamiento proporcionada mediante el par\u00e1metro rc_exported_zip_file. Esto hace posible que atacantes no autenticados redirijan a los usuarios a sitios potencialmente maliciosos si logran enga\u00f1arlos para que realicen una acci\u00f3n." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-361xx/CVE-2024-36115.json b/CVE-2024/CVE-2024-361xx/CVE-2024-36115.json index ffb8fee48d4..41e38cb1a37 100644 --- a/CVE-2024/CVE-2024-361xx/CVE-2024-36115.json +++ b/CVE-2024/CVE-2024-361xx/CVE-2024-36115.json @@ -2,12 +2,16 @@ "id": "CVE-2024-36115", "sourceIdentifier": "security-advisories@github.com", "published": "2024-06-19T18:15:10.597", - "lastModified": "2024-06-19T18:15:10.597", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Reposilite is an open source, lightweight and easy-to-use repository manager for Maven based artifacts in JVM ecosystem. As a Maven repository manager, Reposilite provides the ability to view the artifacts content in the browser, as well as perform administrative tasks via API. The problem lies in the fact that the artifact's content is served via the same origin (protocol/host/port) as the Admin UI. If the artifact contains HTML content with javascript inside, the javascript is executed within the same origin. Therefore, if an authenticated user is viewing the artifacts content, the javascript inside can access the browser's local storage where the user's password (aka 'token-secret') is stored. It is especially dangerous in scenarios where Reposilite is configured to mirror third party repositories, like the Maven Central Repository. Since anyone can publish an artifact to Maven Central under its own name, such malicious packages can be used to attack the Reposilite instance. This issue may lead to the full Reposilite instance compromise. If this attack is performed against the admin user, it's possible to use the admin API to modify settings and artifacts on the instance. In the worst case scenario, an attacker would be able to obtain the Remote code execution on all systems that use artifacts from Reposilite. It's important to note that the attacker does not need to lure a victim user to use a malicious artifact, but just open a link in the browser. This link can be silently loaded among the other HTML content, making this attack unnoticeable. Even if the Reposilite instance is located in an isolated environment, such as behind a VPN or in the local network, this attack is still possible as it can be performed from the admin browser. Reposilite has addressed this issue in version 3.5.12. Users are advised to upgrade. There are no known workarounds for this vulnerability. This issue was discovered and reported by the GitHub Security lab and is also tracked as GHSL-2024-072." + }, + { + "lang": "es", + "value": "Reposilite es un administrador de repositorio de c\u00f3digo abierto, liviano y f\u00e1cil de usar para artefactos basados en Maven en el ecosistema JVM. Como administrador de repositorio de Maven, Reposilite brinda la capacidad de ver el contenido de los artefactos en el navegador, as\u00ed como realizar tareas administrativas a trav\u00e9s de API. El problema radica en el hecho de que el contenido del artefacto se entrega a trav\u00e9s del mismo origen (protocolo/host/puerto) que la interfaz de usuario del administrador. Si el artefacto contiene contenido HTML con javascript dentro, el javascript se ejecuta dentro del mismo origen. Por lo tanto, si un usuario autenticado est\u00e1 viendo el contenido de los artefactos, el javascript interno puede acceder al almacenamiento local del navegador donde se almacena la contrase\u00f1a del usuario (tambi\u00e9n conocida como 'token-secret'). Es especialmente peligroso en escenarios donde Reposilite est\u00e1 configurado para reflejar repositorios de terceros, como el Repositorio Central de Maven. Dado que cualquiera puede publicar un artefacto en Maven Central con su propio nombre, dichos paquetes maliciosos se pueden utilizar para atacar la instancia de Reposilite. Este problema puede provocar que la instancia de Reposilite se vea comprometida por completo. Si este ataque se realiza contra el usuario administrador, es posible utilizar la API de administrador para modificar la configuraci\u00f3n y los artefactos en la instancia. En el peor de los casos, un atacante podr\u00eda obtener la ejecuci\u00f3n remota de c\u00f3digo en todos los sistemas que utilicen artefactos de Reposilite. Es importante tener en cuenta que el atacante no necesita atraer al usuario v\u00edctima para que utilice un artefacto malicioso, sino simplemente abrir un enlace en el navegador. Este enlace se puede cargar silenciosamente entre el resto del contenido HTML, lo que hace que este ataque pase desapercibido. Incluso si la instancia de Reposilite est\u00e1 ubicada en un entorno aislado, como detr\u00e1s de una VPN o en la red local, este ataque a\u00fan es posible ya que se puede realizar desde el navegador de administraci\u00f3n. Reposilite ha solucionado este problema en la versi\u00f3n 3.5.12. Se recomienda a los usuarios que actualicen. No se conocen workarounds para esta vulnerabilidad. Este problema fue descubierto e informado por el laboratorio de seguridad de GitHub y tambi\u00e9n se rastrea como GHSL-2024-072." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-361xx/CVE-2024-36116.json b/CVE-2024/CVE-2024-361xx/CVE-2024-36116.json index 0d1f14e2f38..9c2866df54d 100644 --- a/CVE-2024/CVE-2024-361xx/CVE-2024-36116.json +++ b/CVE-2024/CVE-2024-361xx/CVE-2024-36116.json @@ -2,12 +2,16 @@ "id": "CVE-2024-36116", "sourceIdentifier": "security-advisories@github.com", "published": "2024-06-19T18:15:10.910", - "lastModified": "2024-06-19T18:15:10.910", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Reposilite is an open source, lightweight and easy-to-use repository manager for Maven based artifacts in JVM ecosystem. Reposilite provides support for JavaDocs files, which are archives that contain documentation for artifacts. Specifically, JavadocEndpoints.kt controller allows to expand the javadoc archive into the server's file system and return its content. The problem is in the way how the archives are expanded, specifically how the new filename is created. The `file.name` taken from the archive can contain path traversal characters, such as '/../../../anything.txt', so the resulting extraction path can be outside the target directory. If the archive is taken from an untrusted source, such as Maven Central or JitPack for example, an attacker can craft a special archive to overwrite any local file on Reposilite instance. This could lead to remote code execution, for example by placing a new plugin into the '$workspace$/plugins' directory. Alternatively, an attacker can overwrite the content of any other package. Note that the attacker can use its own malicious package from Maven Central to overwrite any other package on Reposilite. Reposilite has addressed this issue in version 3.5.12. Users are advised to upgrade. There are no known workarounds for this vulnerability. This issue was discovered and reported by the GitHub Security lab and is also tracked as GHSL-2024-073." + }, + { + "lang": "es", + "value": "Reposilite es un administrador de repositorio de c\u00f3digo abierto, liviano y f\u00e1cil de usar para artefactos basados en Maven en el ecosistema JVM. Reposilite brinda soporte para archivos JavaDocs, que son archivos que contienen documentaci\u00f3n para artefactos. Espec\u00edficamente, el controlador JavadocEndpoints.kt permite expandir el archivo javadoc al sistema de archivos del servidor y devolver su contenido. El problema est\u00e1 en la forma en que se expanden los archivos, espec\u00edficamente en c\u00f3mo se crea el nuevo nombre de archivo. El `file.name` tomado del archivo puede contener caracteres de path traversal, como '/../../../anything.txt', por lo que la ruta de extracci\u00f3n resultante puede estar fuera del directorio de destino. Si el archivo se toma de una fuente que no es de confianza, como Maven Central o JitPack, por ejemplo, un atacante puede crear un archivo especial para sobrescribir cualquier archivo local en la instancia de Reposilite. Esto podr\u00eda conducir a la ejecuci\u00f3n remota de c\u00f3digo, por ejemplo, colocando un nuevo complemento en el directorio '$workspace$/plugins'. Alternativamente, un atacante puede sobrescribir el contenido de cualquier otro paquete. Tenga en cuenta que el atacante puede utilizar su propio paquete malicioso de Maven Central para sobrescribir cualquier otro paquete en Reposilite. Reposilite ha solucionado este problema en la versi\u00f3n 3.5.12. Se recomienda a los usuarios que actualicen. No se conocen workarounds para esta vulnerabilidad. Este problema fue descubierto e informado por el laboratorio de seguridad de GitHub y tambi\u00e9n se rastrea como GHSL-2024-073." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-361xx/CVE-2024-36117.json b/CVE-2024/CVE-2024-361xx/CVE-2024-36117.json index 7cdcf67269e..17672a6b914 100644 --- a/CVE-2024/CVE-2024-361xx/CVE-2024-36117.json +++ b/CVE-2024/CVE-2024-361xx/CVE-2024-36117.json @@ -2,12 +2,16 @@ "id": "CVE-2024-36117", "sourceIdentifier": "security-advisories@github.com", "published": "2024-06-19T18:15:11.220", - "lastModified": "2024-06-19T18:15:11.220", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Reposilite is an open source, lightweight and easy-to-use repository manager for Maven based artifacts in JVM ecosystem. Reposilite v3.5.10 is affected by an Arbitrary File Read vulnerability via path traversal while serving expanded javadoc files. Reposilite has addressed this issue in version 3.5.12. There are no known workarounds for this vulnerability. This issue was discovered and reported by the GitHub Security lab and is also tracked as GHSL-2024-074." + }, + { + "lang": "es", + "value": "Reposilite es un administrador de repositorio de c\u00f3digo abierto, liviano y f\u00e1cil de usar para artefactos basados en Maven en el ecosistema JVM. Reposilite v3.5.10 se ve afectado por una vulnerabilidad de lectura arbitraria de archivos a trav\u00e9s del recorrido de ruta mientras sirve archivos javadoc expandidos. Reposilite ha solucionado este problema en la versi\u00f3n 3.5.12. No se conocen workarounds para esta vulnerabilidad. Este problema fue descubierto e informado por el laboratorio de seguridad de GitHub y tambi\u00e9n se rastrea como GHSL-2024-074." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-362xx/CVE-2024-36252.json b/CVE-2024/CVE-2024-362xx/CVE-2024-36252.json index dfdf50e4626..0789f0d6708 100644 --- a/CVE-2024/CVE-2024-362xx/CVE-2024-36252.json +++ b/CVE-2024/CVE-2024-362xx/CVE-2024-36252.json @@ -2,12 +2,16 @@ "id": "CVE-2024-36252", "sourceIdentifier": "vultures@jpcert.or.jp", "published": "2024-06-19T07:15:46.200", - "lastModified": "2024-06-19T07:15:46.200", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Improper restriction of communication channel to intended endpoints issue exists in Ricoh Streamline NX PC Client ver.3.6.x and earlier. If this vulnerability is exploited, arbitrary code may be executed on the PC where the product is installed." + }, + { + "lang": "es", + "value": "Existe un problema de restricci\u00f3n inadecuada del canal de comunicaci\u00f3n a los endpoints previstos en Ricoh Streamline NX PC Client versi\u00f3n 3.6.x y versiones anteriores. Si se explota esta vulnerabilidad, se puede ejecutar c\u00f3digo arbitrario en la PC donde est\u00e1 instalado el producto." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-364xx/CVE-2024-36480.json b/CVE-2024/CVE-2024-364xx/CVE-2024-36480.json index 1cb7a5531ed..5895f2a8563 100644 --- a/CVE-2024/CVE-2024-364xx/CVE-2024-36480.json +++ b/CVE-2024/CVE-2024-364xx/CVE-2024-36480.json @@ -2,12 +2,16 @@ "id": "CVE-2024-36480", "sourceIdentifier": "vultures@jpcert.or.jp", "published": "2024-06-19T07:15:46.340", - "lastModified": "2024-06-19T07:15:46.340", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Use of hard-coded credentials issue exists in Ricoh Streamline NX PC Client ver.3.7.2 and earlier. If this vulnerability is exploited, an attacker may obtain LocalSystem Account of the PC where the product is installed. As a result, unintended operations may be performed on the PC." + }, + { + "lang": "es", + "value": "Existe un problema de uso de credenciales codificadas en Ricoh Streamline NX PC Client versi\u00f3n 3.7.2 y versiones anteriores. Si se explota esta vulnerabilidad, un atacante puede obtener la cuenta LocalSystem de la PC donde est\u00e1 instalado el producto. Como resultado, es posible que se realicen operaciones no deseadas en la PC." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-365xx/CVE-2024-36527.json b/CVE-2024/CVE-2024-365xx/CVE-2024-36527.json index 874defe46b9..bc9965eedee 100644 --- a/CVE-2024/CVE-2024-365xx/CVE-2024-36527.json +++ b/CVE-2024/CVE-2024-365xx/CVE-2024-36527.json @@ -2,12 +2,16 @@ "id": "CVE-2024-36527", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T18:15:16.767", - "lastModified": "2024-06-17T18:15:16.767", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "puppeteer-renderer v.3.2.0 and before is vulnerable to Directory Traversal. Attackers can exploit the URL parameter using the file protocol to read sensitive information from the server." + }, + { + "lang": "es", + "value": "puppeteer-renderer v.3.2.0 y anteriores es vulnerable a Directory Traversal. Los atacantes pueden explotar el par\u00e1metro URL utilizando el protocolo de archivo para leer informaci\u00f3n confidencial del servidor." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-365xx/CVE-2024-36543.json b/CVE-2024/CVE-2024-365xx/CVE-2024-36543.json index c87feb0ad12..ee855c41bef 100644 --- a/CVE-2024/CVE-2024-365xx/CVE-2024-36543.json +++ b/CVE-2024/CVE-2024-365xx/CVE-2024-36543.json @@ -2,12 +2,16 @@ "id": "CVE-2024-36543", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T19:15:58.353", - "lastModified": "2024-06-17T19:15:58.353", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Incorrect access control in the Kafka Connect REST API in the STRIMZI Project 0.41.0 and earlier allows an attacker to deny the service for Kafka Mirroring, potentially mirror the topics' content to his Kafka cluster via a malicious connector (bypassing Kafka ACL if it exists), and potentially steal Kafka SASL credentials, by querying the MirrorMaker Kafka REST API." + }, + { + "lang": "es", + "value": "El control de acceso incorrecto en la API REST de Kafka Connect en el proyecto STRIMZI 0.41.0 y versiones anteriores permite a un atacante denegar el servicio de Kafka Mirroring y potencialmente reflejar el contenido de los temas en su cl\u00faster de Kafka a trav\u00e9s de un conector malicioso (evitando Kafka ACL si existe), y potencialmente robar credenciales SASL de Kafka consultando la API REST de MirrorMaker Kafka." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-365xx/CVE-2024-36573.json b/CVE-2024/CVE-2024-365xx/CVE-2024-36573.json index f7beedd8ca9..d07ca5a74a0 100644 --- a/CVE-2024/CVE-2024-365xx/CVE-2024-36573.json +++ b/CVE-2024/CVE-2024-365xx/CVE-2024-36573.json @@ -2,12 +2,16 @@ "id": "CVE-2024-36573", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T16:15:14.947", - "lastModified": "2024-06-17T16:15:14.947", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "almela obx before v.0.0.4 has a Prototype Pollution issue which allows arbitrary code execution via the obx/build/index.js:656), reduce (@almela/obx/build/index.js:470), Object.set (obx/build/index.js:269) component." + }, + { + "lang": "es", + "value": "almela obx anterior a v.0.0.4 tiene un problema de contaminaci\u00f3n de prototipos que permite la ejecuci\u00f3n de c\u00f3digo arbitrario a trav\u00e9s de obx/build/index.js:656), reduce (@almela/obx/build/index.js:470), Object.set (obx/build/index.js:269) componente." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-365xx/CVE-2024-36574.json b/CVE-2024/CVE-2024-365xx/CVE-2024-36574.json index 6da76b725c4..2c097594637 100644 --- a/CVE-2024/CVE-2024-365xx/CVE-2024-36574.json +++ b/CVE-2024/CVE-2024-365xx/CVE-2024-36574.json @@ -2,12 +2,16 @@ "id": "CVE-2024-36574", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T16:15:15.040", - "lastModified": "2024-06-17T16:15:15.040", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A Prototype Pollution issue in flatten-json 1.0.1 allows an attacker to execute arbitrary code via module.exports.unflattenJSON (flatten-json/index.js:42)" + }, + { + "lang": "es", + "value": "Un problema de contaminaci\u00f3n de prototipos en flatten-json 1.0.1 permite a un atacante ejecutar c\u00f3digo arbitrario a trav\u00e9s de module.exports.unflattenJSON (flatten-json/index.js:42)" } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-365xx/CVE-2024-36575.json b/CVE-2024/CVE-2024-365xx/CVE-2024-36575.json index 57bb373665c..2e14e126757 100644 --- a/CVE-2024/CVE-2024-365xx/CVE-2024-36575.json +++ b/CVE-2024/CVE-2024-365xx/CVE-2024-36575.json @@ -2,12 +2,16 @@ "id": "CVE-2024-36575", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T16:15:15.140", - "lastModified": "2024-06-17T16:15:15.140", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A Prototype Pollution issue in getsetprop 1.1.0 allows an attacker to execute arbitrary code via global.accessor." + }, + { + "lang": "es", + "value": "Un problema de contaminaci\u00f3n de prototipos en getsetprop 1.1.0 permite a un atacante ejecutar c\u00f3digo arbitrario a trav\u00e9s de global.accessor." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-365xx/CVE-2024-36577.json b/CVE-2024/CVE-2024-365xx/CVE-2024-36577.json index 5d17a461b12..49dfe481ce0 100644 --- a/CVE-2024/CVE-2024-365xx/CVE-2024-36577.json +++ b/CVE-2024/CVE-2024-365xx/CVE-2024-36577.json @@ -2,12 +2,16 @@ "id": "CVE-2024-36577", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T16:15:15.233", - "lastModified": "2024-06-17T16:15:15.233", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "apphp js-object-resolver < 3.1.1 is vulnerable to Prototype Pollution via Module.setNestedProperty." + }, + { + "lang": "es", + "value": "apphp js-object-resolver < 3.1.1 es vulnerable a la contaminaci\u00f3n de prototipos a trav\u00e9s de Module.setNestedProperty." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-365xx/CVE-2024-36578.json b/CVE-2024/CVE-2024-365xx/CVE-2024-36578.json index f7c57344093..00fcbf37421 100644 --- a/CVE-2024/CVE-2024-365xx/CVE-2024-36578.json +++ b/CVE-2024/CVE-2024-365xx/CVE-2024-36578.json @@ -2,12 +2,16 @@ "id": "CVE-2024-36578", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T16:15:15.333", - "lastModified": "2024-06-17T16:15:15.333", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "akbr update 1.0.0 is vulnerable to Prototype Pollution via update/index.js." + }, + { + "lang": "es", + "value": "La actualizaci\u00f3n 1.0.0 de akbr es vulnerable a Prototype Pollution a trav\u00e9s de update/index.js." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-365xx/CVE-2024-36580.json b/CVE-2024/CVE-2024-365xx/CVE-2024-36580.json index 0356acf338a..19af4badf16 100644 --- a/CVE-2024/CVE-2024-365xx/CVE-2024-36580.json +++ b/CVE-2024/CVE-2024-365xx/CVE-2024-36580.json @@ -2,12 +2,16 @@ "id": "CVE-2024-36580", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T14:15:10.227", - "lastModified": "2024-06-17T14:15:10.227", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A Prototype Pollution issue in cdr0 sg 1.0.10 allows an attacker to execute arbitrary code." + }, + { + "lang": "es", + "value": "Un problema de contaminaci\u00f3n de prototipos en cdr0 sg 1.0.10 permite a un atacante ejecutar c\u00f3digo arbitrario." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-365xx/CVE-2024-36581.json b/CVE-2024/CVE-2024-365xx/CVE-2024-36581.json index 9f97c6175c7..535613e8729 100644 --- a/CVE-2024/CVE-2024-365xx/CVE-2024-36581.json +++ b/CVE-2024/CVE-2024-365xx/CVE-2024-36581.json @@ -2,12 +2,16 @@ "id": "CVE-2024-36581", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T15:15:51.130", - "lastModified": "2024-06-17T15:15:51.130", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A Prototype Pollution issue in abw badger-database 1.2.1 allows an attacker to execute arbitrary code via dist/badger-database.esm." + }, + { + "lang": "es", + "value": "Un problema de contaminaci\u00f3n de prototipos en abw Badger-database 1.2.1 permite a un atacante ejecutar c\u00f3digo arbitrario a trav\u00e9s de dist/badger-database.esm." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-365xx/CVE-2024-36582.json b/CVE-2024/CVE-2024-365xx/CVE-2024-36582.json index dedcca3158e..c9faadef558 100644 --- a/CVE-2024/CVE-2024-365xx/CVE-2024-36582.json +++ b/CVE-2024/CVE-2024-365xx/CVE-2024-36582.json @@ -2,12 +2,16 @@ "id": "CVE-2024-36582", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T15:15:51.243", - "lastModified": "2024-06-17T15:15:51.243", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "alexbinary object-deep-assign 1.0.11 is vulnerable to Prototype Pollution via the extend() method of Module.deepAssign (/src/index.js)" + }, + { + "lang": "es", + "value": "alexbinary object-deep-assign 1.0.11 es vulnerable a Prototype Pollution a trav\u00e9s del m\u00e9todo extend() de Module.deepAssign (/src/index.js)" } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-365xx/CVE-2024-36583.json b/CVE-2024/CVE-2024-365xx/CVE-2024-36583.json index 1e5c8080639..1aa0204b8dc 100644 --- a/CVE-2024/CVE-2024-365xx/CVE-2024-36583.json +++ b/CVE-2024/CVE-2024-365xx/CVE-2024-36583.json @@ -2,12 +2,16 @@ "id": "CVE-2024-36583", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T14:15:10.330", - "lastModified": "2024-06-17T14:15:10.330", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A Prototype Pollution issue in byondreal accessor <= 1.0.0 allows an attacker to execute arbitrary code via @byondreal/accessor/index." + }, + { + "lang": "es", + "value": "Un problema de contaminaci\u00f3n de prototipo en byondreal accessor <= 1.0.0 permite a un atacante ejecutar c\u00f3digo arbitrario a trav\u00e9s de @byondreal/accessor/index." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-366xx/CVE-2024-36677.json b/CVE-2024/CVE-2024-366xx/CVE-2024-36677.json index 55d2bc52b58..e295603e50b 100644 --- a/CVE-2024/CVE-2024-366xx/CVE-2024-36677.json +++ b/CVE-2024/CVE-2024-366xx/CVE-2024-36677.json @@ -2,12 +2,16 @@ "id": "CVE-2024-36677", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-19T21:15:57.257", - "lastModified": "2024-06-19T21:15:57.257", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the module \"Login as customer PRO\" (loginascustomerpro) <1.2.7 from Weblir for PrestaShop, a guest can access direct link to connect to each customer account of the Shop if the module is not installed OR if a secret accessible to administrator is stolen." + }, + { + "lang": "es", + "value": "En el m\u00f3dulo \"Iniciar sesi\u00f3n como cliente PRO\" (loginascustomerpro) <1.2.7 de Weblir para PrestaShop, un invitado puede acceder a un enlace directo para conectarse a cada cuenta de cliente de la Tienda si el m\u00f3dulo no est\u00e1 instalado O si hay un secreto accesible para el administrador. robado." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-366xx/CVE-2024-36678.json b/CVE-2024/CVE-2024-366xx/CVE-2024-36678.json index e7470c8df4d..8adb2d9289a 100644 --- a/CVE-2024/CVE-2024-366xx/CVE-2024-36678.json +++ b/CVE-2024/CVE-2024-366xx/CVE-2024-36678.json @@ -2,12 +2,16 @@ "id": "CVE-2024-36678", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-19T21:15:57.363", - "lastModified": "2024-06-19T21:15:57.363", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the module \"Theme settings\" (pk_themesettings) <= 1.8.8 from Promokit.eu for PrestaShop, a guest can perform SQL injection. The script ajax.php have a sensitive SQL call that can be executed with a trivial http call and exploited to forge a SQL injection." + }, + { + "lang": "es", + "value": "En el m\u00f3dulo \"Configuraci\u00f3n del tema\" (pk_themesettings) <= 1.8.8 de Promokit.eu para PrestaShop, un invitado puede realizar una inyecci\u00f3n SQL. El script ajax.php tiene una llamada SQL sensible que puede ejecutarse con una llamada http trivial y explotarse para falsificar una inyecci\u00f3n SQL." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-366xx/CVE-2024-36679.json b/CVE-2024/CVE-2024-366xx/CVE-2024-36679.json index 778a4ea629d..56909faefb6 100644 --- a/CVE-2024/CVE-2024-366xx/CVE-2024-36679.json +++ b/CVE-2024/CVE-2024-366xx/CVE-2024-36679.json @@ -2,12 +2,16 @@ "id": "CVE-2024-36679", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-19T21:15:57.470", - "lastModified": "2024-06-19T21:15:57.470", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the module \"Module Live Chat Pro (All in One Messaging)\" (livechatpro) <=8.4.0, a guest can perform PHP Code injection. Due to a predictable token, the method `Lcp::saveTranslations()` suffer of a white writer that can inject PHP code into a PHP file." + }, + { + "lang": "es", + "value": "En el m\u00f3dulo \"M\u00f3dulo Live Chat Pro (Mensajer\u00eda todo en uno)\" (livechatpro) <=8.4.0, un invitado puede realizar la inyecci\u00f3n de c\u00f3digo PHP. Debido a un token predecible, el m\u00e9todo `Lcp::saveTranslations()` sufre de un escritor blanco que puede inyectar c\u00f3digo PHP en un archivo PHP." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-366xx/CVE-2024-36680.json b/CVE-2024/CVE-2024-366xx/CVE-2024-36680.json index cb185db84c8..56d6f7d57d0 100644 --- a/CVE-2024/CVE-2024-366xx/CVE-2024-36680.json +++ b/CVE-2024/CVE-2024-366xx/CVE-2024-36680.json @@ -2,12 +2,16 @@ "id": "CVE-2024-36680", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-19T21:15:57.577", - "lastModified": "2024-06-19T21:15:57.577", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the module \"Facebook\" (pkfacebook) <=1.0.1 from Promokit.eu for PrestaShop, a guest can perform SQL injection. The ajax script facebookConnect.php have a sensitive SQL call that can be executed with a trivial http call and exploited to forge a SQL injection." + }, + { + "lang": "es", + "value": "En el m\u00f3dulo \"Facebook\" (pkfacebook) <=1.0.1 de Promokit.eu para PrestaShop, un invitado puede realizar una inyecci\u00f3n SQL. El script ajax facebookConnect.php tiene una llamada SQL sensible que puede ejecutarse con una llamada http trivial y explotarse para falsificar una inyecci\u00f3n SQL." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-366xx/CVE-2024-36684.json b/CVE-2024/CVE-2024-366xx/CVE-2024-36684.json index 118ee82499b..d478d36a309 100644 --- a/CVE-2024/CVE-2024-366xx/CVE-2024-36684.json +++ b/CVE-2024/CVE-2024-366xx/CVE-2024-36684.json @@ -2,12 +2,16 @@ "id": "CVE-2024-36684", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-19T21:15:57.680", - "lastModified": "2024-06-19T21:15:57.680", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the module \"Custom links\" (pk_customlinks) <= 2.3 from Promokit.eu for PrestaShop, a guest can perform SQL injection. The script ajax.php have a sensitive SQL call that can be executed with a trivial http call and exploited to forge a SQL injection." + }, + { + "lang": "es", + "value": "En el m\u00f3dulo \"Enlaces personalizados\" (pk_customlinks) <= 2.3 de Promokit.eu para PrestaShop, un invitado puede realizar una inyecci\u00f3n SQL. El script ajax.php tiene una llamada SQL sensible que puede ejecutarse con una llamada http trivial y explotarse para falsificar una inyecci\u00f3n SQL." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-369xx/CVE-2024-36973.json b/CVE-2024/CVE-2024-369xx/CVE-2024-36973.json index 0d012b4bad0..60ab6150d8a 100644 --- a/CVE-2024/CVE-2024-369xx/CVE-2024-36973.json +++ b/CVE-2024/CVE-2024-369xx/CVE-2024-36973.json @@ -2,12 +2,16 @@ "id": "CVE-2024-36973", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-17T18:15:17.043", - "lastModified": "2024-06-17T18:15:17.043", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmisc: microchip: pci1xxxx: fix double free in the error handling of gp_aux_bus_probe()\n\nWhen auxiliary_device_add() returns error and then calls\nauxiliary_device_uninit(), callback function\ngp_auxiliary_device_release() calls ida_free() and\nkfree(aux_device_wrapper) to free memory. We should't\ncall them again in the error handling path.\n\nFix this by skipping the redundant cleanup functions." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: misc: microchip: pci1xxxx: corrige double free en el manejo de errores de gp_aux_bus_probe() Cuando auxiliar_device_add() devuelve error y luego llama a auxiliar_device_uninit(), la funci\u00f3n de devoluci\u00f3n de llamada gp_auxiliary_device_release() llama a ida_free( ) y kfree(aux_device_wrapper) para liberar memoria. No deber\u00edamos volver a llamarlos en la ruta de manejo de errores. Solucione este problema omitiendo las funciones de limpieza redundantes." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-369xx/CVE-2024-36974.json b/CVE-2024/CVE-2024-369xx/CVE-2024-36974.json index 7f4e225fa88..a768bd21c70 100644 --- a/CVE-2024/CVE-2024-369xx/CVE-2024-36974.json +++ b/CVE-2024/CVE-2024-369xx/CVE-2024-36974.json @@ -2,12 +2,16 @@ "id": "CVE-2024-36974", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-18T20:15:13.257", - "lastModified": "2024-06-18T20:15:13.257", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: taprio: always validate TCA_TAPRIO_ATTR_PRIOMAP\n\nIf one TCA_TAPRIO_ATTR_PRIOMAP attribute has been provided,\ntaprio_parse_mqprio_opt() must validate it, or userspace\ncan inject arbitrary data to the kernel, the second time\ntaprio_change() is called.\n\nFirst call (with valid attributes) sets dev->num_tc\nto a non zero value.\n\nSecond call (with arbitrary mqprio attributes)\nreturns early from taprio_parse_mqprio_opt()\nand bad things can happen." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: net/sched: taprio: validar siempre TCA_TAPRIO_ATTR_PRIOMAP Si se ha proporcionado un atributo TCA_TAPRIO_ATTR_PRIOMAP, taprio_parse_mqprio_opt() debe validarlo, o el espacio de usuario puede inyectar datos arbitrarios al kernel, la segunda vez taprio_change () se llama. La primera llamada (con atributos v\u00e1lidos) establece dev->num_tc en un valor distinto de cero. La segunda llamada (con atributos mqprio arbitrarios) regresa temprano desde taprio_parse_mqprio_opt() y pueden suceder cosas malas." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-369xx/CVE-2024-36975.json b/CVE-2024/CVE-2024-369xx/CVE-2024-36975.json index f01838ccf84..7ea6eed98c5 100644 --- a/CVE-2024/CVE-2024-369xx/CVE-2024-36975.json +++ b/CVE-2024/CVE-2024-369xx/CVE-2024-36975.json @@ -2,12 +2,16 @@ "id": "CVE-2024-36975", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-18T20:15:13.340", - "lastModified": "2024-06-18T20:15:13.340", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nKEYS: trusted: Do not use WARN when encode fails\n\nWhen asn1_encode_sequence() fails, WARN is not the correct solution.\n\n1. asn1_encode_sequence() is not an internal function (located\n in lib/asn1_encode.c).\n2. Location is known, which makes the stack trace useless.\n3. Results a crash if panic_on_warn is set.\n\nIt is also noteworthy that the use of WARN is undocumented, and it\nshould be avoided unless there is a carefully considered rationale to\nuse it.\n\nReplace WARN with pr_err, and print the return value instead, which is\nonly useful piece of information." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: LLAVES: confiable: no usar WARN cuando falla la codificaci\u00f3n Cuando falla asn1_encode_sequence(), WARN no es la soluci\u00f3n correcta. 1. asn1_encode_sequence() no es una funci\u00f3n interna (ubicada en lib/asn1_encode.c). 2. Se conoce la ubicaci\u00f3n, lo que hace que el seguimiento de la pila sea in\u00fatil. 3. Se produce un bloqueo si se configura p\u00e1nico_on_warn. Tambi\u00e9n es digno de menci\u00f3n que el uso de WARN no est\u00e1 documentado y debe evitarse a menos que exista una justificaci\u00f3n cuidadosamente considerada para su uso. Reemplace WARN con pr_err e imprima el valor de retorno, que es solo informaci\u00f3n \u00fatil." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-369xx/CVE-2024-36976.json b/CVE-2024/CVE-2024-369xx/CVE-2024-36976.json index fe6f1cff954..cb6f5804f1a 100644 --- a/CVE-2024/CVE-2024-369xx/CVE-2024-36976.json +++ b/CVE-2024/CVE-2024-369xx/CVE-2024-36976.json @@ -2,12 +2,16 @@ "id": "CVE-2024-36976", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-18T20:15:13.437", - "lastModified": "2024-06-18T20:15:13.437", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nRevert \"media: v4l2-ctrls: show all owned controls in log_status\"\n\nThis reverts commit 9801b5b28c6929139d6fceeee8d739cc67bb2739.\n\nThis patch introduced a potential deadlock scenario:\n\n[Wed May 8 10:02:06 2024] Possible unsafe locking scenario:\n\n[Wed May 8 10:02:06 2024] CPU0 CPU1\n[Wed May 8 10:02:06 2024] ---- ----\n[Wed May 8 10:02:06 2024] lock(vivid_ctrls:1620:(hdl_vid_cap)->_lock);\n[Wed May 8 10:02:06 2024] lock(vivid_ctrls:1608:(hdl_user_vid)->_lock);\n[Wed May 8 10:02:06 2024] lock(vivid_ctrls:1620:(hdl_vid_cap)->_lock);\n[Wed May 8 10:02:06 2024] lock(vivid_ctrls:1608:(hdl_user_vid)->_lock);\n\nFor now just revert." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: Revertir \"media: v4l2-ctrls: mostrar todos los controles de propiedad en log_status\" Esto revierte el commit 9801b5b28c6929139d6fceeee8d739cc67bb2739. Este parche introdujo un posible escenario de bloqueo: [mi\u00e9rcoles 8 de mayo 10:02:06 2024] Posible escenario de bloqueo inseguro: [mi\u00e9rcoles 8 de mayo 10:02:06 2024] CPU0 CPU1 [mi\u00e9rcoles 8 de mayo 10:02:06 2024] -- -- ---- [mi\u00e9rcoles 8 de mayo 10:02:06 2024] lock(vivid_ctrls:1620:(hdl_vid_cap)->_lock); [Mi\u00e9rcoles 8 de mayo 10:02:06 2024] lock(vivid_ctrls:1608:(hdl_user_vid)->_lock); [Mi\u00e9rcoles 8 de mayo 10:02:06 2024] lock(vivid_ctrls:1620:(hdl_vid_cap)->_lock); [Mi\u00e9rcoles 8 de mayo 10:02:06 2024] lock(vivid_ctrls:1608:(hdl_user_vid)->_lock); Por ahora simplemente revertir." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-369xx/CVE-2024-36977.json b/CVE-2024/CVE-2024-369xx/CVE-2024-36977.json index a3af8f33717..bac59c68c3b 100644 --- a/CVE-2024/CVE-2024-369xx/CVE-2024-36977.json +++ b/CVE-2024/CVE-2024-369xx/CVE-2024-36977.json @@ -2,12 +2,16 @@ "id": "CVE-2024-36977", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-18T20:15:13.517", - "lastModified": "2024-06-18T20:15:13.517", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nusb: dwc3: Wait unconditionally after issuing EndXfer command\n\nCurrently all controller IP/revisions except DWC3_usb3 >= 310a\nwait 1ms unconditionally for ENDXFER completion when IOC is not\nset. This is because DWC_usb3 controller revisions >= 3.10a\nsupports GUCTL2[14: Rst_actbitlater] bit which allows polling\nCMDACT bit to know whether ENDXFER command is completed.\n\nConsider a case where an IN request was queued, and parallelly\nsoft_disconnect was called (due to ffs_epfile_release). This\neventually calls stop_active_transfer with IOC cleared, hence\nsend_gadget_ep_cmd() skips waiting for CMDACT cleared during\nEndXfer. For DWC3 controllers with revisions >= 310a, we don't\nforcefully wait for 1ms either, and we proceed by unmapping the\nrequests. If ENDXFER didn't complete by this time, it leads to\nSMMU faults since the controller would still be accessing those\nrequests.\n\nFix this by ensuring ENDXFER completion by adding 1ms delay in\n__dwc3_stop_active_transfer() unconditionally." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: usb: dwc3: Espere incondicionalmente despu\u00e9s de emitir el comando EndXfer Actualmente, todas las IP/revisiones del controlador excepto DWC3_usb3 >= 310a esperan 1 ms incondicionalmente para que ENDXFER se complete cuando el IOC no est\u00e1 configurado. Esto se debe a que las revisiones del controlador DWC_usb3 >= 3.10a admiten el bit GUCTL2[14: Rst_actbitlater] que permite sondear el bit CMDACT para saber si se complet\u00f3 el comando ENDXFER. Considere un caso en el que se puso en cola una solicitud IN y, en paralelo, se llam\u00f3 a soft_disconnect (debido a ffs_epfile_release). Esto eventualmente llama a stop_active_transfer con el IOC borrado, por lo tanto, send_gadget_ep_cmd() omite la espera de que CMDACT se borre durante EndXfer. Para los controladores DWC3 con revisiones >= 310a, tampoco esperamos forzosamente 1 ms y procedemos a desasignar las solicitudes. Si ENDXFER no se complet\u00f3 en este momento, se producir\u00e1n fallas de SMMU ya que el controlador a\u00fan estar\u00eda accediendo a esas solicitudes. Solucione este problema asegurando la finalizaci\u00f3n de ENDXFER agregando un retraso de 1 ms en __dwc3_stop_active_transfer() incondicionalmente." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-369xx/CVE-2024-36978.json b/CVE-2024/CVE-2024-369xx/CVE-2024-36978.json index f8657eeb481..4259543ff5b 100644 --- a/CVE-2024/CVE-2024-369xx/CVE-2024-36978.json +++ b/CVE-2024/CVE-2024-369xx/CVE-2024-36978.json @@ -2,12 +2,16 @@ "id": "CVE-2024-36978", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T07:15:46.437", - "lastModified": "2024-06-19T07:15:46.437", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: sched: sch_multiq: fix possible OOB write in multiq_tune()\n\nq->bands will be assigned to qopt->bands to execute subsequent code logic\nafter kmalloc. So the old q->bands should not be used in kmalloc.\nOtherwise, an out-of-bounds write will occur." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: net: sched: sch_multiq: corrige posible escritura OOB en multiq_tune() q->bands se asignar\u00e1n a qopt->bands para ejecutar la l\u00f3gica de c\u00f3digo posterior despu\u00e9s de kmalloc. Por lo tanto, las antiguas q->bands no deber\u00edan usarse en kmalloc. De lo contrario, se producir\u00e1 una escritura fuera de los l\u00edmites." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-369xx/CVE-2024-36979.json b/CVE-2024/CVE-2024-369xx/CVE-2024-36979.json index 99348dbd09f..f79801cd07c 100644 --- a/CVE-2024/CVE-2024-369xx/CVE-2024-36979.json +++ b/CVE-2024/CVE-2024-369xx/CVE-2024-36979.json @@ -2,12 +2,16 @@ "id": "CVE-2024-36979", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:13.620", - "lastModified": "2024-06-19T14:15:13.620", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: bridge: mst: fix vlan use-after-free\n\nsyzbot reported a suspicious rcu usage[1] in bridge's mst code. While\nfixing it I noticed that nothing prevents a vlan to be freed while\nwalking the list from the same path (br forward delay timer). Fix the rcu\nusage and also make sure we are not accessing freed memory by making\nbr_mst_vlan_set_state use rcu read lock.\n\n[1]\n WARNING: suspicious RCU usage\n 6.9.0-rc6-syzkaller #0 Not tainted\n -----------------------------\n net/bridge/br_private.h:1599 suspicious rcu_dereference_protected() usage!\n ...\n stack backtrace:\n CPU: 1 PID: 8017 Comm: syz-executor.1 Not tainted 6.9.0-rc6-syzkaller #0\n Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024\n Call Trace:\n \n __dump_stack lib/dump_stack.c:88 [inline]\n dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114\n lockdep_rcu_suspicious+0x221/0x340 kernel/locking/lockdep.c:6712\n nbp_vlan_group net/bridge/br_private.h:1599 [inline]\n br_mst_set_state+0x1ea/0x650 net/bridge/br_mst.c:105\n br_set_state+0x28a/0x7b0 net/bridge/br_stp.c:47\n br_forward_delay_timer_expired+0x176/0x440 net/bridge/br_stp_timer.c:88\n call_timer_fn+0x18e/0x650 kernel/time/timer.c:1793\n expire_timers kernel/time/timer.c:1844 [inline]\n __run_timers kernel/time/timer.c:2418 [inline]\n __run_timer_base+0x66a/0x8e0 kernel/time/timer.c:2429\n run_timer_base kernel/time/timer.c:2438 [inline]\n run_timer_softirq+0xb7/0x170 kernel/time/timer.c:2448\n __do_softirq+0x2c6/0x980 kernel/softirq.c:554\n invoke_softirq kernel/softirq.c:428 [inline]\n __irq_exit_rcu+0xf2/0x1c0 kernel/softirq.c:633\n irq_exit_rcu+0x9/0x30 kernel/softirq.c:645\n instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1043 [inline]\n sysvec_apic_timer_interrupt+0xa6/0xc0 arch/x86/kernel/apic/apic.c:1043\n \n \n asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:702\n RIP: 0010:lock_acquire+0x264/0x550 kernel/locking/lockdep.c:5758\n Code: 2b 00 74 08 4c 89 f7 e8 ba d1 84 00 f6 44 24 61 02 0f 85 85 01 00 00 41 f7 c7 00 02 00 00 74 01 fb 48 c7 44 24 40 0e 36 e0 45 <4b> c7 44 25 00 00 00 00 00 43 c7 44 25 09 00 00 00 00 43 c7 44 25\n RSP: 0018:ffffc90013657100 EFLAGS: 00000206\n RAX: 0000000000000001 RBX: 1ffff920026cae2c RCX: 0000000000000001\n RDX: dffffc0000000000 RSI: ffffffff8bcaca00 RDI: ffffffff8c1eaa60\n RBP: ffffc90013657260 R08: ffffffff92efe507 R09: 1ffffffff25dfca0\n R10: dffffc0000000000 R11: fffffbfff25dfca1 R12: 1ffff920026cae28\n R13: dffffc0000000000 R14: ffffc90013657160 R15: 0000000000000246" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: net: bridge: mst: fix vlan use-after-free syzbot inform\u00f3 un uso sospechoso de rcu[1] en el c\u00f3digo mst del puente. Mientras lo solucionaba, not\u00e9 que nada impide que se libere una VLAN mientras se recorre la lista desde el mismo camino (br temporizador de retardo de avance). Corrija el uso de rcu y tambi\u00e9n aseg\u00farese de que no accedamos a la memoria liberada haciendo que br_mst_vlan_set_state use el bloqueo de lectura de rcu. [1] ADVERTENCIA: uso sospechoso de RCU 6.9.0-rc6-syzkaller #0 No contaminado ----------------------- net/ bridge/br_private.h:1599 \u00a1uso sospechoso de rcu_dereference_protected()! ... seguimiento de pila: CPU: 1 PID: 8017 Comm: syz-executor.1 No contaminado 6.9.0-rc6-syzkaller #0 Nombre del hardware: Google Google Compute Engine/Google Compute Engine, BIOS Google 27/03/2024 Llamada Seguimiento: __dump_stack lib/dump_stack.c:88 [en l\u00ednea] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114 lockdep_rcu_suspicious+0x221/0x340 kernel/locking/lockdep.c:6712 nbp_vlan_group net/bridge/br_private.h :1599 [en l\u00ednea] br_mst_set_state+0x1ea/0x650 net/bridge/br_mst.c:105 br_set_state+0x28a/0x7b0 net/bridge/br_stp.c:47 br_forward_delay_timer_expired+0x176/0x440 net/bridge/br_stp_timer.c:88 n+0x18e /0x650 kernel/time/timer.c:1793 expire_timers kernel/time/timer.c:1844 [en l\u00ednea] __run_timers kernel/time/timer.c:2418 [en l\u00ednea] __run_timer_base+0x66a/0x8e0 kernel/time/timer.c: 2429 run_timer_base kernel/time/timer.c:2438 [en l\u00ednea] run_timer_softirq+0xb7/0x170 kernel/time/timer.c:2448 __do_softirq+0x2c6/0x980 kernel/softirq.c:554 invoke_softirq kernel/softirq.c:428 [en l\u00ednea ] __irq_exit_rcu+0xf2/0x1c0 kernel/softirq.c:633 irq_exit_rcu+0x9/0x30 kernel/softirq.c:645 instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1043 [en l\u00ednea] 0xc0 arco/x86 /kernel/apic/apic.c:1043 asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:702 RIP: 0010:lock_acquire+0x264/0x550 kernel/locking/lockdep. c:5758 C\u00f3digo: 2b 00 74 08 4c 89 f7 e8 ba d1 84 00 f6 44 24 61 02 0f 85 85 01 00 00 41 f7 c7 00 02 00 00 74 01 fb 48 c7 44 24 40 0e 36 e0 <4b> c7 44 25 00 00 00 00 00 43 c7 44 25 09 00 00 00 00 43 c7 44 25 RSP: 0018:ffffc90013657100 EFLAGS: 00000206 RAX: 0000000000000001 RBX: ffff920026cae2c RCX: 0000000000000001 RDX: dffffc0000000000 RSI: ffffffff8bcaca00 RDI: ffffffff8c1eaa60 RBP: ffffc90013657260 R08: ffffffff92efe507 R09: 1ffffffff25dfca0 R10: dffffc0000000000 R11: ffffbfff25dfca1 R12: 1ffff920026cae28 R13: dffffc0000000000 R14: ffffc90013657160 5: 0000000000000246" } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-36xx/CVE-2024-3602.json b/CVE-2024/CVE-2024-36xx/CVE-2024-3602.json index 043bfb2c98d..47b5dedd502 100644 --- a/CVE-2024/CVE-2024-36xx/CVE-2024-3602.json +++ b/CVE-2024/CVE-2024-36xx/CVE-2024-3602.json @@ -2,12 +2,16 @@ "id": "CVE-2024-3602", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-20T02:15:10.590", - "lastModified": "2024-06-20T02:15:10.590", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "The Pop ups, Exit intent popups, email popups, banners, bars, countdowns and cart savers \u2013 Promolayer plugin for WordPress is vulnerable to unauthorized plugin settings update due to a missing capability check on the disconnect_promolayer function in all versions up to, and including, 1.1.0. This makes it possible for authenticated attackers, with subscriber access or higher, to remove the Promolayer connection." + }, + { + "lang": "es", + "value": "El complemento Pop ups, Exit intent popups, email popups, banners, bars, countdowns and cart savers \u2013 Promolayer para WordPress es vulnerable a actualizaciones no autorizadas de la configuraci\u00f3n del complemento debido a una falta de verificaci\u00f3n de capacidad en la funci\u00f3n de desconexi\u00f3n_promolayer en todas las versiones hasta, e incluyendo, 1.1.0. Esto hace posible que atacantes autenticados, con acceso de suscriptor o superior, eliminen la conexi\u00f3n de Promolayer." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-36xx/CVE-2024-3605.json b/CVE-2024/CVE-2024-36xx/CVE-2024-3605.json index a981686838b..e10c72ec1a6 100644 --- a/CVE-2024/CVE-2024-36xx/CVE-2024-3605.json +++ b/CVE-2024/CVE-2024-36xx/CVE-2024-3605.json @@ -2,12 +2,16 @@ "id": "CVE-2024-3605", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-20T02:15:10.817", - "lastModified": "2024-06-20T02:15:10.817", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "The WP Hotel Booking plugin for WordPress is vulnerable to SQL Injection via the 'room_type' parameter of the /wphb/v1/rooms/search-rooms REST API endpoint in all versions up to, and including, 2.1.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database." + }, + { + "lang": "es", + "value": "El complemento WP Hotel Booking para WordPress es vulnerable a la inyecci\u00f3n SQL a trav\u00e9s del par\u00e1metro 'room_type' del endpoint de la API REST /wphb/v1/rooms/search-rooms en todas las versiones hasta la 2.1.0 incluida debido a un escape insuficiente en el par\u00e1metro proporcionado por el usuario y la falta de preparaci\u00f3n suficiente en la consulta SQL existente. Esto hace posible que atacantes no autenticados agreguen consultas SQL adicionales a consultas ya existentes que pueden usarse para extraer informaci\u00f3n confidencial de la base de datos." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-36xx/CVE-2024-3627.json b/CVE-2024/CVE-2024-36xx/CVE-2024-3627.json index 12b5fab2ce9..ccdb022312d 100644 --- a/CVE-2024/CVE-2024-36xx/CVE-2024-3627.json +++ b/CVE-2024/CVE-2024-36xx/CVE-2024-3627.json @@ -2,12 +2,16 @@ "id": "CVE-2024-3627", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-20T02:15:11.040", - "lastModified": "2024-06-20T02:15:11.040", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "The Wheel of Life: Coaching and Assessment Tool for Life Coach plugin for WordPress is vulnerable to unauthorized modification and loss of data due to a missing capability check on several functions in the AjaxFunctions.php file in all versions up to, and including, 1.1.7. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete arbitrary posts and modify settings." + }, + { + "lang": "es", + "value": "El complemento Wheel of Life: Coaching and Assessment Tool for Life Coach para WordPress es vulnerable a modificaciones no autorizadas y p\u00e9rdida de datos debido a una falta de verificaci\u00f3n de capacidad en varias funciones en el archivo AjaxFunctions.php en todas las versiones hasta la 1.1.7 incluida. Esto hace posible que atacantes autenticados, con acceso de nivel de suscriptor y superior, eliminen publicaciones arbitrarias y modifiquen configuraciones." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-370xx/CVE-2024-37079.json b/CVE-2024/CVE-2024-370xx/CVE-2024-37079.json index e262f88332a..088258a4789 100644 --- a/CVE-2024/CVE-2024-370xx/CVE-2024-37079.json +++ b/CVE-2024/CVE-2024-370xx/CVE-2024-37079.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37079", "sourceIdentifier": "security@vmware.com", "published": "2024-06-18T06:15:11.350", - "lastModified": "2024-06-18T06:15:11.350", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "vCenter Server contains a heap-overflow vulnerability in the implementation of the DCERPC protocol. A malicious actor with network access to vCenter Server may trigger this vulnerability by sending a specially crafted network packet potentially leading to remote code execution." + }, + { + "lang": "es", + "value": "vCenter Server contiene una vulnerabilidad de desbordamiento de mont\u00f3n en la implementaci\u00f3n del protocolo DCERPC. Un actor malintencionado con acceso a la red de vCenter Server puede desencadenar esta vulnerabilidad al enviar un paquete de red especialmente manipulado que podr\u00eda conducir a la ejecuci\u00f3n remota de c\u00f3digo." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-370xx/CVE-2024-37080.json b/CVE-2024/CVE-2024-370xx/CVE-2024-37080.json index 87ffaead8d8..8e19695efa2 100644 --- a/CVE-2024/CVE-2024-370xx/CVE-2024-37080.json +++ b/CVE-2024/CVE-2024-370xx/CVE-2024-37080.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37080", "sourceIdentifier": "security@vmware.com", "published": "2024-06-18T06:15:11.640", - "lastModified": "2024-06-18T06:15:11.640", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "vCenter Server contains a heap-overflow vulnerability in the implementation of the DCERPC protocol. A malicious actor with network access to vCenter Server may trigger this vulnerability by sending a specially crafted network packet potentially leading to remote code execution." + }, + { + "lang": "es", + "value": "vCenter Server contiene una vulnerabilidad de desbordamiento de mont\u00f3n en la implementaci\u00f3n del protocolo DCERPC. Un actor malintencionado con acceso a la red de vCenter Server puede desencadenar esta vulnerabilidad al enviar un paquete de red especialmente manipulado que podr\u00eda conducir a la ejecuci\u00f3n remota de c\u00f3digo." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-370xx/CVE-2024-37081.json b/CVE-2024/CVE-2024-370xx/CVE-2024-37081.json index c9a6e582046..3d9f0447fc1 100644 --- a/CVE-2024/CVE-2024-370xx/CVE-2024-37081.json +++ b/CVE-2024/CVE-2024-370xx/CVE-2024-37081.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37081", "sourceIdentifier": "security@vmware.com", "published": "2024-06-18T06:15:11.900", - "lastModified": "2024-06-18T06:15:11.900", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The vCenter Server contains multiple local privilege escalation vulnerabilities due to misconfiguration of sudo.\u00a0An authenticated local user with non-administrative privileges may exploit these issues to elevate privileges to root on vCenter Server Appliance." + }, + { + "lang": "es", + "value": "vCenter Server contiene m\u00faltiples vulnerabilidades de escalada de privilegios locales debido a una mala configuraci\u00f3n de sudo. Un usuario local autenticado con privilegios no administrativos puede aprovechar estos problemas para elevar los privilegios a root en vCenter Server Appliance." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-371xx/CVE-2024-37124.json b/CVE-2024/CVE-2024-371xx/CVE-2024-37124.json index b5e26e4ea07..18cdbc06c20 100644 --- a/CVE-2024/CVE-2024-371xx/CVE-2024-37124.json +++ b/CVE-2024/CVE-2024-371xx/CVE-2024-37124.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37124", "sourceIdentifier": "vultures@jpcert.or.jp", "published": "2024-06-19T07:15:46.547", - "lastModified": "2024-06-19T07:15:46.547", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Use of potentially dangerous function issue exists in Ricoh Streamline NX PC Client. If this vulnerability is exploited, an attacker may create an arbitrary file in the PC where the product is installed." + }, + { + "lang": "es", + "value": "Existe un problema de uso de funciones potencialmente peligrosas en Ricoh Streamline NX PC Client. Si se aprovecha esta vulnerabilidad, un atacante puede crear un archivo arbitrario en la PC donde est\u00e1 instalado el producto." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-371xx/CVE-2024-37158.json b/CVE-2024/CVE-2024-371xx/CVE-2024-37158.json index 9b86fbd185e..2bc4c5e6890 100644 --- a/CVE-2024/CVE-2024-371xx/CVE-2024-37158.json +++ b/CVE-2024/CVE-2024-371xx/CVE-2024-37158.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37158", "sourceIdentifier": "security-advisories@github.com", "published": "2024-06-17T14:15:10.430", - "lastModified": "2024-06-17T14:15:10.430", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Evmos is the Ethereum Virtual Machine (EVM) Hub on the Cosmos Network. Preliminary checks on actions computed by the clawback vesting accounts are performed in the ante handler. Evmos core, implements two different ante handlers: one for Cosmos transactions and one for Ethereum transactions. Checks performed on the two implementation are different. The vulnerability discovered allowed a clawback account to bypass Cosmos ante handler checks by sending an Ethereum transaction targeting a precompile used to interact with a Cosmos SDK module. This vulnerability is fixed in 18.0.0.\n\n" + }, + { + "lang": "es", + "value": "Evmos es el centro de m\u00e1quinas virtuales Ethereum (EVM) en Cosmos Network. Las comprobaciones preliminares de las acciones calculadas por las cuentas de recuperaci\u00f3n de derechos se realizan en el gestor ante. El n\u00facleo de Evmos implementa dos controladores de ante diferentes: uno para transacciones Cosmos y otro para transacciones Ethereum. Las comprobaciones realizadas en las dos implementaciones son diferentes. La vulnerabilidad descubierta permiti\u00f3 que una cuenta de recuperaci\u00f3n eludiera las comprobaciones del ante handler de Cosmos enviando una transacci\u00f3n de Ethereum dirigida a una precompilaci\u00f3n utilizada para interactuar con un m\u00f3dulo SDK de Cosmos. Esta vulnerabilidad se solucion\u00f3 en 18.0.0." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-371xx/CVE-2024-37159.json b/CVE-2024/CVE-2024-371xx/CVE-2024-37159.json index 75b03fdcba2..e33bc666660 100644 --- a/CVE-2024/CVE-2024-371xx/CVE-2024-37159.json +++ b/CVE-2024/CVE-2024-371xx/CVE-2024-37159.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37159", "sourceIdentifier": "security-advisories@github.com", "published": "2024-06-17T14:15:10.693", - "lastModified": "2024-06-17T14:15:10.693", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Evmos is the Ethereum Virtual Machine (EVM) Hub on the Cosmos Network. This vulnerability allowed a user to create a validator using vested tokens to deposit the self-bond. This vulnerability is fixed in 18.0.0." + }, + { + "lang": "es", + "value": "Evmos es el centro de m\u00e1quinas virtuales Ethereum (EVM) en Cosmos Network. Esta vulnerabilidad permiti\u00f3 a un usuario crear un validador utilizando tokens adquiridos para depositar el autobono. Esta vulnerabilidad se solucion\u00f3 en 18.0.0." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-373xx/CVE-2024-37305.json b/CVE-2024/CVE-2024-373xx/CVE-2024-37305.json index 96d194ba3fa..48847978c33 100644 --- a/CVE-2024/CVE-2024-373xx/CVE-2024-37305.json +++ b/CVE-2024/CVE-2024-373xx/CVE-2024-37305.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37305", "sourceIdentifier": "security-advisories@github.com", "published": "2024-06-17T20:15:12.880", - "lastModified": "2024-06-17T20:15:12.880", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "oqs-provider is a provider for the OpenSSL 3 cryptography library that adds support for post-quantum cryptography in TLS, X.509, and S/MIME using post-quantum algorithms from liboqs. Flaws have been identified in the way oqs-provider handles lengths decoded with DECODE_UINT32 at the start of serialized hybrid (traditional + post-quantum) keys and signatures. Unchecked length values are later used for memory reads and writes; malformed input can lead to crashes or information leakage. Handling of plain/non-hybrid PQ key operation is not affected. This issue has been patched in in v0.6.1. All users are advised to upgrade. There are no workarounds for this issue." + }, + { + "lang": "es", + "value": "oqs-provider es un proveedor de la librer\u00eda de criptograf\u00eda OpenSSL 3 que agrega soporte para criptograf\u00eda poscu\u00e1ntica en TLS, X.509 y S/MIME utilizando algoritmos poscu\u00e1nticos de liboqs. Se han identificado fallas en la forma en que oqs-provider maneja las longitudes decodificadas con DECODE_UINT32 al inicio de firmas y claves h\u00edbridas serializadas (tradicionales + poscu\u00e1nticas). Los valores de longitud no verificados se utilizan posteriormente para lecturas y escrituras de memoria; La entrada mal formada puede provocar fallas o fugas de informaci\u00f3n. El manejo de la operaci\u00f3n de clave PQ simple/no h\u00edbrida no se ve afectado. Este problema se solucion\u00f3 en la versi\u00f3n 0.6.1. Se recomienda a todos los usuarios que actualicen. No existen workarounds para este problema." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-373xx/CVE-2024-37387.json b/CVE-2024/CVE-2024-373xx/CVE-2024-37387.json index edd50c913a0..2ccf6a16fbc 100644 --- a/CVE-2024/CVE-2024-373xx/CVE-2024-37387.json +++ b/CVE-2024/CVE-2024-373xx/CVE-2024-37387.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37387", "sourceIdentifier": "vultures@jpcert.or.jp", "published": "2024-06-19T07:15:46.647", - "lastModified": "2024-06-19T07:15:46.647", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Use of potentially dangerous function issue exists in Ricoh Streamline NX PC Client. If this vulnerability is exploited, files in the PC where the product is installed may be altered." + }, + { + "lang": "es", + "value": "Existe un problema de uso de funciones potencialmente peligrosas en Ricoh Streamline NX PC Client. Si se aprovecha esta vulnerabilidad, es posible que se modifiquen los archivos del PC donde est\u00e1 instalado el producto." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-376xx/CVE-2024-37619.json b/CVE-2024/CVE-2024-376xx/CVE-2024-37619.json index b40294b7a1d..55764ccd57b 100644 --- a/CVE-2024/CVE-2024-376xx/CVE-2024-37619.json +++ b/CVE-2024/CVE-2024-376xx/CVE-2024-37619.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37619", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T14:15:10.943", - "lastModified": "2024-06-17T14:15:10.943", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "StrongShop v1.0 was discovered to contain a reflected cross-site scripting (XSS) vulnerability via the spec_group_id parameter at /spec/index.blade.php." + }, + { + "lang": "es", + "value": "Se descubri\u00f3 que StrongShop v1.0 conten\u00eda una vulnerabilidad de cross site scripting (XSS) reflejado a trav\u00e9s del par\u00e1metro spec_group_id en /spec/index.blade.php." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-376xx/CVE-2024-37620.json b/CVE-2024/CVE-2024-376xx/CVE-2024-37620.json index be61c39b68a..80ac8540548 100644 --- a/CVE-2024/CVE-2024-376xx/CVE-2024-37620.json +++ b/CVE-2024/CVE-2024-376xx/CVE-2024-37620.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37620", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T14:15:11.047", - "lastModified": "2024-06-17T14:15:11.047", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "PHPVOD v4.0 was discovered to contain a reflected cross-site scripting (XSS) vulnerability via the id parameter at /view/admin/view.php." + }, + { + "lang": "es", + "value": "Se descubri\u00f3 que PHPVOD v4.0 conten\u00eda una vulnerabilidad de cross site scripting (XSS) reflejado a trav\u00e9s del par\u00e1metro id en /view/admin/view.php." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-376xx/CVE-2024-37621.json b/CVE-2024/CVE-2024-376xx/CVE-2024-37621.json index 3c978cf701c..57b6ad84e03 100644 --- a/CVE-2024/CVE-2024-376xx/CVE-2024-37621.json +++ b/CVE-2024/CVE-2024-376xx/CVE-2024-37621.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37621", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T14:15:11.153", - "lastModified": "2024-06-17T14:15:11.153", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "StrongShop v1.0 was discovered to contain a Server-Side Template Injection (SSTI) vulnerability via the component /shippingOptionConfig/index.blade.php." + }, + { + "lang": "es", + "value": "Se descubri\u00f3 que StrongShop v1.0 conten\u00eda una vulnerabilidad de inyecci\u00f3n de plantilla del lado del servidor (SSTI) a trav\u00e9s del componente /shippingOptionConfig/index.blade.php." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-376xx/CVE-2024-37622.json b/CVE-2024/CVE-2024-376xx/CVE-2024-37622.json index ed16a1950a2..e30beb88bcd 100644 --- a/CVE-2024/CVE-2024-376xx/CVE-2024-37622.json +++ b/CVE-2024/CVE-2024-376xx/CVE-2024-37622.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37622", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T14:15:11.480", - "lastModified": "2024-06-17T14:15:11.480", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Xinhu RockOA v2.6.3 was discovered to contain a reflected cross-site scripting (XSS) vulnerability via the num parameter at /flow/flow.php." + }, + { + "lang": "es", + "value": "Se descubri\u00f3 que Xinhu RockOA v2.6.3 contiene una vulnerabilidad de cross site scripting (XSS) reflejado a trav\u00e9s del par\u00e1metro num en /flow/flow.php." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-376xx/CVE-2024-37623.json b/CVE-2024/CVE-2024-376xx/CVE-2024-37623.json index b517d0c3237..81a17c843b5 100644 --- a/CVE-2024/CVE-2024-376xx/CVE-2024-37623.json +++ b/CVE-2024/CVE-2024-376xx/CVE-2024-37623.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37623", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T14:15:11.580", - "lastModified": "2024-06-17T14:15:11.580", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Xinhu RockOA v2.6.3 was discovered to contain a reflected cross-site scripting (XSS) vulnerability via the /kaoqin/tpl_kaoqin_locationchange.html component." + }, + { + "lang": "es", + "value": "Se descubri\u00f3 que Xinhu RockOA v2.6.3 contiene una vulnerabilidad de cross site scripting (XSS) reflejado a trav\u00e9s del componente /kaoqin/tpl_kaoqin_locationchange.html." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-376xx/CVE-2024-37624.json b/CVE-2024/CVE-2024-376xx/CVE-2024-37624.json index 781553a62e2..124a348bf10 100644 --- a/CVE-2024/CVE-2024-376xx/CVE-2024-37624.json +++ b/CVE-2024/CVE-2024-376xx/CVE-2024-37624.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37624", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T14:15:11.680", - "lastModified": "2024-06-17T14:15:11.680", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Xinhu RockOA v2.6.3 was discovered to contain a reflected cross-site scripting (XSS) vulnerability via the /chajian/inputChajian.php. component." + }, + { + "lang": "es", + "value": "Se descubri\u00f3 que Xinhu RockOA v2.6.3 conten\u00eda una vulnerabilidad de cross site scripting (XSS) reflejado a trav\u00e9s de /chajian/inputChajian.php. componente." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-376xx/CVE-2024-37625.json b/CVE-2024/CVE-2024-376xx/CVE-2024-37625.json index 4a0a1d7ea56..f393b00b8d9 100644 --- a/CVE-2024/CVE-2024-376xx/CVE-2024-37625.json +++ b/CVE-2024/CVE-2024-376xx/CVE-2024-37625.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37625", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T14:15:11.790", - "lastModified": "2024-06-17T14:15:11.790", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "zhimengzhe iBarn v1.5 was discovered to contain a reflected cross-site scripting (XSS) vulnerability via the $search parameter at /index.php." + }, + { + "lang": "es", + "value": "Se descubri\u00f3 que zhimengzhe iBarn v1.5 conten\u00eda una vulnerabilidad de cross site scripting (XSS) reflejado a trav\u00e9s del par\u00e1metro $search en /index.php." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-376xx/CVE-2024-37661.json b/CVE-2024/CVE-2024-376xx/CVE-2024-37661.json index 2c02c8d0942..c04b821dfff 100644 --- a/CVE-2024/CVE-2024-376xx/CVE-2024-37661.json +++ b/CVE-2024/CVE-2024-376xx/CVE-2024-37661.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37661", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T18:15:17.463", - "lastModified": "2024-06-17T18:15:17.463", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "TP-LINK TL-7DR5130 v1.0.23 is vulnerable to forged ICMP redirect message attacks. An attacker in the same WLAN as the victim can hijack the traffic between the victim and any remote server by sending out forged ICMP redirect messages." + }, + { + "lang": "es", + "value": "TP-LINK TL-7DR5130 v1.0.23 es vulnerable a ataques de mensajes de redireccionamiento ICMP falsificados. Un atacante en la misma WLAN que la v\u00edctima puede secuestrar el tr\u00e1fico entre la v\u00edctima y cualquier servidor remoto enviando mensajes de redireccionamiento ICMP falsificados." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-376xx/CVE-2024-37662.json b/CVE-2024/CVE-2024-376xx/CVE-2024-37662.json index 12e4bdd4a3a..937d6ddb1e3 100644 --- a/CVE-2024/CVE-2024-376xx/CVE-2024-37662.json +++ b/CVE-2024/CVE-2024-376xx/CVE-2024-37662.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37662", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T18:15:17.560", - "lastModified": "2024-06-17T18:15:17.560", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "TP-LINK TL-7DR5130 v1.0.23 is vulnerable to TCP DoS or hijacking attacks. An attacker in the same WLAN as the victim can disconnect or hijack the traffic between the victim and any remote server by sending out forged TCP RST messages to evict NAT mappings in the router." + }, + { + "lang": "es", + "value": "TP-LINK TL-7DR5130 v1.0.23 es vulnerable a TCP DoS o ataques de secuestro. Un atacante en la misma WLAN que la v\u00edctima puede desconectar o secuestrar el tr\u00e1fico entre la v\u00edctima y cualquier servidor remoto enviando mensajes TCP RST falsificados para desalojar las asignaciones NAT en el enrutador." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-376xx/CVE-2024-37663.json b/CVE-2024/CVE-2024-376xx/CVE-2024-37663.json index 50c6bb37eb3..7ea541e6cf9 100644 --- a/CVE-2024/CVE-2024-376xx/CVE-2024-37663.json +++ b/CVE-2024/CVE-2024-376xx/CVE-2024-37663.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37663", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T18:15:17.653", - "lastModified": "2024-06-17T18:15:17.653", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Redmi router RB03 v1.0.57 is vulnerable to forged ICMP redirect message attacks. An attacker in the same WLAN as the victim can hijack the traffic between the victim and any remote server by sending out forged ICMP redirect messages." + }, + { + "lang": "es", + "value": "El enrutador Redmi RB03 v1.0.57 es vulnerable a ataques de mensajes de redireccionamiento ICMP falsificados. Un atacante en la misma WLAN que la v\u00edctima puede secuestrar el tr\u00e1fico entre la v\u00edctima y cualquier servidor remoto enviando mensajes de redireccionamiento ICMP falsificados." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-376xx/CVE-2024-37664.json b/CVE-2024/CVE-2024-376xx/CVE-2024-37664.json index 79bf4572f88..3972152701a 100644 --- a/CVE-2024/CVE-2024-376xx/CVE-2024-37664.json +++ b/CVE-2024/CVE-2024-376xx/CVE-2024-37664.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37664", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T18:15:17.743", - "lastModified": "2024-06-17T18:15:17.743", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Redmi router RB03 v1.0.57 is vulnerable to TCP DoS or hijacking attacks. An attacker in the same WLAN as the victim can disconnect or hijack the traffic between the victim and any remote server by sending out forged TCP RST messages to evict NAT mappings in the router." + }, + { + "lang": "es", + "value": "El enrutador Redmi RB03 v1.0.57 es vulnerable a TCP DoS o ataques de secuestro. Un atacante en la misma WLAN que la v\u00edctima puede desconectar o secuestrar el tr\u00e1fico entre la v\u00edctima y cualquier servidor remoto enviando mensajes TCP RST falsificados para desalojar las asignaciones NAT en el enrutador." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-377xx/CVE-2024-37791.json b/CVE-2024/CVE-2024-377xx/CVE-2024-37791.json index ed79fb0126c..96e39e6be52 100644 --- a/CVE-2024/CVE-2024-377xx/CVE-2024-37791.json +++ b/CVE-2024/CVE-2024-377xx/CVE-2024-37791.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37791", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-18T19:16:00.120", - "lastModified": "2024-06-18T19:16:00.120", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "DuxCMS3 v3.1.3 was discovered to contain a SQL injection vulnerability via the keyword parameter at /article/Content/index?class_id." + }, + { + "lang": "es", + "value": "Se descubri\u00f3 que DuxCMS3 v3.1.3 conten\u00eda una vulnerabilidad de inyecci\u00f3n SQL a trav\u00e9s del par\u00e1metro de palabra clave en /article/Content/index?class_id." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-377xx/CVE-2024-37794.json b/CVE-2024/CVE-2024-377xx/CVE-2024-37794.json index 93ff7a68ace..b2d5525b388 100644 --- a/CVE-2024/CVE-2024-377xx/CVE-2024-37794.json +++ b/CVE-2024/CVE-2024-377xx/CVE-2024-37794.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37794", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T18:15:17.853", - "lastModified": "2024-06-17T18:15:17.853", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Improper input validation in CVC5 Solver v1.1.3 allows attackers to cause a Denial of Service (DoS) via a crafted SMT2 input file." + }, + { + "lang": "es", + "value": "La validaci\u00f3n de entrada incorrecta en CVC5 Solver v1.1.3 permite a los atacantes provocar una denegaci\u00f3n de servicio (DoS) a trav\u00e9s de un archivo de entrada SMT2 manipulado." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-377xx/CVE-2024-37795.json b/CVE-2024/CVE-2024-377xx/CVE-2024-37795.json index 01fc2b9197e..4dac3262b47 100644 --- a/CVE-2024/CVE-2024-377xx/CVE-2024-37795.json +++ b/CVE-2024/CVE-2024-377xx/CVE-2024-37795.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37795", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T18:15:17.953", - "lastModified": "2024-06-17T18:15:17.953", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A segmentation fault in CVC5 Solver v1.1.3 allows attackers to cause a Denial of Service (DoS) via a crafted SMT-LIB input file containing the `set-logic` command with specific formatting errors." + }, + { + "lang": "es", + "value": "Una falla de segmentaci\u00f3n en CVC5 Solver v1.1.3 permite a los atacantes provocar una denegaci\u00f3n de servicio (DoS) a trav\u00e9s de un archivo de entrada SMT-LIB manipulado que contiene el comando `set-logic` con errores de formato espec\u00edficos." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-377xx/CVE-2024-37798.json b/CVE-2024/CVE-2024-377xx/CVE-2024-37798.json index da5bffe27e2..a945c4af37a 100644 --- a/CVE-2024/CVE-2024-377xx/CVE-2024-37798.json +++ b/CVE-2024/CVE-2024-377xx/CVE-2024-37798.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37798", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T21:15:51.180", - "lastModified": "2024-06-17T21:15:51.180", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Cross-site scripting (XSS) vulnerability in search-appointment.php in the Admin Panel in Phpgurukul Beauty Parlour Management System 1.0 allows remote attackers to inject arbitrary web script or HTML via the search input field." + }, + { + "lang": "es", + "value": "Vulnerabilidad de Cross-site scripting (XSS) en search-appointment.php en el Panel de administraci\u00f3n de Phpgurukul Beauty Parlor Management System 1.0 permite a atacantes remotos inyectar scripts web o HTML arbitrarios a trav\u00e9s del campo de entrada de b\u00fasqueda." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-377xx/CVE-2024-37799.json b/CVE-2024/CVE-2024-377xx/CVE-2024-37799.json index 5384b21ce3f..2f7eee255f0 100644 --- a/CVE-2024/CVE-2024-377xx/CVE-2024-37799.json +++ b/CVE-2024/CVE-2024-377xx/CVE-2024-37799.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37799", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-18T17:15:51.910", - "lastModified": "2024-06-18T17:15:51.910", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "CodeProjects Restaurant Reservation System v1.0 was discovered to contain a SQL injection vulnerability via the reserv_id parameter at view_reservations.php." + }, + { + "lang": "es", + "value": "Se descubri\u00f3 que CodeProjects Restaurant Reservation System v1.0 contiene una vulnerabilidad de inyecci\u00f3n SQL a trav\u00e9s del par\u00e1metro reserv_id en view_reservations.php." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-378xx/CVE-2024-37800.json b/CVE-2024/CVE-2024-378xx/CVE-2024-37800.json index 49b3f74fbba..f0ff105ecc1 100644 --- a/CVE-2024/CVE-2024-378xx/CVE-2024-37800.json +++ b/CVE-2024/CVE-2024-378xx/CVE-2024-37800.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37800", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-18T17:15:52.027", - "lastModified": "2024-06-18T17:15:52.027", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "CodeProjects Restaurant Reservation System v1.0 was discovered to contain a reflected cross-site scripting (XSS) vulnerability via the Date parameter at index.php." + }, + { + "lang": "es", + "value": "Se descubri\u00f3 que CodeProjects Restaurant Reservation System v1.0 contiene una vulnerabilidad de cross-site scripting (XSS) reflejado a trav\u00e9s del par\u00e1metro Fecha en index.php." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-378xx/CVE-2024-37802.json b/CVE-2024/CVE-2024-378xx/CVE-2024-37802.json index 9dcef435234..00d88bcf62e 100644 --- a/CVE-2024/CVE-2024-378xx/CVE-2024-37802.json +++ b/CVE-2024/CVE-2024-378xx/CVE-2024-37802.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37802", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-18T17:15:52.133", - "lastModified": "2024-06-18T17:15:52.133", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "CodeProjects Health Care hospital Management System v1.0 was discovered to contain a SQL injection vulnerability in the Patient Info module via the searvalu parameter." + }, + { + "lang": "es", + "value": "Se descubri\u00f3 que CodeProjects Health Care hospital Management System v1.0 conten\u00eda una vulnerabilidad de inyecci\u00f3n SQL en el m\u00f3dulo de informaci\u00f3n del paciente a trav\u00e9s del par\u00e1metro servalu." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-378xx/CVE-2024-37803.json b/CVE-2024/CVE-2024-378xx/CVE-2024-37803.json index 4a80acb8afd..efcc18dbd4a 100644 --- a/CVE-2024/CVE-2024-378xx/CVE-2024-37803.json +++ b/CVE-2024/CVE-2024-378xx/CVE-2024-37803.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37803", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-18T17:15:52.237", - "lastModified": "2024-06-18T17:15:52.237", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "Multiple stored cross-site scripting (XSS) vulnerabilities in CodeProjects Health Care hospital Management System v1.0 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the fname and lname parameters under the Staff Info page." + }, + { + "lang": "es", + "value": "M\u00faltiples vulnerabilidades de cross-site scripting (XSS) almacenado en CodeProjects Health Care hospital Management System v1.0 permiten a los atacantes ejecutar scripts web o HTML arbitrarios a trav\u00e9s de un payload manipulado inyectado en los par\u00e1metros fname y lname en la p\u00e1gina de informaci\u00f3n del personal." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-378xx/CVE-2024-37821.json b/CVE-2024/CVE-2024-378xx/CVE-2024-37821.json index 96d73e6b99c..961919e9d5c 100644 --- a/CVE-2024/CVE-2024-378xx/CVE-2024-37821.json +++ b/CVE-2024/CVE-2024-378xx/CVE-2024-37821.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37821", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-18T20:15:13.640", - "lastModified": "2024-06-18T20:15:13.640", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "An arbitrary file upload vulnerability in the Upload Template function of Dolibarr ERP CRM up to v19.0.1 allows attackers to execute arbitrary code via uploading a crafted .SQL file." + }, + { + "lang": "es", + "value": "Una vulnerabilidad de carga de archivos arbitrarios en la funci\u00f3n Cargar plantilla de Dolibarr ERP CRM hasta v19.0.1 permite a los atacantes ejecutar c\u00f3digo arbitrario cargando un archivo .SQL manipulado." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-378xx/CVE-2024-37828.json b/CVE-2024/CVE-2024-378xx/CVE-2024-37828.json index 43dd76a4bb1..a7b107f6cc2 100644 --- a/CVE-2024/CVE-2024-378xx/CVE-2024-37828.json +++ b/CVE-2024/CVE-2024-378xx/CVE-2024-37828.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37828", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T21:15:51.280", - "lastModified": "2024-06-17T21:15:51.280", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A stored cross-site scripting (XSS) in Vermeg Agile Reporter v23.2.1 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the Message field under the Set Broadcast Message module." + }, + { + "lang": "es", + "value": "Cross-site scripting (XSS) almacenado en Vermeg Agile Reporter v23.2.1 permite a los atacantes ejecutar scripts web o HTML arbitrarios a trav\u00e9s de un payload manipulado inyectado en el campo Mensaje bajo el m\u00f3dulo Establecer mensaje de difusi\u00f3n." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-378xx/CVE-2024-37840.json b/CVE-2024/CVE-2024-378xx/CVE-2024-37840.json index e8abc0f1172..7233e576bd0 100644 --- a/CVE-2024/CVE-2024-378xx/CVE-2024-37840.json +++ b/CVE-2024/CVE-2024-378xx/CVE-2024-37840.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37840", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T19:15:58.470", - "lastModified": "2024-06-17T19:15:58.470", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "SQL injection vulnerability in processscore.php in Itsourcecode Learning Management System Project In PHP With Source Code v1.0 allows remote attackers to execute arbitrary SQL commands via the LessonID parameter." + }, + { + "lang": "es", + "value": "Vulnerabilidad de inyecci\u00f3n SQL en Processscore.php en Itsourcecode Learning Management System Project In PHP With Source Code v1.0 permite a atacantes remotos ejecutar comandos SQL de su elecci\u00f3n a trav\u00e9s del par\u00e1metro LessonID." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-378xx/CVE-2024-37848.json b/CVE-2024/CVE-2024-378xx/CVE-2024-37848.json index 0dd29c702fb..dd39fde04e2 100644 --- a/CVE-2024/CVE-2024-378xx/CVE-2024-37848.json +++ b/CVE-2024/CVE-2024-378xx/CVE-2024-37848.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37848", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T14:15:11.890", - "lastModified": "2024-06-17T14:15:11.890", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "SQL Injection vulnerability in Online-Bookstore-Project-In-PHP v1.0 allows a local attacker to execute arbitrary code via the admin_delete.php component." + }, + { + "lang": "es", + "value": "Vulnerabilidad de inyecci\u00f3n SQL en Online-Bookstore-Project-In-PHP v1.0 permite a un atacante local ejecutar c\u00f3digo arbitrario a trav\u00e9s del componente admin_delete.php." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-378xx/CVE-2024-37881.json b/CVE-2024/CVE-2024-378xx/CVE-2024-37881.json index 81522e483bd..cc333b37a1e 100644 --- a/CVE-2024/CVE-2024-378xx/CVE-2024-37881.json +++ b/CVE-2024/CVE-2024-378xx/CVE-2024-37881.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37881", "sourceIdentifier": "vultures@jpcert.or.jp", "published": "2024-06-19T07:15:46.743", - "lastModified": "2024-06-19T07:15:46.743", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "SiteGuard WP Plugin provides a functionality to customize the path to the login page wp-login.php and implements a measure to avoid redirection from other URLs. However, SiteGuard WP Plugin versions prior to 1.7.7 missed to implement a measure to avoid redirection from wp-register.php. As a result, the customized path to the login page may be exposed." + }, + { + "lang": "es", + "value": "SiteGuard WP Plugin proporciona una funcionalidad para personalizar la ruta a la p\u00e1gina de inicio de sesi\u00f3n wp-login.php e implementa una medida para evitar la redirecci\u00f3n desde otras URL. Sin embargo, las versiones del complemento SiteGuard WP anteriores a la 1.7.7 no implementaron una medida para evitar la redirecci\u00f3n desde wp-register.php. Como resultado, la ruta personalizada a la p\u00e1gina de inicio de sesi\u00f3n puede quedar expuesta." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-378xx/CVE-2024-37890.json b/CVE-2024/CVE-2024-378xx/CVE-2024-37890.json index e130a210a83..92a4829e12c 100644 --- a/CVE-2024/CVE-2024-378xx/CVE-2024-37890.json +++ b/CVE-2024/CVE-2024-378xx/CVE-2024-37890.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37890", "sourceIdentifier": "security-advisories@github.com", "published": "2024-06-17T20:15:13.203", - "lastModified": "2024-06-17T20:15:13.203", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "ws is an open source WebSocket client and server for Node.js. A request with a number of headers exceeding theserver.maxHeadersCount threshold could be used to crash a ws server. The vulnerability was fixed in ws@8.17.1 (e55e510) and backported to ws@7.5.10 (22c2876), ws@6.2.3 (eeb76d3), and ws@5.2.4 (4abd8f6). In vulnerable versions of ws, the issue can be mitigated in the following ways: 1. Reduce the maximum allowed length of the request headers using the --max-http-header-size=size and/or the maxHeaderSize options so that no more headers than the server.maxHeadersCount limit can be sent. 2. Set server.maxHeadersCount to 0 so that no limit is applied." + }, + { + "lang": "es", + "value": "ws es un cliente y servidor WebSocket de c\u00f3digo abierto para Node.js. Una solicitud con una cantidad de encabezados que exceda el umbral server.maxHeadersCount podr\u00eda usarse para bloquear un servidor ws. La vulnerabilidad se solucion\u00f3 en ws@8.17.1 (e55e510) y se actualiz\u00f3 a ws@7.5.10 (22c2876), ws@6.2.3 (eeb76d3) y ws@5.2.4 (4abd8f6). En versiones vulnerables de ws, el problema se puede mitigar de las siguientes maneras: 1. Reduzca la longitud m\u00e1xima permitida de los encabezados de solicitud usando las opciones --max-http-header-size=size y/o maxHeaderSize para que no haya m\u00e1s Se pueden enviar encabezados superiores al l\u00edmite server.maxHeadersCount. 2. Establezca server.maxHeadersCount en 0 para que no se aplique ning\u00fan l\u00edmite." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-378xx/CVE-2024-37891.json b/CVE-2024/CVE-2024-378xx/CVE-2024-37891.json index 19f04554987..992cd445c97 100644 --- a/CVE-2024/CVE-2024-378xx/CVE-2024-37891.json +++ b/CVE-2024/CVE-2024-378xx/CVE-2024-37891.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37891", "sourceIdentifier": "security-advisories@github.com", "published": "2024-06-17T20:15:13.450", - "lastModified": "2024-06-17T20:15:13.450", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": " urllib3 is a user-friendly HTTP client library for Python. When using urllib3's proxy support with `ProxyManager`, the `Proxy-Authorization` header is only sent to the configured proxy, as expected. However, when sending HTTP requests *without* using urllib3's proxy support, it's possible to accidentally configure the `Proxy-Authorization` header even though it won't have any effect as the request is not using a forwarding proxy or a tunneling proxy. In those cases, urllib3 doesn't treat the `Proxy-Authorization` HTTP header as one carrying authentication material and thus doesn't strip the header on cross-origin redirects. Because this is a highly unlikely scenario, we believe the severity of this vulnerability is low for almost all users. Out of an abundance of caution urllib3 will automatically strip the `Proxy-Authorization` header during cross-origin redirects to avoid the small chance that users are doing this on accident. Users should use urllib3's proxy support or disable automatic redirects to achieve safe processing of the `Proxy-Authorization` header, but we still decided to strip the header by default in order to further protect users who aren't using the correct approach. We believe the number of usages affected by this advisory is low. It requires all of the following to be true to be exploited: 1. Setting the `Proxy-Authorization` header without using urllib3's built-in proxy support. 2. Not disabling HTTP redirects. 3. Either not using an HTTPS origin server or for the proxy or target origin to redirect to a malicious origin. Users are advised to update to either version 1.26.19 or version 2.2.2. Users unable to upgrade may use the `Proxy-Authorization` header with urllib3's `ProxyManager`, disable HTTP redirects using `redirects=False` when sending requests, or not user the `Proxy-Authorization` header as mitigations." + }, + { + "lang": "es", + "value": "urllib3 es una librer\u00eda cliente HTTP f\u00e1cil de usar para Python. Cuando se utiliza el soporte de proxy de urllib3 con `ProxyManager`, el encabezado `Proxy-Authorization` solo se env\u00eda al proxy configurado, como se esperaba. Sin embargo, al enviar solicitudes HTTP *sin* utilizar el soporte de proxy de urllib3, es posible configurar accidentalmente el encabezado `Proxy-Authorization` aunque no tendr\u00e1 ning\u00fan efecto ya que la solicitud no utiliza un proxy de reenv\u00edo o un proxy de t\u00fanel. En esos casos, urllib3 no trata el encabezado HTTP \"Proxy-Authorization\" como si llevara material de autenticaci\u00f3n y, por lo tanto, no elimina el encabezado en redirecciones de origen cruzado. Dado que se trata de un escenario muy improbable, creemos que la gravedad de esta vulnerabilidad es baja para casi todos los usuarios. Por precauci\u00f3n, urllib3 eliminar\u00e1 autom\u00e1ticamente el encabezado \"Proxy-Authorization\" durante las redirecciones entre or\u00edgenes para evitar la peque\u00f1a posibilidad de que los usuarios hagan esto por accidente. Los usuarios deben usar el soporte de proxy de urllib3 o desactivar las redirecciones autom\u00e1ticas para lograr un procesamiento seguro del encabezado `Proxy-Authorization`, pero aun as\u00ed decidimos eliminar el encabezado de forma predeterminada para proteger a\u00fan m\u00e1s a los usuarios que no utilizan el enfoque correcto. Creemos que la cantidad de usos afectados por este aviso es baja. Requiere que todo lo siguiente sea cierto para ser explotado: 1. Configurar el encabezado `Proxy-Authorization` sin utilizar el soporte de proxy integrado de urllib3. 2. No deshabilitar las redirecciones HTTP. 3. Ya sea no utilizar un servidor de origen HTTPS o que el proxy o el origen de destino redirija a un origen malicioso. Se recomienda a los usuarios que actualicen a la versi\u00f3n 1.26.19 o a la versi\u00f3n 2.2.2. Los usuarios que no puedan actualizar pueden usar el encabezado `Proxy-Authorization` con `ProxyManager` de urllib3, deshabilitar las redirecciones HTTP usando `redirects=False` al enviar solicitudes o no usar el encabezado `Proxy-Authorization` como mitigaci\u00f3n." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-378xx/CVE-2024-37893.json b/CVE-2024/CVE-2024-378xx/CVE-2024-37893.json index e1391469cac..f0cf62164ee 100644 --- a/CVE-2024/CVE-2024-378xx/CVE-2024-37893.json +++ b/CVE-2024/CVE-2024-378xx/CVE-2024-37893.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37893", "sourceIdentifier": "security-advisories@github.com", "published": "2024-06-17T20:15:13.700", - "lastModified": "2024-06-17T20:15:13.700", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Firefly III is a free and open source personal finance manager. In affected versions an MFA bypass in the Firefly III OAuth flow may allow malicious users to bypass the MFA-check. This allows malicious users to use password spraying to gain access to Firefly III data using passwords stolen from other sources. As OAuth applications are easily enumerable using an incrementing id, an attacker could try sign an OAuth application up to a users profile quite easily if they have created one. The attacker would also need to know the victims username and password. This problem has been patched in Firefly III v6.1.17 and up. Users are advised to upgrade. Users unable to upgrade should Use a unique password for their Firefly III instance and store their password securely, i.e. in a password manager." + }, + { + "lang": "es", + "value": "Firefly III es un administrador de finanzas personales gratuito y de c\u00f3digo abierto. En las versiones afectadas, una omisi\u00f3n de MFA en el flujo OAuth del Firefly III puede permitir a usuarios malintencionados omitir la verificaci\u00f3n de MFA. Esto permite a usuarios malintencionados utilizar la pulverizaci\u00f3n de contrase\u00f1as para obtener acceso a los datos de Firefly III utilizando contrase\u00f1as robadas de otras fuentes. Como las aplicaciones OAuth se pueden enumerar f\u00e1cilmente utilizando una identificaci\u00f3n incremental, un atacante podr\u00eda intentar registrar una aplicaci\u00f3n OAuth en el perfil de un usuario con bastante facilidad si ha creado uno. El atacante tambi\u00e9n necesitar\u00eda saber el nombre de usuario y la contrase\u00f1a de la v\u00edctima. Este problema se solucion\u00f3 en Firefly III v6.1.17 y versiones posteriores. Se recomienda a los usuarios que actualicen. Los usuarios que no puedan actualizar deben utilizar una contrase\u00f1a \u00fanica para su instancia de Firefly III y almacenarla de forma segura, es decir, en un administrador de contrase\u00f1as." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-378xx/CVE-2024-37895.json b/CVE-2024/CVE-2024-378xx/CVE-2024-37895.json index 9f6b64b83f5..cac41d63fe0 100644 --- a/CVE-2024/CVE-2024-378xx/CVE-2024-37895.json +++ b/CVE-2024/CVE-2024-378xx/CVE-2024-37895.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37895", "sourceIdentifier": "security-advisories@github.com", "published": "2024-06-17T20:15:13.970", - "lastModified": "2024-06-17T20:15:13.970", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Lobe Chat is an open-source LLMs/AI chat framework. In affected versions if an attacker can successfully authenticate through SSO/Access Code, they can obtain the real backend API Key by modifying the base URL to their own attack URL on the frontend and setting up a server-side request. This issue has been addressed in version 0.162.25. Users are advised to upgrade. There are no known workarounds for this vulnerability." + }, + { + "lang": "es", + "value": "Lobe Chat es un framework de chat de IA/LLM de c\u00f3digo abierto. En las versiones afectadas, si un atacante puede autenticarse exitosamente a trav\u00e9s de SSO/C\u00f3digo de acceso, puede obtener la clave API de backend real modificando la URL base a su propia URL de ataque en la interfaz y configurando una solicitud del lado del servidor. Este problema se solucion\u00f3 en la versi\u00f3n 0.162.25. Se recomienda a los usuarios que actualicen. No se conocen workarounds para esta vulnerabilidad." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-378xx/CVE-2024-37896.json b/CVE-2024/CVE-2024-378xx/CVE-2024-37896.json index 7c27fd7c2e5..c0dd0d3ac68 100644 --- a/CVE-2024/CVE-2024-378xx/CVE-2024-37896.json +++ b/CVE-2024/CVE-2024-378xx/CVE-2024-37896.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37896", "sourceIdentifier": "security-advisories@github.com", "published": "2024-06-17T20:15:14.213", - "lastModified": "2024-06-17T20:15:14.213", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Gin-vue-admin is a backstage management system based on vue and gin. Gin-vue-admin <= v2.6.5 has SQL injection vulnerability. The SQL injection vulnerabilities occur when a web application allows users to input data into SQL queries without sufficiently validating or sanitizing the input. Failing to properly enforce restrictions on user input could mean that even a basic form input field can be used to inject arbitrary and potentially dangerous SQL commands. This could lead to unauthorized access to the database, data leakage, data manipulation, or even complete compromise of the database server. This vulnerability has been addressed in commit `53d033821` which has been included in release version 2.6.6. Users are advised to upgrade. There are no known workarounds for this vulnerability." + }, + { + "lang": "es", + "value": "Gin-vue-admin es un sistema de gesti\u00f3n detr\u00e1s de escena basado en vue y gin. Gin-vue-admin <= v2.6.5 tiene una vulnerabilidad de inyecci\u00f3n SQL. Las vulnerabilidades de inyecci\u00f3n SQL ocurren cuando una aplicaci\u00f3n web permite a los usuarios ingresar datos en consultas SQL sin validar o sanitizar suficientemente la entrada. No aplicar adecuadamente las restricciones a la entrada del usuario podr\u00eda significar que incluso un campo de entrada de formulario b\u00e1sico pueda usarse para inyectar comandos SQL arbitrarios y potencialmente peligrosos. Esto podr\u00eda provocar un acceso no autorizado a la base de datos, una fuga de datos, una manipulaci\u00f3n de datos o incluso un compromiso total del servidor de la base de datos. Esta vulnerabilidad se solucion\u00f3 en el commit `53d033821` que se incluy\u00f3 en la versi\u00f3n 2.6.6. Se recomienda a los usuarios que actualicen. No se conocen workarounds para esta vulnerabilidad." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-379xx/CVE-2024-37902.json b/CVE-2024/CVE-2024-379xx/CVE-2024-37902.json index 70a16826bd3..1ab4b6362c4 100644 --- a/CVE-2024/CVE-2024-379xx/CVE-2024-37902.json +++ b/CVE-2024/CVE-2024-379xx/CVE-2024-37902.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37902", "sourceIdentifier": "security-advisories@github.com", "published": "2024-06-17T20:15:14.463", - "lastModified": "2024-06-17T20:15:14.463", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "DeepJavaLibrary(DJL) is an Engine-Agnostic Deep Learning Framework in Java. DJL versions 0.1.0 through 0.27.0 do not prevent absolute path archived artifacts from inserting archived files directly into the system, overwriting system files. This is fixed in DJL 0.28.0 and patched in DJL Large Model Inference containers version 0.27.0. Users are advised to upgrade." + }, + { + "lang": "es", + "value": "DeepJavaLibrary (DJL) es un framework de aprendizaje profundo independiente del motor en Java. Las versiones de DJL 0.1.0 a 0.27.0 no impiden que los artefactos archivados de ruta absoluta inserten archivos archivados directamente en el sistema, sobrescribiendo los archivos del sistema. Esto se solucion\u00f3 en DJL 0.28.0 y se parche\u00f3 en los contenedores DJL Large Model Inference versi\u00f3n 0.27.0. Se recomienda a los usuarios que actualicen." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-379xx/CVE-2024-37904.json b/CVE-2024/CVE-2024-379xx/CVE-2024-37904.json index d33daeb0cfa..9dbf45f9f55 100644 --- a/CVE-2024/CVE-2024-379xx/CVE-2024-37904.json +++ b/CVE-2024/CVE-2024-379xx/CVE-2024-37904.json @@ -2,12 +2,16 @@ "id": "CVE-2024-37904", "sourceIdentifier": "security-advisories@github.com", "published": "2024-06-18T17:15:52.337", - "lastModified": "2024-06-18T17:15:52.337", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Minder is an open source Software Supply Chain Security Platform. Minder's Git provider is vulnerable to a denial of service from a maliciously configured GitHub repository. The Git provider clones users repositories using the `github.com/go-git/go-git/v5` library on lines `L55-L89`. The Git provider does the following on the lines `L56-L62`. First, it sets the `CloneOptions`, specifying the url, the depth etc. It then validates the options. It then sets up an in-memory filesystem, to which it clones and Finally, it clones the repository. The `(g *Git) Clone()` method is vulnerable to a DoS attack: A Minder user can instruct Minder to clone a large repository which will exhaust memory and crash the Minder server. The root cause of this vulnerability is a combination of the following conditions: 1. Users can control the Git URL which Minder clones, 2. Minder does not enforce a size limit to the repository, 3. Minder clones the entire repository into memory. This issue has been addressed in commit `7979b43` which has been included in release version v0.0.52. Users are advised to upgrade. There are no known workarounds for this vulnerability." + }, + { + "lang": "es", + "value": "Minder es una plataforma de seguridad de la cadena de suministro de software de c\u00f3digo abierto. El proveedor Git de Minder es vulnerable a una denegaci\u00f3n de servicio desde un repositorio GitHub configurado maliciosamente. El proveedor de Git clona los repositorios de los usuarios utilizando la librer\u00eda `github.com/go-git/go-git/v5` en las l\u00edneas `L55-L89`. El proveedor de Git hace lo siguiente en las l\u00edneas \"L56-L62\". Primero, establece `CloneOptions`, especificando la URL, la profundidad, etc. Luego valida las opciones. Luego configura un sistema de archivos en memoria, al cual clona y, finalmente, clona el repositorio. El m\u00e9todo `(g *Git) Clone()` es vulnerable a un ataque DoS: un usuario de Minder puede indicarle a Minder que clone un repositorio grande que agotar\u00e1 la memoria y bloquear\u00e1 el servidor de Minder. La causa principal de esta vulnerabilidad es una combinaci\u00f3n de las siguientes condiciones: 1. Los usuarios pueden controlar la URL de Git que Minder clona, 2. Minder no impone un l\u00edmite de tama\u00f1o al repositorio, 3. Minder clona todo el repositorio en la memoria. Este problema se solucion\u00f3 en el commit `7979b43` que se incluy\u00f3 en la versi\u00f3n v0.0.52. Se recomienda a los usuarios que actualicen. No se conocen workarounds para esta vulnerabilidad." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-382xx/CVE-2024-38273.json b/CVE-2024/CVE-2024-382xx/CVE-2024-38273.json index 7680cadeeda..4dc6c490140 100644 --- a/CVE-2024/CVE-2024-382xx/CVE-2024-38273.json +++ b/CVE-2024/CVE-2024-382xx/CVE-2024-38273.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38273", "sourceIdentifier": "patrick@puiterwijk.org", "published": "2024-06-18T20:15:13.740", - "lastModified": "2024-06-18T20:15:13.740", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Insufficient capability checks meant it was possible for users to gain access to BigBlueButton join URLs they did not have permission to access." + }, + { + "lang": "es", + "value": "Las comprobaciones de capacidad insuficientes significaron que era posible que los usuarios obtuvieran acceso a las URL de uni\u00f3n de BigBlueButton a las que no ten\u00edan permiso para acceder." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-382xx/CVE-2024-38274.json b/CVE-2024/CVE-2024-382xx/CVE-2024-38274.json index d0faace249d..65ee675aad5 100644 --- a/CVE-2024/CVE-2024-382xx/CVE-2024-38274.json +++ b/CVE-2024/CVE-2024-382xx/CVE-2024-38274.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38274", "sourceIdentifier": "patrick@puiterwijk.org", "published": "2024-06-18T20:15:13.860", - "lastModified": "2024-06-18T20:15:13.860", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Insufficient escaping of calendar event titles resulted in a stored XSS risk in the event deletion prompt." + }, + { + "lang": "es", + "value": "El escape insuficiente de los t\u00edtulos de los eventos del calendario result\u00f3 en un riesgo XSS almacenado en el mensaje de eliminaci\u00f3n del evento." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-382xx/CVE-2024-38275.json b/CVE-2024/CVE-2024-382xx/CVE-2024-38275.json index 92e40ed9ff5..704da001c68 100644 --- a/CVE-2024/CVE-2024-382xx/CVE-2024-38275.json +++ b/CVE-2024/CVE-2024-382xx/CVE-2024-38275.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38275", "sourceIdentifier": "patrick@puiterwijk.org", "published": "2024-06-18T20:15:13.970", - "lastModified": "2024-06-18T20:15:13.970", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The cURL wrapper in Moodle retained the original request headers when following redirects, so HTTP authorization header information could be unintentionally sent in requests to redirect URLs." + }, + { + "lang": "es", + "value": "El contenedor cURL en Moodle retuvo los encabezados de solicitud originales al seguir redirecciones, por lo que la informaci\u00f3n del encabezado de autorizaci\u00f3n HTTP podr\u00eda enviarse involuntariamente en solicitudes para redireccionar URL." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-382xx/CVE-2024-38276.json b/CVE-2024/CVE-2024-382xx/CVE-2024-38276.json index 2fbc45803ee..4b0aad3bcad 100644 --- a/CVE-2024/CVE-2024-382xx/CVE-2024-38276.json +++ b/CVE-2024/CVE-2024-382xx/CVE-2024-38276.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38276", "sourceIdentifier": "patrick@puiterwijk.org", "published": "2024-06-18T20:15:14.093", - "lastModified": "2024-06-18T20:15:14.093", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Incorrect CSRF token checks resulted in multiple CSRF risks." + }, + { + "lang": "es", + "value": "Las comprobaciones incorrectas de tokens CSRF dieron lugar a m\u00faltiples riesgos de CSRF." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-382xx/CVE-2024-38277.json b/CVE-2024/CVE-2024-382xx/CVE-2024-38277.json index 456e51cea35..ac7e7e945e6 100644 --- a/CVE-2024/CVE-2024-382xx/CVE-2024-38277.json +++ b/CVE-2024/CVE-2024-382xx/CVE-2024-38277.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38277", "sourceIdentifier": "patrick@puiterwijk.org", "published": "2024-06-18T20:15:14.210", - "lastModified": "2024-06-18T20:15:14.210", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A unique key should be generated for a user's QR login key and their auto-login key, so the same key cannot be used interchangeably between the two." + }, + { + "lang": "es", + "value": "Se debe generar una clave \u00fanica para la clave de inicio de sesi\u00f3n QR de un usuario y su clave de inicio de sesi\u00f3n autom\u00e1tico, de modo que la misma clave no se pueda usar indistintamente entre las dos." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-383xx/CVE-2024-38329.json b/CVE-2024/CVE-2024-383xx/CVE-2024-38329.json index 7e868da1e87..1293c3e4d76 100644 --- a/CVE-2024/CVE-2024-383xx/CVE-2024-38329.json +++ b/CVE-2024/CVE-2024-383xx/CVE-2024-38329.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38329", "sourceIdentifier": "psirt@us.ibm.com", "published": "2024-06-19T14:15:13.723", - "lastModified": "2024-06-19T14:15:13.723", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "IBM Storage Protect for Virtual Environments: Data Protection for VMware 8.1.0.0 through 8.1.22.0 could allow a remote authenticated attacker to bypass security restrictions, caused by improper validation of user permission. By sending a specially crafted request, an attacker could exploit this vulnerability to change its settings, trigger backups, restore backups, and also delete all previous backups via log rotation. IBM X-Force ID: 294994." + }, + { + "lang": "es", + "value": "IBM Storage Protect for Virtual Environments: Data Protection for VMware 8.1.0.0 a 8.1.22.0 podr\u00eda permitir a un atacante autenticado remoto eludir las restricciones de seguridad causadas por una validaci\u00f3n inadecuada del permiso del usuario. Al enviar una solicitud especialmente manipulada, un atacante podr\u00eda aprovechar esta vulnerabilidad para cambiar su configuraci\u00f3n, activar copias de seguridad, restaurar copias de seguridad y tambi\u00e9n eliminar todas las copias de seguridad anteriores mediante la rotaci\u00f3n de registros. ID de IBM X-Force: 294994." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-383xx/CVE-2024-38347.json b/CVE-2024/CVE-2024-383xx/CVE-2024-38347.json index f07b9124bad..8ae8257cf68 100644 --- a/CVE-2024/CVE-2024-383xx/CVE-2024-38347.json +++ b/CVE-2024/CVE-2024-383xx/CVE-2024-38347.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38347", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-18T17:15:52.583", - "lastModified": "2024-06-18T17:15:52.583", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "CodeProjects Health Care hospital Management System v1.0 was discovered to contain a SQL injection vulnerability in the Room Information module via the id parameter." + }, + { + "lang": "es", + "value": "Se descubri\u00f3 que CodeProjects Health Care hospital Management System v1.0 conten\u00eda una vulnerabilidad de inyecci\u00f3n SQL en el m\u00f3dulo de informaci\u00f3n de la habitaci\u00f3n a trav\u00e9s del par\u00e1metro id." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-383xx/CVE-2024-38348.json b/CVE-2024/CVE-2024-383xx/CVE-2024-38348.json index 9a213fcf5a6..62d8da3a01f 100644 --- a/CVE-2024/CVE-2024-383xx/CVE-2024-38348.json +++ b/CVE-2024/CVE-2024-383xx/CVE-2024-38348.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38348", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-18T17:15:52.677", - "lastModified": "2024-06-18T17:15:52.677", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "CodeProjects Health Care hospital Management System v1.0 was discovered to contain a SQL injection vulnerability in the Staff Info module via the searvalu parameter." + }, + { + "lang": "es", + "value": "Se descubri\u00f3 que CodeProjects Health Care hospital Management System v1.0 conten\u00eda una vulnerabilidad de inyecci\u00f3n SQL en el m\u00f3dulo de informaci\u00f3n del personal a trav\u00e9s del par\u00e1metro servalu." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-383xx/CVE-2024-38351.json b/CVE-2024/CVE-2024-383xx/CVE-2024-38351.json index ce1ae183012..659c481646a 100644 --- a/CVE-2024/CVE-2024-383xx/CVE-2024-38351.json +++ b/CVE-2024/CVE-2024-383xx/CVE-2024-38351.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38351", "sourceIdentifier": "security-advisories@github.com", "published": "2024-06-18T17:15:52.777", - "lastModified": "2024-06-18T17:15:52.777", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Pocketbase is an open source web backend written in go. In affected versions a malicious user may be able to compromise other user accounts. In order to be exploited users must have both OAuth2 and Password auth methods enabled. A possible attack scenario could be: 1. a malicious actor register with the targeted user's email (it is unverified), 2. at some later point in time the targeted user stumble on your app and decides to sign-up with OAuth2 (_this step could be also initiated by the attacker by sending an invite email to the targeted user_), 3. on successful OAuth2 auth we search for an existing PocketBase user matching with the OAuth2 user's email and associate them, 4. because we haven't changed the password of the existing PocketBase user during the linking, the malicious actor has access to the targeted user account and will be able to login with the initially created email/password. To prevent this for happening we now reset the password for this specific case if the previously created user wasn't verified (an exception to this is if the linking is explicit/manual, aka. when you send `Authorization:TOKEN` with the OAuth2 auth call). Additionally to warn existing users we now send an email alert in case the user has logged in with password but has at least one OAuth2 account linked. The flow will be further improved with ongoing refactoring and we will start sending emails for \"unrecognized device\" logins (OTP and MFA is already implemented and will be available with the next v0.23.0 release in the near future). For the time being users are advised to update to version 0.22.14. There are no known workarounds for this vulnerability.\n\n" + }, + { + "lang": "es", + "value": "Pocketbase es un backend web de c\u00f3digo abierto escrito en go. En las versiones afectadas, un usuario malintencionado puede comprometer las cuentas de otros usuarios. Para ser explotados, los usuarios deben tener habilitados los m\u00e9todos de autenticaci\u00f3n OAuth2 y Contrase\u00f1a. Un posible escenario de ataque podr\u00eda ser: 1. un actor malintencionado se registra con el correo electr\u00f3nico del usuario objetivo (no est\u00e1 verificado), 2. en alg\u00fan momento posterior, el usuario objetivo tropieza con su aplicaci\u00f3n y decide registrarse con OAuth2 (_este paso El atacante tambi\u00e9n podr\u00eda iniciarlo enviando un correo electr\u00f3nico de invitaci\u00f3n al usuario objetivo_), 3. en una autenticaci\u00f3n OAuth2 exitosa, buscamos un usuario de PocketBase existente que coincida con el correo electr\u00f3nico del usuario OAuth2 y lo asociamos, 4. porque no hemos cambiado el contrase\u00f1a del usuario de PocketBase existente durante la vinculaci\u00f3n, el actor malicioso tiene acceso a la cuenta de usuario objetivo y podr\u00e1 iniciar sesi\u00f3n con el correo electr\u00f3nico/contrase\u00f1a creado inicialmente. Para evitar que esto suceda, ahora restablecemos la contrase\u00f1a para este caso espec\u00edfico si el usuario creado anteriormente no fue verificado (una excepci\u00f3n a esto es si el enlace es expl\u00edcito/manual, tambi\u00e9n conocido como cuando env\u00eda `Autorizaci\u00f3n:TOKEN` con OAuth2 llamada de autenticaci\u00f3n). Adem\u00e1s, para advertir a los usuarios existentes, ahora enviamos una alerta por correo electr\u00f3nico en caso de que el usuario haya iniciado sesi\u00f3n con contrase\u00f1a pero tenga al menos una cuenta OAuth2 vinculada. El flujo se mejorar\u00e1 a\u00fan m\u00e1s con la refactorizaci\u00f3n continua y comenzaremos a enviar correos electr\u00f3nicos para inicios de sesi\u00f3n de \"dispositivos no reconocidos\" (OTP y MFA ya est\u00e1n implementados y estar\u00e1n disponibles con la pr\u00f3xima versi\u00f3n v0.23.0 en un futuro pr\u00f3ximo). Por el momento, se recomienda a los usuarios que actualicen a la versi\u00f3n 0.22.14. No se conocen workarounds para esta vulnerabilidad." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-383xx/CVE-2024-38355.json b/CVE-2024/CVE-2024-383xx/CVE-2024-38355.json index 29f0363f6a5..af31f29fe82 100644 --- a/CVE-2024/CVE-2024-383xx/CVE-2024-38355.json +++ b/CVE-2024/CVE-2024-383xx/CVE-2024-38355.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38355", "sourceIdentifier": "security-advisories@github.com", "published": "2024-06-19T20:15:11.180", - "lastModified": "2024-06-19T20:15:11.180", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Socket.IO is an open source, real-time, bidirectional, event-based, communication framework. A specially crafted Socket.IO packet can trigger an uncaught exception on the Socket.IO server, thus killing the Node.js process. This issue is fixed by commit `15af22fc22` which has been included in `socket.io@4.6.2` (released in May 2023). The fix was backported in the 2.x branch as well with commit `d30630ba10`. Users are advised to upgrade. Users unable to upgrade may attach a listener for the \"error\" event to catch these errors.\n" + }, + { + "lang": "es", + "value": "Socket.IO es un framework de comunicaci\u00f3n de c\u00f3digo abierto, en tiempo real, bidireccional y basado en eventos. Un paquete Socket.IO especialmente manipulado puede desencadenar una excepci\u00f3n no detectada en el servidor Socket.IO, matando as\u00ed el proceso Node.js. Este problema se solucion\u00f3 mediante el commit `15af22fc22` que se incluy\u00f3 en `socket.io@4.6.2` (publicado en mayo de 2023). La soluci\u00f3n tambi\u00e9n se respald\u00f3 en la rama 2.x con el commit `d30630ba10`. Se recomienda a los usuarios que actualicen. Los usuarios que no puedan actualizar pueden adjuntar un detector del evento \"error\" para detectar estos errores." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-383xx/CVE-2024-38356.json b/CVE-2024/CVE-2024-383xx/CVE-2024-38356.json index f18e211ab95..8f9a03339d1 100644 --- a/CVE-2024/CVE-2024-383xx/CVE-2024-38356.json +++ b/CVE-2024/CVE-2024-383xx/CVE-2024-38356.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38356", "sourceIdentifier": "security-advisories@github.com", "published": "2024-06-19T20:15:11.453", - "lastModified": "2024-06-19T20:15:11.453", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "TinyMCE is an open source rich text editor. A cross-site scripting (XSS) vulnerability was discovered in TinyMCE\u2019s content extraction code. When using the `noneditable_regexp` option, specially crafted HTML attributes containing malicious code were able to be executed when content was extracted from the editor. This vulnerability has been patched in TinyMCE 7.2.0, TinyMCE 6.8.4 and TinyMCE 5.11.0 LTS by ensuring that, when using the `noneditable_regexp` option, any content within an attribute is properly verified to match the configured regular expression before being added. Users are advised to upgrade. There are no known workarounds for this vulnerability.\n" + }, + { + "lang": "es", + "value": "TinyMCE es un editor de texto enriquecido de c\u00f3digo abierto. Se descubri\u00f3 una vulnerabilidad de cross-site scripting (XSS) en el c\u00f3digo de extracci\u00f3n de contenido de TinyMCE. Al utilizar la opci\u00f3n `noneditable_regexp`, se pod\u00edan ejecutar atributos HTML especialmente manipulados que conten\u00edan c\u00f3digo malicioso cuando se extra\u00eda el contenido del editor. Esta vulnerabilidad se ha solucionado en TinyMCE 7.2.0, TinyMCE 6.8.4 y TinyMCE 5.11.0 LTS garantizando que, al utilizar la opci\u00f3n `noneditable_regexp`, se verifique correctamente que cualquier contenido dentro de un atributo coincida con la expresi\u00f3n regular configurada antes de agregarlo. Se recomienda a los usuarios que actualicen. No se conocen workarounds para esta vulnerabilidad." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-383xx/CVE-2024-38357.json b/CVE-2024/CVE-2024-383xx/CVE-2024-38357.json index 1a5acaa12d8..9b63b97c250 100644 --- a/CVE-2024/CVE-2024-383xx/CVE-2024-38357.json +++ b/CVE-2024/CVE-2024-383xx/CVE-2024-38357.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38357", "sourceIdentifier": "security-advisories@github.com", "published": "2024-06-19T20:15:11.727", - "lastModified": "2024-06-19T20:15:11.727", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "TinyMCE is an open source rich text editor. A cross-site scripting (XSS) vulnerability was discovered in TinyMCE\u2019s content parsing code. This allowed specially crafted noscript elements containing malicious code to be executed when that content was loaded into the editor. This vulnerability has been patched in TinyMCE 7.2.0, TinyMCE 6.8.4 and TinyMCE 5.11.0 LTS by ensuring that content within noscript elements are properly parsed. Users are advised to upgrade. There are no known workarounds for this vulnerability.\n" + }, + { + "lang": "es", + "value": "TinyMCE es un editor de texto enriquecido de c\u00f3digo abierto. Se descubri\u00f3 una vulnerabilidad de cross-site scripting (XSS) en el c\u00f3digo de an\u00e1lisis de contenido de TinyMCE. Esto permiti\u00f3 que se ejecutaran elementos noscript especialmente manipulados que conten\u00edan c\u00f3digo malicioso cuando ese contenido se cargaba en el editor. Esta vulnerabilidad se ha solucionado en TinyMCE 7.2.0, TinyMCE 6.8.4 y TinyMCE 5.11.0 LTS garantizando que el contenido dentro de los elementos noscript se analice correctamente. Se recomienda a los usuarios que actualicen. No se conocen workarounds para esta vulnerabilidad." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-383xx/CVE-2024-38358.json b/CVE-2024/CVE-2024-383xx/CVE-2024-38358.json index 61593e83176..ae4f644d1ac 100644 --- a/CVE-2024/CVE-2024-383xx/CVE-2024-38358.json +++ b/CVE-2024/CVE-2024-383xx/CVE-2024-38358.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38358", "sourceIdentifier": "security-advisories@github.com", "published": "2024-06-19T20:15:11.990", - "lastModified": "2024-06-19T20:15:11.990", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Wasmer is a web assembly (wasm) Runtime supporting WASIX, WASI and Emscripten. If the preopened directory has a symlink pointing outside, WASI programs can traverse the symlink and access host filesystem if the caller sets both `oflags::creat` and `rights::fd_write`. Programs can also crash the runtime by creating a symlink pointing outside with `path_symlink` and `path_open`ing the link. This issue has been addressed in commit `b9483d022` which has been included in release version 4.3.2. Users are advised to upgrade. There are no known workarounds for this vulnerability." + }, + { + "lang": "es", + "value": "Wasmer es un tiempo de ejecuci\u00f3n de ensamblaje web (wasm) que admite WASIX, WASI y Emscripten. Si el directorio preabierto tiene un enlace simb\u00f3lico que apunta hacia afuera, los programas WASI pueden atravesar el enlace simb\u00f3lico y acceder al sistema de archivos del host si la persona que llama configura tanto `oflags::creat` como `rights::fd_write`. Los programas tambi\u00e9n pueden bloquear el tiempo de ejecuci\u00f3n al crear un enlace simb\u00f3lico que apunte hacia afuera con `path_symlink` y `path_open` en el enlace. Este problema se solucion\u00f3 en el commit `b9483d022` que se incluy\u00f3 en la versi\u00f3n 4.3.2. Se recomienda a los usuarios que actualicen. No se conocen workarounds para esta vulnerabilidad." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-384xx/CVE-2024-38449.json b/CVE-2024/CVE-2024-384xx/CVE-2024-38449.json index f54564aae43..f78eacce89e 100644 --- a/CVE-2024/CVE-2024-384xx/CVE-2024-38449.json +++ b/CVE-2024/CVE-2024-384xx/CVE-2024-38449.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38449", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T19:15:58.567", - "lastModified": "2024-06-17T19:15:58.567", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A Directory Traversal vulnerability in KasmVNC 1.3.1.230e50f7b89663316c70de7b0e3db6f6b9340489 and possibly earlier versions allows remote authenticated attackers to browse parent directories and read the content of files outside the scope of the application." + }, + { + "lang": "es", + "value": "Una vulnerabilidad de Directory Traversal en KasmVNC 1.3.1.230e50f7b89663316c70de7b0e3db6f6b9340489 y posiblemente versiones anteriores permite a atacantes remotos autenticados explorar directorios principales y leer el contenido de archivos fuera del alcance de la aplicaci\u00f3n." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-384xx/CVE-2024-38469.json b/CVE-2024/CVE-2024-384xx/CVE-2024-38469.json index b2e078f8b57..50f61ccd9a6 100644 --- a/CVE-2024/CVE-2024-384xx/CVE-2024-38469.json +++ b/CVE-2024/CVE-2024-384xx/CVE-2024-38469.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38469", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T14:15:12.070", - "lastModified": "2024-06-17T14:15:12.070", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "zhimengzhe iBarn v1.5 was discovered to contain a reflected cross-site scripting (XSS) vulnerability via the $search parameter at /pay.php." + }, + { + "lang": "es", + "value": "Se descubri\u00f3 que zhimengzhe iBarn v1.5 conten\u00eda una vulnerabilidad de cross site scripting (XSS) reflejado a trav\u00e9s del par\u00e1metro $search en /pay.php." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-384xx/CVE-2024-38470.json b/CVE-2024/CVE-2024-384xx/CVE-2024-38470.json index 01e2a78eee5..4e6a855537e 100644 --- a/CVE-2024/CVE-2024-384xx/CVE-2024-38470.json +++ b/CVE-2024/CVE-2024-384xx/CVE-2024-38470.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38470", "sourceIdentifier": "cve@mitre.org", "published": "2024-06-17T14:15:12.183", - "lastModified": "2024-06-17T14:15:12.183", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "zhimengzhe iBarn v1.5 was discovered to contain a reflected cross-site scripting (XSS) vulnerability via the $search parameter at /own.php." + }, + { + "lang": "es", + "value": "Se descubri\u00f3 que zhimengzhe iBarn v1.5 conten\u00eda una vulnerabilidad de cross site scripting (XSS) reflejado a trav\u00e9s del par\u00e1metro $search en /own.php." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38504.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38504.json index 836a4afb7fd..5a092428b06 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38504.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38504.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38504", "sourceIdentifier": "cve@jetbrains.com", "published": "2024-06-18T11:15:51.467", - "lastModified": "2024-06-18T11:15:51.467", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In JetBrains YouTrack before 2024.2.34646 the Guest User Account was enabled for attaching files to articles" + }, + { + "lang": "es", + "value": "En JetBrains YouTrack antes de 2024.2.34646, la cuenta de usuario invitado estaba habilitada para adjuntar archivos a art\u00edculos" } ], "metrics": { diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38505.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38505.json index 282eb260e61..c579a8493ae 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38505.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38505.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38505", "sourceIdentifier": "cve@jetbrains.com", "published": "2024-06-18T11:15:51.733", - "lastModified": "2024-06-18T11:15:51.733", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In JetBrains YouTrack before 2024.2.34646 user access token was sent to the third-party site" + }, + { + "lang": "es", + "value": "En JetBrains YouTrack antes de 2024.2.34646 se enviaba el token de acceso del usuario al sitio de terceros" } ], "metrics": { diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38506.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38506.json index a4b8af70b79..7fef7406848 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38506.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38506.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38506", "sourceIdentifier": "cve@jetbrains.com", "published": "2024-06-18T11:15:52.030", - "lastModified": "2024-06-18T11:15:52.030", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In JetBrains YouTrack before 2024.2.34646 user without appropriate permissions could enable the auto-attach option for workflows" + }, + { + "lang": "es", + "value": "En JetBrains YouTrack anterior a 2024.2.34646, el usuario sin los permisos adecuados pod\u00eda habilitar la opci\u00f3n de conexi\u00f3n autom\u00e1tica para flujos de trabajo" } ], "metrics": { diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38507.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38507.json index bcacca92827..e53a77e915c 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38507.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38507.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38507", "sourceIdentifier": "cve@jetbrains.com", "published": "2024-06-18T11:15:52.267", - "lastModified": "2024-06-18T11:15:52.267", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In JetBrains Hub before 2024.2.34646 stored XSS via project description was possible" + }, + { + "lang": "es", + "value": "En JetBrains Hub antes de 2024.2.34646 era posible XSS Almacenado a trav\u00e9s de la descripci\u00f3n del proyecto" } ], "metrics": { diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38538.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38538.json index 9a033bcc69c..d3d4ddd6aa1 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38538.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38538.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38538", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:14.107", - "lastModified": "2024-06-19T14:15:14.107", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: bridge: xmit: make sure we have at least eth header len bytes\n\nsyzbot triggered an uninit value[1] error in bridge device's xmit path\nby sending a short (less than ETH_HLEN bytes) skb. To fix it check if\nwe can actually pull that amount instead of assuming.\n\nTested with dropwatch:\n drop at: br_dev_xmit+0xb93/0x12d0 [bridge] (0xffffffffc06739b3)\n origin: software\n timestamp: Mon May 13 11:31:53 2024 778214037 nsec\n protocol: 0x88a8\n length: 2\n original length: 2\n drop reason: PKT_TOO_SMALL\n\n[1]\nBUG: KMSAN: uninit-value in br_dev_xmit+0x61d/0x1cb0 net/bridge/br_device.c:65\n br_dev_xmit+0x61d/0x1cb0 net/bridge/br_device.c:65\n __netdev_start_xmit include/linux/netdevice.h:4903 [inline]\n netdev_start_xmit include/linux/netdevice.h:4917 [inline]\n xmit_one net/core/dev.c:3531 [inline]\n dev_hard_start_xmit+0x247/0xa20 net/core/dev.c:3547\n __dev_queue_xmit+0x34db/0x5350 net/core/dev.c:4341\n dev_queue_xmit include/linux/netdevice.h:3091 [inline]\n __bpf_tx_skb net/core/filter.c:2136 [inline]\n __bpf_redirect_common net/core/filter.c:2180 [inline]\n __bpf_redirect+0x14a6/0x1620 net/core/filter.c:2187\n ____bpf_clone_redirect net/core/filter.c:2460 [inline]\n bpf_clone_redirect+0x328/0x470 net/core/filter.c:2432\n ___bpf_prog_run+0x13fe/0xe0f0 kernel/bpf/core.c:1997\n __bpf_prog_run512+0xb5/0xe0 kernel/bpf/core.c:2238\n bpf_dispatcher_nop_func include/linux/bpf.h:1234 [inline]\n __bpf_prog_run include/linux/filter.h:657 [inline]\n bpf_prog_run include/linux/filter.h:664 [inline]\n bpf_test_run+0x499/0xc30 net/bpf/test_run.c:425\n bpf_prog_test_run_skb+0x14ea/0x1f20 net/bpf/test_run.c:1058\n bpf_prog_test_run+0x6b7/0xad0 kernel/bpf/syscall.c:4269\n __sys_bpf+0x6aa/0xd90 kernel/bpf/syscall.c:5678\n __do_sys_bpf kernel/bpf/syscall.c:5767 [inline]\n __se_sys_bpf kernel/bpf/syscall.c:5765 [inline]\n __x64_sys_bpf+0xa0/0xe0 kernel/bpf/syscall.c:5765\n x64_sys_call+0x96b/0x3b50 arch/x86/include/generated/asm/syscalls_64.h:322\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xcf/0x1e0 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: net: bridge: xmit: aseg\u00farese de tener al menos el encabezado eth len bytes syzbot desencaden\u00f3 un error de valor uninit[1] en la ruta xmit del dispositivo puente al enviar un mensaje corto (menos de ETH_HLEN bytes) skb. Para solucionarlo, compruebe si realmente podemos retirar esa cantidad en lugar de suponerla. Probado con dropwatch: soltar en: br_dev_xmit+0xb93/0x12d0 [puente] (0xffffffffc06739b3) origen: marca de tiempo del software: lunes 13 de mayo 11:31:53 2024 778214037 protocolo nsec: 0x88a8 longitud: 2 longitud original: 2 motivo de ca\u00edda: PKT_TOO_SMALL [1 ] ERROR: KMSAN: valor uninit en br_dev_xmit+0x61d/0x1cb0 net/bridge/br_device.c:65 br_dev_xmit+0x61d/0x1cb0 net/bridge/br_device.c:65 __netdev_start_xmit include/linux/netdevice.h:4903 [en l\u00ednea] netdev_start_xmit include/linux/netdevice.h:4917 [en l\u00ednea] xmit_one net/core/dev.c:3531 [en l\u00ednea] dev_hard_start_xmit+0x247/0xa20 net/core/dev.c:3547 __dev_queue_xmit+0x34db/0x5350 net/core/dev .c:4341 dev_queue_xmit include/linux/netdevice.h:3091 [en l\u00ednea] __bpf_tx_skb net/core/filter.c:2136 [en l\u00ednea] __bpf_redirect_common net/core/filter.c:2180 [en l\u00ednea] __bpf_redirect+0x14a6/0x1620 net/ Core/Filter.C: 2187 ____BPF_CLONE_REDIRECT NET/CORE/FILTRO.C: 2460 [Inline] BPF_CLONE_REDIRECT+0x328/0x470 NET/Core/Filter.c: 2432 ___ BPF_PROG_RUN+0X13FE/0XE0F0 KERNEL/BPF/BPF/CORE. 0xb5/0xe0 kernel/bpf/core.c:2238 bpf_dispatcher_nop_func include/linux/bpf.h:1234 [en l\u00ednea] __bpf_prog_run include/linux/filter.h:657 [en l\u00ednea] bpf_prog_run include/linux/filter.h:664 [en l\u00ednea ] bpf_test_run+0x499/0xc30 net/bpf/test_run.c:425 bpf_prog_test_run_skb+0x14ea/0x1f20 net/bpf/test_run.c:1058 bpf_prog_test_run+0x6b7/0xad0 kernel/bpf/syscall.c:4269 pf+0x6aa/0xd90 n\u00facleo/ bpf/syscall.c:5678 __do_sys_bpf kernel/bpf/syscall.c:5767 [en l\u00ednea] __se_sys_bpf kernel/bpf/syscall.c:5765 [en l\u00ednea] __x64_sys_bpf+0xa0/0xe0 kernel/bpf/syscall.c:5765 ys_call+0x96b /0x3b50 arch/x86/include/generated/asm/syscalls_64.h:322 do_syscall_x64 arch/x86/entry/common.c:52 [en l\u00ednea] do_syscall_64+0xcf/0x1e0 arch/x86/entry/common.c:83 Entry_SYSCALL_64_after_hwframe+ 0x77/0x7f" } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38539.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38539.json index b89d13526eb..69bf0456974 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38539.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38539.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38539", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:14.193", - "lastModified": "2024-06-19T14:15:14.193", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/cma: Fix kmemleak in rdma_core observed during blktests nvme/rdma use siw\n\nWhen running blktests nvme/rdma, the following kmemleak issue will appear.\n\nkmemleak: Kernel memory leak detector initialized (mempool available:36041)\nkmemleak: Automatic memory scanning thread started\nkmemleak: 2 new suspected memory leaks (see /sys/kernel/debug/kmemleak)\nkmemleak: 8 new suspected memory leaks (see /sys/kernel/debug/kmemleak)\nkmemleak: 17 new suspected memory leaks (see /sys/kernel/debug/kmemleak)\nkmemleak: 4 new suspected memory leaks (see /sys/kernel/debug/kmemleak)\n\nunreferenced object 0xffff88855da53400 (size 192):\n comm \"rdma\", pid 10630, jiffies 4296575922\n hex dump (first 32 bytes):\n 37 00 00 00 00 00 00 00 c0 ff ff ff 1f 00 00 00 7...............\n 10 34 a5 5d 85 88 ff ff 10 34 a5 5d 85 88 ff ff .4.].....4.]....\n backtrace (crc 47f66721):\n [] kmalloc_trace+0x30d/0x3b0\n [] alloc_gid_entry+0x47/0x380 [ib_core]\n [] add_modify_gid+0x166/0x930 [ib_core]\n [] ib_cache_update.part.0+0x6d8/0x910 [ib_core]\n [] ib_cache_setup_one+0x24a/0x350 [ib_core]\n [] ib_register_device+0x9e/0x3a0 [ib_core]\n [] 0xffffffffc2a3d389\n [] nldev_newlink+0x2b8/0x520 [ib_core]\n [] rdma_nl_rcv_msg+0x2c3/0x520 [ib_core]\n []\nrdma_nl_rcv_skb.constprop.0.isra.0+0x23c/0x3a0 [ib_core]\n [] netlink_unicast+0x445/0x710\n [] netlink_sendmsg+0x761/0xc40\n [] __sys_sendto+0x3a9/0x420\n [] __x64_sys_sendto+0xdc/0x1b0\n [] do_syscall_64+0x93/0x180\n [] entry_SYSCALL_64_after_hwframe+0x71/0x79\n\nThe root cause: rdma_put_gid_attr is not called when sgid_attr is set\nto ERR_PTR(-ENODEV)." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: RDMA/cma: corrija kmemleak en rdma_core observado durante el uso de blktests nvme/rdma siw Al ejecutar blktests nvme/rdma, aparecer\u00e1 el siguiente problema de kmemleak. kmemleak: detector de p\u00e9rdida de memoria del kernel inicializado (mempool disponible: 36041) kmemleak: hilo de escaneo autom\u00e1tico de memoria iniciado kmemleak: 2 nuevas p\u00e9rdidas de memoria sospechosas (ver /sys/kernel/debug/kmemleak) kmemleak: 8 nuevas p\u00e9rdidas de memoria sospechosas (ver /sys/ kernel/debug/kmemleak) kmemleak: 17 nuevas p\u00e9rdidas de memoria sospechosas (ver /sys/kernel/debug/kmemleak) kmemleak: 4 nuevas p\u00e9rdidas de memoria sospechosas (ver /sys/kernel/debug/kmemleak) objeto sin referencia 0xffff88855da53400 (tama\u00f1o 192): comm \"rdma\", pid 10630, sjiffies 4296575922 volcado hexadecimal (primeros 32 bytes): 37 00 00 00 00 00 00 00 c0 ff ff ff 1f 00 00 00 7................. 10 34 a5 5d 85 88 ff ff 10 34 a5 5d 85 88 ff ff .4.].....4.].... backtrace (crc 47f66721): [] kmalloc_trace+0x30d/0x3b0 [< ffffffffc2640ff7>] alloc_gid_entry+0x47/0x380 [ib_core] [] add_modify_gid+0x166/0x930 [ib_core] [] ib_cache_update.part.0+0x6d8/0x910 [ib_core] [] ib_cache_setup_one+0x24a/ 0x350 [ib_core] [] ib_register_device+0x9e/0x3a0 [ib_core] [] 0xffffffffc2a3d389 [] nldev_newlink+0x2b8/0x520 [ib_core] ffffffffc2645fe3>] rdma_nl_rcv_msg+0x2c3/0x520 [ib_core] [ ] rdma_nl_rcv_skb.constprop.0.isra.0+0x23c/0x3a0 [ib_core] [] netlink_unicast+0x445/0x710 [] 0 [] __sys_sendto+0x3a9/0x420 [] __x64_sys_sendto+0xdc/0x1b0 [] do_syscall_64+0x93/0x180 [] Entry_SYSCALL_64_after_hwframe+0x71/0x79 La causa ra\u00edz: _gid_attr no se llama cuando sgid_attr est\u00e1 configurado en ERR_PTR(-ENODEV)." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38540.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38540.json index 31c0a27e9b8..ad5b98819fb 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38540.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38540.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38540", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:14.290", - "lastModified": "2024-06-19T14:15:14.290", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbnxt_re: avoid shift undefined behavior in bnxt_qplib_alloc_init_hwq\n\nUndefined behavior is triggered when bnxt_qplib_alloc_init_hwq is called\nwith hwq_attr->aux_depth != 0 and hwq_attr->aux_stride == 0.\nIn that case, \"roundup_pow_of_two(hwq_attr->aux_stride)\" gets called.\nroundup_pow_of_two is documented as undefined for 0.\n\nFix it in the one caller that had this combination.\n\nThe undefined behavior was detected by UBSAN:\n UBSAN: shift-out-of-bounds in ./include/linux/log2.h:57:13\n shift exponent 64 is too large for 64-bit type 'long unsigned int'\n CPU: 24 PID: 1075 Comm: (udev-worker) Not tainted 6.9.0-rc6+ #4\n Hardware name: Abacus electric, s.r.o. - servis@abacus.cz Super Server/H12SSW-iN, BIOS 2.7 10/25/2023\n Call Trace:\n \n dump_stack_lvl+0x5d/0x80\n ubsan_epilogue+0x5/0x30\n __ubsan_handle_shift_out_of_bounds.cold+0x61/0xec\n __roundup_pow_of_two+0x25/0x35 [bnxt_re]\n bnxt_qplib_alloc_init_hwq+0xa1/0x470 [bnxt_re]\n bnxt_qplib_create_qp+0x19e/0x840 [bnxt_re]\n bnxt_re_create_qp+0x9b1/0xcd0 [bnxt_re]\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? __kmalloc+0x1b6/0x4f0\n ? create_qp.part.0+0x128/0x1c0 [ib_core]\n ? __pfx_bnxt_re_create_qp+0x10/0x10 [bnxt_re]\n create_qp.part.0+0x128/0x1c0 [ib_core]\n ib_create_qp_kernel+0x50/0xd0 [ib_core]\n create_mad_qp+0x8e/0xe0 [ib_core]\n ? __pfx_qp_event_handler+0x10/0x10 [ib_core]\n ib_mad_init_device+0x2be/0x680 [ib_core]\n add_client_context+0x10d/0x1a0 [ib_core]\n enable_device_and_get+0xe0/0x1d0 [ib_core]\n ib_register_device+0x53c/0x630 [ib_core]\n ? srso_alias_return_thunk+0x5/0xfbef5\n bnxt_re_probe+0xbd8/0xe50 [bnxt_re]\n ? __pfx_bnxt_re_probe+0x10/0x10 [bnxt_re]\n auxiliary_bus_probe+0x49/0x80\n ? driver_sysfs_add+0x57/0xc0\n really_probe+0xde/0x340\n ? pm_runtime_barrier+0x54/0x90\n ? __pfx___driver_attach+0x10/0x10\n __driver_probe_device+0x78/0x110\n driver_probe_device+0x1f/0xa0\n __driver_attach+0xba/0x1c0\n bus_for_each_dev+0x8f/0xe0\n bus_add_driver+0x146/0x220\n driver_register+0x72/0xd0\n __auxiliary_driver_register+0x6e/0xd0\n ? __pfx_bnxt_re_mod_init+0x10/0x10 [bnxt_re]\n bnxt_re_mod_init+0x3e/0xff0 [bnxt_re]\n ? __pfx_bnxt_re_mod_init+0x10/0x10 [bnxt_re]\n do_one_initcall+0x5b/0x310\n do_init_module+0x90/0x250\n init_module_from_file+0x86/0xc0\n idempotent_init_module+0x121/0x2b0\n __x64_sys_finit_module+0x5e/0xb0\n do_syscall_64+0x82/0x160\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? syscall_exit_to_user_mode_prepare+0x149/0x170\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? syscall_exit_to_user_mode+0x75/0x230\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? do_syscall_64+0x8e/0x160\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? __count_memcg_events+0x69/0x100\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? count_memcg_events.constprop.0+0x1a/0x30\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? handle_mm_fault+0x1f0/0x300\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? do_user_addr_fault+0x34e/0x640\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? srso_alias_return_thunk+0x5/0xfbef5\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n RIP: 0033:0x7f4e5132821d\n Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e3 db 0c 00 f7 d8 64 89 01 48\n RSP: 002b:00007ffca9c906a8 EFLAGS: 00000246 ORIG_RAX: 0000000000000139\n RAX: ffffffffffffffda RBX: 0000563ec8a8f130 RCX: 00007f4e5132821d\n RDX: 0000000000000000 RSI: 00007f4e518fa07d RDI: 000000000000003b\n RBP: 00007ffca9c90760 R08: 00007f4e513f6b20 R09: 00007ffca9c906f0\n R10: 0000563ec8a8faa0 R11: 0000000000000246 R12: 00007f4e518fa07d\n R13: 0000000000020000 R14: 0000563ec8409e90 R15: 0000563ec8a8fa60\n \n ---[ end trace ]---" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: bnxt_re: evita el comportamiento de cambio indefinido en bnxt_qplib_alloc_init_hwq El comportamiento indefinido se activa cuando se llama a bnxt_qplib_alloc_init_hwq con hwq_attr->aux_ Depth != 0 y hwq_attr->aux_stride == 0. En ese caso, \" Se llama a roundup_pow_of_two(hwq_attr->aux_stride)\". roundup_pow_of_two est\u00e1 documentado como indefinido para 0. Corr\u00edjalo en la \u00fanica persona que llam\u00f3 que ten\u00eda esta combinaci\u00f3n. UBSAN detect\u00f3 el comportamiento indefinido: UBSAN: desplazamiento fuera de los l\u00edmites en ./include/linux/log2.h:57:13 el exponente de desplazamiento 64 es demasiado grande para CPU 'long unsigned int' de tipo de 64 bits: 24 PID: 1075 Comm: (udev-worker) Not tainted 6.9.0-rc6+ #4 Nombre del hardware: Abacus electric, sro - servis@abacus.cz Super Server/H12SSW-iN, BIOS 2.7 25/10/2023 Seguimiento de llamadas: < TAREA> dump_stack_lvl+0x5d/0x80 ubsan_epilogue+0x5/0x30 __ubsan_handle_shift_out_of_bounds.cold+0x61/0xec __roundup_pow_of_two+0x25/0x35 [bnxt_re] bnxt_qplib_alloc_init_hwq+0xa1/0x470 bnxt_re] bnxt_qplib_create_qp+0x19e/0x840 [bnxt_re] bnxt_re_create_qp+0x9b1/0xcd0 [bnxt_re ] ? srso_alias_return_thunk+0x5/0xfbef5? srso_alias_return_thunk+0x5/0xfbef5? __kmalloc+0x1b6/0x4f0 ? create_qp.part.0+0x128/0x1c0 [ib_core]? __pfx_bnxt_re_create_qp+0x10/0x10 [bnxt_re] create_qp.part.0+0x128/0x1c0 [ib_core] ib_create_qp_kernel+0x50/0xd0 [ib_core] create_mad_qp+0x8e/0xe0 [ib_core] ? __pfx_qp_event_handler+0x10/0x10 [ib_core] ib_mad_init_device+0x2be/0x680 [ib_core] add_client_context+0x10d/0x1a0 [ib_core] enable_device_and_get+0xe0/0x1d0 [ib_register_device+0x53c/0x63 0 [ib_core] ? srso_alias_return_thunk+0x5/0xfbef5 bnxt_re_probe+0xbd8/0xe50 [bnxt_re] ? __pfx_bnxt_re_probe+0x10/0x10 [bnxt_re] sonda_bus_auxiliar+0x49/0x80 ? driver_sysfs_add+0x57/0xc0 realmente_probe+0xde/0x340? pm_runtime_barrier+0x54/0x90? __pfx___driver_attach+0x10/0x10 __driver_probe_device+0x78/0x110 driver_probe_device+0x1f/0xa0 __driver_attach+0xba/0x1c0 bus_for_each_dev+0x8f/0xe0 bus_add_driver+0x146/0x220 driver_register+0x72/ 0xd0 __auxiliary_driver_register+0x6e/0xd0 ? __pfx_bnxt_re_mod_init+0x10/0x10 [bnxt_re] bnxt_re_mod_init+0x3e/0xff0 [bnxt_re] ? __pfx_bnxt_re_mod_init+0x10/0x10 [bnxt_re] do_one_initcall+0x5b/0x310 do_init_module+0x90/0x250 init_module_from_file+0x86/0xc0 idempotent_init_module+0x121/0x2b0 __x64_sys_finit _module+0x5e/0xb0 do_syscall_64+0x82/0x160 ? srso_alias_return_thunk+0x5/0xfbef5? syscall_exit_to_user_mode_prepare+0x149/0x170? srso_alias_return_thunk+0x5/0xfbef5? syscall_exit_to_user_mode+0x75/0x230? srso_alias_return_thunk+0x5/0xfbef5? do_syscall_64+0x8e/0x160? srso_alias_return_thunk+0x5/0xfbef5? __count_memcg_events+0x69/0x100? srso_alias_return_thunk+0x5/0xfbef5? count_memcg_events.constprop.0+0x1a/0x30? srso_alias_return_thunk+0x5/0xfbef5? handle_mm_fault+0x1f0/0x300? srso_alias_return_thunk+0x5/0xfbef5? do_user_addr_fault+0x34e/0x640? srso_alias_return_thunk+0x5/0xfbef5? srso_alias_return_thunk+0x5/0xfbef5 Entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7f4e5132821d C\u00f3digo: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 9 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e3 db 0c 00 f7 d8 64 89 01 48 RSP: 002b:00007ffca9c906a8 EFLAGS: 00000246 IG_RAX: 0000000000000139 RAX: ffffffffffffffda RBX: 0000563ec8a8f130 RCX: 00007f4e5132821d RDX: 0000000000000000 RSI: 00007f4e518fa07d RDI: 000000000000003b RBP: 00007ffca9c90760 R08: 00007f4e513f6b20 00007ffca9c906f0 R10: 0000563ec8a8faa0 R11: 0000000000000246 R12: 00007f4e518fa07d R13: 0000000000020000 R14: 0000563ec8409e90 R15: 0563ec8a8fa60 ---[ finalizar rastreo ] ---" } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38541.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38541.json index b6fb81c902f..ce96c9c76a5 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38541.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38541.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38541", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:14.383", - "lastModified": "2024-06-19T14:15:14.383", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nof: module: add buffer overflow check in of_modalias()\n\nIn of_modalias(), if the buffer happens to be too small even for the 1st\nsnprintf() call, the len parameter will become negative and str parameter\n(if not NULL initially) will point beyond the buffer's end. Add the buffer\noverflow check after the 1st snprintf() call and fix such check after the\nstrlen() call (accounting for the terminating NUL char)." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: of: m\u00f3dulo: agregar control de desbordamiento del b\u00fafer of_modalias() En of_modalias(), si el b\u00fafer es demasiado peque\u00f1o incluso para la primera llamada a snprintf(), el par\u00e1metro len se vuelve negativo y el par\u00e1metro str (si no es NULL inicialmente) apuntar\u00e1 m\u00e1s all\u00e1 del final del b\u00fafer. Agregue la verificaci\u00f3n de desbordamiento del b\u00fafer despu\u00e9s de la primera llamada a snprintf() y corrija dicha verificaci\u00f3n despu\u00e9s de la llamada strlen() (teniendo en cuenta el car\u00e1cter NUL de terminaci\u00f3n)." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38542.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38542.json index b0ded4779e6..d542874f779 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38542.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38542.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38542", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:14.487", - "lastModified": "2024-06-19T14:15:14.487", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/mana_ib: boundary check before installing cq callbacks\n\nAdd a boundary check inside mana_ib_install_cq_cb to prevent index overflow." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: RDMA/mana_ib: verificaci\u00f3n de los l\u00edmites antes de instalar devoluciones de llamadas de cq Agregue una verificaci\u00f3n de los l\u00edmites dentro de mana_ib_install_cq_cb para evitar el desbordamiento del \u00edndice." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38543.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38543.json index 5fc195b129c..ac5a2e68d67 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38543.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38543.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38543", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:14.587", - "lastModified": "2024-06-19T14:15:14.587", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nlib/test_hmm.c: handle src_pfns and dst_pfns allocation failure\n\nThe kcalloc() in dmirror_device_evict_chunk() will return null if the\nphysical memory has run out. As a result, if src_pfns or dst_pfns is\ndereferenced, the null pointer dereference bug will happen.\n\nMoreover, the device is going away. If the kcalloc() fails, the pages\nmapping a chunk could not be evicted. So add a __GFP_NOFAIL flag in\nkcalloc().\n\nFinally, as there is no need to have physically contiguous memory, Switch\nkcalloc() to kvcalloc() in order to avoid failing allocations." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: lib/test_hmm.c: maneja el error de asignaci\u00f3n de src_pfns y dst_pfns El kcalloc() en dmirror_device_evict_chunk() devolver\u00e1 nulo si la memoria f\u00edsica se ha agotado. Como resultado, si se desreferencia src_pfns o dst_pfns, se producir\u00e1 el error de desreferencia del puntero nulo. Adem\u00e1s, el dispositivo va a desaparecer. Si kcalloc() falla, las p\u00e1ginas que asignan un fragmento no podr\u00e1n ser desalojadas. Entonces agregue una bandera __GFP_NOFAIL en kcalloc(). Finalmente, como no es necesario tener memoria f\u00edsicamente contigua, cambie kcalloc() a kvcalloc() para evitar asignaciones fallidas." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38544.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38544.json index 6e3904cba39..4c81f3a8270 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38544.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38544.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38544", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:14.687", - "lastModified": "2024-06-19T14:15:14.687", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/rxe: Fix seg fault in rxe_comp_queue_pkt\n\nIn rxe_comp_queue_pkt() an incoming response packet skb is enqueued to the\nresp_pkts queue and then a decision is made whether to run the completer\ntask inline or schedule it. Finally the skb is dereferenced to bump a 'hw'\nperformance counter. This is wrong because if the completer task is\nalready running in a separate thread it may have already processed the skb\nand freed it which can cause a seg fault. This has been observed\ninfrequently in testing at high scale.\n\nThis patch fixes this by changing the order of enqueuing the packet until\nafter the counter is accessed." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: RDMA/rxe: corrige la falla de segmentaci\u00f3n en rxe_comp_queue_pkt En rxe_comp_queue_pkt(), un paquete de respuesta entrante skb se pone en cola en la cola resp_pkts y luego se toma una decisi\u00f3n si se ejecuta la tarea de finalizaci\u00f3n en l\u00ednea o programarla. Finalmente, se elimina la referencia al skb para aumentar un contador de rendimiento 'hw'. Esto es incorrecto porque si la tarea de finalizaci\u00f3n ya se est\u00e1 ejecutando en un hilo separado, es posible que ya haya procesado el skb y lo haya liberado, lo que puede causar una falla de segmentaci\u00f3n. Esto se ha observado con poca frecuencia en pruebas a gran escala. Este parche soluciona este problema cambiando el orden de poner en cola el paquete hasta que se accede al contador." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38545.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38545.json index 12fd2e52111..c03f83acb58 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38545.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38545.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38545", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:14.787", - "lastModified": "2024-06-19T14:15:14.787", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/hns: Fix UAF for cq async event\n\nThe refcount of CQ is not protected by locks. When CQ asynchronous\nevents and CQ destruction are concurrent, CQ may have been released,\nwhich will cause UAF.\n\nUse the xa_lock() to protect the CQ refcount." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: RDMA/hns: corrige UAF para el evento cq async El recuento de CQ no est\u00e1 protegido por bloqueos. Cuando los eventos asincr\u00f3nicos de CQ y la destrucci\u00f3n de CQ son simult\u00e1neos, es posible que se haya liberado CQ, lo que provocar\u00e1 UAF. Utilice xa_lock() para proteger el recuento de CQ." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38546.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38546.json index 39b4c70e192..3c1dc5b46a2 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38546.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38546.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38546", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:14.877", - "lastModified": "2024-06-19T14:15:14.877", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm: vc4: Fix possible null pointer dereference\n\nIn vc4_hdmi_audio_init() of_get_address() may return\nNULL which is later dereferenced. Fix this bug by adding NULL check.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: drm: vc4: corrige posible desreferencia del puntero nulo En vc4_hdmi_audio_init() of_get_address() puede devolver NULL, que luego se desreferencia. Corrija este error agregando una verificaci\u00f3n NULL. Encontrado por el Centro de verificaci\u00f3n de Linux (linuxtesting.org) con SVACE." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38547.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38547.json index ff819301649..8c459d065e5 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38547.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38547.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38547", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:14.973", - "lastModified": "2024-06-19T14:15:14.973", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: atomisp: ssh_css: Fix a null-pointer dereference in load_video_binaries\n\nThe allocation failure of mycs->yuv_scaler_binary in load_video_binaries()\nis followed with a dereference of mycs->yuv_scaler_binary after the\nfollowing call chain:\n\nsh_css_pipe_load_binaries()\n |-> load_video_binaries(mycs->yuv_scaler_binary == NULL)\n |\n |-> sh_css_pipe_unload_binaries()\n |-> unload_video_binaries()\n\nIn unload_video_binaries(), it calls to ia_css_binary_unload with argument\n&pipe->pipe_settings.video.yuv_scaler_binary[i], which refers to the\nsame memory slot as mycs->yuv_scaler_binary. Thus, a null-pointer\ndereference is triggered." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: media: atomisp: ssh_css: corrige una desreferencia de puntero nulo en load_video_binaries La falla de asignaci\u00f3n de mycs->yuv_scaler_binary en load_video_binaries() va seguida de una desreferencia de mycs->yuv_scaler_binary despu\u00e9s de siguiente cadena de llamadas: sh_css_pipe_load_binaries() |-> load_video_binaries(mycs->yuv_scaler_binary == NULL) | |-> sh_css_pipe_unload_binaries() |-> unload_video_binaries() En unload_video_binaries(), llama a ia_css_binary_unload con el argumento &pipe->pipe_settings.video.yuv_scaler_binary[i], que se refiere a la misma ranura de memoria que mycs->yuv_scaler_binary. Por lo tanto, se activa una desreferencia de puntero nulo." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38548.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38548.json index 29c52b2ac24..36c7a392c8e 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38548.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38548.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38548", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:15.063", - "lastModified": "2024-06-19T14:15:15.063", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm: bridge: cdns-mhdp8546: Fix possible null pointer dereference\n\nIn cdns_mhdp_atomic_enable(), the return value of drm_mode_duplicate() is\nassigned to mhdp_state->current_mode, and there is a dereference of it in\ndrm_mode_set_name(), which will lead to a NULL pointer dereference on\nfailure of drm_mode_duplicate().\n\nFix this bug add a check of mhdp_state->current_mode." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: drm: bridge: cdns-mhdp8546: corrige posible desreferencia del puntero nulo En cdns_mhdp_atomic_enable(), el valor de retorno de drm_mode_duplicate() se asigna a mhdp_state->current_mode, y hay una desreferencia de \u00e9l en drm_mode_set_name(), lo que conducir\u00e1 a una desreferencia del puntero NULL en caso de falla de drm_mode_duplicate(). Solucione este error y agregue una verificaci\u00f3n de mhdp_state->current_mode." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38549.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38549.json index 2efe2277621..2cbe7ee3843 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38549.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38549.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38549", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:15.163", - "lastModified": "2024-06-19T14:15:15.163", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/mediatek: Add 0 size check to mtk_drm_gem_obj\n\nAdd a check to mtk_drm_gem_init if we attempt to allocate a GEM object\nof 0 bytes. Currently, no such check exists and the kernel will panic if\na userspace application attempts to allocate a 0x0 GBM buffer.\n\nTested by attempting to allocate a 0x0 GBM buffer on an MT8188 and\nverifying that we now return EINVAL." + }, + { + "lang": "es", + "value": "En el kernel de Linux se ha resuelto la siguiente vulnerabilidad: drm/mediatek: Agregar verificaci\u00f3n de tama\u00f1o 0 a mtk_drm_gem_obj Agregar una verificaci\u00f3n a mtk_drm_gem_init si intentamos asignar un objeto GEM de 0 bytes. Actualmente, no existe tal verificaci\u00f3n y el kernel entrar\u00e1 en p\u00e1nico si una aplicaci\u00f3n de espacio de usuario intenta asignar un b\u00fafer GBM 0x0. Probado intentando asignar un b\u00fafer GBM 0x0 en un MT8188 y verificando que ahora devolvemos EINVAL." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38550.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38550.json index 8b23d10c9ce..fa79fe62e6e 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38550.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38550.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38550", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:15.270", - "lastModified": "2024-06-19T14:15:15.270", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nASoC: kirkwood: Fix potential NULL dereference\n\nIn kirkwood_dma_hw_params() mv_mbus_dram_info() returns NULL if\nCONFIG_PLAT_ORION macro is not defined.\nFix this bug by adding NULL check.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: ASoC: kirkwood: corrige una posible desreferencia NULL En kirkwood_dma_hw_params() mv_mbus_dram_info() devuelve NULL si la macro CONFIG_PLAT_ORION no est\u00e1 definida. Corrija este error agregando una verificaci\u00f3n NULL. Encontrado por el Centro de verificaci\u00f3n de Linux (linuxtesting.org) con SVACE." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38551.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38551.json index 79001178923..b14b3af3e40 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38551.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38551.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38551", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:15.357", - "lastModified": "2024-06-19T14:15:15.357", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nASoC: mediatek: Assign dummy when codec not specified for a DAI link\n\nMediaTek sound card drivers are checking whether a DAI link is present\nand used on a board to assign the correct parameters and this is done\nby checking the codec DAI names at probe time.\n\nIf no real codec is present, assign the dummy codec to the DAI link\nto avoid NULL pointer during string comparison." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: ASoC: mediatek: Asignar dummy cuando el c\u00f3dec no est\u00e1 especificado para un enlace DAI Los controladores de la tarjeta de sonido MediaTek est\u00e1n comprobando si hay un enlace DAI presente y utilizado en una placa para asignar los par\u00e1metros correctos y esto se realiza comprobando los nombres DAI del c\u00f3dec en el momento de la sonda. Si no hay ning\u00fan c\u00f3dec real, asigne el c\u00f3dec ficticio al enlace DAI para evitar el puntero NULL durante la comparaci\u00f3n de cadenas." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38552.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38552.json index a0e3eb749e4..4165c8ff9a1 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38552.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38552.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38552", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:15.450", - "lastModified": "2024-06-19T14:15:15.450", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/display: Fix potential index out of bounds in color transformation function\n\nFixes index out of bounds issue in the color transformation function.\nThe issue could occur when the index 'i' exceeds the number of transfer\nfunction points (TRANSFER_FUNC_POINTS).\n\nThe fix adds a check to ensure 'i' is within bounds before accessing the\ntransfer function points. If 'i' is out of bounds, an error message is\nlogged and the function returns false to indicate an error.\n\nReported by smatch:\ndrivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:405 cm_helper_translate_curve_to_hw_format() error: buffer overflow 'output_tf->tf_pts.red' 1025 <= s32max\ndrivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:406 cm_helper_translate_curve_to_hw_format() error: buffer overflow 'output_tf->tf_pts.green' 1025 <= s32max\ndrivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:407 cm_helper_translate_curve_to_hw_format() error: buffer overflow 'output_tf->tf_pts.blue' 1025 <= s32max" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: drm/amd/display: corrige un posible \u00edndice fuera de los l\u00edmites en la funci\u00f3n de transformaci\u00f3n de color. Corrige el problema de \u00edndice fuera de los l\u00edmites en la funci\u00f3n de transformaci\u00f3n de color. El problema podr\u00eda ocurrir cuando el \u00edndice 'i' excede la cantidad de puntos de funci\u00f3n de transferencia (TRANSFER_FUNC_POINTS). La soluci\u00f3n agrega una verificaci\u00f3n para garantizar que 'i' est\u00e9 dentro de los l\u00edmites antes de acceder a los puntos de funci\u00f3n de transferencia. Si 'i' est\u00e1 fuera de los l\u00edmites, se registra un mensaje de error y la funci\u00f3n devuelve falso para indicar un error. Reportado por smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:405 cm_helper_translate_curve_to_hw_format() error: desbordamiento del b\u00fafer 'output_tf->tf_pts.red' 1025 <= controladores s32max/gpu /drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:406 cm_helper_translate_curve_to_hw_format() error: desbordamiento del b\u00fafer 'output_tf->tf_pts.green' 1025 <= controladores s32max/gpu/drm/amd/amdgpu/ ../display/dc/dcn10/dcn10_cm_common.c:407 error de cm_helper_translate_curve_to_hw_format(): desbordamiento del b\u00fafer 'output_tf->tf_pts.blue' 1025 <= s32max" } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38553.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38553.json index 6c1dbe5685d..5979ceeefdc 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38553.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38553.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38553", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:15.550", - "lastModified": "2024-06-19T14:15:15.550", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: fec: remove .ndo_poll_controller to avoid deadlocks\n\nThere is a deadlock issue found in sungem driver, please refer to the\ncommit ac0a230f719b (\"eth: sungem: remove .ndo_poll_controller to avoid\ndeadlocks\"). The root cause of the issue is that netpoll is in atomic\ncontext and disable_irq() is called by .ndo_poll_controller interface\nof sungem driver, however, disable_irq() might sleep. After analyzing\nthe implementation of fec_poll_controller(), the fec driver should have\nthe same issue. Due to the fec driver uses NAPI for TX completions, the\n.ndo_poll_controller is unnecessary to be implemented in the fec driver,\nso fec_poll_controller() can be safely removed." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: net: fec: elimine .ndo_poll_controller para evitar interbloqueos. Se encontr\u00f3 un problema de interbloqueo en el controlador sungem; consulte el commit ac0a230f719b (\"eth: sungem: elimine .ndo_poll_controller para evitar interbloqueos \"). La causa principal del problema es que netpoll est\u00e1 en un contexto at\u00f3mico y la interfaz .ndo_poll_controller del controlador sungem llama a enable_irq(); sin embargo, enable_irq() puede estar inactivo. Despu\u00e9s de analizar la implementaci\u00f3n de fec_poll_controller(), el controlador fec deber\u00eda tener el mismo problema. Debido a que el controlador fec utiliza NAPI para las completaciones de TX, no es necesario implementar .ndo_poll_controller en el controlador fec, por lo que fec_poll_controller() se puede eliminar de forma segura." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38554.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38554.json index a14a20aaac1..63872cf78d5 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38554.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38554.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38554", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:15.627", - "lastModified": "2024-06-19T14:15:15.627", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nax25: Fix reference count leak issue of net_device\n\nThere is a reference count leak issue of the object \"net_device\" in\nax25_dev_device_down(). When the ax25 device is shutting down, the\nax25_dev_device_down() drops the reference count of net_device one\nor zero times depending on if we goto unlock_put or not, which will\ncause memory leak.\n\nIn order to solve the above issue, decrease the reference count of\nnet_device after dev->ax25_ptr is set to null." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: ax25: Solucionar el problema de fuga del recuento de referencias de net_device Hay un problema de fuga del recuento de referencias del objeto \"net_device\" en ax25_dev_device_down(). Cuando el dispositivo ax25 se est\u00e1 apagando, ax25_dev_device_down() elimina el recuento de referencia de net_device una o cero veces dependiendo de si vamos a unlock_put o no, lo que provocar\u00e1 una p\u00e9rdida de memoria. Para resolver el problema anterior, reduzca el recuento de referencias de net_device despu\u00e9s de que dev->ax25_ptr se establezca en nulo." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38555.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38555.json index b33eaa9e908..f136f794dd0 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38555.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38555.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38555", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:15.720", - "lastModified": "2024-06-19T14:15:15.720", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: Discard command completions in internal error\n\nFix use after free when FW completion arrives while device is in\ninternal error state. Avoid calling completion handler in this case,\nsince the device will flush the command interface and trigger all\ncompletions manually.\n\nKernel log:\n------------[ cut here ]------------\nrefcount_t: underflow; use-after-free.\n...\nRIP: 0010:refcount_warn_saturate+0xd8/0xe0\n...\nCall Trace:\n\n? __warn+0x79/0x120\n? refcount_warn_saturate+0xd8/0xe0\n? report_bug+0x17c/0x190\n? handle_bug+0x3c/0x60\n? exc_invalid_op+0x14/0x70\n? asm_exc_invalid_op+0x16/0x20\n? refcount_warn_saturate+0xd8/0xe0\ncmd_ent_put+0x13b/0x160 [mlx5_core]\nmlx5_cmd_comp_handler+0x5f9/0x670 [mlx5_core]\ncmd_comp_notifier+0x1f/0x30 [mlx5_core]\nnotifier_call_chain+0x35/0xb0\natomic_notifier_call_chain+0x16/0x20\nmlx5_eq_async_int+0xf6/0x290 [mlx5_core]\nnotifier_call_chain+0x35/0xb0\natomic_notifier_call_chain+0x16/0x20\nirq_int_handler+0x19/0x30 [mlx5_core]\n__handle_irq_event_percpu+0x4b/0x160\nhandle_irq_event+0x2e/0x80\nhandle_edge_irq+0x98/0x230\n__common_interrupt+0x3b/0xa0\ncommon_interrupt+0x7b/0xa0\n\n\nasm_common_interrupt+0x22/0x40" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: net/mlx5: descartar la finalizaci\u00f3n de comandos en caso de error interno. Se corrige el use-after-free cuando llega la finalizaci\u00f3n del FW mientras el dispositivo est\u00e1 en estado de error interno. Evite llamar al controlador de finalizaci\u00f3n en este caso, ya que el dispositivo limpiar\u00e1 la interfaz de comando y activar\u00e1 todas las finalizaciones manualmente. Registro del kernel: ------------[ cortar aqu\u00ed ]------------ refcount_t: underflow; use-after-free. ... RIP: 0010:refcount_warn_saturate+0xd8/0xe0 ... Seguimiento de llamadas: ? __advertir+0x79/0x120 ? refcount_warn_saturate+0xd8/0xe0? report_bug+0x17c/0x190? handle_bug+0x3c/0x60? exc_invalid_op+0x14/0x70? asm_exc_invalid_op+0x16/0x20? refcount_warn_saturate+0xd8/0xe0 cmd_ent_put+0x13b/0x160 [mlx5_core] mlx5_cmd_comp_handler+0x5f9/0x670 [mlx5_core] cmd_comp_notifier+0x1f/0x30 [mlx5_core] notifier_call_chain+0x35/0xb0 cadena+0x16/0x20 mlx5_eq_async_int+0xf6/0x290 [mlx5_core] notifier_call_chain+0x35 /0xb0 atomic_notifier_call_chain+0x16/0x20 irq_int_handler+0x19/0x30 [mlx5_core] __handle_irq_event_percpu+0x4b/0x160 handle_irq_event+0x2e/0x80 handle_edge_irq+0x98/0x230 __common_interrupt+0x3b/0 xa0 interrupci\u00f3n_com\u00fan+0x7b/0xa0 asm_interrupci\u00f3n_com\u00fan+0x22 /0x40" } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38556.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38556.json index b730d7f7cea..0702931f304 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38556.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38556.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38556", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:15.810", - "lastModified": "2024-06-19T14:15:15.810", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: Add a timeout to acquire the command queue semaphore\n\nPrevent forced completion handling on an entry that has not yet been\nassigned an index, causing an out of bounds access on idx = -22.\nInstead of waiting indefinitely for the sem, blocking flow now waits for\nindex to be allocated or a sem acquisition timeout before beginning the\ntimer for FW completion.\n\nKernel log example:\nmlx5_core 0000:06:00.0: wait_func_handle_exec_timeout:1128:(pid 185911): cmd[-22]: CREATE_UCTX(0xa04) No done completion" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: net/mlx5: agrega un tiempo de espera para adquirir el sem\u00e1foro de la cola de comandos. Evita el manejo de finalizaci\u00f3n forzada en una entrada a la que a\u00fan no se le ha asignado un \u00edndice, lo que provoca un acceso fuera de los l\u00edmites en idx = -22. En lugar de esperar indefinidamente el sem, el flujo de bloqueo ahora espera a que se asigne el \u00edndice o a que se agote el tiempo de espera de adquisici\u00f3n del sem antes de iniciar el temporizador para completar el FW. Ejemplo de registro del kernel: mlx5_core 0000:06:00.0: wait_func_handle_exec_timeout:1128:(pid 185911): cmd[-22]: CREATE_UCTX(0xa04) No se complet\u00f3" } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38557.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38557.json index d2fa0e0b1e0..a28145e6c2a 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38557.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38557.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38557", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:15.900", - "lastModified": "2024-06-19T14:15:15.900", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: Reload only IB representors upon lag disable/enable\n\nOn lag disable, the bond IB device along with all of its\nrepresentors are destroyed, and then the slaves' representors get reloaded.\n\nIn case the slave IB representor load fails, the eswitch error flow\nunloads all representors, including ethernet representors, where the\nnetdevs get detached and removed from lag bond. Such flow is inaccurate\nas the lag driver is not responsible for loading/unloading ethernet\nrepresentors. Furthermore, the flow described above begins by holding\nlag lock to prevent bond changes during disable flow. However, when\nreaching the ethernet representors detachment from lag, the lag lock is\nrequired again, triggering the following deadlock:\n\nCall trace:\n__switch_to+0xf4/0x148\n__schedule+0x2c8/0x7d0\nschedule+0x50/0xe0\nschedule_preempt_disabled+0x18/0x28\n__mutex_lock.isra.13+0x2b8/0x570\n__mutex_lock_slowpath+0x1c/0x28\nmutex_lock+0x4c/0x68\nmlx5_lag_remove_netdev+0x3c/0x1a0 [mlx5_core]\nmlx5e_uplink_rep_disable+0x70/0xa0 [mlx5_core]\nmlx5e_detach_netdev+0x6c/0xb0 [mlx5_core]\nmlx5e_netdev_change_profile+0x44/0x138 [mlx5_core]\nmlx5e_netdev_attach_nic_profile+0x28/0x38 [mlx5_core]\nmlx5e_vport_rep_unload+0x184/0x1b8 [mlx5_core]\nmlx5_esw_offloads_rep_load+0xd8/0xe0 [mlx5_core]\nmlx5_eswitch_reload_reps+0x74/0xd0 [mlx5_core]\nmlx5_disable_lag+0x130/0x138 [mlx5_core]\nmlx5_lag_disable_change+0x6c/0x70 [mlx5_core] // hold ldev->lock\nmlx5_devlink_eswitch_mode_set+0xc0/0x410 [mlx5_core]\ndevlink_nl_cmd_eswitch_set_doit+0xdc/0x180\ngenl_family_rcv_msg_doit.isra.17+0xe8/0x138\ngenl_rcv_msg+0xe4/0x220\nnetlink_rcv_skb+0x44/0x108\ngenl_rcv+0x40/0x58\nnetlink_unicast+0x198/0x268\nnetlink_sendmsg+0x1d4/0x418\nsock_sendmsg+0x54/0x60\n__sys_sendto+0xf4/0x120\n__arm64_sys_sendto+0x30/0x40\nel0_svc_common+0x8c/0x120\ndo_el0_svc+0x30/0xa0\nel0_svc+0x20/0x30\nel0_sync_handler+0x90/0xb8\nel0_sync+0x160/0x180\n\nThus, upon lag enable/disable, load and unload only the IB representors\nof the slaves preventing the deadlock mentioned above.\n\nWhile at it, refactor the mlx5_esw_offloads_rep_load() function to have\na static helper method for its internal logic, in symmetry with the\nrepresentor unload design." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: net/mlx5: recarga solo los representantes IB al desactivar/activar el retraso. Al desactivar el retraso, el dispositivo IB de enlace junto con todos sus representantes se destruyen y luego se recargan los representantes de los esclavos. . En caso de que falle la carga del representante IB esclavo, el flujo de error de conmutaci\u00f3n descarga todos los representantes, incluidos los representantes de Ethernet, donde los netdevs se desconectan y se eliminan del v\u00ednculo de retraso. Dicho flujo es inexacto ya que el controlador de retraso no es responsable de cargar/descargar representantes de Ethernet. Adem\u00e1s, el flujo descrito anteriormente comienza manteniendo el bloqueo de retardo para evitar cambios de uni\u00f3n durante la desactivaci\u00f3n del flujo. Sin embargo, cuando se alcanza la separaci\u00f3n del retraso de los representantes de Ethernet, se requiere nuevamente el bloqueo del retraso, lo que desencadena el siguiente punto muerto: Seguimiento de llamadas: __switch_to+0xf4/0x148 __schedule+0x2c8/0x7d0 Schedule+0x50/0xe0 Schedule_preempt_disabled+0x18/0x28 __mutex_lock.isra. 13+0x2b8/0x570 __mutex_lock_slowpath+0x1c/0x28 mutex_lock+0x4c/0x68 mlx5_lag_remove_netdev+0x3c/0x1a0 [mlx5_core] mlx5e_uplink_rep_disable+0x70/0xa0 [mlx5_core] 6c/0xb0 [mlx5_core] mlx5e_netdev_change_profile+0x44/0x138 [mlx5_core] mlx5e_netdev_attach_nic_profile+0x28 /0x38 [mlx5_core] mlx5e_vport_rep_unload+0x184/0x1b8 [mlx5_core] mlx5_esw_offloads_rep_load+0xd8/0xe0 [mlx5_core] mlx5_eswitch_reload_reps+0x74/0xd0 [mlx5_core] 138 [mlx5_core] mlx5_lag_disable_change+0x6c/0x70 [mlx5_core] // mantenga presionado ldev- >bloquear mlx5_devlink_eswitch_mode_set+0xc0/0x410 [mlx5_core] devlink_nl_cmd_eswitch_set_doit+0xdc/0x180 genl_family_rcv_msg_doit.isra.17+0xe8/0x138 genl_rcv_msg+0xe4/0x220 b+0x44/0x108 genl_rcv+0x40/0x58 netlink_unicast+0x198/0x268 netlink_sendmsg+0x1d4/0x418 sock_sendmsg +0x54/0x60 __sys_sendto+0xf4/0x120 __arm64_sys_sendto+0x30/0x40 el0_svc_common+0x8c/0x120 do_el0_svc+0x30/0xa0 el0_svc+0x20/0x30 el0_sync_handler+0x90/0xb8 el0_sync+0x160/0x180 Por lo tanto, tras el retraso habilitar/deshabilitar, cargar y descargar s\u00f3lo los representantes IB de los esclavos evitan el punto muerto mencionado anteriormente. Mientras lo hace, refactorice la funci\u00f3n mlx5_esw_offloads_rep_load() para tener un m\u00e9todo auxiliar est\u00e1tico para su l\u00f3gica interna, en simetr\u00eda con el dise\u00f1o de descarga del representante." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38558.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38558.json index bd9327294a9..a3ca8980869 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38558.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38558.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38558", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:15.983", - "lastModified": "2024-06-19T14:15:15.983", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: openvswitch: fix overwriting ct original tuple for ICMPv6\n\nOVS_PACKET_CMD_EXECUTE has 3 main attributes:\n - OVS_PACKET_ATTR_KEY - Packet metadata in a netlink format.\n - OVS_PACKET_ATTR_PACKET - Binary packet content.\n - OVS_PACKET_ATTR_ACTIONS - Actions to execute on the packet.\n\nOVS_PACKET_ATTR_KEY is parsed first to populate sw_flow_key structure\nwith the metadata like conntrack state, input port, recirculation id,\netc. Then the packet itself gets parsed to populate the rest of the\nkeys from the packet headers.\n\nWhenever the packet parsing code starts parsing the ICMPv6 header, it\nfirst zeroes out fields in the key corresponding to Neighbor Discovery\ninformation even if it is not an ND packet.\n\nIt is an 'ipv6.nd' field. However, the 'ipv6' is a union that shares\nthe space between 'nd' and 'ct_orig' that holds the original tuple\nconntrack metadata parsed from the OVS_PACKET_ATTR_KEY.\n\nND packets should not normally have conntrack state, so it's fine to\nshare the space, but normal ICMPv6 Echo packets or maybe other types of\nICMPv6 can have the state attached and it should not be overwritten.\n\nThe issue results in all but the last 4 bytes of the destination\naddress being wiped from the original conntrack tuple leading to\nincorrect packet matching and potentially executing wrong actions\nin case this packet recirculates within the datapath or goes back\nto userspace.\n\nND fields should not be accessed in non-ND packets, so not clearing\nthem should be fine. Executing memset() only for actual ND packets to\navoid the issue.\n\nInitializing the whole thing before parsing is needed because ND packet\nmay not contain all the options.\n\nThe issue only affects the OVS_PACKET_CMD_EXECUTE path and doesn't\naffect packets entering OVS datapath from network interfaces, because\nin this case CT metadata is populated from skb after the packet is\nalready parsed." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: net: openvswitch: corrige la sobrescritura de la tupla original de ct para ICMPv6 OVS_PACKET_CMD_EXECUTE tiene 3 atributos principales: - OVS_PACKET_ATTR_KEY - Metadatos de paquetes en formato netlink. - OVS_PACKET_ATTR_PACKET: contenido del paquete binario. - OVS_PACKET_ATTR_ACTIONS: acciones a ejecutar en el paquete. OVS_PACKET_ATTR_KEY se analiza primero para completar la estructura sw_flow_key con metadatos como el estado de conexi\u00f3n, el puerto de entrada, la identificaci\u00f3n de recirculaci\u00f3n, etc. Luego, el paquete en s\u00ed se analiza para completar el resto de las claves de los encabezados del paquete. Siempre que el c\u00f3digo de an\u00e1lisis de paquetes comienza a analizar el encabezado ICMPv6, primero pone a cero los campos en la clave correspondiente a la informaci\u00f3n de descubrimiento de vecinos, incluso si no es un paquete ND. Es un campo 'ipv6.nd'. Sin embargo, 'ipv6' es una uni\u00f3n que comparte el espacio entre 'nd' y 'ct_orig' que contiene los metadatos de conntrack de tupla originales analizados a partir de OVS_PACKET_ATTR_KEY. Los paquetes ND normalmente no deber\u00edan tener estado de seguimiento, por lo que est\u00e1 bien compartir el espacio, pero los paquetes ICMPv6 Echo normales o tal vez otros tipos de ICMPv6 pueden tener el estado adjunto y no deben sobrescribirse. El problema provoca que todos, excepto los \u00faltimos 4 bytes de la direcci\u00f3n de destino, se borren de la tupla conntrack original, lo que provoca una coincidencia incorrecta de paquetes y, potencialmente, la ejecuci\u00f3n de acciones incorrectas en caso de que este paquete recircule dentro de la ruta de datos o regrese al espacio de usuario. No se debe acceder a los campos ND en paquetes que no sean ND, por lo que no borrarlos deber\u00eda estar bien. Ejecutar memset() solo para paquetes ND reales para evitar el problema. Es necesario inicializar todo antes del an\u00e1lisis porque es posible que el paquete ND no contenga todas las opciones. El problema solo afecta la ruta OVS_PACKET_CMD_EXECUTE y no afecta a los paquetes que ingresan a la ruta de datos OVS desde las interfaces de red, porque en este caso los metadatos CT se completan desde skb despu\u00e9s de que el paquete ya se haya analizado." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38559.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38559.json index 33a40720081..b8026f715ba 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38559.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38559.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38559", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:16.077", - "lastModified": "2024-06-19T14:15:16.077", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qedf: Ensure the copied buf is NUL terminated\n\nCurrently, we allocate a count-sized kernel buffer and copy count from\nuserspace to that buffer. Later, we use kstrtouint on this buffer but we\ndon't ensure that the string is terminated inside the buffer, this can\nlead to OOB read when using kstrtouint. Fix this issue by using\nmemdup_user_nul instead of memdup_user." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: scsi: qedf: aseg\u00farese de que el buf copiado tenga terminaci\u00f3n NUL. Actualmente, asignamos un b\u00fafer del kernel del tama\u00f1o de un conteo y copiamos el conteo desde el espacio de usuario a ese b\u00fafer. M\u00e1s adelante, usamos kstrtouint en este b\u00fafer pero no nos aseguramos de que la cadena termine dentro del b\u00fafer, esto puede provocar una lectura OOB cuando usamos kstrtouint. Solucione este problema utilizando memdup_user_nul en lugar de memdup_user." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38560.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38560.json index 34fe909d99c..a50a5cb7bf6 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38560.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38560.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38560", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:16.187", - "lastModified": "2024-06-19T14:15:16.187", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: bfa: Ensure the copied buf is NUL terminated\n\nCurrently, we allocate a nbytes-sized kernel buffer and copy nbytes from\nuserspace to that buffer. Later, we use sscanf on this buffer but we don't\nensure that the string is terminated inside the buffer, this can lead to\nOOB read when using sscanf. Fix this issue by using memdup_user_nul instead\nof memdup_user." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: scsi: bfa: aseg\u00farese de que el buf copiado tenga terminaci\u00f3n NUL. Actualmente, asignamos un b\u00fafer del kernel de tama\u00f1o nbytes y copiamos nbytes del espacio de usuario a ese b\u00fafer. M\u00e1s adelante, usamos sscanf en este b\u00fafer pero no nos aseguramos de que la cadena termine dentro del b\u00fafer, esto puede provocar una lectura OOB cuando usamos sscanf. Solucione este problema utilizando memdup_user_nul en lugar de memdup_user." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38561.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38561.json index 3b611f75eda..c40aa775599 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38561.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38561.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38561", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:16.313", - "lastModified": "2024-06-19T14:15:16.313", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nkunit: Fix kthread reference\n\nThere is a race condition when a kthread finishes after the deadline and\nbefore the call to kthread_stop(), which may lead to use after free." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: kunit: Fix kthread reference Hay una condici\u00f3n de ejecuci\u00f3n cuando un kthread finaliza despu\u00e9s de la fecha l\u00edmite y antes de la llamada a kthread_stop(), lo que puede llevar a su use-after-free." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38562.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38562.json index 339dfc0460e..0773df98c1f 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38562.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38562.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38562", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:16.393", - "lastModified": "2024-06-19T14:15:16.393", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: nl80211: Avoid address calculations via out of bounds array indexing\n\nBefore request->channels[] can be used, request->n_channels must be set.\nAdditionally, address calculations for memory after the \"channels\" array\nneed to be calculated from the allocation base (\"request\") rather than\nvia the first \"out of bounds\" index of \"channels\", otherwise run-time\nbounds checking will throw a warning." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: wifi: nl80211: evitar c\u00e1lculos de direcciones mediante indexaci\u00f3n de matrices fuera de los l\u00edmites Antes de poder utilizar request->channels[], se debe configurar request->n_channels. Adem\u00e1s, los c\u00e1lculos de direcciones para la memoria despu\u00e9s de la matriz de \"canales\" deben calcularse a partir de la base de asignaci\u00f3n (\"solicitud\") en lugar de mediante el primer \u00edndice \"fuera de los l\u00edmites\" de \"canales\"; de lo contrario, la verificaci\u00f3n de los l\u00edmites en tiempo de ejecuci\u00f3n arrojar\u00e1 un advertencia." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38563.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38563.json index 8571cda538c..668c5bb8fde 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38563.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38563.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38563", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:16.480", - "lastModified": "2024-06-19T14:15:16.480", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: mt76: mt7996: fix potential memory leakage when reading chip temperature\n\nWithout this commit, reading chip temperature will cause memory leakage." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: wifi: mt76: mt7996: corrige una posible p\u00e9rdida de memoria al leer la temperatura del chip Sin esta confirmaci\u00f3n, la lectura de la temperatura del chip provocar\u00e1 una p\u00e9rdida de memoria." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38564.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38564.json index 46eb5e513ac..26e62fbcfcd 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38564.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38564.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38564", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:16.560", - "lastModified": "2024-06-19T14:15:16.560", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Add BPF_PROG_TYPE_CGROUP_SKB attach type enforcement in BPF_LINK_CREATE\n\nbpf_prog_attach uses attach_type_to_prog_type to enforce proper\nattach type for BPF_PROG_TYPE_CGROUP_SKB. link_create uses\nbpf_prog_get and relies on bpf_prog_attach_check_attach_type\nto properly verify prog_type <> attach_type association.\n\nAdd missing attach_type enforcement for the link_create case.\nOtherwise, it's currently possible to attach cgroup_skb prog\ntypes to other cgroup hooks." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: bpf: agregue la aplicaci\u00f3n del tipo de archivo adjunto BPF_PROG_TYPE_CGROUP_SKB en BPF_LINK_CREATE bpf_prog_attach usa adjunto_type_to_prog_type para aplicar el tipo de archivo adjunto adecuado para BPF_PROG_TYPE_CGROUP_SKB. link_create usa bpf_prog_get y se basa en bpf_prog_attach_check_attach_type para verificar correctamente la asociaci\u00f3n prog_type <> adjunto_tipo. Agregue la aplicaci\u00f3n de adjunto_tipo faltante para el caso link_create. De lo contrario, actualmente es posible adjuntar tipos de programa cgroup_skb a otros enlaces de cgroup." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38565.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38565.json index 708d81b226c..f712cfaafd6 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38565.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38565.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38565", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:16.667", - "lastModified": "2024-06-19T14:15:16.667", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: ar5523: enable proper endpoint verification\n\nSyzkaller reports [1] hitting a warning about an endpoint in use\nnot having an expected type to it.\n\nFix the issue by checking for the existence of all proper\nendpoints with their according types intact.\n\nSadly, this patch has not been tested on real hardware.\n\n[1] Syzkaller report:\n------------[ cut here ]------------\nusb 1-1: BOGUS urb xfer, pipe 3 != type 1\nWARNING: CPU: 0 PID: 3643 at drivers/usb/core/urb.c:504 usb_submit_urb+0xed6/0x1880 drivers/usb/core/urb.c:504\n...\nCall Trace:\n \n ar5523_cmd+0x41b/0x780 drivers/net/wireless/ath/ar5523/ar5523.c:275\n ar5523_cmd_read drivers/net/wireless/ath/ar5523/ar5523.c:302 [inline]\n ar5523_host_available drivers/net/wireless/ath/ar5523/ar5523.c:1376 [inline]\n ar5523_probe+0x14b0/0x1d10 drivers/net/wireless/ath/ar5523/ar5523.c:1655\n usb_probe_interface+0x30f/0x7f0 drivers/usb/core/driver.c:396\n call_driver_probe drivers/base/dd.c:560 [inline]\n really_probe+0x249/0xb90 drivers/base/dd.c:639\n __driver_probe_device+0x1df/0x4d0 drivers/base/dd.c:778\n driver_probe_device+0x4c/0x1a0 drivers/base/dd.c:808\n __device_attach_driver+0x1d4/0x2e0 drivers/base/dd.c:936\n bus_for_each_drv+0x163/0x1e0 drivers/base/bus.c:427\n __device_attach+0x1e4/0x530 drivers/base/dd.c:1008\n bus_probe_device+0x1e8/0x2a0 drivers/base/bus.c:487\n device_add+0xbd9/0x1e90 drivers/base/core.c:3517\n usb_set_configuration+0x101d/0x1900 drivers/usb/core/message.c:2170\n usb_generic_driver_probe+0xbe/0x100 drivers/usb/core/generic.c:238\n usb_probe_device+0xd8/0x2c0 drivers/usb/core/driver.c:293\n call_driver_probe drivers/base/dd.c:560 [inline]\n really_probe+0x249/0xb90 drivers/base/dd.c:639\n __driver_probe_device+0x1df/0x4d0 drivers/base/dd.c:778\n driver_probe_device+0x4c/0x1a0 drivers/base/dd.c:808\n __device_attach_driver+0x1d4/0x2e0 drivers/base/dd.c:936\n bus_for_each_drv+0x163/0x1e0 drivers/base/bus.c:427\n __device_attach+0x1e4/0x530 drivers/base/dd.c:1008\n bus_probe_device+0x1e8/0x2a0 drivers/base/bus.c:487\n device_add+0xbd9/0x1e90 drivers/base/core.c:3517\n usb_new_device.cold+0x685/0x10ad drivers/usb/core/hub.c:2573\n hub_port_connect drivers/usb/core/hub.c:5353 [inline]\n hub_port_connect_change drivers/usb/core/hub.c:5497 [inline]\n port_event drivers/usb/core/hub.c:5653 [inline]\n hub_event+0x26cb/0x45d0 drivers/usb/core/hub.c:5735\n process_one_work+0x9bf/0x1710 kernel/workqueue.c:2289\n worker_thread+0x669/0x1090 kernel/workqueue.c:2436\n kthread+0x2e8/0x3a0 kernel/kthread.c:376\n ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306\n " + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: wifi: ar5523: habilite la verificaci\u00f3n adecuada del endpoint Syzkaller informa [1] que aparece una advertencia sobre un endpoint en uso que no tiene el tipo esperado. Solucione el problema verificando la existencia de todos los endpoints adecuados con sus tipos correspondientes intactos. Lamentablemente, este parche no se ha probado en hardware real. [1] Informe Syzkaller: ------------[ cortar aqu\u00ed ]------------ usb 1-1: BOGUS urb xfer, tuber\u00eda 3 != tipo 1 ADVERTENCIA : CPU: 0 PID: 3643 en drivers/usb/core/urb.c:504 usb_submit_urb+0xed6/0x1880 drivers/usb/core/urb.c:504 ... Seguimiento de llamadas: ar5523_cmd+0x41b/0x780 drivers /net/wireless/ath/ar5523/ar5523.c:275 ar5523_cmd_read drivers/net/wireless/ath/ar5523/ar5523.c:302 [en l\u00ednea] ar5523_host_available drivers/net/wireless/ath/ar5523/ar5523.c:1376 [ en l\u00ednea] ar5523_probe+0x14b0/0x1d10 drivers/net/wireless/ath/ar5523/ar5523.c:1655 usb_probe_interface+0x30f/0x7f0 drivers/usb/core/driver.c:396 call_driver_probe drivers/base/dd.c:560 [en l\u00ednea ] very_probe+0x249/0xb90 drivers/base/dd.c:639 __driver_probe_device+0x1df/0x4d0 drivers/base/dd.c:778 driver_probe_device+0x4c/0x1a0 drivers/base/dd.c:808 __device_attach_driver+0x1d4/0x2e0 drivers/ base/dd.c:936 bus_for_each_drv+0x163/0x1e0 controladores/base/bus.c:427 __device_attach+0x1e4/0x530 controladores/base/dd.c:1008 bus_probe_device+0x1e8/0x2a0 controladores/base/bus.c:487 device_add +0xbd9/0x1e90 controladores/base/core.c:3517 usb_set_configuration+0x101d/0x1900 controladores/usb/core/message.c:2170 usb_generic_driver_probe+0xbe/0x100 controladores/usb/core/generic.c:238 usb_probe_device+0xd8/0x2c0 drivers/usb/core/driver.c:293 call_driver_probe drivers/base/dd.c:560 [en l\u00ednea] very_probe+0x249/0xb90 drivers/base/dd.c:639 __driver_probe_device+0x1df/0x4d0 drivers/base/dd.c :778 driver_probe_device+0x4c/0x1a0 controladores/base/dd.c:808 __device_attach_driver+0x1d4/0x2e0 controladores/base/dd.c:936 bus_for_each_drv+0x163/0x1e0 controladores/base/bus.c:427 __device_attach+0x1e4/0x530 controladores /base/dd.c:1008 bus_probe_device+0x1e8/0x2a0 controladores/base/bus.c:487 device_add+0xbd9/0x1e90 controladores/base/core.c:3517 usb_new_device.cold+0x685/0x10ad controladores/usb/core/hub .c:2573 hub_port_connect drivers/usb/core/hub.c:5353 [en l\u00ednea] hub_port_connect_change drivers/usb/core/hub.c:5497 [en l\u00ednea] port_event drivers/usb/core/hub.c:5653 [en l\u00ednea] hub_event +0x26cb/0x45d0 controladores/usb/core/hub.c:5735 Process_one_work+0x9bf/0x1710 kernel/workqueue.c:2289 trabajador_thread+0x669/0x1090 kernel/workqueue.c:2436 kthread+0x2e8/0x3a0 kernel/kthread.c: 376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306 " } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38566.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38566.json index 64700948353..7d9a7f629b5 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38566.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38566.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38566", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:16.767", - "lastModified": "2024-06-19T14:15:16.767", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix verifier assumptions about socket->sk\n\nThe verifier assumes that 'sk' field in 'struct socket' is valid\nand non-NULL when 'socket' pointer itself is trusted and non-NULL.\nThat may not be the case when socket was just created and\npassed to LSM socket_accept hook.\nFix this verifier assumption and adjust tests." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: bpf: corrige las suposiciones del verificador sobre socket->sk. El verificador asume que el campo 'sk' en 'struct socket' es v\u00e1lido y no NULL cuando el puntero 'socket' en s\u00ed es confiable y no NULL. Puede que ese no sea el caso cuando el socket se acaba de crear y se pas\u00f3 al gancho LSM socket_accept. Corrija esta suposici\u00f3n del verificador y ajuste las pruebas." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38567.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38567.json index 785aad1a69e..b03df25560f 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38567.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38567.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38567", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:16.850", - "lastModified": "2024-06-19T14:15:16.850", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: carl9170: add a proper sanity check for endpoints\n\nSyzkaller reports [1] hitting a warning which is caused by presence\nof a wrong endpoint type at the URB sumbitting stage. While there\nwas a check for a specific 4th endpoint, since it can switch types\nbetween bulk and interrupt, other endpoints are trusted implicitly.\nSimilar warning is triggered in a couple of other syzbot issues [2].\n\nFix the issue by doing a comprehensive check of all endpoints\ntaking into account difference between high- and full-speed\nconfiguration.\n\n[1] Syzkaller report:\n...\nWARNING: CPU: 0 PID: 4721 at drivers/usb/core/urb.c:504 usb_submit_urb+0xed6/0x1880 drivers/usb/core/urb.c:504\n...\nCall Trace:\n \n carl9170_usb_send_rx_irq_urb+0x273/0x340 drivers/net/wireless/ath/carl9170/usb.c:504\n carl9170_usb_init_device drivers/net/wireless/ath/carl9170/usb.c:939 [inline]\n carl9170_usb_firmware_finish drivers/net/wireless/ath/carl9170/usb.c:999 [inline]\n carl9170_usb_firmware_step2+0x175/0x240 drivers/net/wireless/ath/carl9170/usb.c:1028\n request_firmware_work_func+0x130/0x240 drivers/base/firmware_loader/main.c:1107\n process_one_work+0x9bf/0x1710 kernel/workqueue.c:2289\n worker_thread+0x669/0x1090 kernel/workqueue.c:2436\n kthread+0x2e8/0x3a0 kernel/kthread.c:376\n ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308\n \n\n[2] Related syzkaller crashes:" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: wifi: carl9170: agregue una verificaci\u00f3n de integridad adecuada para los endpoints Syzkaller informa [1] que aparece una advertencia causada por la presencia de un tipo de endpoint incorrecto en la etapa de env\u00edo de URB. Si bien hubo una verificaci\u00f3n para un cuarto endpoint espec\u00edfico, dado que puede cambiar de tipo entre masivo e interrupci\u00f3n, se conf\u00eda impl\u00edcitamente en otros endpoints. Se activa una advertencia similar en un par de otros problemas de syzbot [2]. Solucione el problema realizando una verificaci\u00f3n exhaustiva de todos los endpoints teniendo en cuenta la diferencia entre la configuraci\u00f3n de alta y m\u00e1xima velocidad. [1] Informe de Syzkaller: ... ADVERTENCIA: CPU: 0 PID: 4721 en drivers/usb/core/urb.c:504 usb_submit_urb+0xed6/0x1880 drivers/usb/core/urb.c:504 ... Seguimiento de llamadas : carl9170_usb_send_rx_irq_urb+0x273/0x340 drivers/net/wireless/ath/carl9170/usb.c:504 carl9170_usb_init_device drivers/net/wireless/ath/carl9170/usb.c:939 [en l\u00ednea] carl9170_usb_firmware_finish drivers/net /inal\u00e1mbrico/ ath/carl9170/usb.c:999 [en l\u00ednea] carl9170_usb_firmware_step2+0x175/0x240 drivers/net/wireless/ath/carl9170/usb.c:1028 request_firmware_work_func+0x130/0x240 drivers/base/firmware_loader/main.c:1107 Process_one_work+ 0x9bf/0x1710 kernel/workqueue.c:2289 trabajador_thread+0x669/0x1090 kernel/workqueue.c:2436 kthread+0x2e8/0x3a0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308 [2] Fallos relacionados con syzkaller:" } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38568.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38568.json index b5f559ebd4f..3306d7121a3 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38568.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38568.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38568", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:16.950", - "lastModified": "2024-06-19T14:15:16.950", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrivers/perf: hisi: hns3: Fix out-of-bound access when valid event group\n\nThe perf tool allows users to create event groups through following\ncmd [1], but the driver does not check whether the array index is out\nof bounds when writing data to the event_group array. If the number of\nevents in an event_group is greater than HNS3_PMU_MAX_HW_EVENTS, the\nmemory write overflow of event_group array occurs.\n\nAdd array index check to fix the possible array out of bounds violation,\nand return directly when write new events are written to array bounds.\n\nThere are 9 different events in an event_group.\n[1] perf stat -e '{pmu/event1/, ... ,pmu/event9/}" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: drivers/perf: hisi: hns3: corrige el acceso fuera de los l\u00edmites cuando el grupo de eventos es v\u00e1lido. La herramienta perf permite a los usuarios crear grupos de eventos mediante el siguiente cmd [1], pero el controlador no comprueba si el \u00edndice de la matriz est\u00e1 fuera de los l\u00edmites al escribir datos en la matriz event_group. Si el n\u00famero de eventos en un event_group es mayor que HNS3_PMU_MAX_HW_EVENTS, se produce un desbordamiento de escritura en la memoria de la matriz event_group. Agregue la verificaci\u00f3n del \u00edndice de la matriz para corregir la posible infracci\u00f3n de la matriz fuera de los l\u00edmites y regrese directamente cuando se escriban nuevos eventos en los l\u00edmites de la matriz. Hay 9 eventos diferentes en un grupo de eventos. [1] estad\u00edstica de rendimiento -e '{pmu/event1/, ...,pmu/event9/}" } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38569.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38569.json index fd96332b480..091c527b84b 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38569.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38569.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38569", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:17.060", - "lastModified": "2024-06-19T14:15:17.060", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrivers/perf: hisi_pcie: Fix out-of-bound access when valid event group\n\nThe perf tool allows users to create event groups through following\ncmd [1], but the driver does not check whether the array index is out of\nbounds when writing data to the event_group array. If the number of events\nin an event_group is greater than HISI_PCIE_MAX_COUNTERS, the memory write\noverflow of event_group array occurs.\n\nAdd array index check to fix the possible array out of bounds violation,\nand return directly when write new events are written to array bounds.\n\nThere are 9 different events in an event_group.\n[1] perf stat -e '{pmu/event1/, ... ,pmu/event9/}'" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: drivers/perf: hisi_pcie: corrige el acceso fuera de los l\u00edmites cuando el grupo de eventos es v\u00e1lido. La herramienta perf permite a los usuarios crear grupos de eventos mediante el siguiente cmd [1], pero el controlador no compruebe si el \u00edndice de la matriz est\u00e1 fuera de los l\u00edmites al escribir datos en la matriz event_group. Si el n\u00famero de eventos en un event_group es mayor que HISI_PCIE_MAX_COUNTERS, se produce un desbordamiento de escritura en la memoria de la matriz event_group. Agregue la verificaci\u00f3n del \u00edndice de la matriz para corregir la posible infracci\u00f3n de la matriz fuera de los l\u00edmites y regrese directamente cuando se escriban nuevos eventos en los l\u00edmites de la matriz. Hay 9 eventos diferentes en un grupo de eventos. [1] estad\u00edstica de rendimiento -e '{pmu/event1/, ...,pmu/event9/}'" } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38570.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38570.json index a62cea1745e..db20f64f1e3 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38570.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38570.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38570", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:17.153", - "lastModified": "2024-06-19T14:15:17.153", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: Fix potential glock use-after-free on unmount\n\nWhen a DLM lockspace is released and there ares still locks in that\nlockspace, DLM will unlock those locks automatically. Commit\nfb6791d100d1b started exploiting this behavior to speed up filesystem\nunmount: gfs2 would simply free glocks it didn't want to unlock and then\nrelease the lockspace. This didn't take the bast callbacks for\nasynchronous lock contention notifications into account, which remain\nactive until until a lock is unlocked or its lockspace is released.\n\nTo prevent those callbacks from accessing deallocated objects, put the\nglocks that should not be unlocked on the sd_dead_glocks list, release\nthe lockspace, and only then free those glocks.\n\nAs an additional measure, ignore unexpected ast and bast callbacks if\nthe receiving glock is dead." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: gfs2: soluciona el posible use-after-free de glock al desmontar Cuando se libera un espacio de bloqueo de DLM y todav\u00eda hay bloqueos en ese espacio de bloqueo, DLM desbloquear\u00e1 esos bloqueos autom\u00e1ticamente. El commit fb6791d100d1b comenz\u00f3 a explotar este comportamiento para acelerar el desmontaje del sistema de archivos: gfs2 simplemente liberar\u00eda las glocks que no quer\u00eda desbloquear y luego liberar\u00eda el espacio de bloqueo. Esto no tuvo en cuenta las devoluciones de llamada de bast para notificaciones de contenci\u00f3n de bloqueo asincr\u00f3nicas, que permanecen activas hasta que se desbloquea un bloqueo o se libera su espacio de bloqueo. Para evitar que esas devoluciones de llamada accedan a objetos desasignados, coloque las glocks que no deben desbloquearse en la lista sd_dead_glocks, libere el espacio de bloqueo y solo entonces libere esas glocks. Como medida adicional, ignore las devoluciones de llamada inesperadas de ast y bast si la glock receptora est\u00e1 muerta." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38571.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38571.json index feed2937707..f317b9edd27 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38571.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38571.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38571", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:17.250", - "lastModified": "2024-06-19T14:15:17.250", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nthermal/drivers/tsens: Fix null pointer dereference\n\ncompute_intercept_slope() is called from calibrate_8960() (in tsens-8960.c)\nas compute_intercept_slope(priv, p1, NULL, ONE_PT_CALIB) which lead to null\npointer dereference (if DEBUG or DYNAMIC_DEBUG set).\nFix this bug by adding null pointer check.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: Thermal/drivers/tsens: se corrigi\u00f3 la desreferencia del puntero nulo Compute_intercept_slope() se llama desde calibrate_8960() (en tsens-8960.c) como Compute_intercept_slope(priv, p1, NULL, ONE_PT_CALIB) lo que conduce a la desreferencia del puntero nulo (si DEBUG o DYNAMIC_DEBUG est\u00e1n configurados). Corrija este error agregando una verificaci\u00f3n de puntero nulo. Encontrado por el Centro de verificaci\u00f3n de Linux (linuxtesting.org) con SVACE." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38572.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38572.json index 2bc968a6d9c..5399d2e45fd 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38572.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38572.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38572", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:17.333", - "lastModified": "2024-06-19T14:15:17.333", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: ath12k: fix out-of-bound access of qmi_invoke_handler()\n\nCurrently, there is no terminator entry for ath12k_qmi_msg_handlers hence\nfacing below KASAN warning,\n\n ==================================================================\n BUG: KASAN: global-out-of-bounds in qmi_invoke_handler+0xa4/0x148\n Read of size 8 at addr ffffffd00a6428d8 by task kworker/u8:2/1273\n\n CPU: 0 PID: 1273 Comm: kworker/u8:2 Not tainted 5.4.213 #0\n Workqueue: qmi_msg_handler qmi_data_ready_work\n Call trace:\n dump_backtrace+0x0/0x20c\n show_stack+0x14/0x1c\n dump_stack+0xe0/0x138\n print_address_description.isra.5+0x30/0x330\n __kasan_report+0x16c/0x1bc\n kasan_report+0xc/0x14\n __asan_load8+0xa8/0xb0\n qmi_invoke_handler+0xa4/0x148\n qmi_handle_message+0x18c/0x1bc\n qmi_data_ready_work+0x4ec/0x528\n process_one_work+0x2c0/0x440\n worker_thread+0x324/0x4b8\n kthread+0x210/0x228\n ret_from_fork+0x10/0x18\n\n The address belongs to the variable:\n ath12k_mac_mon_status_filter_default+0x4bd8/0xfffffffffffe2300 [ath12k]\n [...]\n ==================================================================\n\nAdd a dummy terminator entry at the end to assist the qmi_invoke_handler()\nin traversing up to the terminator entry without accessing an\nout-of-boundary index.\n\nTested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.0.1-00029-QCAHKSWPL_SILICONZ-1" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: wifi: ath12k: corrige el acceso fuera de los l\u00edmites de qmi_invoke_handler() Actualmente, no hay ninguna entrada de terminador para ath12k_qmi_msg_handlers, por lo que se enfrenta a la siguiente advertencia de KASAN, ======== ==================================================== ======== ERROR: KASAN: global fuera de los l\u00edmites en qmi_invoke_handler+0xa4/0x148 Lectura de tama\u00f1o 8 en la direcci\u00f3n ffffffd00a6428d8 por tarea kworker/u8:2/1273 CPU: 0 PID: 1273 Comm: kworker /u8:2 No contaminado 5.4.213 #0 Cola de trabajo: qmi_msg_handler qmi_data_ready_work Rastreo de llamadas: dump_backtrace+0x0/0x20c show_stack+0x14/0x1c dump_stack+0xe0/0x138 print_address_description.isra.5+0x30/0x330 __kasan_report+0x16 c/0x1bc kasan_report+0xc /0x14 __asan_load8+0xa8/0xb0 qmi_invoke_handler+0xa4/0x148 qmi_handle_message+0x18c/0x1bc qmi_data_ready_work+0x4ec/0x528 Process_one_work+0x2c0/0x440 trabajador_thread+0x324/0x4b8 0x228 ret_from_fork+0x10/0x18 La direcci\u00f3n pertenece a la variable: ath12k_mac_mon_status_filter_default +0x4bd8/0xfffffffffffe2300 [ath12k] [...] ======================================= ============================ Agregue una entrada de terminador ficticia al final para ayudar a qmi_invoke_handler() a atravesar hasta la entrada del terminador sin acceder a un \u00edndice fuera de los l\u00edmites. Probado en: QCN9274 hw2.0 PCI WLAN.WBE.1.0.1-00029-QCAHKSWPL_SILICONZ-1" } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38573.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38573.json index c41d33305ab..773161ec001 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38573.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38573.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38573", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:17.420", - "lastModified": "2024-06-19T14:15:17.420", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ncppc_cpufreq: Fix possible null pointer dereference\n\ncppc_cpufreq_get_rate() and hisi_cppc_cpufreq_get_rate() can be called from\ndifferent places with various parameters. So cpufreq_cpu_get() can return\nnull as 'policy' in some circumstances.\nFix this bug by adding null return check.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: cppc_cpufreq: se corrige la posible desreferencia del puntero nulo. cppc_cpufreq_get_rate() y hisi_cppc_cpufreq_get_rate() se pueden llamar desde diferentes lugares con varios par\u00e1metros. Entonces cpufreq_cpu_get() puede devolver nulo como 'pol\u00edtica' en algunas circunstancias. Corrija este error agregando una verificaci\u00f3n de devoluci\u00f3n nula. Encontrado por el Centro de verificaci\u00f3n de Linux (linuxtesting.org) con SVACE." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38574.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38574.json index 18c5ab5fdd3..e3268433377 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38574.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38574.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38574", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:17.520", - "lastModified": "2024-06-19T14:15:17.520", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nlibbpf: Prevent null-pointer dereference when prog to load has no BTF\n\nIn bpf_objec_load_prog(), there's no guarantee that obj->btf is non-NULL\nwhen passing it to btf__fd(), and this function does not perform any\ncheck before dereferencing its argument (as bpf_object__btf_fd() used to\ndo). As a consequence, we get segmentation fault errors in bpftool (for\nexample) when trying to load programs that come without BTF information.\n\nv2: Keep btf__fd() in the fix instead of reverting to bpf_object__btf_fd()." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: libbpf: evita la desreferencia del puntero nulo cuando el programa a cargar no tiene BTF. En bpf_objec_load_prog(), no hay garant\u00eda de que obj->btf no sea NULL al pasarlo a btf__fd() , y esta funci\u00f3n no realiza ninguna verificaci\u00f3n antes de eliminar la referencia a su argumento (como sol\u00eda hacer bpf_object__btf_fd()). Como consecuencia, obtenemos errores de segmentaci\u00f3n en bpftool (por ejemplo) cuando intentamos cargar programas que vienen sin informaci\u00f3n BTF. v2: Mantenga btf__fd() en la soluci\u00f3n en lugar de volver a bpf_object__btf_fd()." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38575.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38575.json index 63b96317536..f40d8ee5f05 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38575.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38575.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38575", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:17.603", - "lastModified": "2024-06-19T14:15:17.603", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: brcmfmac: pcie: handle randbuf allocation failure\n\nThe kzalloc() in brcmf_pcie_download_fw_nvram() will return null\nif the physical memory has run out. As a result, if we use\nget_random_bytes() to generate random bytes in the randbuf, the\nnull pointer dereference bug will happen.\n\nIn order to prevent allocation failure, this patch adds a separate\nfunction using buffer on kernel stack to generate random bytes in\nthe randbuf, which could prevent the kernel stack from overflow." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: wifi: brcmfmac: pcie: manejar fallo de asignaci\u00f3n de randbuf El kzalloc() en brcmf_pcie_download_fw_nvram() devolver\u00e1 nulo si la memoria f\u00edsica se ha agotado. Como resultado, si usamos get_random_bytes() para generar bytes aleatorios en randbuf, se producir\u00e1 el error de desreferencia del puntero nulo. Para evitar fallas en la asignaci\u00f3n, este parche agrega una funci\u00f3n separada que utiliza el b\u00fafer en la pila del kernel para generar bytes aleatorios en randbuf, lo que podr\u00eda evitar que la pila del kernel se desborde." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38576.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38576.json index 72a1bfb45b6..df80d81ab3e 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38576.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38576.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38576", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:17.700", - "lastModified": "2024-06-19T14:15:17.700", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nrcu: Fix buffer overflow in print_cpu_stall_info()\n\nThe rcuc-starvation output from print_cpu_stall_info() might overflow the\nbuffer if there is a huge difference in jiffies difference. The situation\nmight seem improbable, but computers sometimes get very confused about\ntime, which can result in full-sized integers, and, in this case,\nbuffer overflow.\n\nAlso, the unsigned jiffies difference is printed using %ld, which is\nnormally for signed integers. This is intentional for debugging purposes,\nbut it is not obvious from the code.\n\nThis commit therefore changes sprintf() to snprintf() and adds a\nclarifying comment about intention of %ld format.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: rcu: corrige el desbordamiento del b\u00fafer en print_cpu_stall_info() La salida rcuc-starvation de print_cpu_stall_info() podr\u00eda desbordar el b\u00fafer si hay una gran diferencia en santiam\u00e9n. La situaci\u00f3n puede parecer improbable, pero las computadoras a veces se confunden mucho con el tiempo, lo que puede resultar en n\u00fameros enteros de tama\u00f1o completo y, en este caso, en un desbordamiento del b\u00fafer. Adem\u00e1s, la diferencia de santiam\u00e9n sin signo se imprime usando %ld, que normalmente es para enteros con signo. Esto es intencional con fines de depuraci\u00f3n, pero no es obvio en el c\u00f3digo. Por lo tanto, esta confirmaci\u00f3n cambia sprintf() a snprintf() y agrega un comentario aclaratorio sobre la intenci\u00f3n del formato %ld. Encontrado por el Centro de verificaci\u00f3n de Linux (linuxtesting.org) con SVACE." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38577.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38577.json index 94e272c5428..bd4b934c61a 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38577.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38577.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38577", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:17.787", - "lastModified": "2024-06-19T14:15:17.787", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nrcu-tasks: Fix show_rcu_tasks_trace_gp_kthread buffer overflow\n\nThere is a possibility of buffer overflow in\nshow_rcu_tasks_trace_gp_kthread() if counters, passed\nto sprintf() are huge. Counter numbers, needed for this\nare unrealistically high, but buffer overflow is still\npossible.\n\nUse snprintf() with buffer size instead of sprintf().\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: rcu-tasks: Corrige show_rcu_tasks_trace_gp_kthread desbordamiento del b\u00fafer. Existe la posibilidad de que se produzca un desbordamiento del b\u00fafer en show_rcu_tasks_trace_gp_kthread() si los contadores pasados a sprintf() son enormes. Los n\u00fameros de contador necesarios para esto son excesivamente altos, pero a\u00fan es posible un desbordamiento del b\u00fafer. Utilice snprintf() con tama\u00f1o de b\u00fafer en lugar de sprintf(). Encontrado por el Centro de verificaci\u00f3n de Linux (linuxtesting.org) con SVACE." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38578.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38578.json index 8cf033560f0..733c5f28d8c 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38578.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38578.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38578", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:17.870", - "lastModified": "2024-06-19T14:15:17.870", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\necryptfs: Fix buffer size for tag 66 packet\n\nThe 'TAG 66 Packet Format' description is missing the cipher code and\nchecksum fields that are packed into the message packet. As a result,\nthe buffer allocated for the packet is 3 bytes too small and\nwrite_tag_66_packet() will write up to 3 bytes past the end of the\nbuffer.\n\nFix this by increasing the size of the allocation so the whole packet\nwill always fit in the buffer.\n\nThis fixes the below kasan slab-out-of-bounds bug:\n\n BUG: KASAN: slab-out-of-bounds in ecryptfs_generate_key_packet_set+0x7d6/0xde0\n Write of size 1 at addr ffff88800afbb2a5 by task touch/181\n\n CPU: 0 PID: 181 Comm: touch Not tainted 6.6.13-gnu #1 4c9534092be820851bb687b82d1f92a426598dc6\n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2/GNU Guix 04/01/2014\n Call Trace:\n \n dump_stack_lvl+0x4c/0x70\n print_report+0xc5/0x610\n ? ecryptfs_generate_key_packet_set+0x7d6/0xde0\n ? kasan_complete_mode_report_info+0x44/0x210\n ? ecryptfs_generate_key_packet_set+0x7d6/0xde0\n kasan_report+0xc2/0x110\n ? ecryptfs_generate_key_packet_set+0x7d6/0xde0\n __asan_store1+0x62/0x80\n ecryptfs_generate_key_packet_set+0x7d6/0xde0\n ? __pfx_ecryptfs_generate_key_packet_set+0x10/0x10\n ? __alloc_pages+0x2e2/0x540\n ? __pfx_ovl_open+0x10/0x10 [overlay 30837f11141636a8e1793533a02e6e2e885dad1d]\n ? dentry_open+0x8f/0xd0\n ecryptfs_write_metadata+0x30a/0x550\n ? __pfx_ecryptfs_write_metadata+0x10/0x10\n ? ecryptfs_get_lower_file+0x6b/0x190\n ecryptfs_initialize_file+0x77/0x150\n ecryptfs_create+0x1c2/0x2f0\n path_openat+0x17cf/0x1ba0\n ? __pfx_path_openat+0x10/0x10\n do_filp_open+0x15e/0x290\n ? __pfx_do_filp_open+0x10/0x10\n ? __kasan_check_write+0x18/0x30\n ? _raw_spin_lock+0x86/0xf0\n ? __pfx__raw_spin_lock+0x10/0x10\n ? __kasan_check_write+0x18/0x30\n ? alloc_fd+0xf4/0x330\n do_sys_openat2+0x122/0x160\n ? __pfx_do_sys_openat2+0x10/0x10\n __x64_sys_openat+0xef/0x170\n ? __pfx___x64_sys_openat+0x10/0x10\n do_syscall_64+0x60/0xd0\n entry_SYSCALL_64_after_hwframe+0x6e/0xd8\n RIP: 0033:0x7f00a703fd67\n Code: 25 00 00 41 00 3d 00 00 41 00 74 37 64 8b 04 25 18 00 00 00 85 c0 75 5b 44 89 e2 48 89 ee bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 85 00 00 00 48 83 c4 68 5d 41 5c c3 0f 1f\n RSP: 002b:00007ffc088e30b0 EFLAGS: 00000246 ORIG_RAX: 0000000000000101\n RAX: ffffffffffffffda RBX: 00007ffc088e3368 RCX: 00007f00a703fd67\n RDX: 0000000000000941 RSI: 00007ffc088e48d7 RDI: 00000000ffffff9c\n RBP: 00007ffc088e48d7 R08: 0000000000000001 R09: 0000000000000000\n R10: 00000000000001b6 R11: 0000000000000246 R12: 0000000000000941\n R13: 0000000000000000 R14: 00007ffc088e48d7 R15: 00007f00a7180040\n \n\n Allocated by task 181:\n kasan_save_stack+0x2f/0x60\n kasan_set_track+0x29/0x40\n kasan_save_alloc_info+0x25/0x40\n __kasan_kmalloc+0xc5/0xd0\n __kmalloc+0x66/0x160\n ecryptfs_generate_key_packet_set+0x6d2/0xde0\n ecryptfs_write_metadata+0x30a/0x550\n ecryptfs_initialize_file+0x77/0x150\n ecryptfs_create+0x1c2/0x2f0\n path_openat+0x17cf/0x1ba0\n do_filp_open+0x15e/0x290\n do_sys_openat2+0x122/0x160\n __x64_sys_openat+0xef/0x170\n do_syscall_64+0x60/0xd0\n entry_SYSCALL_64_after_hwframe+0x6e/0xd8" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: ecryptfs: corrige el tama\u00f1o del b\u00fafer para el paquete etiqueta 66. A la descripci\u00f3n 'Formato de paquete TAG 66' le faltan el c\u00f3digo de cifrado y los campos de suma de verificaci\u00f3n que est\u00e1n empaquetados en el paquete de mensaje. Como resultado, el b\u00fafer asignado para el paquete es 3 bytes demasiado peque\u00f1o y write_tag_66_packet() escribir\u00e1 hasta 3 bytes m\u00e1s all\u00e1 del final del b\u00fafer. Solucione este problema aumentando el tama\u00f1o de la asignaci\u00f3n para que todo el paquete siempre quepa en el b\u00fafer. Esto corrige el siguiente error de kasan slab-out-of-bounds: ERROR: KASAN: slab-out-of-bounds in ecryptfs_generate_key_packet_set+0x7d6/0xde0 Escritura de tama\u00f1o 1 en la direcci\u00f3n ffff88800afbb2a5 mediante tarea t\u00e1ctil/181 CPU: 0 PID: 181 Comm : touch No contaminado 6.6.13-gnu #1 4c9534092be820851bb687b82d1f92a426598dc6 Nombre del hardware: PC est\u00e1ndar QEMU (i440FX + PIIX, 1996), BIOS 1.16.2/GNU Guix 01/04/2014 Seguimiento de llamadas: 3d 00 f0 ff ff 0f 87 85 00 00 00 48 83 c4 68 5d 41 5c c3 0f 1f RSP: 002b:00007ffc088e30b0 EFLAGS: 00000246 ORIG_RAX: 0000000000000101 RAX : ffffffffffffffda RBX: 00007ffc088e3368 RCX: 00007f00a703fd67 RDX: 0000000000000941 RSI: 00007ffc088e48d7 RDI: 00000000ffffff9c RBP: 00007ffc088e4 8d7 R08: 0000000000000001 R09: 0000000000000000 R10: 00000000000001b6 R11: 0000000000000246 R12: 0000000000000941 R13: 00000 R14: 00007ffc088e48d7 R15: 00007f00a7180040 Asignado por tarea 181: kasan_save_stack+0x2f/0x60 kasan_set_track+0x29/0x40 kasan_save_alloc_info+0x25/0x40 __kasan_kmalloc+0xc5/0xd0 __kmalloc+0x66/0x160 ecryptfs_generate_key_packet_set+0x6d2/0xde0 _write_metadata+0x30a/0x550 ecryptfs_initialize_file+0x77/0x150 ecryptfs_create+0x1c2/0x2f0 ruta_openat+ 0x17cf/0x1ba0 do_filp_open+0x15e/0x290 do_sys_openat2+0x122/0x160 __x64_sys_openat+0xef/0x170 do_syscall_64+0x60/0xd0 Entry_SYSCALL_64_after_hwframe+0x6e/0xd8" } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38579.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38579.json index 01fbed1cb7c..3ce7c3b27fa 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38579.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38579.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38579", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:17.960", - "lastModified": "2024-06-19T14:15:17.960", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: bcm - Fix pointer arithmetic\n\nIn spu2_dump_omd() value of ptr is increased by ciph_key_len\ninstead of hash_iv_len which could lead to going beyond the\nbuffer boundaries.\nFix this bug by changing ciph_key_len to hash_iv_len.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: crypto: bcm - Arreglar la aritm\u00e9tica de punteros En spu2_dump_omd() el valor de ptr aumenta en ciph_key_len en lugar de hash_iv_len, lo que podr\u00eda llevar a ir m\u00e1s all\u00e1 de los l\u00edmites del b\u00fafer. Corrija este error cambiando ciph_key_len a hash_iv_len. Encontrado por el Centro de verificaci\u00f3n de Linux (linuxtesting.org) con SVACE." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38580.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38580.json index ef942708d4a..6327c89a0c3 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38580.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38580.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38580", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:18.057", - "lastModified": "2024-06-19T14:15:18.057", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nepoll: be better about file lifetimes\n\nepoll can call out to vfs_poll() with a file pointer that may race with\nthe last 'fput()'. That would make f_count go down to zero, and while\nthe ep->mtx locking means that the resulting file pointer tear-down will\nbe blocked until the poll returns, it means that f_count is already\ndead, and any use of it won't actually get a reference to the file any\nmore: it's dead regardless.\n\nMake sure we have a valid ref on the file pointer before we call down to\nvfs_poll() from the epoll routines." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: epoll: mejore la duraci\u00f3n de los archivos epoll puede llamar a vfs_poll() con un puntero de archivo que puede competir con el \u00faltimo 'fput()'. Eso har\u00eda que f_count bajara a cero, y aunque el bloqueo ep->mtx significa que el desmontaje del puntero del archivo resultante se bloquear\u00e1 hasta que regrese la encuesta, significa que f_count ya est\u00e1 muerto y no se podr\u00e1 utilizar. De hecho, ya no obtengo una referencia al archivo: est\u00e1 muerto de todos modos. Aseg\u00farese de tener una referencia v\u00e1lida en el puntero del archivo antes de llamar a vfs_poll() desde las rutinas de epoll." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38581.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38581.json index 3f0fed41a21..56327cff18b 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38581.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38581.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38581", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:18.150", - "lastModified": "2024-06-19T14:15:18.150", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu/mes: fix use-after-free issue\n\nDelete fence fallback timer to fix the ramdom\nuse-after-free issue.\n\nv2: move to amdgpu_mes.c" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: drm/amdgpu/mes: soluciona el problema de use-after-free. Elimina el temporizador de reserva de valla para solucionar el problema de use-after-free. v2: pasar a amdgpu_mes.c" } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38582.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38582.json index f0c28a98e71..9644defe790 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38582.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38582.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38582", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:18.273", - "lastModified": "2024-06-19T14:15:18.273", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnilfs2: fix potential hang in nilfs_detach_log_writer()\n\nSyzbot has reported a potential hang in nilfs_detach_log_writer() called\nduring nilfs2 unmount.\n\nAnalysis revealed that this is because nilfs_segctor_sync(), which\nsynchronizes with the log writer thread, can be called after\nnilfs_segctor_destroy() terminates that thread, as shown in the call trace\nbelow:\n\nnilfs_detach_log_writer\n nilfs_segctor_destroy\n nilfs_segctor_kill_thread --> Shut down log writer thread\n flush_work\n nilfs_iput_work_func\n nilfs_dispose_list\n iput\n nilfs_evict_inode\n nilfs_transaction_commit\n nilfs_construct_segment (if inode needs sync)\n nilfs_segctor_sync --> Attempt to synchronize with\n log writer thread\n *** DEADLOCK ***\n\nFix this issue by changing nilfs_segctor_sync() so that the log writer\nthread returns normally without synchronizing after it terminates, and by\nforcing tasks that are already waiting to complete once after the thread\nterminates.\n\nThe skipped inode metadata flushout will then be processed together in the\nsubsequent cleanup work in nilfs_segctor_destroy()." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: nilfs2: soluciona un posible bloqueo en nilfs_detach_log_writer() Syzbot ha informado de un posible bloqueo en nilfs_detach_log_writer() llamado durante el desmontaje de nilfs2. El an\u00e1lisis revel\u00f3 que esto se debe a que nilfs_segctor_sync(), que se sincroniza con el hilo del escritor de registros, puede ser llamado despu\u00e9s de que nilfs_segctor_destroy() finalice ese hilo, como se muestra en el seguimiento de llamadas a continuaci\u00f3n: nilfs_detach_log_writer nilfs_segctor_destroy nilfs_segctor_kill_thread --> Apagar el hilo del escritor de registros Flush_work nilfs_iput_work_func nilfs_dispose_list iput nilfs_evict_inode nilfs_transaction_commit nilfs_construct_segment (si el inodo necesita sincronizaci\u00f3n) nilfs_segctor_sync --> Intente sincronizar con el hilo del escritor de registros *** DEADLOCK *** Solucione este problema cambiando nilfs_segctor_sync() para que el hilo del escritor de registros regrese normalmente sin sincronizarse despu\u00e9s de que termine y forzando las tareas que ya est\u00e1n esperando a completarse una vez que finaliza el hilo. La eliminaci\u00f3n de metadatos del inodo omitido se procesar\u00e1 en conjunto en el trabajo de limpieza posterior en nilfs_segctor_destroy()." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38583.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38583.json index 52fa4e409b9..b9a15ebdbfd 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38583.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38583.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38583", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:18.397", - "lastModified": "2024-06-19T14:15:18.397", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnilfs2: fix use-after-free of timer for log writer thread\n\nPatch series \"nilfs2: fix log writer related issues\".\n\nThis bug fix series covers three nilfs2 log writer-related issues,\nincluding a timer use-after-free issue and potential deadlock issue on\nunmount, and a potential freeze issue in event synchronization found\nduring their analysis. Details are described in each commit log.\n\n\nThis patch (of 3):\n\nA use-after-free issue has been reported regarding the timer sc_timer on\nthe nilfs_sc_info structure.\n\nThe problem is that even though it is used to wake up a sleeping log\nwriter thread, sc_timer is not shut down until the nilfs_sc_info structure\nis about to be freed, and is used regardless of the thread's lifetime.\n\nFix this issue by limiting the use of sc_timer only while the log writer\nthread is alive." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: nilfs2: corrige el use-after-free del temporizador para el hilo del escritor de registros Serie de parches \"nilfs2: corrige problemas relacionados con el escritor de registros\". Esta serie de correcci\u00f3n de errores cubre tres problemas relacionados con el escritor de registros nilfs2, incluido un problema de use-after-free del temporizador y un posible problema de bloqueo al desmontar, y un posible problema de congelaci\u00f3n en la sincronizaci\u00f3n de eventos encontrado durante su an\u00e1lisis. Los detalles se describen en cada registro de confirmaci\u00f3n. Este parche (de 3): Se inform\u00f3 un problema de use-after-free con respecto al temporizador sc_timer en la estructura nilfs_sc_info. El problema es que, aunque se utiliza para reactivar un subproceso de escritura de registros inactivo, sc_timer no se cierra hasta que la estructura nilfs_sc_info est\u00e1 a punto de liberarse y se utiliza independientemente de la vida \u00fatil del subproceso. Solucione este problema limitando el uso de sc_timer solo mientras el subproceso del escritor de registros est\u00e9 activo." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38584.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38584.json index 8b8cb1575d8..14b88f3d4bf 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38584.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38584.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38584", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:18.530", - "lastModified": "2024-06-19T14:15:18.530", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: ti: icssg_prueth: Fix NULL pointer dereference in prueth_probe()\n\nIn the prueth_probe() function, if one of the calls to emac_phy_connect()\nfails due to of_phy_connect() returning NULL, then the subsequent call to\nphy_attached_info() will dereference a NULL pointer.\n\nCheck the return code of emac_phy_connect and fail cleanly if there is an\nerror." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: net: ti: icssg_prueth: corrige la desreferencia del puntero NULL en prueth_probe() En la funci\u00f3n prueth_probe(), si una de las llamadas a emac_phy_connect() falla debido a que of_phy_connect() devuelve NULL , entonces la llamada posterior a phy_attached_info() eliminar\u00e1 la referencia a un puntero NULL. Verifique el c\u00f3digo de retorno de emac_phy_connect y falle limpiamente si hay un error." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38585.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38585.json index cd6bf093678..60e9554b62a 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38585.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38585.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38585", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:18.610", - "lastModified": "2024-06-19T14:15:18.610", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ntools/nolibc/stdlib: fix memory error in realloc()\n\nPass user_p_len to memcpy() instead of heap->len to prevent realloc()\nfrom copying an extra sizeof(heap) bytes from beyond the allocated\nregion." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: tools/nolibc/stdlib: corrige el error de memoria en realloc() Pase user_p_len a memcpy() en lugar de heap->len para evitar que realloc() copie un tama\u00f1o extra de(heap) bytes m\u00e1s all\u00e1 de la regi\u00f3n asignada." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38586.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38586.json index d49af4808ec..1355be885ab 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38586.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38586.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38586", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:18.700", - "lastModified": "2024-06-19T14:15:18.700", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nr8169: Fix possible ring buffer corruption on fragmented Tx packets.\n\nAn issue was found on the RTL8125b when transmitting small fragmented\npackets, whereby invalid entries were inserted into the transmit ring\nbuffer, subsequently leading to calls to dma_unmap_single() with a null\naddress.\n\nThis was caused by rtl8169_start_xmit() not noticing changes to nr_frags\nwhich may occur when small packets are padded (to work around hardware\nquirks) in rtl8169_tso_csum_v2().\n\nTo fix this, postpone inspecting nr_frags until after any padding has been\napplied." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: r8169: corrige una posible corrupci\u00f3n del b\u00fafer en anillo en paquetes Tx fragmentados. Se encontr\u00f3 un problema en el RTL8125b al transmitir peque\u00f1os paquetes fragmentados, por el cual se insertaban entradas no v\u00e1lidas en el b\u00fafer del anillo de transmisi\u00f3n, lo que posteriormente generaba llamadas a dma_unmap_single() con una direcci\u00f3n nula. Esto se debi\u00f3 a que rtl8169_start_xmit() no not\u00f3 los cambios en nr_frags que pueden ocurrir cuando se rellenan paquetes peque\u00f1os (para evitar peculiaridades del hardware) en rtl8169_tso_csum_v2(). Para solucionar este problema, posponga la inspecci\u00f3n de nr_frags hasta que se haya aplicado el relleno." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38587.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38587.json index 12afba57eb5..6a115aaa93c 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38587.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38587.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38587", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:18.800", - "lastModified": "2024-06-19T14:15:18.800", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nspeakup: Fix sizeof() vs ARRAY_SIZE() bug\n\nThe \"buf\" pointer is an array of u16 values. This code should be\nusing ARRAY_SIZE() (which is 256) instead of sizeof() (which is 512),\notherwise it can the still got out of bounds." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: Speakup: corrige el error sizeof() vs ARRAY_SIZE() El puntero \"buf\" es una matriz de valores u16. Este c\u00f3digo deber\u00eda usar ARRAY_SIZE() (que es 256) en lugar de sizeof() (que es 512), de lo contrario a\u00fan puede salirse de los l\u00edmites." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38588.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38588.json index e75f8a5dff9..143a27d5a64 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38588.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38588.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38588", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:18.907", - "lastModified": "2024-06-19T14:15:18.907", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nftrace: Fix possible use-after-free issue in ftrace_location()\n\nKASAN reports a bug:\n\n BUG: KASAN: use-after-free in ftrace_location+0x90/0x120\n Read of size 8 at addr ffff888141d40010 by task insmod/424\n CPU: 8 PID: 424 Comm: insmod Tainted: G W 6.9.0-rc2+\n [...]\n Call Trace:\n \n dump_stack_lvl+0x68/0xa0\n print_report+0xcf/0x610\n kasan_report+0xb5/0xe0\n ftrace_location+0x90/0x120\n register_kprobe+0x14b/0xa40\n kprobe_init+0x2d/0xff0 [kprobe_example]\n do_one_initcall+0x8f/0x2d0\n do_init_module+0x13a/0x3c0\n load_module+0x3082/0x33d0\n init_module_from_file+0xd2/0x130\n __x64_sys_finit_module+0x306/0x440\n do_syscall_64+0x68/0x140\n entry_SYSCALL_64_after_hwframe+0x71/0x79\n\nThe root cause is that, in lookup_rec(), ftrace record of some address\nis being searched in ftrace pages of some module, but those ftrace pages\nat the same time is being freed in ftrace_release_mod() as the\ncorresponding module is being deleted:\n\n CPU1 | CPU2\n register_kprobes() { | delete_module() {\n check_kprobe_address_safe() { |\n arch_check_ftrace_location() { |\n ftrace_location() { |\n lookup_rec() // USE! | ftrace_release_mod() // Free!\n\nTo fix this issue:\n 1. Hold rcu lock as accessing ftrace pages in ftrace_location_range();\n 2. Use ftrace_location_range() instead of lookup_rec() in\n ftrace_location();\n 3. Call synchronize_rcu() before freeing any ftrace pages both in\n ftrace_process_locs()/ftrace_release_mod()/ftrace_free_mem()." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: ftrace: Solucionar posible problema de use-after-free en ftrace_location() KASAN informa un error: ERROR: KASAN: use-after-free en ftrace_location+0x90/0x120 Lectura de tama\u00f1o 8 en addr ffff888141d40010 por tarea insmod/424 CPU: 8 PID: 424 Comm: insmod Tainted: GW 6.9.0-rc2+ [...] Rastreo de llamadas: dump_stack_lvl+0x68/0xa0 print_report+0xcf/0x610 kasan_report+0xb5/ 0xe0 ftrace_location+0x90/0x120 Register_kprobe+0x14b/0xa40 kprobe_init+0x2d/0xff0 [kprobe_example] do_one_initcall+0x8f/0x2d0 do_init_module+0x13a/0x3c0 load_module+0x3082/0x33d0 init_module_from _file+0xd2/0x130 __x64_sys_finit_module+0x306/0x440 do_syscall_64+0x68/0x140 entrada_SYSCALL_64_after_hwframe +0x71/0x79 La causa principal es que, en lookup_rec(), el registro ftrace de alguna direcci\u00f3n se busca en las p\u00e1ginas ftrace de alg\u00fan m\u00f3dulo, pero esas p\u00e1ginas ftrace al mismo tiempo se liberan en ftrace_release_mod() como lo est\u00e1 el m\u00f3dulo correspondiente. siendo eliminado: CPU1 | CPU2 registro_kprobes() { | eliminar_m\u00f3dulo() { check_kprobe_address_safe() { | arch_check_ftrace_location() { | ftrace_ubicaci\u00f3n() { | lookup_rec() // \u00a1UTILIZAR! | ftrace_release_mod() // \u00a1Gratis! Para solucionar este problema: 1. Mantenga presionado rcu lock mientras accede a las p\u00e1ginas de ftrace en ftrace_location_range(); 2. Utilice ftrace_location_range() en lugar de lookup_rec() en ftrace_location(); 3. Llame a sincronizar_rcu() antes de liberar cualquier p\u00e1gina ftrace tanto en ftrace_process_locs()/ftrace_release_mod()/ftrace_free_mem()." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38589.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38589.json index d46eb22c82a..f0a1334558f 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38589.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38589.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38589", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:19.000", - "lastModified": "2024-06-19T14:15:19.000", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnetrom: fix possible dead-lock in nr_rt_ioctl()\n\nsyzbot loves netrom, and found a possible deadlock in nr_rt_ioctl [1]\n\nMake sure we always acquire nr_node_list_lock before nr_node_lock(nr_node)\n\n[1]\nWARNING: possible circular locking dependency detected\n6.9.0-rc7-syzkaller-02147-g654de42f3fc6 #0 Not tainted\n------------------------------------------------------\nsyz-executor350/5129 is trying to acquire lock:\n ffff8880186e2070 (&nr_node->node_lock){+...}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:356 [inline]\n ffff8880186e2070 (&nr_node->node_lock){+...}-{2:2}, at: nr_node_lock include/net/netrom.h:152 [inline]\n ffff8880186e2070 (&nr_node->node_lock){+...}-{2:2}, at: nr_dec_obs net/netrom/nr_route.c:464 [inline]\n ffff8880186e2070 (&nr_node->node_lock){+...}-{2:2}, at: nr_rt_ioctl+0x1bb/0x1090 net/netrom/nr_route.c:697\n\nbut task is already holding lock:\n ffffffff8f7053b8 (nr_node_list_lock){+...}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:356 [inline]\n ffffffff8f7053b8 (nr_node_list_lock){+...}-{2:2}, at: nr_dec_obs net/netrom/nr_route.c:462 [inline]\n ffffffff8f7053b8 (nr_node_list_lock){+...}-{2:2}, at: nr_rt_ioctl+0x10a/0x1090 net/netrom/nr_route.c:697\n\nwhich lock already depends on the new lock.\n\nthe existing dependency chain (in reverse order) is:\n\n-> #1 (nr_node_list_lock){+...}-{2:2}:\n lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5754\n __raw_spin_lock_bh include/linux/spinlock_api_smp.h:126 [inline]\n _raw_spin_lock_bh+0x35/0x50 kernel/locking/spinlock.c:178\n spin_lock_bh include/linux/spinlock.h:356 [inline]\n nr_remove_node net/netrom/nr_route.c:299 [inline]\n nr_del_node+0x4b4/0x820 net/netrom/nr_route.c:355\n nr_rt_ioctl+0xa95/0x1090 net/netrom/nr_route.c:683\n sock_do_ioctl+0x158/0x460 net/socket.c:1222\n sock_ioctl+0x629/0x8e0 net/socket.c:1341\n vfs_ioctl fs/ioctl.c:51 [inline]\n __do_sys_ioctl fs/ioctl.c:904 [inline]\n __se_sys_ioctl+0xfc/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\n-> #0 (&nr_node->node_lock){+...}-{2:2}:\n check_prev_add kernel/locking/lockdep.c:3134 [inline]\n check_prevs_add kernel/locking/lockdep.c:3253 [inline]\n validate_chain+0x18cb/0x58e0 kernel/locking/lockdep.c:3869\n __lock_acquire+0x1346/0x1fd0 kernel/locking/lockdep.c:5137\n lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5754\n __raw_spin_lock_bh include/linux/spinlock_api_smp.h:126 [inline]\n _raw_spin_lock_bh+0x35/0x50 kernel/locking/spinlock.c:178\n spin_lock_bh include/linux/spinlock.h:356 [inline]\n nr_node_lock include/net/netrom.h:152 [inline]\n nr_dec_obs net/netrom/nr_route.c:464 [inline]\n nr_rt_ioctl+0x1bb/0x1090 net/netrom/nr_route.c:697\n sock_do_ioctl+0x158/0x460 net/socket.c:1222\n sock_ioctl+0x629/0x8e0 net/socket.c:1341\n vfs_ioctl fs/ioctl.c:51 [inline]\n __do_sys_ioctl fs/ioctl.c:904 [inline]\n __se_sys_ioctl+0xfc/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\nother info that might help us debug this:\n\n Possible unsafe locking scenario:\n\n CPU0 CPU1\n ---- ----\n lock(nr_node_list_lock);\n lock(&nr_node->node_lock);\n lock(nr_node_list_lock);\n lock(&nr_node->node_lock);\n\n *** DEADLOCK ***\n\n1 lock held by syz-executor350/5129:\n #0: ffffffff8f7053b8 (nr_node_list_lock){+...}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:356 [inline]\n #0: ffffffff8f7053b8 (nr_node_list_lock){+...}-{2:2}, at: nr_dec_obs net/netrom/nr_route.c:462 [inline]\n #0: ffffffff8f70\n---truncated---" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: netrom: solucion\u00f3 un posible bloqueo en nr_rt_ioctl() syzbot ama netrom y encontr\u00f3 un posible bloqueo en nr_rt_ioctl [1] Aseg\u00farese de adquirir siempre nr_node_list_lock antes de nr_node_lock(nr_node) [1 ] ADVERTENCIA: se detect\u00f3 posible dependencia de bloqueo circular 6.9.0-rc7-syzkaller-02147-g654de42f3fc6 #0 No contaminado --------------------- --------------------- syz-executor350/5129 est\u00e1 intentando adquirir el bloqueo: ffff8880186e2070 (&nr_node->node_lock){+... }-{2:2}, en: spin_lock_bh include/linux/spinlock.h:356 [en l\u00ednea] ffff8880186e2070 (&nr_node->node_lock){+...}-{2:2}, en: nr_node_lock include/net/ netrom.h:152 [en l\u00ednea] ffff8880186e2070 (&nr_node->node_lock){+...}-{2:2}, en: nr_dec_obs net/netrom/nr_route.c:464 [en l\u00ednea] ffff8880186e2070 (&nr_node->node_lock) {+...}-{2:2}, en: nr_rt_ioctl+0x1bb/0x1090 net/netrom/nr_route.c:697 pero la tarea ya est\u00e1 bloqueada: fffffffff8f7053b8 (nr_node_list_lock){+...}-{2: 2}, en: spin_lock_bh include/linux/spinlock.h:356 [en l\u00ednea] fffffff8f7053b8 (nr_node_list_lock){+...}-{2:2}, en: nr_dec_obs net/netrom/nr_route.c:462 [en l\u00ednea] ffffffff8f7053b8 (nr_node_list_lock){+...}-{2:2}, en: nr_rt_ioctl+0x10a/0x1090 net/netrom/nr_route.c:697 cuyo bloqueo ya depende del nuevo bloqueo. la cadena de dependencia existente (en orden inverso) es: -> #1 (nr_node_list_lock){+...}-{2:2}: lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5754 __raw_spin_lock_bh include/linux/ spinlock_api_smp.h:126 [en l\u00ednea] _raw_spin_lock_bh+0x35/0x50 kernel/locking/spinlock.c:178 spin_lock_bh include/linux/spinlock.h:356 [en l\u00ednea] nr_remove_node net/netrom/nr_route.c:299 [en l\u00ednea] nr_del_node+ 0x4b4/0x820 net/netrom/nr_route.c:355 nr_rt_ioctl+0xa95/0x1090 net/netrom/nr_route.c:683 sock_do_ioctl+0x158/0x460 net/socket.c:1222 sock_ioctl+0x629/0x8e0 net/socket.c:13 41 vfs_ioctl fs/ioctl.c:51 [en l\u00ednea] __do_sys_ioctl fs/ioctl.c:904 [en l\u00ednea] __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:890 do_syscall_x64 arch/x86/entry/common.c:52 [en l\u00ednea] do_syscall_64 +0xf5/0x240 arch/x86/entry/common.c:83 Entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (&nr_node->node_lock){+...}-{2:2}: check_prev_add kernel/locking/lockdep. c:3134 [en l\u00ednea] check_prevs_add kernel/locking/lockdep.c:3253 [en l\u00ednea] validar_chain+0x18cb/0x58e0 kernel/locking/lockdep.c:3869 __lock_acquire+0x1346/0x1fd0 kernel/locking/lockdep.c:5137 lock_acquire+0x1ed /0x550 kernel/locking/lockdep.c:5754 __raw_spin_lock_bh include/linux/spinlock_api_smp.h:126 [en l\u00ednea] _raw_spin_lock_bh+0x35/0x50 kernel/locking/spinlock.c:178 spin_lock_bh include/linux/spinlock.h:356 [en l\u00ednea ] nr_node_lock include/net/netrom.h:152 [en l\u00ednea] nr_dec_obs net/netrom/nr_route.c:464 [en l\u00ednea] nr_rt_ioctl+0x1bb/0x1090 net/netrom/nr_route.c:697 sock_do_ioctl+0x158/0x460 net/socket. c:1222 sock_ioctl+0x629/0x8e0 net/socket.c:1341 vfs_ioctl fs/ioctl.c:51 [en l\u00ednea] __do_sys_ioctl fs/ioctl.c:904 [en l\u00ednea] __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:890 llamada_x64 arch/x86/entry/common.c:52 [en l\u00ednea] do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83 Entry_SYSCALL_64_after_hwframe+0x77/0x7f otra informaci\u00f3n que podr\u00eda ayudarnos a depurar esto: Posible escenario de bloqueo inseguro: CPU0 CPU1 ---- ---- bloqueo(nr_node_list_lock); bloquear(&nr_nodo->nodo_lock); bloquear(nr_node_list_lock); bloquear(&nr_nodo->nodo_lock); *** DEADLOCK *** 1 bloqueo retenido por syz-executor350/5129: #0: ffffffff8f7053b8 (nr_node_list_lock){+...}-{2:2}, en: spin_lock_bh include/linux/spinlock.h:356 [ en l\u00ednea] #0: ffffffff8f7053b8 (nr_node_list_lock){+...}-{2:2}, en: nr_dec_obs net/netrom/nr_route.c:462 [en l\u00ednea] #0: ffffffff8f70 ---truncado---" } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38590.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38590.json index 82d081fb153..7804dc55327 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38590.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38590.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38590", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:19.113", - "lastModified": "2024-06-19T14:15:19.113", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/hns: Modify the print level of CQE error\n\nToo much print may lead to a panic in kernel. Change ibdev_err() to\nibdev_err_ratelimited(), and change the printing level of cqe dump\nto debug level." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: RDMA/hns: Modifique el nivel de impresi\u00f3n del error CQE. Demasiada impresi\u00f3n puede provocar p\u00e1nico en el kernel. Cambie ibdev_err() a ibdev_err_ratelimited() y cambie el nivel de impresi\u00f3n del volcado cqe al nivel de depuraci\u00f3n." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38591.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38591.json index 8bbbcc1eda4..adaa1657dd4 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38591.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38591.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38591", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:19.207", - "lastModified": "2024-06-19T14:15:19.207", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/hns: Fix deadlock on SRQ async events.\n\nxa_lock for SRQ table may be required in AEQ. Use xa_store_irq()/\nxa_erase_irq() to avoid deadlock." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: RDMA/hns: corrige el punto muerto en eventos as\u00edncronos de SRQ. Es posible que se requiera xa_lock para la tabla SRQ en AEQ. Utilice xa_store_irq()/ xa_erase_irq() para evitar un punto muerto." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38592.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38592.json index db53d2e78de..e3d5d949d66 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38592.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38592.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38592", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:19.297", - "lastModified": "2024-06-19T14:15:19.297", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/mediatek: Init `ddp_comp` with devm_kcalloc()\n\nIn the case where `conn_routes` is true we allocate an extra slot in\nthe `ddp_comp` array but mtk_drm_crtc_create() never seemed to\ninitialize it in the test case I ran. For me, this caused a later\ncrash when we looped through the array in mtk_drm_crtc_mode_valid().\nThis showed up for me when I booted with `slub_debug=FZPUA` which\npoisons the memory initially. Without `slub_debug` I couldn't\nreproduce, presumably because the later code handles the value being\nNULL and in most cases (not guaranteed in all cases) the memory the\nallocator returned started out as 0.\n\nIt really doesn't hurt to initialize the array with devm_kcalloc()\nsince the array is small and the overhead of initting a handful of\nelements to 0 is small. In general initting memory to zero is a safer\npractice and usually it's suggested to only use the non-initting alloc\nfunctions if you really need to.\n\nLet's switch the function to use an allocation function that zeros the\nmemory. For me, this avoids the crash." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: drm/mediatek: Init `ddp_comp` con devm_kcalloc() En el caso de que `conn_routes` sea verdadero, asignamos una ranura adicional en la matriz `ddp_comp` pero mtk_drm_crtc_create() nunca apareci\u00f3 para inicializarlo en el caso de prueba que ejecut\u00e9. Para m\u00ed, esto provoc\u00f3 un bloqueo posterior cuando recorrimos la matriz en mtk_drm_crtc_mode_valid(). Esto me apareci\u00f3 cuando arranqu\u00e9 con `slub_debug=FZPUA` que envenena la memoria inicialmente. Sin `slub_debug` no pude reproducir, presumiblemente porque el c\u00f3digo posterior maneja que el valor sea NULL y en la mayor\u00eda de los casos (no garantizado en todos los casos) la memoria que devolvi\u00f3 el asignador comenz\u00f3 como 0. Realmente no est\u00e1 de m\u00e1s inicializar el array con devm_kcalloc() ya que la matriz es peque\u00f1a y la sobrecarga de iniciar un pu\u00f1ado de elementos en 0 es peque\u00f1a. En general, iniciar la memoria a cero es una pr\u00e1ctica m\u00e1s segura y, por lo general, se sugiere usar solo las funciones de asignaci\u00f3n que no son de inicio si realmente es necesario. Cambiemos la funci\u00f3n para usar una funci\u00f3n de asignaci\u00f3n que ponga a cero la memoria. Para m\u00ed, esto evita el accidente." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38593.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38593.json index c196fd63c0a..d33c48dd7c9 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38593.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38593.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38593", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:19.387", - "lastModified": "2024-06-19T14:15:19.387", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: micrel: Fix receiving the timestamp in the frame for lan8841\n\nThe blamed commit started to use the ptp workqueue to get the second\npart of the timestamp. And when the port was set down, then this\nworkqueue is stopped. But if the config option NETWORK_PHY_TIMESTAMPING\nis not enabled, then the ptp_clock is not initialized so then it would\ncrash when it would try to access the delayed work.\nSo then basically by setting up and then down the port, it would crash.\nThe fix consists in checking if the ptp_clock is initialized and only\nthen cancel the delayed work." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: net: micrel: Se corrigi\u00f3 la recepci\u00f3n de la marca de tiempo en el framework para lan8841. El commit culpable comenz\u00f3 a usar la cola de trabajo ptp para obtener la segunda parte de la marca de tiempo. Y cuando se establece el puerto, esta cola de trabajo se detiene. Pero si la opci\u00f3n de configuraci\u00f3n NETWORK_PHY_TIMESTAMPING no est\u00e1 habilitada, entonces ptp_clock no se inicializa, por lo que se bloquear\u00e1 cuando intente acceder al trabajo retrasado. Entonces, b\u00e1sicamente, al configurar y luego desactivar el puerto, fallar\u00eda. La soluci\u00f3n consiste en comprobar si el ptp_clock est\u00e1 inicializado y s\u00f3lo entonces cancelar el trabajo retrasado." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38594.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38594.json index 3be49fa1f7d..01bb5622028 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38594.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38594.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38594", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:19.467", - "lastModified": "2024-06-19T14:15:19.467", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: stmmac: move the EST lock to struct stmmac_priv\n\nReinitialize the whole EST structure would also reset the mutex\nlock which is embedded in the EST structure, and then trigger\nthe following warning. To address this, move the lock to struct\nstmmac_priv. We also need to reacquire the mutex lock when doing\nthis initialization.\n\nDEBUG_LOCKS_WARN_ON(lock->magic != lock)\nWARNING: CPU: 3 PID: 505 at kernel/locking/mutex.c:587 __mutex_lock+0xd84/0x1068\n Modules linked in:\n CPU: 3 PID: 505 Comm: tc Not tainted 6.9.0-rc6-00053-g0106679839f7-dirty #29\n Hardware name: NXP i.MX8MPlus EVK board (DT)\n pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n pc : __mutex_lock+0xd84/0x1068\n lr : __mutex_lock+0xd84/0x1068\n sp : ffffffc0864e3570\n x29: ffffffc0864e3570 x28: ffffffc0817bdc78 x27: 0000000000000003\n x26: ffffff80c54f1808 x25: ffffff80c9164080 x24: ffffffc080d723ac\n x23: 0000000000000000 x22: 0000000000000002 x21: 0000000000000000\n x20: 0000000000000000 x19: ffffffc083bc3000 x18: ffffffffffffffff\n x17: ffffffc08117b080 x16: 0000000000000002 x15: ffffff80d2d40000\n x14: 00000000000002da x13: ffffff80d2d404b8 x12: ffffffc082b5a5c8\n x11: ffffffc082bca680 x10: ffffffc082bb2640 x9 : ffffffc082bb2698\n x8 : 0000000000017fe8 x7 : c0000000ffffefff x6 : 0000000000000001\n x5 : ffffff8178fe0d48 x4 : 0000000000000000 x3 : 0000000000000027\n x2 : ffffff8178fe0d50 x1 : 0000000000000000 x0 : 0000000000000000\n Call trace:\n __mutex_lock+0xd84/0x1068\n mutex_lock_nested+0x28/0x34\n tc_setup_taprio+0x118/0x68c\n stmmac_setup_tc+0x50/0xf0\n taprio_change+0x868/0xc9c" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: net: stmmac: mover el bloqueo EST a la estructura stmmac_priv Reinicializar toda la estructura EST tambi\u00e9n restablecer\u00eda el bloqueo mutex que est\u00e1 incrustado en la estructura EST y luego activar\u00eda la siguiente advertencia. Para solucionar esto, mueva el candado a la estructura stmmac_priv. Tambi\u00e9n necesitamos volver a adquirir el bloqueo mutex al realizar esta inicializaci\u00f3n. DEBUG_LOCKS_WARN_ON(lock->magic != lock) ADVERTENCIA: CPU: 3 PID: 505 en kernel/locking/mutex.c:587 __mutex_lock+0xd84/0x1068 M\u00f3dulos vinculados en: CPU: 3 PID: 505 Comm: tc No contaminado 6.9. 0-rc6-00053-g0106679839f7-dirty #29 Nombre del hardware: NXP i.MX8MPlus Placa EVK (DT) pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc: __mutex_lock+0xd84/ 0x1068 lr: __mutex_lock+0xd84/0x1068 sp: ffffffc0864e3570 x29: ffffffc0864e3570 x28: ffffffc0817bdc78 x27: 0000000000000003 x26: ffffff80c54f1808 : ffffff80c9164080 x24: ffffffc080d723ac x23: 0000000000000000 x22: 0000000000000002 x21: 00000000000000000 x20: 0000000000000000 x19: c083bc3000 x18: ffffffffffffffff x17: ffffffc08117b080 x16: 0000000000000002 x15: ffffff80d2d40000 x14: 00000000000002da x13: ffffff80d2d404b8 x12: ffffffc082b5a5c8 x11: ffffffc082bca680 x10: 2bb2640 x9: ffffffc082bb2698 x8: 0000000000017fe8 x7: c0000000fffffff x6: 0000000000000001 x5: ffffff8178fe0d48 x4: 0000000000000000 x3: 00000000 00000027 x2: ffffff8178fe0d50 x1: 0000000000000000 x0: 0000000000000000 Rastreo de llamadas: __mutex_lock+0xd84/0x1068 mutex_lock_nested+0x28/0x34 tc_setup_taprio+0x118/0x68c stmmac_setup_tc+0x50/0xf0 taprio_change+0x868/0xc9c" } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38595.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38595.json index 512d41939cd..d45c1744c00 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38595.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38595.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38595", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:19.550", - "lastModified": "2024-06-19T14:15:19.550", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: Fix peer devlink set for SF representor devlink port\n\nThe cited patch change register devlink flow, and neglect to reflect\nthe changes for peer devlink set logic. Peer devlink set is\ntriggering a call trace if done after devl_register.[1]\n\nHence, align peer devlink set logic with register devlink flow.\n\n[1]\nWARNING: CPU: 4 PID: 3394 at net/devlink/core.c:155 devlink_rel_nested_in_add+0x177/0x180\nCPU: 4 PID: 3394 Comm: kworker/u40:1 Not tainted 6.9.0-rc4_for_linust_min_debug_2024_04_16_14_08 #1\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014\nWorkqueue: mlx5_vhca_event0 mlx5_vhca_state_work_handler [mlx5_core]\nRIP: 0010:devlink_rel_nested_in_add+0x177/0x180\nCall Trace:\n \n ? __warn+0x78/0x120\n ? devlink_rel_nested_in_add+0x177/0x180\n ? report_bug+0x16d/0x180\n ? handle_bug+0x3c/0x60\n ? exc_invalid_op+0x14/0x70\n ? asm_exc_invalid_op+0x16/0x20\n ? devlink_port_init+0x30/0x30\n ? devlink_port_type_clear+0x50/0x50\n ? devlink_rel_nested_in_add+0x177/0x180\n ? devlink_rel_nested_in_add+0xdd/0x180\n mlx5_sf_mdev_event+0x74/0xb0 [mlx5_core]\n notifier_call_chain+0x35/0xb0\n blocking_notifier_call_chain+0x3d/0x60\n mlx5_blocking_notifier_call_chain+0x22/0x30 [mlx5_core]\n mlx5_sf_dev_probe+0x185/0x3e0 [mlx5_core]\n auxiliary_bus_probe+0x38/0x80\n ? driver_sysfs_add+0x51/0x80\n really_probe+0xc5/0x3a0\n ? driver_probe_device+0x90/0x90\n __driver_probe_device+0x80/0x160\n driver_probe_device+0x1e/0x90\n __device_attach_driver+0x7d/0x100\n bus_for_each_drv+0x80/0xd0\n __device_attach+0xbc/0x1f0\n bus_probe_device+0x86/0xa0\n device_add+0x64f/0x860\n __auxiliary_device_add+0x3b/0xa0\n mlx5_sf_dev_add+0x139/0x330 [mlx5_core]\n mlx5_sf_dev_state_change_handler+0x1e4/0x250 [mlx5_core]\n notifier_call_chain+0x35/0xb0\n blocking_notifier_call_chain+0x3d/0x60\n mlx5_vhca_state_work_handler+0x151/0x200 [mlx5_core]\n process_one_work+0x13f/0x2e0\n worker_thread+0x2bd/0x3c0\n ? rescuer_thread+0x410/0x410\n kthread+0xc4/0xf0\n ? kthread_complete_and_exit+0x20/0x20\n ret_from_fork+0x2d/0x50\n ? kthread_complete_and_exit+0x20/0x20\n ret_from_fork_asm+0x11/0x20\n " + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: net/mlx5: corrige el conjunto de enlaces de desarrollo de pares para el puerto devlink del representante SF. El flujo de devlink del registro de cambios de parche citado y no refleja los cambios para la l\u00f3gica del conjunto de enlaces de desarrollo de pares. El conjunto de devlink de pares activa un seguimiento de llamadas si se realiza despu\u00e9s de devl_register.[1] Por lo tanto, alinee la l\u00f3gica del conjunto de devlink de pares con el flujo de registro de devlink. [1] ADVERTENCIA: CPU: 4 PID: 3394 en net/devlink/core.c:155 devlink_rel_nested_in_add+0x177/0x180 CPU: 4 PID: 3394 Comm: kworker/u40:1 No contaminado 6.9.0-rc4_for_linust_min_debug_2024_04_16_14_0 8 #1 Nombre del hardware : PC est\u00e1ndar QEMU (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 01/04/2014 Cola de trabajo: mlx5_vhca_event0 mlx5_vhca_state_work_handler [mlx5_core] RIP 0010:devlink_rel_nested_in_ agregar+0x177/0x180 Llamar Seguimiento: ? __advertir+0x78/0x120 ? devlink_rel_nested_in_add+0x177/0x180? report_bug+0x16d/0x180? handle_bug+0x3c/0x60? exc_invalid_op+0x14/0x70? asm_exc_invalid_op+0x16/0x20? devlink_port_init+0x30/0x30? devlink_port_type_clear+0x50/0x50? devlink_rel_nested_in_add+0x177/0x180? devlink_rel_nested_in_add+0xdd/0x180 mlx5_sf_mdev_event+0x74/0xb0 [mlx5_core] notifier_call_chain+0x35/0xb0 blocking_notifier_call_chain+0x3d/0x60 mlx5_blocking_notifier_call_chain+0x22/0x30 [mlx5_core] x5_sf_dev_probe+0x185/0x3e0 [mlx5_core] auxiliar_bus_probe+0x38/0x80? driver_sysfs_add+0x51/0x80 realmente_probe+0xc5/0x3a0? driver_probe_device+0x90/0x90 __driver_probe_device+0x80/0x160 driver_probe_device+0x1e/0x90 __device_attach_driver+0x7d/0x100 bus_for_each_drv+0x80/0xd0 __device_attach+0xbc/0x1f0 bus_probe_device+0x8 6/0xa0 dispositivo_add+0x64f/0x860 __auxiliary_device_add+0x3b/0xa0 mlx5_sf_dev_add+0x139/0x330 [mlx5_core] mlx5_sf_dev_state_change_handler+0x1e4/0x250 [mlx5_core] notifier_call_chain+0x35/0xb0 blocking_notifier_call_chain+0x3d/0x60 mlx5_vhca_state_work_handler+0x151/0x200 [mlx5_core Process_one_work+0x13f] /0x2e0 hilo_trabajador+0x2bd/0x3c0 ? hilo_rescate+0x410/0x410 kthread+0xc4/0xf0 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x2d/0x50 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork_asm+0x11/0x20 " } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38596.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38596.json index 40a27ad4dab..b6112e64998 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38596.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38596.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38596", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:19.640", - "lastModified": "2024-06-19T14:15:19.640", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\naf_unix: Fix data races in unix_release_sock/unix_stream_sendmsg\n\nA data-race condition has been identified in af_unix. In one data path,\nthe write function unix_release_sock() atomically writes to\nsk->sk_shutdown using WRITE_ONCE. However, on the reader side,\nunix_stream_sendmsg() does not read it atomically. Consequently, this\nissue is causing the following KCSAN splat to occur:\n\n\tBUG: KCSAN: data-race in unix_release_sock / unix_stream_sendmsg\n\n\twrite (marked) to 0xffff88867256ddbb of 1 bytes by task 7270 on cpu 28:\n\tunix_release_sock (net/unix/af_unix.c:640)\n\tunix_release (net/unix/af_unix.c:1050)\n\tsock_close (net/socket.c:659 net/socket.c:1421)\n\t__fput (fs/file_table.c:422)\n\t__fput_sync (fs/file_table.c:508)\n\t__se_sys_close (fs/open.c:1559 fs/open.c:1541)\n\t__x64_sys_close (fs/open.c:1541)\n\tx64_sys_call (arch/x86/entry/syscall_64.c:33)\n\tdo_syscall_64 (arch/x86/entry/common.c:?)\n\tentry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\n\n\tread to 0xffff88867256ddbb of 1 bytes by task 989 on cpu 14:\n\tunix_stream_sendmsg (net/unix/af_unix.c:2273)\n\t__sock_sendmsg (net/socket.c:730 net/socket.c:745)\n\t____sys_sendmsg (net/socket.c:2584)\n\t__sys_sendmmsg (net/socket.c:2638 net/socket.c:2724)\n\t__x64_sys_sendmmsg (net/socket.c:2753 net/socket.c:2750 net/socket.c:2750)\n\tx64_sys_call (arch/x86/entry/syscall_64.c:33)\n\tdo_syscall_64 (arch/x86/entry/common.c:?)\n\tentry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\n\n\tvalue changed: 0x01 -> 0x03\n\nThe line numbers are related to commit dd5a440a31fa (\"Linux 6.9-rc7\").\n\nCommit e1d09c2c2f57 (\"af_unix: Fix data races around sk->sk_shutdown.\")\naddressed a comparable issue in the past regarding sk->sk_shutdown.\nHowever, it overlooked resolving this particular data path.\nThis patch only offending unix_stream_sendmsg() function, since the\nother reads seem to be protected by unix_state_lock() as discussed in" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: af_unix: corrige ejecuci\u00f3ns de datos en unix_release_sock/unix_stream_sendmsg Se identific\u00f3 una condici\u00f3n de ejecuci\u00f3n de datos en af_unix. En una ruta de datos, la funci\u00f3n de escritura unix_release_sock() escribe at\u00f3micamente en sk->sk_shutdown usando WRITE_ONCE. Sin embargo, en el lado del lector, unix_stream_sendmsg() no lo lee at\u00f3micamente. En consecuencia, este problema est\u00e1 provocando que se produzca el siguiente s\u00edmbolo de KCSAN: ERROR: KCSAN: data-race en unix_release_sock / unix_stream_sendmsg escribe (marcado) en 0xffff88867256ddbb de 1 byte por tarea 7270 en la CPU 28: unix_release_sock (net/unix/af_unix.c: 640) unix_release (net/unix/af_unix.c:1050) sock_close (net/socket.c:659 net/socket.c:1421) __fput (fs/file_table.c:422) __fput_sync (fs/file_table.c:508 ) __se_sys_close (fs/open.c:1559 fs/open.c:1541) __x64_sys_close (fs/open.c:1541) x64_sys_call (arch/x86/entry/syscall_64.c:33) do_syscall_64 (arch/x86/entry/ common.c:?) Entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130) le\u00eddo en 0xffff88867256ddbb de 1 bytes por la tarea 989 en la CPU 14: unix_stream_sendmsg (net/unix/af_unix.c:2273) __sock_sendmsg (net/socket .c:730 net/socket.c:745) ____sys_sendmsg (net/socket.c:2584) __sys_sendmmsg (net/socket.c:2638 net/socket.c:2724) __x64_sys_sendmmsg (net/socket.c:2753 net/ socket.c:2750 net/socket.c:2750) x64_sys_call (arch/x86/entry/syscall_64.c:33) do_syscall_64 (arch/x86/entry/common.c:?) Entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64 .S:130) valor cambiado: 0x01 -> 0x03 Los n\u00fameros de l\u00ednea est\u00e1n relacionados con el commit dd5a440a31fa (\"Linux 6.9-rc7\"). El commit e1d09c2c2f57 (\"af_unix: corregir ejecuci\u00f3ns de datos alrededor de sk->sk_shutdown.\") abord\u00f3 un problema comparable en el pasado con respecto a sk->sk_shutdown. Sin embargo, pas\u00f3 por alto resolver esta ruta de datos en particular. Este parche solo ofende la funci\u00f3n unix_stream_sendmsg(), ya que las otras lecturas parecen estar protegidas por unix_state_lock() como se explica en" } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38597.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38597.json index b2b343086a1..9c398de6e4d 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38597.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38597.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38597", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:19.730", - "lastModified": "2024-06-19T14:15:19.730", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\neth: sungem: remove .ndo_poll_controller to avoid deadlocks\n\nErhard reports netpoll warnings from sungem:\n\n netpoll_send_skb_on_dev(): eth0 enabled interrupts in poll (gem_start_xmit+0x0/0x398)\n WARNING: CPU: 1 PID: 1 at net/core/netpoll.c:370 netpoll_send_skb+0x1fc/0x20c\n\ngem_poll_controller() disables interrupts, which may sleep.\nWe can't sleep in netpoll, it has interrupts disabled completely.\nStrangely, gem_poll_controller() doesn't even poll the completions,\nand instead acts as if an interrupt has fired so it just schedules\nNAPI and exits. None of this has been necessary for years, since\nnetpoll invokes NAPI directly." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: eth: sungem: elimine .ndo_poll_controller para evitar interbloqueos Erhard informa advertencias de netpoll desde sungem: netpoll_send_skb_on_dev(): eth0 habilit\u00f3 interrupciones en la encuesta (gem_start_xmit+0x0/0x398) ADVERTENCIA: CPU: 1 PID: 1 en net/core/netpoll.c:370 netpoll_send_skb+0x1fc/0x20c gem_poll_controller() desactiva las interrupciones, que pueden dormir. No podemos dormir en netpoll, tiene las interrupciones desactivadas por completo. Curiosamente, gem_poll_controller() ni siquiera sondea las finalizaciones y, en cambio, act\u00faa como si se hubiera disparado una interrupci\u00f3n, por lo que simplemente programa NAPI y sale. Nada de esto ha sido necesario durante a\u00f1os, ya que netpoll invoca directamente a NAPI." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38598.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38598.json index 7c8b1a0f867..3d0365a27be 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38598.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38598.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38598", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:19.813", - "lastModified": "2024-06-19T14:15:19.813", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmd: fix resync softlockup when bitmap size is less than array size\n\nIs is reported that for dm-raid10, lvextend + lvchange --syncaction will\ntrigger following softlockup:\n\nkernel:watchdog: BUG: soft lockup - CPU#3 stuck for 26s! [mdX_resync:6976]\nCPU: 7 PID: 3588 Comm: mdX_resync Kdump: loaded Not tainted 6.9.0-rc4-next-20240419 #1\nRIP: 0010:_raw_spin_unlock_irq+0x13/0x30\nCall Trace:\n \n md_bitmap_start_sync+0x6b/0xf0\n raid10_sync_request+0x25c/0x1b40 [raid10]\n md_do_sync+0x64b/0x1020\n md_thread+0xa7/0x170\n kthread+0xcf/0x100\n ret_from_fork+0x30/0x50\n ret_from_fork_asm+0x1a/0x30\n\nAnd the detailed process is as follows:\n\nmd_do_sync\n j = mddev->resync_min\n while (j < max_sectors)\n sectors = raid10_sync_request(mddev, j, &skipped)\n if (!md_bitmap_start_sync(..., &sync_blocks))\n // md_bitmap_start_sync set sync_blocks to 0\n return sync_blocks + sectors_skippe;\n // sectors = 0;\n j += sectors;\n // j never change\n\nRoot cause is that commit 301867b1c168 (\"md/raid10: check\nslab-out-of-bounds in md_bitmap_get_counter\") return early from\nmd_bitmap_get_counter(), without setting returned blocks.\n\nFix this problem by always set returned blocks from\nmd_bitmap_get_counter\"(), as it used to be.\n\nNoted that this patch just fix the softlockup problem in kernel, the\ncase that bitmap size doesn't match array size still need to be fixed." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: md: corrige el bloqueo suave de resincronizaci\u00f3n cuando el tama\u00f1o del mapa de bits es menor que el tama\u00f1o de la matriz. Se informa que para dm-raid10, lvextend + lvchange --syncaction activar\u00e1 el siguiente bloqueo suave: kernel:watchdog: ERROR : bloqueo suave - \u00a1CPU n.\u00b0 3 bloqueada durante 26 segundos! [mdX_resync:6976] CPU: 7 PID: 3588 Comm: mdX_resync Kdump: cargado No contaminado 6.9.0-rc4-next-20240419 #1 RIP: 0010:_raw_spin_unlock_irq+0x13/0x30 Seguimiento de llamadas: md_bitmap_start_sync+0x6b/0xf0 raid10_sync_request+0x25c/0x1b40 [raid10] md_do_sync+0x64b/0x1020 md_thread+0xa7/0x170 kthread+0xcf/0x100 ret_from_fork+0x30/0x50 ret_from_fork_asm+0x1a/0x30 Y el proceso detallado es el siguiente: _sync j = mddev->resync_min mientras ( j < max_sectors) sectores = raid10_sync_request(mddev, j, &skipped) if (!md_bitmap_start_sync(..., &sync_blocks)) // md_bitmap_start_sync establece sync_blocks en 0 return sync_blocks + sectores_skippe; // sectores = 0; j += sectores; // j nunca cambia La causa principal es que el commit 301867b1c168 (\"md/raid10: check slab-out-of-bounds in md_bitmap_get_counter\") regresa antes de md_bitmap_get_counter(), sin configurar los bloques devueltos. Solucione este problema estableciendo siempre los bloques devueltos desde md_bitmap_get_counter\"(), como sol\u00eda ser. Tenga en cuenta que este parche solo soluciona el problema de bloqueo suave en el kernel, el caso de que el tama\u00f1o del mapa de bits no coincida con el tama\u00f1o de la matriz a\u00fan debe solucionarse." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-385xx/CVE-2024-38599.json b/CVE-2024/CVE-2024-385xx/CVE-2024-38599.json index c09fd693b33..5d9b51c7af6 100644 --- a/CVE-2024/CVE-2024-385xx/CVE-2024-38599.json +++ b/CVE-2024/CVE-2024-385xx/CVE-2024-38599.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38599", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:19.903", - "lastModified": "2024-06-19T14:15:19.903", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\njffs2: prevent xattr node from overflowing the eraseblock\n\nAdd a check to make sure that the requested xattr node size is no larger\nthan the eraseblock minus the cleanmarker.\n\nUnlike the usual inode nodes, the xattr nodes aren't split into parts\nand spread across multiple eraseblocks, which means that a xattr node\nmust not occupy more than one eraseblock. If the requested xattr value is\ntoo large, the xattr node can spill onto the next eraseblock, overwriting\nthe nodes and causing errors such as:\n\njffs2: argh. node added in wrong place at 0x0000b050(2)\njffs2: nextblock 0x0000a000, expected at 0000b00c\njffs2: error: (823) do_verify_xattr_datum: node CRC failed at 0x01e050,\nread=0xfc892c93, calc=0x000000\njffs2: notice: (823) jffs2_get_inode_nodes: Node header CRC failed\nat 0x01e00c. {848f,2fc4,0fef511f,59a3d171}\njffs2: Node at 0x0000000c with length 0x00001044 would run over the\nend of the erase block\njffs2: Perhaps the file system was created with the wrong erase size?\njffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found\nat 0x00000010: 0x1044 instead\n\nThis breaks the filesystem and can lead to KASAN crashes such as:\n\nBUG: KASAN: slab-out-of-bounds in jffs2_sum_add_kvec+0x125e/0x15d0\nRead of size 4 at addr ffff88802c31e914 by task repro/830\nCPU: 0 PID: 830 Comm: repro Not tainted 6.9.0-rc3+ #1\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996),\nBIOS Arch Linux 1.16.3-1-1 04/01/2014\nCall Trace:\n \n dump_stack_lvl+0xc6/0x120\n print_report+0xc4/0x620\n ? __virt_addr_valid+0x308/0x5b0\n kasan_report+0xc1/0xf0\n ? jffs2_sum_add_kvec+0x125e/0x15d0\n ? jffs2_sum_add_kvec+0x125e/0x15d0\n jffs2_sum_add_kvec+0x125e/0x15d0\n jffs2_flash_direct_writev+0xa8/0xd0\n jffs2_flash_writev+0x9c9/0xef0\n ? __x64_sys_setxattr+0xc4/0x160\n ? do_syscall_64+0x69/0x140\n ? entry_SYSCALL_64_after_hwframe+0x76/0x7e\n [...]\n\nFound by Linux Verification Center (linuxtesting.org) with Syzkaller." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: jffs2: evita que el nodo xattr desborde el bloque de borrado. Agregue una verificaci\u00f3n para asegurarse de que el tama\u00f1o del nodo xattr solicitado no sea mayor que el bloque de borrado menos el marcador de limpieza. A diferencia de los nodos de inodo habituales, los nodos xattr no se dividen en partes ni se distribuyen en m\u00faltiples bloques de borrado, lo que significa que un nodo xattr no debe ocupar m\u00e1s de un bloque de borrado. Si el valor xattr solicitado es demasiado grande, el nodo xattr puede extenderse al siguiente bloque de borrado, sobrescribiendo los nodos y provocando errores como: jffs2: argh. nodo agregado en un lugar incorrecto en 0x0000b050(2) jffs2: nextblock 0x0000a000, esperado en 0000b00c jffs2: error: (823) do_verify_xattr_datum: el CRC del nodo fall\u00f3 en 0x01e050, read=0xfc892c93, calc=0x000000 jffs2: aviso: 823) jffs2_get_inode_nodes: Nodo El CRC del encabezado fall\u00f3 en 0x01e00c. {848f,2fc4,0fef511f,59a3d171} jffs2: El nodo en 0x0000000c con longitud 0x00001044 se ejecutar\u00eda sobre el final del bloque de borrado jffs2: \u00bfQuiz\u00e1s el sistema de archivos se cre\u00f3 con un tama\u00f1o de borrado incorrecto? jffs2: jffs2_scan_eraseblock(): M\u00e1scara de bits m\u00e1gica 0x1985 no encontrada en 0x00000010: 0x1044 en su lugar. Esto rompe el sistema de archivos y puede provocar fallas de KASAN como: ERROR: KASAN: losa fuera de los l\u00edmites en jffs2_sum_add_kvec+0x125e/0x15d0 Lectura de tama\u00f1o 4 en addr ffff88802c31e914 por tarea repro/830 CPU: 0 PID: 830 Comm: repro Not tainted 6.9.0-rc3+ #1 Nombre de hardware: PC est\u00e1ndar QEMU (i440FX + PIIX, 1996), BIOS Arch Linux 1.16.3-1-1 01/04/2014 Seguimiento de llamadas: dump_stack_lvl+0xc6/0x120 print_report+0xc4/0x620 ? __virt_addr_valid+0x308/0x5b0 kasan_report+0xc1/0xf0 ? jffs2_sum_add_kvec+0x125e/0x15d0? jffs2_sum_add_kvec+0x125e/0x15d0 jffs2_sum_add_kvec+0x125e/0x15d0 jffs2_flash_direct_writev+0xa8/0xd0 jffs2_flash_writev+0x9c9/0xef0 ? __x64_sys_setxattr+0xc4/0x160 ? do_syscall_64+0x69/0x140? Entry_SYSCALL_64_after_hwframe+0x76/0x7e [...] Encontrado por el Centro de verificaci\u00f3n de Linux (linuxtesting.org) con Syzkaller." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-386xx/CVE-2024-38600.json b/CVE-2024/CVE-2024-386xx/CVE-2024-38600.json index 2d0f09568e0..fd478c680bc 100644 --- a/CVE-2024/CVE-2024-386xx/CVE-2024-38600.json +++ b/CVE-2024/CVE-2024-386xx/CVE-2024-38600.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38600", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:19.990", - "lastModified": "2024-06-19T14:15:19.990", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nALSA: Fix deadlocks with kctl removals at disconnection\n\nIn snd_card_disconnect(), we set card->shutdown flag at the beginning,\ncall callbacks and do sync for card->power_ref_sleep waiters at the\nend. The callback may delete a kctl element, and this can lead to a\ndeadlock when the device was in the suspended state. Namely:\n\n* A process waits for the power up at snd_power_ref_and_wait() in\n snd_ctl_info() or read/write() inside card->controls_rwsem.\n\n* The system gets disconnected meanwhile, and the driver tries to\n delete a kctl via snd_ctl_remove*(); it tries to take\n card->controls_rwsem again, but this is already locked by the\n above. Since the sleeper isn't woken up, this deadlocks.\n\nAn easy fix is to wake up sleepers before processing the driver\ndisconnect callbacks but right after setting the card->shutdown flag.\nThen all sleepers will abort immediately, and the code flows again.\n\nSo, basically this patch moves the wait_event() call at the right\ntiming. While we're at it, just to be sure, call wait_event_all()\ninstead of wait_event(), although we don't use exclusive events on\nthis queue for now." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: ALSA: soluciona interbloqueos con eliminaciones de kctl al desconectar fin. La devoluci\u00f3n de llamada puede eliminar un elemento kctl y esto puede provocar un punto muerto cuando el dispositivo estaba en estado suspendido. Es decir: * Un proceso espera el encendido en snd_power_ref_and_wait() en snd_ctl_info() o lectura/escritura() dentro de card->controls_rwsem. * Mientras tanto, el sistema se desconecta y el controlador intenta eliminar un kctl mediante snd_ctl_remove*(); intenta tomar card->controls_rwsem nuevamente, pero esto ya est\u00e1 bloqueado por lo anterior. Como el durmiente no se despierta, esto se bloquea. Una soluci\u00f3n f\u00e1cil es despertar a los durmientes antes de procesar las devoluciones de llamada de desconexi\u00f3n del controlador, pero justo despu\u00e9s de configurar la tarjeta->indicador de apagado. Entonces todos los durmientes abortar\u00e1n inmediatamente y el c\u00f3digo fluir\u00e1 nuevamente. B\u00e1sicamente, este parche mueve la llamada wait_event() en el momento adecuado. Mientras estamos en esto, solo para estar seguros, llame a wait_event_all() en lugar de wait_event(), aunque no usamos eventos exclusivos en esta cola por ahora." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-386xx/CVE-2024-38601.json b/CVE-2024/CVE-2024-386xx/CVE-2024-38601.json index df62cc13a7b..307334920a0 100644 --- a/CVE-2024/CVE-2024-386xx/CVE-2024-38601.json +++ b/CVE-2024/CVE-2024-386xx/CVE-2024-38601.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38601", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:20.087", - "lastModified": "2024-06-19T14:15:20.087", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nring-buffer: Fix a race between readers and resize checks\n\nThe reader code in rb_get_reader_page() swaps a new reader page into the\nring buffer by doing cmpxchg on old->list.prev->next to point it to the\nnew page. Following that, if the operation is successful,\nold->list.next->prev gets updated too. This means the underlying\ndoubly-linked list is temporarily inconsistent, page->prev->next or\npage->next->prev might not be equal back to page for some page in the\nring buffer.\n\nThe resize operation in ring_buffer_resize() can be invoked in parallel.\nIt calls rb_check_pages() which can detect the described inconsistency\nand stop further tracing:\n\n[ 190.271762] ------------[ cut here ]------------\n[ 190.271771] WARNING: CPU: 1 PID: 6186 at kernel/trace/ring_buffer.c:1467 rb_check_pages.isra.0+0x6a/0xa0\n[ 190.271789] Modules linked in: [...]\n[ 190.271991] Unloaded tainted modules: intel_uncore_frequency(E):1 skx_edac(E):1\n[ 190.272002] CPU: 1 PID: 6186 Comm: cmd.sh Kdump: loaded Tainted: G E 6.9.0-rc6-default #5 158d3e1e6d0b091c34c3b96bfd99a1c58306d79f\n[ 190.272011] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.0-0-gd239552c-rebuilt.opensuse.org 04/01/2014\n[ 190.272015] RIP: 0010:rb_check_pages.isra.0+0x6a/0xa0\n[ 190.272023] Code: [...]\n[ 190.272028] RSP: 0018:ffff9c37463abb70 EFLAGS: 00010206\n[ 190.272034] RAX: ffff8eba04b6cb80 RBX: 0000000000000007 RCX: ffff8eba01f13d80\n[ 190.272038] RDX: ffff8eba01f130c0 RSI: ffff8eba04b6cd00 RDI: ffff8eba0004c700\n[ 190.272042] RBP: ffff8eba0004c700 R08: 0000000000010002 R09: 0000000000000000\n[ 190.272045] R10: 00000000ffff7f52 R11: ffff8eba7f600000 R12: ffff8eba0004c720\n[ 190.272049] R13: ffff8eba00223a00 R14: 0000000000000008 R15: ffff8eba067a8000\n[ 190.272053] FS: 00007f1bd64752c0(0000) GS:ffff8eba7f680000(0000) knlGS:0000000000000000\n[ 190.272057] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 190.272061] CR2: 00007f1bd6662590 CR3: 000000010291e001 CR4: 0000000000370ef0\n[ 190.272070] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[ 190.272073] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n[ 190.272077] Call Trace:\n[ 190.272098] \n[ 190.272189] ring_buffer_resize+0x2ab/0x460\n[ 190.272199] __tracing_resize_ring_buffer.part.0+0x23/0xa0\n[ 190.272206] tracing_resize_ring_buffer+0x65/0x90\n[ 190.272216] tracing_entries_write+0x74/0xc0\n[ 190.272225] vfs_write+0xf5/0x420\n[ 190.272248] ksys_write+0x67/0xe0\n[ 190.272256] do_syscall_64+0x82/0x170\n[ 190.272363] entry_SYSCALL_64_after_hwframe+0x76/0x7e\n[ 190.272373] RIP: 0033:0x7f1bd657d263\n[ 190.272381] Code: [...]\n[ 190.272385] RSP: 002b:00007ffe72b643f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001\n[ 190.272391] RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 00007f1bd657d263\n[ 190.272395] RDX: 0000000000000002 RSI: 0000555a6eb538e0 RDI: 0000000000000001\n[ 190.272398] RBP: 0000555a6eb538e0 R08: 000000000000000a R09: 0000000000000000\n[ 190.272401] R10: 0000555a6eb55190 R11: 0000000000000246 R12: 00007f1bd6662500\n[ 190.272404] R13: 0000000000000002 R14: 00007f1bd6667c00 R15: 0000000000000002\n[ 190.272412] \n[ 190.272414] ---[ end trace 0000000000000000 ]---\n\nNote that ring_buffer_resize() calls rb_check_pages() only if the parent\ntrace_buffer has recording disabled. Recent commit d78ab792705c\n(\"tracing: Stop current tracer when resizing buffer\") causes that it is\nnow always the case which makes it more likely to experience this issue.\n\nThe window to hit this race is nonetheless very small. To help\nreproducing it, one can add a delay loop in rb_get_reader_page():\n\n ret = rb_head_page_replace(reader, cpu_buffer->reader_page);\n if (!ret)\n \tgoto spin;\n for (unsigned i = 0; i < 1U << 26; i++) /* inserted delay loop */\n \t__asm__ __volatile__ (\"\" : : : \"memory\");\n rb_list_head(reader->list.next)->prev = &cpu_buffer->reader_page->list;\n\n.. \n---truncated---" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: ring-buffer: corrige una ejecuci\u00f3n entre lectores y cambia el tama\u00f1o de las comprobaciones. El c\u00f3digo del lector en rb_get_reader_page() intercambia una nueva p\u00e1gina del lector en el b\u00fafer circular haciendo cmpxchg en old->list.prev ->siguiente para apuntar a la nueva p\u00e1gina. Despu\u00e9s de eso, si la operaci\u00f3n es exitosa, old->list.next->prev tambi\u00e9n se actualiza. Esto significa que la lista doblemente enlazada subyacente es temporalmente inconsistente, p\u00e1gina->anterior->siguiente o p\u00e1gina->siguiente->anterior podr\u00eda no ser igual a la p\u00e1gina para alguna p\u00e1gina en el b\u00fafer circular. La operaci\u00f3n de cambio de tama\u00f1o en ring_buffer_resize() se puede invocar en paralelo. Llama a rb_check_pages(), que puede detectar la inconsistencia descrita y detener el seguimiento: [190.271762] ------------[ cortar aqu\u00ed ]------------ [ 190.271771] ADVERTENCIA: CPU: 1 PID: 6186 en kernel/trace/ring_buffer.c:1467 rb_check_pages.isra.0+0x6a/0xa0 [190.271789] M\u00f3dulos vinculados en: [...] [190.271991] M\u00f3dulos contaminados descargados: intel_uncore_frequency(E) :1 skx_edac(E):1 [ 190.272002] CPU: 1 PID: 6186 Comm: cmd.sh Kdump: cargado Contaminado: GE 6.9.0-rc6-default #5 158d3e1e6d0b091c34c3b96bfd99a1c58306d79f [ 190.272011] Nombre del hardware: PC est\u00e1ndar QEMU (Q35 + ICH9, 2009), BIOS rel-1.16.0-0-gd239552c-rebuilt.opensuse.org 01/04/2014 [ 190.272015] RIP: 0010:rb_check_pages.isra.0+0x6a/0xa0 [ 190.272023] C\u00f3digo: [.. .] [ 190.272028] RSP: 0018:ffff9c37463abb70 EFLAGS: 00010206 [ 190.272034] RAX: ffff8eba04b6cb80 RBX: 00000000000000007 RCX: ffff8eba01f13d80 [ 19 0.272038] RDX: ffff8eba01f130c0 RSI: ffff8eba04b6cd00 RDI: ffff8eba0004c700 [ 190.272042] RBP: ffff8eba0004c700 R08: 0000000000010002 R09: 00000000 [ 190.272045] R10: 00000000ffff7f52 R11: ffff8eba7f600000 R12: ffff8eba0004c720 [ 190.272049] R13: ffff8eba00223a00 R14: 0000000000000008 R15: ffff8eba067a8000 [ 190.272053] FS: 00007f1bd64752c0(0000) GS:ffff8eba7f680000(0000) knlGS:000000000000000000 [ 190.272057] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 190.272061] CR2: 00007f1bd6662590 CR3: 000000010291e001 CR4: 0000000000370ef0 [ 190.272070] DR0: 000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 190.272073] DR3: 0000000000000000 DR6: 00000000ffe0ff0 DR7: 0000000000000400 [ 190 .272077] Seguimiento de llamadas: [190.272098 ] [ 190.272189] ring_buffer_resize+0x2ab/0x460 [ 190.272199] __tracing_resize_ring_buffer.part.0+0x23/0xa0 [ 190.272206] tracing_resize_ring_buffer+0x65/0x90 [ 190.272216] _entries_write+0x74/0xc0 [ 190.272225] vfs_write+0xf5/0x420 [ 190.272248 ] ksys_write+0x67/0xe0 [ 190.272256] do_syscall_64+0x82/0x170 [ 190.272363] Entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 190.272373] RIP: 0033:0x7f1bd657d26 3 [ 190.272381] C\u00f3digo: [...] [ 190.272385] RSP: 002b:00007ffe72b643f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 [ 190.272391] RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 00007f1bd657d263 [ 190.272395] RDX: 0000000 000000002 RSI: 0000555a6eb538e0 RDI: 0000000000000001 [ 190.272398] RBP: 0000555a6eb538e0 R08: 000000000000000a R09: 0000000000000000 [ 190.272401] R10: 0000555a6eb55190 R11: 0000000000000246 R12 : 00007f1bd6662500 [ 190.272404] R13: 0000000000000002 R14: 00007f1bd6667c00 R15: 00000000000000002 [ 190.272412] [ 4] ---[ end trace 0000000000000000 ]--- Tenga en cuenta que ring_buffer_resize() llama a rb_check_pages() solo si el trace_buffer principal tiene grabaci\u00f3n desactivada. El reciente commit d78ab792705c (\"rastreo: detener el rastreador actual al cambiar el tama\u00f1o del b\u00fafer\") hace que ahora sea siempre el caso, lo que hace que sea m\u00e1s probable experimentar este problema. No obstante, la ventana para llegar a esta ejecuci\u00f3n es muy peque\u00f1a. Para ayudar a reproducirlo, se puede agregar un bucle de retardo en rb_get_reader_page(): ret = rb_head_page_replace(reader, cpu_buffer->reader_page); if (!ret) ir a girar; for (unsigned i = 0; i < 1U << 26; i++) /* bucle de retardo insertado ---truncado---" } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-386xx/CVE-2024-38602.json b/CVE-2024/CVE-2024-386xx/CVE-2024-38602.json index 3a18d937f68..99d52ef8d05 100644 --- a/CVE-2024/CVE-2024-386xx/CVE-2024-38602.json +++ b/CVE-2024/CVE-2024-386xx/CVE-2024-38602.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38602", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:20.183", - "lastModified": "2024-06-19T14:15:20.183", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nax25: Fix reference count leak issues of ax25_dev\n\nThe ax25_addr_ax25dev() and ax25_dev_device_down() exist a reference\ncount leak issue of the object \"ax25_dev\".\n\nMemory leak issue in ax25_addr_ax25dev():\n\nThe reference count of the object \"ax25_dev\" can be increased multiple\ntimes in ax25_addr_ax25dev(). This will cause a memory leak.\n\nMemory leak issues in ax25_dev_device_down():\n\nThe reference count of ax25_dev is set to 1 in ax25_dev_device_up() and\nthen increase the reference count when ax25_dev is added to ax25_dev_list.\nAs a result, the reference count of ax25_dev is 2. But when the device is\nshutting down. The ax25_dev_device_down() drops the reference count once\nor twice depending on if we goto unlock_put or not, which will cause\nmemory leak.\n\nAs for the issue of ax25_addr_ax25dev(), it is impossible for one pointer\nto be on a list twice. So add a break in ax25_addr_ax25dev(). As for the\nissue of ax25_dev_device_down(), increase the reference count of ax25_dev\nonce in ax25_dev_device_up() and decrease the reference count of ax25_dev\nafter it is removed from the ax25_dev_list." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: ax25: soluciona problemas de p\u00e9rdida de recuento de referencias de ax25_dev. Ax25_addr_ax25dev() y ax25_dev_device_down() existen un problema de p\u00e9rdida de recuento de referencias del objeto \"ax25_dev\". Problema de p\u00e9rdida de memoria en ax25_addr_ax25dev(): el recuento de referencias del objeto \"ax25_dev\" se puede aumentar varias veces en ax25_addr_ax25dev(). Esto provocar\u00e1 una p\u00e9rdida de memoria. Problemas de p\u00e9rdida de memoria en ax25_dev_device_down(): el recuento de referencias de ax25_dev se establece en 1 en ax25_dev_device_up() y luego aumenta el recuento de referencias cuando se agrega ax25_dev a ax25_dev_list. Como resultado, el recuento de referencia de ax25_dev es 2. Pero cuando el dispositivo se est\u00e1 apagando. El ax25_dev_device_down() reduce el recuento de referencias una o dos veces dependiendo de si vamos a unlock_put o no, lo que provocar\u00e1 una p\u00e9rdida de memoria. En cuanto al problema de ax25_addr_ax25dev(), es imposible que un puntero est\u00e9 en una lista dos veces. Entonces agregue una interrupci\u00f3n en ax25_addr_ax25dev(). En cuanto al problema de ax25_dev_device_down(), aumente el recuento de referencias de ax25_dev una vez en ax25_dev_device_up() y disminuya el recuento de referencias de ax25_dev despu\u00e9s de que se elimine de ax25_dev_list." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-386xx/CVE-2024-38603.json b/CVE-2024/CVE-2024-386xx/CVE-2024-38603.json index f747d854fd0..1e2c57e76e8 100644 --- a/CVE-2024/CVE-2024-386xx/CVE-2024-38603.json +++ b/CVE-2024/CVE-2024-386xx/CVE-2024-38603.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38603", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:20.270", - "lastModified": "2024-06-19T14:15:20.270", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrivers/perf: hisi: hns3: Actually use devm_add_action_or_reset()\n\npci_alloc_irq_vectors() allocates an irq vector. When devm_add_action()\nfails, the irq vector is not freed, which leads to a memory leak.\n\nReplace the devm_add_action with devm_add_action_or_reset to ensure\nthe irq vector can be destroyed when it fails." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: drivers/perf: hisi: hns3: en realidad usa devm_add_action_or_reset() pci_alloc_irq_vectors() asigna un vector irq. Cuando devm_add_action() falla, el vector irq no se libera, lo que provoca una p\u00e9rdida de memoria. Reemplace devm_add_action con devm_add_action_or_reset para garantizar que el vector irq pueda destruirse cuando falla." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-386xx/CVE-2024-38604.json b/CVE-2024/CVE-2024-386xx/CVE-2024-38604.json index 7e379895cc3..8d6cabb5c26 100644 --- a/CVE-2024/CVE-2024-386xx/CVE-2024-38604.json +++ b/CVE-2024/CVE-2024-386xx/CVE-2024-38604.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38604", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:20.357", - "lastModified": "2024-06-19T14:15:20.357", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nblock: refine the EOF check in blkdev_iomap_begin\n\nblkdev_iomap_begin rounds down the offset to the logical block size\nbefore stashing it in iomap->offset and checking that it still is\ninside the inode size.\n\nCheck the i_size check to the raw pos value so that we don't try a\nzero size write if iter->pos is unaligned." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: bloque: refina la comprobaci\u00f3n de EOF en blkdev_iomap_begin blkdev_iomap_begin redondea hacia abajo el desplazamiento al tama\u00f1o del bloque l\u00f3gico antes de guardarlo en iomap->offset y comprobar que todav\u00eda est\u00e1 dentro del tama\u00f1o del inodo. Verifique la verificaci\u00f3n i_size en el valor pos sin formato para que no intentemos una escritura de tama\u00f1o cero si iter->pos no est\u00e1 alineado." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-386xx/CVE-2024-38605.json b/CVE-2024/CVE-2024-386xx/CVE-2024-38605.json index ac2496bc771..06e89cdf2ff 100644 --- a/CVE-2024/CVE-2024-386xx/CVE-2024-38605.json +++ b/CVE-2024/CVE-2024-386xx/CVE-2024-38605.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38605", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:20.443", - "lastModified": "2024-06-19T14:15:20.443", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nALSA: core: Fix NULL module pointer assignment at card init\n\nThe commit 81033c6b584b (\"ALSA: core: Warn on empty module\")\nintroduced a WARN_ON() for a NULL module pointer passed at snd_card\nobject creation, and it also wraps the code around it with '#ifdef\nMODULE'. This works in most cases, but the devils are always in\ndetails. \"MODULE\" is defined when the target code (i.e. the sound\ncore) is built as a module; but this doesn't mean that the caller is\nalso built-in or not. Namely, when only the sound core is built-in\n(CONFIG_SND=y) while the driver is a module (CONFIG_SND_USB_AUDIO=m),\nthe passed module pointer is ignored even if it's non-NULL, and\ncard->module remains as NULL. This would result in the missing module\nreference up/down at the device open/close, leading to a race with the\ncode execution after the module removal.\n\nFor addressing the bug, move the assignment of card->module again out\nof ifdef. The WARN_ON() is still wrapped with ifdef because the\nmodule can be really NULL when all sound drivers are built-in.\n\nNote that we keep 'ifdef MODULE' for WARN_ON(), otherwise it would\nlead to a false-positive NULL module check. Admittedly it won't catch\nperfectly, i.e. no check is performed when CONFIG_SND=y. But, it's no\nreal problem as it's only for debugging, and the condition is pretty\nrare." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: ALSA: n\u00facleo: corrige la asignaci\u00f3n del puntero del m\u00f3dulo NULL en el inicio de la tarjeta el commit 81033c6b584b (\"ALSA: n\u00facleo: Advertencia sobre m\u00f3dulo vac\u00edo\") introdujo un WARN_ON() para un puntero de m\u00f3dulo NULL pasado en la creaci\u00f3n del objeto snd_card, y tambi\u00e9n envuelve el c\u00f3digo a su alrededor con '#ifdef MODULE'. Esto funciona en la mayor\u00eda de los casos, pero los problemas siempre est\u00e1n en los detalles. \"M\u00d3DULO\" se define cuando el c\u00f3digo objetivo (es decir, el n\u00facleo de sonido) se construye como un m\u00f3dulo; pero esto no significa que la persona que llama tambi\u00e9n est\u00e9 integrada o no. Es decir, cuando solo el n\u00facleo de sonido est\u00e1 integrado (CONFIG_SND=y) mientras el controlador es un m\u00f3dulo (CONFIG_SND_USB_AUDIO=m), el puntero del m\u00f3dulo pasado se ignora incluso si no es NULL, y tarjeta->m\u00f3dulo permanece como NULL. Esto dar\u00eda como resultado que la referencia del m\u00f3dulo faltante suba o baje en la apertura o cierre del dispositivo, lo que provocar\u00eda una ejecuci\u00f3n con la ejecuci\u00f3n del c\u00f3digo despu\u00e9s de la eliminaci\u00f3n del m\u00f3dulo. Para solucionar el error, mueva la asignaci\u00f3n de tarjeta->m\u00f3dulo nuevamente fuera de ifdef. WARN_ON() todav\u00eda est\u00e1 incluido en ifdef porque el m\u00f3dulo puede ser realmente NULL cuando todos los controladores de sonido est\u00e1n integrados. Tenga en cuenta que mantenemos 'ifdef MODULE' para WARN_ON(); de lo contrario, se producir\u00eda una verificaci\u00f3n de m\u00f3dulo NULL falsamente positiva. Es cierto que no se detectar\u00e1 perfectamente, es decir, no se realiza ninguna verificaci\u00f3n cuando CONFIG_SND=y. Pero no es un problema real ya que es solo para depurar y la condici\u00f3n es bastante rara." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-386xx/CVE-2024-38606.json b/CVE-2024/CVE-2024-386xx/CVE-2024-38606.json index 613202e4a87..e158b49e631 100644 --- a/CVE-2024/CVE-2024-386xx/CVE-2024-38606.json +++ b/CVE-2024/CVE-2024-386xx/CVE-2024-38606.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38606", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:20.567", - "lastModified": "2024-06-19T14:15:20.567", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: qat - validate slices count returned by FW\n\nThe function adf_send_admin_tl_start() enables the telemetry (TL)\nfeature on a QAT device by sending the ICP_QAT_FW_TL_START message to\nthe firmware. This triggers the FW to start writing TL data to a DMA\nbuffer in memory and returns an array containing the number of\naccelerators of each type (slices) supported by this HW.\nThe pointer to this array is stored in the adf_tl_hw_data data\nstructure called slice_cnt.\n\nThe array slice_cnt is then used in the function tl_print_dev_data()\nto report in debugfs only statistics about the supported accelerators.\nAn incorrect value of the elements in slice_cnt might lead to an out\nof bounds memory read.\nAt the moment, there isn't an implementation of FW that returns a wrong\nvalue, but for robustness validate the slice count array returned by FW." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: crypto: qat: valida el recuento de segmentos devueltos por el FW. La funci\u00f3n adf_send_admin_tl_start() habilita la funci\u00f3n de telemetr\u00eda (TL) en un dispositivo QAT enviando el mensaje ICP_QAT_FW_TL_START al firmware. Esto hace que el FW comience a escribir datos TL en un b\u00fafer DMA en la memoria y devuelve una matriz que contiene la cantidad de aceleradores de cada tipo (porciones) admitidos por este HW. El puntero a esta matriz se almacena en la estructura de datos adf_tl_hw_data llamada slice_cnt. La matriz slice_cnt luego se usa en la funci\u00f3n tl_print_dev_data() para informar en debugfs solo estad\u00edsticas sobre los aceleradores admitidos. Un valor incorrecto de los elementos en slice_cnt podr\u00eda provocar una lectura de memoria fuera de los l\u00edmites. Por el momento, no existe una implementaci\u00f3n de FW que devuelva un valor incorrecto, pero para mayor solidez, valide la matriz de recuento de sectores devuelta por FW." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-386xx/CVE-2024-38607.json b/CVE-2024/CVE-2024-386xx/CVE-2024-38607.json index 44f8404e34d..96e70452dac 100644 --- a/CVE-2024/CVE-2024-386xx/CVE-2024-38607.json +++ b/CVE-2024/CVE-2024-386xx/CVE-2024-38607.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38607", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:20.650", - "lastModified": "2024-06-19T14:15:20.650", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmacintosh/via-macii: Fix \"BUG: sleeping function called from invalid context\"\n\nThe via-macii ADB driver calls request_irq() after disabling hard\ninterrupts. But disabling interrupts isn't necessary here because the\nVIA shift register interrupt was masked during VIA1 initialization." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: macintosh/via-macii: Correcci\u00f3n \"ERROR: funci\u00f3n de suspensi\u00f3n llamada desde un contexto no v\u00e1lido\" El controlador ADB via-macii llama a request_irq() despu\u00e9s de deshabilitar las interrupciones bruscas. Pero aqu\u00ed no es necesario deshabilitar las interrupciones porque la interrupci\u00f3n del registro de desplazamiento de VIA se enmascar\u00f3 durante la inicializaci\u00f3n de VIA1." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-386xx/CVE-2024-38608.json b/CVE-2024/CVE-2024-386xx/CVE-2024-38608.json index 44a53420626..2822b52f390 100644 --- a/CVE-2024/CVE-2024-386xx/CVE-2024-38608.json +++ b/CVE-2024/CVE-2024-386xx/CVE-2024-38608.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38608", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:20.737", - "lastModified": "2024-06-19T14:15:20.737", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Fix netif state handling\n\nmlx5e_suspend cleans resources only if netif_device_present() returns\ntrue. However, mlx5e_resume changes the state of netif, via\nmlx5e_nic_enable, only if reg_state == NETREG_REGISTERED.\nIn the below case, the above leads to NULL-ptr Oops[1] and memory\nleaks:\n\nmlx5e_probe\n _mlx5e_resume\n mlx5e_attach_netdev\n mlx5e_nic_enable <-- netdev not reg, not calling netif_device_attach()\n register_netdev <-- failed for some reason.\nERROR_FLOW:\n _mlx5e_suspend <-- netif_device_present return false, resources aren't freed :(\n\nHence, clean resources in this case as well.\n\n[1]\nBUG: kernel NULL pointer dereference, address: 0000000000000000\nPGD 0 P4D 0\nOops: 0010 [#1] SMP\nCPU: 2 PID: 9345 Comm: test-ovs-ct-gen Not tainted 6.5.0_for_upstream_min_debug_2023_09_05_16_01 #1\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014\nRIP: 0010:0x0\nCode: Unable to access opcode bytes at0xffffffffffffffd6.\nRSP: 0018:ffff888178aaf758 EFLAGS: 00010246\nCall Trace:\n \n ? __die+0x20/0x60\n ? page_fault_oops+0x14c/0x3c0\n ? exc_page_fault+0x75/0x140\n ? asm_exc_page_fault+0x22/0x30\n notifier_call_chain+0x35/0xb0\n blocking_notifier_call_chain+0x3d/0x60\n mlx5_blocking_notifier_call_chain+0x22/0x30 [mlx5_core]\n mlx5_core_uplink_netdev_event_replay+0x3e/0x60 [mlx5_core]\n mlx5_mdev_netdev_track+0x53/0x60 [mlx5_ib]\n mlx5_ib_roce_init+0xc3/0x340 [mlx5_ib]\n __mlx5_ib_add+0x34/0xd0 [mlx5_ib]\n mlx5r_probe+0xe1/0x210 [mlx5_ib]\n ? auxiliary_match_id+0x6a/0x90\n auxiliary_bus_probe+0x38/0x80\n ? driver_sysfs_add+0x51/0x80\n really_probe+0xc9/0x3e0\n ? driver_probe_device+0x90/0x90\n __driver_probe_device+0x80/0x160\n driver_probe_device+0x1e/0x90\n __device_attach_driver+0x7d/0x100\n bus_for_each_drv+0x80/0xd0\n __device_attach+0xbc/0x1f0\n bus_probe_device+0x86/0xa0\n device_add+0x637/0x840\n __auxiliary_device_add+0x3b/0xa0\n add_adev+0xc9/0x140 [mlx5_core]\n mlx5_rescan_drivers_locked+0x22a/0x310 [mlx5_core]\n mlx5_register_device+0x53/0xa0 [mlx5_core]\n mlx5_init_one_devl_locked+0x5c4/0x9c0 [mlx5_core]\n mlx5_init_one+0x3b/0x60 [mlx5_core]\n probe_one+0x44c/0x730 [mlx5_core]\n local_pci_probe+0x3e/0x90\n pci_device_probe+0xbf/0x210\n ? kernfs_create_link+0x5d/0xa0\n ? sysfs_do_create_link_sd+0x60/0xc0\n really_probe+0xc9/0x3e0\n ? driver_probe_device+0x90/0x90\n __driver_probe_device+0x80/0x160\n driver_probe_device+0x1e/0x90\n __device_attach_driver+0x7d/0x100\n bus_for_each_drv+0x80/0xd0\n __device_attach+0xbc/0x1f0\n pci_bus_add_device+0x54/0x80\n pci_iov_add_virtfn+0x2e6/0x320\n sriov_enable+0x208/0x420\n mlx5_core_sriov_configure+0x9e/0x200 [mlx5_core]\n sriov_numvfs_store+0xae/0x1a0\n kernfs_fop_write_iter+0x10c/0x1a0\n vfs_write+0x291/0x3c0\n ksys_write+0x5f/0xe0\n do_syscall_64+0x3d/0x90\n entry_SYSCALL_64_after_hwframe+0x46/0xb0\n CR2: 0000000000000000\n ---[ end trace 0000000000000000 ]---" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: net/mlx5e: corrige el manejo del estado de netif. mlx5e_suspend limpia los recursos solo si netif_device_present() devuelve verdadero. Sin embargo, mlx5e_resume cambia el estado de netif, a trav\u00e9s de mlx5e_nic_enable, solo si reg_state == NETREG_REGISTERED. En el siguiente caso, lo anterior conduce a NULL-ptr Ups[1] y p\u00e9rdidas de memoria: mlx5e_probe _mlx5e_resume mlx5e_attach_netdev mlx5e_nic_enable <-- netdev no se registra, no llama a netif_device_attach() Register_netdev <-- fall\u00f3 por alg\u00fan motivo. ERROR_FLOW: _mlx5e_suspend <-- netif_device_present devuelve falso, los recursos no se liberan :( Por lo tanto, limpie los recursos en este caso tambi\u00e9n. [1] ERROR: desreferencia del puntero NULL del kernel, direcci\u00f3n: 00000000000000000 PGD 0 P4D 0 Ups: 0010 [#1 ] SMP CPU: 2 PID: 9345 Comm: test-ovs-ct-gen Not tainted 6.5.0_for_upstream_min_debug_2023_09_05_16_01 #1 Nombre del hardware: PC est\u00e1ndar QEMU (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuild .qemu.org 01/04/2014 RIP: 0010:0x0 C\u00f3digo: No se puede acceder a los bytes del c\u00f3digo de operaci\u00f3n at0xffffffffffffffd6 RSP: 0018:ffff888178aaf758 EFLAGS: 00010246 Seguimiento de llamadas: __die+0x20/0x60 +0x14c/0x3c0? exc_page_fault+0x75/0x140 ? _replay+0x3e/0x60 [mlx5_core] mlx5_mdev_netdev_track+0x53/0x60 [mlx5_ib] mlx5_ib_roce_init+0xc3/0x340 [mlx5_ib] __mlx5_ib_add+0x34/0xd0 [mlx5_ib] mlx5r_probe+0xe1/0x210 [mlx5_ib] ? auxiliar_match_id+0x6a/0x90 sonda_bus_auxiliar+0x38/0x80 ? driver_sysfs_add+0x51/0x80 realmente_probe+0xc9/0x3e0? driver_probe_device+0x90/0x90 __driver_probe_device+0x80/0x160 driver_probe_device+0x1e/0x90 __device_attach_driver+0x7d/0x100 bus_for_each_drv+0x80/0xd0 __device_attach+0xbc/0x1f0 bus_probe_device+0x8 6/0xa0 dispositivo_add+0x637/0x840 __auxiliary_device_add+0x3b/0xa0 add_adev+0xc9/0x140 [mlx5_core] mlx5_rescan_drivers_locked+0x22a/0x310 [mlx5_core] mlx5_register_device+0x53/0xa0 [mlx5_core] mlx5_init_one_devl_locked+0x5c4/0x9c0 [mlx5_core] mlx5_init_one+0x3b/0x60 [mlx5_core] _uno+0x44c/0x730 [mlx5_core] local_pci_probe+0x3e/0x90 pci_device_probe+ 0xbf/0x210 ? kernfs_create_link+0x5d/0xa0? sysfs_do_create_link_sd+0x60/0xc0 realmente_probe+0xc9/0x3e0? driver_probe_device+0x90/0x90 __driver_probe_device+0x80/0x160 driver_probe_device+0x1e/0x90 __device_attach_driver+0x7d/0x100 bus_for_each_drv+0x80/0xd0 __device_attach+0xbc/0x1f0 pci_bus_add_device+ 0x54/0x80 pci_iov_add_virtfn+0x2e6/0x320 sriov_enable+0x208/0x420 mlx5_core_sriov_configure+0x9e/0x200 [mlx5_core] sriov_numvfs_store+0xae/0x1a0 kernfs_fop_write_iter+0x10c/0x1a0 vfs_write+0x291/0x3c0 ksys_write+0x5f/0xe0 do_syscall_64+0x3d/0x90 Entry_SYSCALL_64_after_hwframe+0x4 6/0xb0 CR2: 0000000000000000 ---[ final de seguimiento 0000000000000000 ]---" } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-386xx/CVE-2024-38609.json b/CVE-2024/CVE-2024-386xx/CVE-2024-38609.json index 068ce56be40..e7271baabe1 100644 --- a/CVE-2024/CVE-2024-386xx/CVE-2024-38609.json +++ b/CVE-2024/CVE-2024-386xx/CVE-2024-38609.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38609", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:20.813", - "lastModified": "2024-06-19T14:15:20.813", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: mt76: connac: check for null before dereferencing\n\nThe wcid can be NULL. It should be checked for validity before\ndereferencing it to avoid crash." + }, + { + "lang": "es", + "value": "En el kernel de Linux se ha resuelto la siguiente vulnerabilidad: wifi: mt76: connac: comprobar nulo antes de desreferenciar El wcid puede ser NULL. Se debe verificar su validez antes de eliminar la referencia para evitar fallas." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-386xx/CVE-2024-38610.json b/CVE-2024/CVE-2024-386xx/CVE-2024-38610.json index 2d16061b57e..1488cfb7bd4 100644 --- a/CVE-2024/CVE-2024-386xx/CVE-2024-38610.json +++ b/CVE-2024/CVE-2024-386xx/CVE-2024-38610.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38610", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:20.893", - "lastModified": "2024-06-19T14:15:20.893", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrivers/virt/acrn: fix PFNMAP PTE checks in acrn_vm_ram_map()\n\nPatch series \"mm: follow_pte() improvements and acrn follow_pte() fixes\".\n\nPatch #1 fixes a bunch of issues I spotted in the acrn driver. It\ncompiles, that's all I know. I'll appreciate some review and testing from\nacrn folks.\n\nPatch #2+#3 improve follow_pte(), passing a VMA instead of the MM, adding\nmore sanity checks, and improving the documentation. Gave it a quick test\non x86-64 using VM_PAT that ends up using follow_pte().\n\n\nThis patch (of 3):\n\nWe currently miss handling various cases, resulting in a dangerous\nfollow_pte() (previously follow_pfn()) usage.\n\n(1) We're not checking PTE write permissions.\n\nMaybe we should simply always require pte_write() like we do for\npin_user_pages_fast(FOLL_WRITE)? Hard to tell, so let's check for\nACRN_MEM_ACCESS_WRITE for now.\n\n(2) We're not rejecting refcounted pages.\n\nAs we are not using MMU notifiers, messing with refcounted pages is\ndangerous and can result in use-after-free. Let's make sure to reject them.\n\n(3) We are only looking at the first PTE of a bigger range.\n\nWe only lookup a single PTE, but memmap->len may span a larger area.\nLet's loop over all involved PTEs and make sure the PFN range is\nactually contiguous. Reject everything else: it couldn't have worked\neither way, and rather made use access PFNs we shouldn't be accessing." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: drivers/virt/acrn: corrige las comprobaciones de PFNMAP PTE en acrn_vm_ram_map() Serie de parches \"mm: mejoras en follow_pte() y correcciones en acrn follow_pte()\". El parche n.\u00ba 1 soluciona varios problemas que detect\u00e9 en el controlador acrn. Se compila, eso es todo lo que s\u00e9. Apreciar\u00e9 algunas revisiones y pruebas por parte de la gente de acrn. El parche #2+#3 mejora follow_pte(), pasa un VMA en lugar del MM, agrega m\u00e1s controles de cordura y mejora la documentaci\u00f3n. Lo prob\u00e9 r\u00e1pidamente en x86-64 usando VM_PAT y termin\u00f3 usando follow_pte(). Este parche (de 3): Actualmente no manejamos varios casos, lo que resulta en un uso peligroso de follow_pte() (anteriormente follow_pfn()). (1) No estamos verificando los permisos de escritura de PTE. \u00bfQuiz\u00e1s simplemente deber\u00edamos requerir siempre pte_write() como lo hacemos para pin_user_pages_fast(FOLL_WRITE)? Es dif\u00edcil saberlo, as\u00ed que busquemos ACRN_MEM_ACCESS_WRITE por ahora. (2) No rechazamos p\u00e1ginas recontadas. Como no utilizamos notificadores MMU, jugar con p\u00e1ginas descontadas es peligroso y puede resultar en use-after-free. Asegur\u00e9monos de rechazarlos. (3) S\u00f3lo estamos ante el primer PTE de una gama mayor. Solo buscamos una PTE, pero memmap->len puede abarcar un \u00e1rea m\u00e1s grande. Recorramos todos los PTE involucrados y asegur\u00e9monos de que el rango de PFN sea realmente contiguo. Rechace todo lo dem\u00e1s: no podr\u00eda haber funcionado de ninguna manera, y m\u00e1s bien utiliz\u00f3 PFN de acceso a los que no deber\u00edamos acceder." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-386xx/CVE-2024-38611.json b/CVE-2024/CVE-2024-386xx/CVE-2024-38611.json index d5193602f4c..1666651e067 100644 --- a/CVE-2024/CVE-2024-386xx/CVE-2024-38611.json +++ b/CVE-2024/CVE-2024-386xx/CVE-2024-38611.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38611", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:20.980", - "lastModified": "2024-06-19T14:15:20.980", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: i2c: et8ek8: Don't strip remove function when driver is builtin\n\nUsing __exit for the remove function results in the remove callback\nbeing discarded with CONFIG_VIDEO_ET8EK8=y. When such a device gets\nunbound (e.g. using sysfs or hotplug), the driver is just removed\nwithout the cleanup being performed. This results in resource leaks. Fix\nit by compiling in the remove callback unconditionally.\n\nThis also fixes a W=1 modpost warning:\n\n\tWARNING: modpost: drivers/media/i2c/et8ek8/et8ek8: section mismatch in reference: et8ek8_i2c_driver+0x10 (section: .data) -> et8ek8_remove (section: .exit.text)" + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: medios: i2c: et8ek8: No eliminar la funci\u00f3n de eliminaci\u00f3n cuando el controlador est\u00e1 integrado. El uso de __exit para la funci\u00f3n de eliminaci\u00f3n hace que la devoluci\u00f3n de llamada de eliminaci\u00f3n se descarte con CONFIG_VIDEO_ET8EK8=y. Cuando un dispositivo de este tipo se desvincula (por ejemplo, usando sysfs o hotplug), el controlador simplemente se elimina sin que se realice la limpieza. Esto da como resultado fugas de recursos. Solucionarlo compilando la devoluci\u00f3n de llamada de eliminaci\u00f3n incondicionalmente. Esto tambi\u00e9n corrige una advertencia de modpost W=1: ADVERTENCIA: modpost: drivers/media/i2c/et8ek8/et8ek8: secci\u00f3n no coincide en referencia: et8ek8_i2c_driver+0x10 (secci\u00f3n: .data) -> et8ek8_remove (secci\u00f3n: .exit.text)" } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-386xx/CVE-2024-38612.json b/CVE-2024/CVE-2024-386xx/CVE-2024-38612.json index 0ae321d4b6e..8210ac748ab 100644 --- a/CVE-2024/CVE-2024-386xx/CVE-2024-38612.json +++ b/CVE-2024/CVE-2024-386xx/CVE-2024-38612.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38612", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:21.060", - "lastModified": "2024-06-19T14:15:21.060", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nipv6: sr: fix invalid unregister error path\n\nThe error path of seg6_init() is wrong in case CONFIG_IPV6_SEG6_LWTUNNEL\nis not defined. In that case if seg6_hmac_init() fails, the\ngenl_unregister_family() isn't called.\n\nThis issue exist since commit 46738b1317e1 (\"ipv6: sr: add option to control\nlwtunnel support\"), and commit 5559cea2d5aa (\"ipv6: sr: fix possible\nuse-after-free and null-ptr-deref\") replaced unregister_pernet_subsys()\nwith genl_unregister_family() in this error path." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: ipv6: sr: corrige la ruta de error de cancelaci\u00f3n de registro no v\u00e1lida La ruta de error de seg6_init() es incorrecta en caso de que CONFIG_IPV6_SEG6_LWTUNNEL no est\u00e9 definido. En ese caso, si seg6_hmac_init() falla, no se llama a genl_unregister_family(). Este problema existe desde que el commit 46738b1317e1 (\"ipv6: sr: agregar opci\u00f3n para controlar la compatibilidad con lwtunnel\") y el commit 5559cea2d5aa (\"ipv6: sr: corregir posible use-after-free y null-ptr-deref\") reemplaz\u00f3 unregister_pernet_subsys() con genl_unregister_family() en esta ruta de error." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-386xx/CVE-2024-38613.json b/CVE-2024/CVE-2024-386xx/CVE-2024-38613.json index 60fcda0b071..a817e95249a 100644 --- a/CVE-2024/CVE-2024-386xx/CVE-2024-38613.json +++ b/CVE-2024/CVE-2024-386xx/CVE-2024-38613.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38613", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:21.147", - "lastModified": "2024-06-19T14:15:21.147", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nm68k: Fix spinlock race in kernel thread creation\n\nContext switching does take care to retain the correct lock owner across\nthe switch from 'prev' to 'next' tasks. This does rely on interrupts\nremaining disabled for the entire duration of the switch.\n\nThis condition is guaranteed for normal process creation and context\nswitching between already running processes, because both 'prev' and\n'next' already have interrupts disabled in their saved copies of the\nstatus register.\n\nThe situation is different for newly created kernel threads. The status\nregister is set to PS_S in copy_thread(), which does leave the IPL at 0.\nUpon restoring the 'next' thread's status register in switch_to() aka\nresume(), interrupts then become enabled prematurely. resume() then\nreturns via ret_from_kernel_thread() and schedule_tail() where run queue\nlock is released (see finish_task_switch() and finish_lock_switch()).\n\nA timer interrupt calling scheduler_tick() before the lock is released\nin finish_task_switch() will find the lock already taken, with the\ncurrent task as lock owner. This causes a spinlock recursion warning as\nreported by Guenter Roeck.\n\nAs far as I can ascertain, this race has been opened in commit\n533e6903bea0 (\"m68k: split ret_from_fork(), simplify kernel_thread()\")\nbut I haven't done a detailed study of kernel history so it may well\npredate that commit.\n\nInterrupts cannot be disabled in the saved status register copy for\nkernel threads (init will complain about interrupts disabled when\nfinally starting user space). Disable interrupts temporarily when\nswitching the tasks' register sets in resume().\n\nNote that a simple oriw 0x700,%sr after restoring sr is not enough here\n- this leaves enough of a race for the 'spinlock recursion' warning to\nstill be observed.\n\nTested on ARAnyM and qemu (Quadra 800 emulation)." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: m68k: corrige la ejecuci\u00f3n de bloqueo de giro en la creaci\u00f3n de subprocesos del kernel. El cambio de contexto se encarga de retener el propietario del bloqueo correcto durante el cambio de las tareas 'anteriores' a las 'siguientes'. Esto depende de que las interrupciones permanezcan deshabilitadas durante toda la duraci\u00f3n del cambio. Esta condici\u00f3n est\u00e1 garantizada para la creaci\u00f3n normal de procesos y el cambio de contexto entre procesos que ya se est\u00e1n ejecutando, porque tanto 'anterior' como 'siguiente' ya tienen las interrupciones deshabilitadas en sus copias guardadas del registro de estado. La situaci\u00f3n es diferente para los subprocesos del kernel reci\u00e9n creados. El registro de estado se establece en PS_S en copy_thread(), lo que deja la IPL en 0. Al restaurar el registro de estado del 'siguiente' subproceso en switch_to() tambi\u00e9n conocido como resume(), las interrupciones se habilitan prematuramente. resume() luego regresa a trav\u00e9s de ret_from_kernel_thread() y Schedule_tail() donde se libera el bloqueo de la cola de ejecuci\u00f3n (consulte Finish_task_switch() y Finish_lock_switch()). Una interrupci\u00f3n del temporizador que llama a Scheduler_tick() antes de que se libere el bloqueo en Finish_task_switch() encontrar\u00e1 el bloqueo ya tomado, con la tarea actual como propietario del bloqueo. Esto provoca una advertencia de recursividad de spinlock seg\u00fan lo informado por Guenter Roeck. Hasta donde puedo determinar, esta ejecuci\u00f3n se abri\u00f3 en el commit 533e6903bea0 (\"m68k: split ret_from_fork(), simplifica kernel_thread()\") pero no he realizado un estudio detallado de la historia del kernel, por lo que es posible que sea anterior a esa confirmaci\u00f3n. Las interrupciones no se pueden deshabilitar en la copia del registro de estado guardado para los subprocesos del kernel (init se quejar\u00e1 de las interrupciones deshabilitadas cuando finalmente inicie el espacio de usuario). Deshabilite las interrupciones temporalmente al cambiar los conjuntos de registros de tareas en resume(). Tenga en cuenta que un simple oriw 0x700,%sr despu\u00e9s de restaurar sr no es suficiente aqu\u00ed; esto deja suficiente ejecuci\u00f3n para que a\u00fan se observe la advertencia de 'recursi\u00f3n de spinlock'. Probado en ARAnyM y qemu (emulaci\u00f3n Quadra 800)." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-386xx/CVE-2024-38614.json b/CVE-2024/CVE-2024-386xx/CVE-2024-38614.json index b1a473fcfc9..8a001ed2766 100644 --- a/CVE-2024/CVE-2024-386xx/CVE-2024-38614.json +++ b/CVE-2024/CVE-2024-386xx/CVE-2024-38614.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38614", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:21.240", - "lastModified": "2024-06-19T14:15:21.240", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nopenrisc: traps: Don't send signals to kernel mode threads\n\nOpenRISC exception handling sends signals to user processes on floating\npoint exceptions and trap instructions (for debugging) among others.\nThere is a bug where the trap handling logic may send signals to kernel\nthreads, we should not send these signals to kernel threads, if that\nhappens we treat it as an error.\n\nThis patch adds conditions to die if the kernel receives these\nexceptions in kernel mode code." + }, + { + "lang": "es", + "value": "En el kernel de Linux se ha resuelto la siguiente vulnerabilidad: openrisc: trampas: no env\u00eda se\u00f1ales a subprocesos en modo kernel. El manejo de excepciones de OpenRISC env\u00eda se\u00f1ales a los procesos del usuario sobre excepciones de punto flotante e instrucciones de captura (para depuraci\u00f3n), entre otros. Hay un error en el que la l\u00f3gica de manejo de trampas puede enviar se\u00f1ales a los subprocesos del kernel. No debemos enviar estas se\u00f1ales a los subprocesos del kernel; si eso sucede, lo tratamos como un error. Este parche agrega condiciones para morir si el kernel recibe estas excepciones en el c\u00f3digo del modo kernel." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-386xx/CVE-2024-38615.json b/CVE-2024/CVE-2024-386xx/CVE-2024-38615.json index 48a83dd26c7..ba581526f26 100644 --- a/CVE-2024/CVE-2024-386xx/CVE-2024-38615.json +++ b/CVE-2024/CVE-2024-386xx/CVE-2024-38615.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38615", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:21.320", - "lastModified": "2024-06-19T14:15:21.320", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ncpufreq: exit() callback is optional\n\nThe exit() callback is optional and shouldn't be called without checking\na valid pointer first.\n\nAlso, we must clear freq_table pointer even if the exit() callback isn't\npresent." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: cpufreq: la devoluci\u00f3n de llamada exit() es opcional La devoluci\u00f3n de llamada exit() es opcional y no debe llamarse sin verificar primero un puntero v\u00e1lido. Adem\u00e1s, debemos borrar el puntero freq_table incluso si la devoluci\u00f3n de llamada exit() no est\u00e1 presente." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-386xx/CVE-2024-38616.json b/CVE-2024/CVE-2024-386xx/CVE-2024-38616.json index 85f86472ab8..559ede8f71b 100644 --- a/CVE-2024/CVE-2024-386xx/CVE-2024-38616.json +++ b/CVE-2024/CVE-2024-386xx/CVE-2024-38616.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38616", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:21.403", - "lastModified": "2024-06-19T14:15:21.403", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: carl9170: re-fix fortified-memset warning\n\nThe carl9170_tx_release() function sometimes triggers a fortified-memset\nwarning in my randconfig builds:\n\nIn file included from include/linux/string.h:254,\n from drivers/net/wireless/ath/carl9170/tx.c:40:\nIn function 'fortify_memset_chk',\n inlined from 'carl9170_tx_release' at drivers/net/wireless/ath/carl9170/tx.c:283:2,\n inlined from 'kref_put' at include/linux/kref.h:65:3,\n inlined from 'carl9170_tx_put_skb' at drivers/net/wireless/ath/carl9170/tx.c:342:9:\ninclude/linux/fortify-string.h:493:25: error: call to '__write_overflow_field' declared with attribute warning: detected write beyond size of field (1st parameter); maybe use struct_group()? [-Werror=attribute-warning]\n 493 | __write_overflow_field(p_size_field, size);\n\nKees previously tried to avoid this by using memset_after(), but it seems\nthis does not fully address the problem. I noticed that the memset_after()\nhere is done on a different part of the union (status) than the original\ncast was from (rate_driver_data), which may confuse the compiler.\n\nUnfortunately, the memset_after() trick does not work on driver_rates[]\nbecause that is part of an anonymous struct, and I could not get\nstruct_group() to do this either. Using two separate memset() calls\non the two members does address the warning though." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: wifi: carl9170: volver a corregir la advertencia de memset fortificado La funci\u00f3n carl9170_tx_release() a veces activa una advertencia de memset fortificado en mis compilaciones de randconfig: en el archivo incluido en include/linux/string. h:254, de drivers/net/wireless/ath/carl9170/tx.c:40: en la funci\u00f3n 'fortify_memset_chk', insertado desde 'carl9170_tx_release' en drivers/net/wireless/ath/carl9170/tx.c:283:2 , incluido desde 'kref_put' en include/linux/kref.h:65:3, incluido desde 'carl9170_tx_put_skb' en drivers/net/wireless/ath/carl9170/tx.c:342:9: include/linux/fortify-string .h:493:25: error: llamada a '__write_overflow_field' declarada con advertencia de atributo: escritura detectada m\u00e1s all\u00e1 del tama\u00f1o del campo (primer par\u00e1metro); \u00bfQuiz\u00e1s usar struct_group()? [-Werror=advertencia-atributo] 493 | __write_overflow_field(p_size_field, tama\u00f1o); Kees anteriormente intent\u00f3 evitar esto usando memset_after(), pero parece que esto no soluciona completamente el problema. Me di cuenta de que memset_after() aqu\u00ed se realiza en una parte diferente de la uni\u00f3n (estado) de la que proven\u00eda la conversi\u00f3n original (rate_driver_data), lo que puede confundir al compilador. Desafortunadamente, el truco memset_after() no funciona en driver_rates[] porque es parte de una estructura an\u00f3nima y tampoco pude lograr que struct_group() hiciera esto. Sin embargo, el uso de dos llamadas memset() separadas en los dos miembros soluciona la advertencia." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-386xx/CVE-2024-38617.json b/CVE-2024/CVE-2024-386xx/CVE-2024-38617.json index 2b9d5e5264a..3a5ee048a35 100644 --- a/CVE-2024/CVE-2024-386xx/CVE-2024-38617.json +++ b/CVE-2024/CVE-2024-386xx/CVE-2024-38617.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38617", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:21.490", - "lastModified": "2024-06-19T14:15:21.490", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nkunit/fortify: Fix mismatched kvalloc()/vfree() usage\n\nThe kv*() family of tests were accidentally freeing with vfree() instead\nof kvfree(). Use kvfree() instead." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: kunit/fortify: corrige el uso no coincidente de kvalloc()/vfree() La familia de pruebas kv*() se liberaba accidentalmente con vfree() en lugar de kvfree(). Utilice kvfree() en su lugar." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-386xx/CVE-2024-38618.json b/CVE-2024/CVE-2024-386xx/CVE-2024-38618.json index 233effab038..ca52d407620 100644 --- a/CVE-2024/CVE-2024-386xx/CVE-2024-38618.json +++ b/CVE-2024/CVE-2024-386xx/CVE-2024-38618.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38618", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-19T14:15:21.567", - "lastModified": "2024-06-19T14:15:21.567", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nALSA: timer: Set lower bound of start tick time\n\nCurrently ALSA timer doesn't have the lower limit of the start tick\ntime, and it allows a very small size, e.g. 1 tick with 1ns resolution\nfor hrtimer. Such a situation may lead to an unexpected RCU stall,\nwhere the callback repeatedly queuing the expire update, as reported\nby fuzzer.\n\nThis patch introduces a sanity check of the timer start tick time, so\nthat the system returns an error when a too small start size is set.\nAs of this patch, the lower limit is hard-coded to 100us, which is\nsmall enough but can still work somehow." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: ALSA: temporizador: establece el l\u00edmite inferior del tiempo de inicio. Actualmente, el temporizador ALSA no tiene el l\u00edmite inferior del tiempo de inicio y permite un tama\u00f1o muy peque\u00f1o, por ejemplo, 1 tic. con resoluci\u00f3n de 1ns para hrtimer. Tal situaci\u00f3n puede provocar una parada inesperada de la RCU, donde la devoluci\u00f3n de llamada pone en cola repetidamente la actualizaci\u00f3n caducada, seg\u00fan lo informado por fuzzer. Este parche introduce una verificaci\u00f3n de cordura del tiempo de inicio del temporizador, de modo que el sistema devuelve un error cuando se establece un tama\u00f1o de inicio demasiado peque\u00f1o. A partir de este parche, el l\u00edmite inferior est\u00e1 codificado en 100us, que es bastante peque\u00f1o pero a\u00fan puede funcionar de alguna manera." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-386xx/CVE-2024-38619.json b/CVE-2024/CVE-2024-386xx/CVE-2024-38619.json index f5bad221572..e7fb53c477a 100644 --- a/CVE-2024/CVE-2024-386xx/CVE-2024-38619.json +++ b/CVE-2024/CVE-2024-386xx/CVE-2024-38619.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38619", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-20T07:15:41.830", - "lastModified": "2024-06-20T07:15:41.830", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nusb-storage: alauda: Check whether the media is initialized\n\nThe member \"uzonesize\" of struct alauda_info will remain 0\nif alauda_init_media() fails, potentially causing divide errors\nin alauda_read_data() and alauda_write_lba().\n- Add a member \"media_initialized\" to struct alauda_info.\n- Change a condition in alauda_check_media() to ensure the\n first initialization.\n- Add an error check for the return value of alauda_init_media()." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: usb-storage: alauda: compruebe si el medio est\u00e1 inicializado. El miembro \"uzonesize\" de la estructura alauda_info permanecer\u00e1 0 si alauda_init_media() falla, lo que podr\u00eda provocar errores de divisi\u00f3n en alauda_read_data() y alauda_write_lba(). - Agregue un miembro \"media_initialized\" a la estructura alauda_info. - Cambiar una condici\u00f3n en alauda_check_media() para asegurar la primera inicializaci\u00f3n. - Agregue una verificaci\u00f3n de errores para el valor de retorno de alauda_init_media()." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-386xx/CVE-2024-38620.json b/CVE-2024/CVE-2024-386xx/CVE-2024-38620.json index 046dd601702..dab570f8208 100644 --- a/CVE-2024/CVE-2024-386xx/CVE-2024-38620.json +++ b/CVE-2024/CVE-2024-386xx/CVE-2024-38620.json @@ -2,12 +2,16 @@ "id": "CVE-2024-38620", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "published": "2024-06-20T08:15:38.377", - "lastModified": "2024-06-20T08:15:38.377", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: HCI: Remove HCI_AMP support\n\nSince BT_HS has been remove HCI_AMP controllers no longer has any use so\nremove it along with the capability of creating AMP controllers.\n\nSince we no longer need to differentiate between AMP and Primary\ncontrollers, as only HCI_PRIMARY is left, this also remove\nhdev->dev_type altogether." + }, + { + "lang": "es", + "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: Bluetooth: HCI: eliminar la compatibilidad con HCI_AMP Dado que se elimin\u00f3 BT_HS, los controladores HCI_AMP ya no tienen ning\u00fan uso, as\u00ed que elim\u00ednelos junto con la capacidad de crear controladores AMP. Como ya no necesitamos diferenciar entre los controladores AMP y primarios, ya que solo queda HCI_PRIMARY, esto tambi\u00e9n elimina hdev->dev_type por completo." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-38xx/CVE-2024-3894.json b/CVE-2024/CVE-2024-38xx/CVE-2024-3894.json index 8cf8ed1ea96..45e38e4d220 100644 --- a/CVE-2024/CVE-2024-38xx/CVE-2024-3894.json +++ b/CVE-2024/CVE-2024-38xx/CVE-2024-3894.json @@ -2,12 +2,16 @@ "id": "CVE-2024-3894", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-19T07:15:46.847", - "lastModified": "2024-06-19T07:15:46.847", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The Photo Gallery, Images, Slider in Rbs Image Gallery plugin for WordPress is vulnerable to Stored Cross-Site Scripting via an Image Title in all versions up to, and including, 3.2.19 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page." + }, + { + "lang": "es", + "value": "El complemento Photo Gallery, Images, Slider in Rbs Image Gallery para WordPress es vulnerable a cross-site scripting almacenado a trav\u00e9s de un t\u00edtulo de imagen en todas las versiones hasta la 3.2.19 incluida debido a una sanitizaci\u00f3n de entrada y un escape de salida insuficientes. Esto hace posible que atacantes autenticados, con acceso a nivel de autor y superior, inyecten scripts web arbitrarios en p\u00e1ginas que se ejecutar\u00e1n cada vez que un usuario acceda a una p\u00e1gina inyectada." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-39xx/CVE-2024-3984.json b/CVE-2024/CVE-2024-39xx/CVE-2024-3984.json index ba55dc94226..1782dd57c4e 100644 --- a/CVE-2024/CVE-2024-39xx/CVE-2024-3984.json +++ b/CVE-2024/CVE-2024-39xx/CVE-2024-3984.json @@ -2,12 +2,16 @@ "id": "CVE-2024-3984", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-19T04:15:11.213", - "lastModified": "2024-06-19T04:15:11.213", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The EmbedSocial \u2013 Social Media Feeds, Reviews and Galleries plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'embedsocial_reviews' shortcode in all versions up to, and including, 1.1.29 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." + }, + { + "lang": "es", + "value": "El complemento EmbedSocial \u2013 Social Media Feeds, Reviews and Galleries para WordPress es vulnerable a cross-site scripting almacenado a trav\u00e9s del c\u00f3digo corto 'embedsocial_reviews' del complemento en todas las versiones hasta la 1.1.29 incluida debido a una sanitizaci\u00f3n de entrada insuficiente y a un escape de salida del usuario. atributos proporcionados. Esto hace posible que atacantes autenticados, con acceso de nivel de colaborador y superior, inyecten scripts web arbitrarios en p\u00e1ginas que se ejecutar\u00e1n cada vez que un usuario acceda a una p\u00e1gina inyectada." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-40xx/CVE-2024-4032.json b/CVE-2024/CVE-2024-40xx/CVE-2024-4032.json index b8e733b2fe8..539a20b74ca 100644 --- a/CVE-2024/CVE-2024-40xx/CVE-2024-4032.json +++ b/CVE-2024/CVE-2024-40xx/CVE-2024-4032.json @@ -2,12 +2,16 @@ "id": "CVE-2024-4032", "sourceIdentifier": "cna@python.org", "published": "2024-06-17T15:15:52.517", - "lastModified": "2024-06-17T18:15:18.047", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The \u201cipaddress\u201d module contained incorrect information about whether certain IPv4 and IPv6 addresses were designated as \u201cglobally reachable\u201d or \u201cprivate\u201d. This affected the is_private and is_global properties of the ipaddress.IPv4Address, ipaddress.IPv4Network, ipaddress.IPv6Address, and ipaddress.IPv6Network classes, where values wouldn\u2019t be returned in accordance with the latest information from the IANA Special-Purpose Address Registries.\n\nCPython 3.12.4 and 3.13.0a6 contain updated information from these registries and thus have the intended behavior." + }, + { + "lang": "es", + "value": "El m\u00f3dulo \"ipaddress\" conten\u00eda informaci\u00f3n incorrecta sobre si ciertas direcciones IPv4 e IPv6 estaban designadas como \"accesibles globalmente\" o \"privadas\". Esto afect\u00f3 las propiedades is_private e is_global de las clases ipaddress.IPv4Address, ipaddress.IPv4Network, ipaddress.IPv6Address y ipaddress.IPv6Network, donde los valores no se devolver\u00edan de acuerdo con la informaci\u00f3n m\u00e1s reciente de los Registros de direcciones de prop\u00f3sito especial de la IANA. CPython 3.12.4 y 3.13.0a6 contienen informaci\u00f3n actualizada de estos registros y, por lo tanto, tienen el comportamiento previsto." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-40xx/CVE-2024-4094.json b/CVE-2024/CVE-2024-40xx/CVE-2024-4094.json index ace666b3e7f..1aff4a8d4a6 100644 --- a/CVE-2024/CVE-2024-40xx/CVE-2024-4094.json +++ b/CVE-2024/CVE-2024-40xx/CVE-2024-4094.json @@ -2,12 +2,16 @@ "id": "CVE-2024-4094", "sourceIdentifier": "contact@wpscan.com", "published": "2024-06-18T06:15:12.360", - "lastModified": "2024-06-18T06:15:12.360", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "The Simple Share Buttons Adder WordPress plugin before 8.5.1 does not sanitise and escape some of its settings, which could allow high privilege users such as editors to perform Cross-Site Scripting attacks even when unfiltered_html is disallowed" + }, + { + "lang": "es", + "value": "El complemento Simple Share Buttons Adder de WordPress anterior a 8.5.1 no sanitiza ni escapa a algunas de sus configuraciones, lo que podr\u00eda permitir a usuarios con altos privilegios, como editores, realizar ataques de cross site scripting incluso cuando unfiltered_html no est\u00e1 permitido." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-40xx/CVE-2024-4098.json b/CVE-2024/CVE-2024-40xx/CVE-2024-4098.json index af625bd2eea..5bb718d1534 100644 --- a/CVE-2024/CVE-2024-40xx/CVE-2024-4098.json +++ b/CVE-2024/CVE-2024-40xx/CVE-2024-4098.json @@ -2,12 +2,16 @@ "id": "CVE-2024-4098", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-20T07:15:41.933", - "lastModified": "2024-06-20T07:15:41.933", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The Shariff Wrapper plugin for WordPress is vulnerable to Local File Inclusion in versions up to, and including, 4.6.13 via the shariff3uu_fetch_sharecounts function. This allows unauthenticated attackers to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other \u201csafe\u201d file types can be uploaded and included." + }, + { + "lang": "es", + "value": "El complemento Shariff Wrapper para WordPress es vulnerable a la inclusi\u00f3n de archivos locales en versiones hasta la 4.6.13 incluida a trav\u00e9s de la funci\u00f3n shariff3uu_fetch_sharecounts. Esto permite a atacantes no autenticados incluir y ejecutar archivos arbitrarios en el servidor, permitiendo la ejecuci\u00f3n de cualquier c\u00f3digo PHP en esos archivos. Esto se puede utilizar para eludir los controles de acceso, obtener datos confidenciales o lograr la ejecuci\u00f3n de c\u00f3digo en los casos en que se puedan cargar e incluir im\u00e1genes y otros tipos de archivos \"seguros\"." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-43xx/CVE-2024-4375.json b/CVE-2024/CVE-2024-43xx/CVE-2024-4375.json index 9e01a2d2e5e..5c279c36dfe 100644 --- a/CVE-2024/CVE-2024-43xx/CVE-2024-4375.json +++ b/CVE-2024/CVE-2024-43xx/CVE-2024-4375.json @@ -2,12 +2,16 @@ "id": "CVE-2024-4375", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-18T03:15:09.797", - "lastModified": "2024-06-18T03:15:09.797", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "The Master Slider \u2013 Responsive Touch Slider plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'ms_layer' shortcode in all versions up to, and including, 3.9.10 due to insufficient input sanitization and output escaping on the 'css_id' user supplied attribute. 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." + }, + { + "lang": "es", + "value": "El complemento Master Slider \u2013 Responsive Touch Slider para WordPress es vulnerable a Cross-Site Scripting Almacenado a trav\u00e9s del c\u00f3digo corto 'ms_layer' del complemento en todas las versiones hasta la 3.9.10 incluida debido a una sanitizaci\u00f3n de entrada insuficiente y a un escape de salida en el 'css_id' atributo proporcionado por el usuario. Esto hace posible que atacantes autenticados, con acceso de nivel de colaborador y superior, inyecten scripts web arbitrarios en p\u00e1ginas que se ejecutar\u00e1n cada vez que un usuario acceda a una p\u00e1gina inyectada." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-43xx/CVE-2024-4390.json b/CVE-2024/CVE-2024-43xx/CVE-2024-4390.json index 415b1027482..3a15a1b4f30 100644 --- a/CVE-2024/CVE-2024-43xx/CVE-2024-4390.json +++ b/CVE-2024/CVE-2024-43xx/CVE-2024-4390.json @@ -2,12 +2,16 @@ "id": "CVE-2024-4390", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-20T04:15:17.857", - "lastModified": "2024-06-20T04:15:17.857", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "The Slider and Carousel slider by Depicter plugin for WordPress is vulnerable to Arbitrary Nonce Generation in all versions up to, and including, 3.0.2. This makes it possible for authenticated attackers with contributor access and above, to generate a valid nonce for any WordPress action/function. This could be used to invoke functionality that is protected only by nonce checks." + }, + { + "lang": "es", + "value": "El complemento Slider and Carousel slider by Depicter para WordPress es vulnerable a Arbitrary Nonce Generation en todas las versiones hasta la 3.0.2 incluida. Esto hace posible que los atacantes autenticados con acceso de colaborador y superior generen un nonce v\u00e1lido para cualquier acci\u00f3n/funci\u00f3n de WordPress. Esto podr\u00eda usarse para invocar una funcionalidad que est\u00e1 protegida \u00fanicamente mediante comprobaciones nonce." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-44xx/CVE-2024-4450.json b/CVE-2024/CVE-2024-44xx/CVE-2024-4450.json index c587437cc68..3add9d6bb10 100644 --- a/CVE-2024/CVE-2024-44xx/CVE-2024-4450.json +++ b/CVE-2024/CVE-2024-44xx/CVE-2024-4450.json @@ -2,12 +2,16 @@ "id": "CVE-2024-4450", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-19T04:15:11.497", - "lastModified": "2024-06-19T04:15:11.497", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The AliExpress Dropshipping with AliNext Lite plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on several functions in the ImportAjaxController.php file in all versions up to, and including, 3.3.5. This makes it possible for authenticated attackers, with subscriber-level access and above, to perform several actions like importing and modifying products." + }, + { + "lang": "es", + "value": "El complemento AliExpress Dropshipping con AliNext Lite para WordPress es vulnerable al acceso no autorizado debido a una falta de verificaci\u00f3n de capacidad en varias funciones en el archivo ImportAjaxController.php en todas las versiones hasta la 3.3.5 incluida. Esto hace posible que los atacantes autenticados, con acceso a nivel de suscriptor y superior, realicen varias acciones como importar y modificar productos." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-45xx/CVE-2024-4541.json b/CVE-2024/CVE-2024-45xx/CVE-2024-4541.json index 1f91c32e9e0..0ff23ea1843 100644 --- a/CVE-2024/CVE-2024-45xx/CVE-2024-4541.json +++ b/CVE-2024/CVE-2024-45xx/CVE-2024-4541.json @@ -2,12 +2,16 @@ "id": "CVE-2024-4541", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-19T04:15:11.793", - "lastModified": "2024-06-19T04:15:11.793", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The Custom Product List Table plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.0.0. This is due to missing or incorrect nonce validation when modifying products. This makes it possible for unauthenticated attackers to add, delete, bulk edit, approve or cancel products via a forged request granted they can trick a site administrator into performing an action such as clicking on a link." + }, + { + "lang": "es", + "value": "El complemento Custom Product List Table para WordPress es vulnerable a Cross-Site Request Forgery en todas las versiones hasta la 3.0.0 incluida. Esto se debe a una validaci\u00f3n nonce faltante o incorrecta al modificar productos. Esto hace posible que atacantes no autenticados agreguen, eliminen, editen en masa, aprueben o cancelen productos a trav\u00e9s de una solicitud falsificada, siempre que puedan enga\u00f1ar a un administrador del sitio para que realice una acci\u00f3n como hacer clic en un enlace." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-45xx/CVE-2024-4565.json b/CVE-2024/CVE-2024-45xx/CVE-2024-4565.json index 5b382fc9ee3..3f9595f96e8 100644 --- a/CVE-2024/CVE-2024-45xx/CVE-2024-4565.json +++ b/CVE-2024/CVE-2024-45xx/CVE-2024-4565.json @@ -2,12 +2,16 @@ "id": "CVE-2024-4565", "sourceIdentifier": "contact@wpscan.com", "published": "2024-06-20T06:15:09.950", - "lastModified": "2024-06-20T06:15:09.950", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "The Advanced Custom Fields (ACF) WordPress plugin before 6.3, Advanced Custom Fields Pro WordPress plugin before 6.3 allows you to display custom field values for any post via shortcode without checking for the correct access" + }, + { + "lang": "es", + "value": "El complemento Advanced Custom Fields (ACF) WordPress anterior a 6.3, el complemento de Advanced Custom Fields Pro WordPress anterior a 6.3 le permite mostrar valores de campo personalizados para cualquier publicaci\u00f3n mediante un c\u00f3digo corto sin verificar el acceso correcto" } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-46xx/CVE-2024-4623.json b/CVE-2024/CVE-2024-46xx/CVE-2024-4623.json index 69e486feea7..f108b242fb0 100644 --- a/CVE-2024/CVE-2024-46xx/CVE-2024-4623.json +++ b/CVE-2024/CVE-2024-46xx/CVE-2024-4623.json @@ -2,12 +2,16 @@ "id": "CVE-2024-4623", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-19T04:15:12.107", - "lastModified": "2024-06-19T04:15:12.107", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The Blogmentor \u2013 Blog Layouts for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the \u2018pagination_style\u2019 parameter in all versions up to, and including, 1.5 due to insufficient input sanitization and output escaping. 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." + }, + { + "lang": "es", + "value": "El complemento Blogmentor \u2013 Blog Layouts for Elementor para WordPress es vulnerable a cross-site scripting almacenado a trav\u00e9s del par\u00e1metro 'pagination_style' en todas las versiones hasta la 1.5 incluida debido a una sanitizaci\u00f3n de entrada y un escape de salida insuficientes. Esto hace posible que atacantes autenticados, con acceso de nivel de colaborador y superior, inyecten scripts web arbitrarios en p\u00e1ginas que se ejecutar\u00e1n cada vez que un usuario acceda a una p\u00e1gina inyectada." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-46xx/CVE-2024-4626.json b/CVE-2024/CVE-2024-46xx/CVE-2024-4626.json index f7d025f1cc2..153902c85c8 100644 --- a/CVE-2024/CVE-2024-46xx/CVE-2024-4626.json +++ b/CVE-2024/CVE-2024-46xx/CVE-2024-4626.json @@ -2,12 +2,16 @@ "id": "CVE-2024-4626", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-20T02:15:11.270", - "lastModified": "2024-06-20T02:15:11.270", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "The JetWidgets For Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the \u2018layout_type\u2019 and 'id' parameters in all versions up to, and including, 1.0.17 due to insufficient input sanitization and output escaping. 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." + }, + { + "lang": "es", + "value": "El complemento JetWidgets For Elementor para WordPress es vulnerable a Cross-Site Scripting Almacenado a trav\u00e9s de los par\u00e1metros 'layout_type' e 'id' en todas las versiones hasta la 1.0.17 incluida debido a una sanitizaci\u00f3n de entrada y un escape de salida insuficientes. Esto hace posible que atacantes autenticados, con acceso de nivel de colaborador y superior, inyecten scripts web arbitrarios en p\u00e1ginas que se ejecutar\u00e1n cada vez que un usuario acceda a una p\u00e1gina inyectada." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-46xx/CVE-2024-4632.json b/CVE-2024/CVE-2024-46xx/CVE-2024-4632.json index 1496aaa0192..34be3ef1d22 100644 --- a/CVE-2024/CVE-2024-46xx/CVE-2024-4632.json +++ b/CVE-2024/CVE-2024-46xx/CVE-2024-4632.json @@ -2,12 +2,16 @@ "id": "CVE-2024-4632", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-19T09:15:11.740", - "lastModified": "2024-06-19T09:15:11.740", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The WooCommerce Checkout & Funnel Builder by CartFlows \u2013 Create High Converting Stores For WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the \u2018custom_upload_mimes\u2019 function in versions up to, and including, 2.0.7 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page." + }, + { + "lang": "es", + "value": "El complemento WooCommerce Checkout & Funnel Builder by CartFlows \u2013 Create High Converting Stores For WooCommerce para WordPress es vulnerable a cross-site scripting almacenado a trav\u00e9s de la funci\u00f3n 'custom_upload_mimes' en versiones hasta la 2.0.7 incluida debido a una sanitizaci\u00f3n de entrada y salida insuficiente escapando. Esto hace posible que atacantes autenticados, con permisos de nivel de colaborador y superiores, inyecten scripts web arbitrarios en p\u00e1ginas que se ejecutar\u00e1n cada vez que un usuario acceda a una p\u00e1gina inyectada." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-46xx/CVE-2024-4663.json b/CVE-2024/CVE-2024-46xx/CVE-2024-4663.json index b6251fa44da..4d8a3e28dbd 100644 --- a/CVE-2024/CVE-2024-46xx/CVE-2024-4663.json +++ b/CVE-2024/CVE-2024-46xx/CVE-2024-4663.json @@ -2,12 +2,16 @@ "id": "CVE-2024-4663", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-19T04:15:12.403", - "lastModified": "2024-06-19T04:15:12.403", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The OSM Map Widget for Elementor plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the \u2018id\u2019 parameter in all versions up to, and including, 1.2.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers 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." + }, + { + "lang": "es", + "value": "El complemento OSM Map Widget para Elementor para WordPress es vulnerable a Cross-Site Scripting Reflejado a trav\u00e9s del par\u00e1metro 'id' en todas las versiones hasta la 1.2.2 incluida debido a una sanitizaci\u00f3n de entrada y un escape de salida insuficientes. Esto hace posible que atacantes no autenticados inyecten scripts web arbitrarios en p\u00e1ginas que se ejecutan si logran enga\u00f1ar a un usuario para que realice una acci\u00f3n como hacer clic en un enlace." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-47xx/CVE-2024-4742.json b/CVE-2024/CVE-2024-47xx/CVE-2024-4742.json index 181cce3c286..ad41f70d73f 100644 --- a/CVE-2024/CVE-2024-47xx/CVE-2024-4742.json +++ b/CVE-2024/CVE-2024-47xx/CVE-2024-4742.json @@ -2,12 +2,16 @@ "id": "CVE-2024-4742", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-20T02:15:11.500", - "lastModified": "2024-06-20T02:15:11.500", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "The Youzify \u2013 BuddyPress Community, User Profile, Social Network & Membership Plugin for WordPress plugin for WordPress is vulnerable to SQL Injection via the order_by shortcode attribute in all versions up to, and including, 1.2.5 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database." + }, + { + "lang": "es", + "value": "El complemento Youzify \u2013 BuddyPress Community, User Profile, Social Network & Membership Plugin para WordPress es vulnerable a la inyecci\u00f3n SQL a trav\u00e9s del atributo shortcode order_by en todas las versiones hasta la 1.2.5 incluida debido a un escape insuficiente en el par\u00e1metro proporcionado por el usuario. y falta de preparaci\u00f3n suficiente en la consulta SQL existente. Esto hace posible que los atacantes autenticados, con acceso de nivel de colaborador y superior, agreguen consultas SQL adicionales a consultas ya existentes que pueden usarse para extraer informaci\u00f3n confidencial de la base de datos." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-47xx/CVE-2024-4787.json b/CVE-2024/CVE-2024-47xx/CVE-2024-4787.json index eca23ea553c..d6c0f7ddb44 100644 --- a/CVE-2024/CVE-2024-47xx/CVE-2024-4787.json +++ b/CVE-2024/CVE-2024-47xx/CVE-2024-4787.json @@ -2,12 +2,16 @@ "id": "CVE-2024-4787", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-19T04:15:12.730", - "lastModified": "2024-06-19T04:15:12.730", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The Cost Calculator Builder PRO for WordPress is vulnerable to arbitrary email sending vulnerability in versions up to, and including, 3.1.75. This is due to insufficient limitations on the email recipient and the content in the 'send_pdf' and the 'send_pdf_front' functions which are reachable via AJAX. This makes it possible for unauthenticated attackers to send emails with any content to any recipient." + }, + { + "lang": "es", + "value": "Cost Calculator Builder PRO para WordPress es vulnerable a una vulnerabilidad de env\u00edo de correo electr\u00f3nico arbitrario en versiones hasta la 3.1.75 incluida. Esto se debe a limitaciones insuficientes en el destinatario del correo electr\u00f3nico y el contenido de las funciones 'send_pdf' y 'send_pdf_front' a las que se puede acceder a trav\u00e9s de AJAX. Esto hace posible que atacantes no autenticados env\u00eden correos electr\u00f3nicos con cualquier contenido a cualquier destinatario." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-48xx/CVE-2024-4873.json b/CVE-2024/CVE-2024-48xx/CVE-2024-4873.json index 17dd6027405..8e722063a49 100644 --- a/CVE-2024/CVE-2024-48xx/CVE-2024-4873.json +++ b/CVE-2024/CVE-2024-48xx/CVE-2024-4873.json @@ -2,12 +2,16 @@ "id": "CVE-2024-4873", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-19T04:15:12.990", - "lastModified": "2024-06-19T04:15:12.990", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The Replace Image plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.1.10 via the image replacement functionality due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Author-level access and above, to replace images uploaded by higher level users such as admins." + }, + { + "lang": "es", + "value": "El complemento Replace Image para WordPress es vulnerable a Insecure Direct Object Reference en todas las versiones hasta la 1.1.10 incluida a trav\u00e9s de la funcionalidad de reemplazo de imagen debido a la falta de validaci\u00f3n en una clave controlada por el usuario. Esto hace posible que atacantes autenticados, con acceso de nivel de autor y superior, reemplacen im\u00e1genes cargadas por usuarios de nivel superior, como administradores." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-50xx/CVE-2024-5021.json b/CVE-2024/CVE-2024-50xx/CVE-2024-5021.json index bdf2ab2b2be..7759f8c872c 100644 --- a/CVE-2024/CVE-2024-50xx/CVE-2024-5021.json +++ b/CVE-2024/CVE-2024-50xx/CVE-2024-5021.json @@ -2,12 +2,16 @@ "id": "CVE-2024-5021", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-19T04:15:13.310", - "lastModified": "2024-06-19T04:15:13.310", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The WordPress Picture / Portfolio / Media Gallery plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 3.0.1 via the 'file_get_contents' function. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services." + }, + { + "lang": "es", + "value": "El complemento WordPress Picture / Portfolio / Media Gallery para WordPress es vulnerable a Server-Side Request Forgery en todas las versiones hasta la 3.0.1 incluida a trav\u00e9s de la funci\u00f3n 'file_get_contents'. Esto hace posible que atacantes no autenticados realicen solicitudes web a ubicaciones arbitrarias que se originan en la aplicaci\u00f3n web y pueden usarse para consultar y modificar informaci\u00f3n de servicios internos." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-50xx/CVE-2024-5036.json b/CVE-2024/CVE-2024-50xx/CVE-2024-5036.json index f50d25975e2..3d4b9a660d7 100644 --- a/CVE-2024/CVE-2024-50xx/CVE-2024-5036.json +++ b/CVE-2024/CVE-2024-50xx/CVE-2024-5036.json @@ -2,12 +2,16 @@ "id": "CVE-2024-5036", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-20T11:15:56.273", - "lastModified": "2024-06-20T11:15:56.273", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The Sina Extension for Elementor (Slider, Gallery, Form, Modal, Data Table, Tab, Particle, Free Elementor Widgets & Elementor Templates) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the \u2018url\u2019 parameter in all versions up to, and including, 3.5.4 due to insufficient input sanitization and output escaping. 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." + }, + { + "lang": "es", + "value": "La extensi\u00f3n Sina para Elementor (control deslizante, galer\u00eda, formulario, modal, tabla de datos, pesta\u00f1a, part\u00edcula, widgets de Elementor gratuitos y plantillas de Elementor) para WordPress es vulnerable a Cross-Site Scripting Almacenado a trav\u00e9s del par\u00e1metro 'url' en todas las versiones hasta , e incluyendo, 3.5.4 debido a una sanitizaci\u00f3n insuficiente de los insumos y al escape de los productos. Esto hace posible que atacantes autenticados, con acceso de nivel de Colaborador y superior, inyecten scripts web arbitrarios en p\u00e1ginas que se ejecutar\u00e1n cada vez que un usuario acceda a una p\u00e1gina inyectada." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-51xx/CVE-2024-5172.json b/CVE-2024/CVE-2024-51xx/CVE-2024-5172.json index 54fa6a3e874..9294c1e4269 100644 --- a/CVE-2024/CVE-2024-51xx/CVE-2024-5172.json +++ b/CVE-2024/CVE-2024-51xx/CVE-2024-5172.json @@ -2,12 +2,16 @@ "id": "CVE-2024-5172", "sourceIdentifier": "contact@wpscan.com", "published": "2024-06-18T06:15:12.440", - "lastModified": "2024-06-18T06:15:12.440", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "The Expert Invoice WordPress plugin through 1.0.2 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup)" + }, + { + "lang": "es", + "value": "El complemento Expert Invoice de WordPress hasta la versi\u00f3n 1.0.2 no sanitiza ni escapa a algunas de sus configuraciones, lo que podr\u00eda permitir a usuarios con privilegios elevados, como el administrador, realizar ataques de Cross-Site Scripting Almacenado incluso cuando la capacidad unfiltered_html no est\u00e1 permitida (por ejemplo, en una configuraci\u00f3n multisitio)." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-51xx/CVE-2024-5182.json b/CVE-2024/CVE-2024-51xx/CVE-2024-5182.json index 80efa1cec2e..bd2bc3ba3ea 100644 --- a/CVE-2024/CVE-2024-51xx/CVE-2024-5182.json +++ b/CVE-2024/CVE-2024-51xx/CVE-2024-5182.json @@ -2,12 +2,16 @@ "id": "CVE-2024-5182", "sourceIdentifier": "security@huntr.dev", "published": "2024-06-20T00:15:09.487", - "lastModified": "2024-06-20T00:15:09.487", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A path traversal vulnerability exists in mudler/localai version 2.14.0, where an attacker can exploit the `model` parameter during the model deletion process to delete arbitrary files. Specifically, by crafting a request with a manipulated `model` parameter, an attacker can traverse the directory structure and target files outside of the intended directory, leading to the deletion of sensitive data. This vulnerability is due to insufficient input validation and sanitization of the `model` parameter." + }, + { + "lang": "es", + "value": "Existe una vulnerabilidad de path traversal en mudler/localai versi\u00f3n 2.14.0, donde un atacante puede explotar el par\u00e1metro `model` durante el proceso de eliminaci\u00f3n del modelo para eliminar archivos arbitrarios. Espec\u00edficamente, al elaborar una solicitud con un par\u00e1metro \"modelo\" manipulado, un atacante puede atravesar la estructura del directorio y apuntar a archivos fuera del directorio deseado, lo que lleva a la eliminaci\u00f3n de datos confidenciales. Esta vulnerabilidad se debe a una validaci\u00f3n de entrada y una sanitizaci\u00f3n insuficientes del par\u00e1metro \"modelo\"." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-52xx/CVE-2024-5208.json b/CVE-2024/CVE-2024-52xx/CVE-2024-5208.json index cd4f2094db6..413e3d014b0 100644 --- a/CVE-2024/CVE-2024-52xx/CVE-2024-5208.json +++ b/CVE-2024/CVE-2024-52xx/CVE-2024-5208.json @@ -2,12 +2,16 @@ "id": "CVE-2024-5208", "sourceIdentifier": "security@huntr.dev", "published": "2024-06-19T06:15:11.420", - "lastModified": "2024-06-19T06:15:11.420", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "An uncontrolled resource consumption vulnerability exists in the `upload-link` endpoint of mintplex-labs/anything-llm. This vulnerability allows attackers to cause a denial of service (DOS) by shutting down the server through sending invalid upload requests. Specifically, the server can be made to shut down by sending an empty body with a 'Content-Length: 0' header or by sending a body with arbitrary content, such as 'asdasdasd', with a 'Content-Length: 9' header. The vulnerability is reproducible by users with at least a 'Manager' role, sending a crafted request to any workspace. This issue indicates that a previous fix was not effective in mitigating the vulnerability." + }, + { + "lang": "es", + "value": "Existe una vulnerabilidad de consumo de recursos incontrolado en el endpoint `upload-link` de mintplex-labs/anything-llm. Esta vulnerabilidad permite a los atacantes provocar una denegaci\u00f3n de servicio (DOS) apagando el servidor mediante el env\u00edo de solicitudes de carga no v\u00e1lidas. Espec\u00edficamente, se puede hacer que el servidor se apague enviando un cuerpo vac\u00edo con un encabezado 'Content-Length: 0' o enviando un cuerpo con contenido arbitrario, como 'asdasdasd', con un encabezado 'Content-Length: 9'. . La vulnerabilidad es reproducible por usuarios con al menos un rol de \"Administrador\", enviando una solicitud manipulada a cualquier espacio de trabajo. Este problema indica que una soluci\u00f3n anterior no fue eficaz para mitigar la vulnerabilidad." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-52xx/CVE-2024-5213.json b/CVE-2024/CVE-2024-52xx/CVE-2024-5213.json index 59b28537fde..3cc4045b4a1 100644 --- a/CVE-2024/CVE-2024-52xx/CVE-2024-5213.json +++ b/CVE-2024/CVE-2024-52xx/CVE-2024-5213.json @@ -2,12 +2,16 @@ "id": "CVE-2024-5213", "sourceIdentifier": "security@huntr.dev", "published": "2024-06-20T03:15:09.067", - "lastModified": "2024-06-20T03:15:09.067", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "In mintplex-labs/anything-llm versions up to and including 1.5.3, an issue was discovered where the password hash of a user is returned in the response after login (`POST /api/request-token`) and after account creations (`POST /api/admin/users/new`). This exposure occurs because the entire User object, including the bcrypt password hash, is included in the response sent to the frontend. This practice could potentially lead to sensitive information exposure despite the use of bcrypt, a strong hashing algorithm. It is recommended not to expose any clues about passwords to the frontend. " + }, + { + "lang": "es", + "value": "En las versiones de mintplex-labs/anything-llm hasta la 1.5.3 incluida, se descubri\u00f3 un problema por el cual el hash de la contrase\u00f1a de un usuario se devuelve en la respuesta despu\u00e9s de iniciar sesi\u00f3n (`POST /api/request-token`) y despu\u00e9s de la creaci\u00f3n de la cuenta. (`POST /api/admin/usuarios/nuevo`). Esta exposici\u00f3n se produce porque todo el objeto Usuario, incluido el hash de la contrase\u00f1a de bcrypt, se incluye en la respuesta enviada al frontend. Esta pr\u00e1ctica podr\u00eda conducir potencialmente a la exposici\u00f3n de informaci\u00f3n confidencial a pesar del uso de bcrypt, un potente algoritmo hash. Se recomienda no exponer ninguna pista sobre contrase\u00f1as en la interfaz." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-52xx/CVE-2024-5275.json b/CVE-2024/CVE-2024-52xx/CVE-2024-5275.json index 6a5965f8670..399e45ce5d1 100644 --- a/CVE-2024/CVE-2024-52xx/CVE-2024-5275.json +++ b/CVE-2024/CVE-2024-52xx/CVE-2024-5275.json @@ -2,12 +2,16 @@ "id": "CVE-2024-5275", "sourceIdentifier": "df4dee71-de3a-4139-9588-11b62fe6c0ff", "published": "2024-06-18T15:15:52.493", - "lastModified": "2024-06-18T15:15:52.493", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A hard-coded password in the FileCatalyst TransferAgent can be found which can be used to unlock the keystore from which contents may be read out, for example, the private key for certificates. Exploit of this vulnerability could lead to a machine-in-the-middle (MiTM) attack against users of the agent. This issue affects all versions of FileCatalyst Direct from 3.8.10 Build 138 and earlier and all versions of\u00a0FileCatalyst Workflow from 5.1.6 Build 130 and earlier." + }, + { + "lang": "es", + "value": "Se puede encontrar una contrase\u00f1a codificada en FileCatalyst TransferAgent que se puede usar para desbloquear el almac\u00e9n de claves desde el cual se pueden leer los contenidos, por ejemplo, la clave privada para los certificados. La explotaci\u00f3n de esta vulnerabilidad podr\u00eda dar lugar a un ataque de m\u00e1quina intermedia (MiTM) contra los usuarios del agente. Este problema afecta a todas las versiones de FileCatalyst Direct desde 3.8.10 Build 138 y anteriores y a todas las versiones de FileCatalyst Workflow desde 5.1.6 Build 130 y anteriores." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-53xx/CVE-2024-5343.json b/CVE-2024/CVE-2024-53xx/CVE-2024-5343.json index 10b4eaabf25..4cb2a77635d 100644 --- a/CVE-2024/CVE-2024-53xx/CVE-2024-5343.json +++ b/CVE-2024/CVE-2024-53xx/CVE-2024-5343.json @@ -2,12 +2,16 @@ "id": "CVE-2024-5343", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-19T06:15:11.723", - "lastModified": "2024-06-19T06:15:11.723", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The Photo Gallery, Images, Slider in Rbs Image Gallery plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.2.19. This is due to missing or incorrect nonce validation on the 'rbs_ajax_create_article' and 'rbs_ajax_reset_views' functions. This makes it possible for unauthenticated attackers to create new posts and reset gallery view counts via a forged request granted they can trick a Contributor+ level user into performing an action such as clicking on a link." + }, + { + "lang": "es", + "value": "El complemento Photo Gallery, Images, Slider in Rbs Image Gallery para WordPress es vulnerable a Cross-Site Request Forgery en todas las versiones hasta la 3.2.19 incluida. Esto se debe a una validaci\u00f3n nonce faltante o incorrecta en las funciones 'rbs_ajax_create_article' y 'rbs_ajax_reset_views'. Esto hace posible que atacantes no autenticados creen nuevas publicaciones y restablezcan el recuento de vistas de la galer\u00eda a trav\u00e9s de una solicitud falsificada, siempre que puedan enga\u00f1ar a un usuario de nivel Contributor+ para que realice una acci\u00f3n como hacer clic en un enlace." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-54xx/CVE-2024-5432.json b/CVE-2024/CVE-2024-54xx/CVE-2024-5432.json index 0da96b3d5eb..2970e7c5613 100644 --- a/CVE-2024/CVE-2024-54xx/CVE-2024-5432.json +++ b/CVE-2024/CVE-2024-54xx/CVE-2024-5432.json @@ -2,12 +2,16 @@ "id": "CVE-2024-5432", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-20T02:15:11.737", - "lastModified": "2024-06-20T02:15:11.737", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "The Lifeline Donation plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 1.2.6. This is due to insufficient verification on the user being supplied during the checkout through the plugin. 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." + }, + { + "lang": "es", + "value": "El complemento Lifeline Donation para WordPress es vulnerable a la omisi\u00f3n de autenticaci\u00f3n en versiones hasta la 1.2.6 incluida. Esto se debe a una verificaci\u00f3n insuficiente del usuario que se proporciona durante el pago a trav\u00e9s del complemento. Esto hace posible que atacantes no autenticados inicien sesi\u00f3n como cualquier usuario existente en el sitio, como un administrador, si tienen acceso al correo electr\u00f3nico." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-54xx/CVE-2024-5475.json b/CVE-2024/CVE-2024-54xx/CVE-2024-5475.json index 363d1b44bf4..9eb4ee78ccb 100644 --- a/CVE-2024/CVE-2024-54xx/CVE-2024-5475.json +++ b/CVE-2024/CVE-2024-54xx/CVE-2024-5475.json @@ -2,12 +2,16 @@ "id": "CVE-2024-5475", "sourceIdentifier": "contact@wpscan.com", "published": "2024-06-20T06:15:10.077", - "lastModified": "2024-06-20T06:15:10.077", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The Responsive video embed WordPress plugin before 0.5.1 does not validate and escape some of its shortcode attributes before outputting them back in a page/post where the shortcode is embed, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks." + }, + { + "lang": "es", + "value": "El complemento Responsive video embed de WordPress anterior a 0.5.1 no valida ni escapa algunos de sus atributos de c\u00f3digo corto antes de devolverlos a una p\u00e1gina/publicaci\u00f3n donde se incrusta el c\u00f3digo corto, lo que podr\u00eda permitir a los usuarios con el rol de colaborador y superior realizar ataques de Cross-Site Scripting Almacenado." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-55xx/CVE-2024-5522.json b/CVE-2024/CVE-2024-55xx/CVE-2024-5522.json index 787eea8efdf..866044d80bd 100644 --- a/CVE-2024/CVE-2024-55xx/CVE-2024-5522.json +++ b/CVE-2024/CVE-2024-55xx/CVE-2024-5522.json @@ -2,12 +2,16 @@ "id": "CVE-2024-5522", "sourceIdentifier": "contact@wpscan.com", "published": "2024-06-20T06:15:10.197", - "lastModified": "2024-06-20T06:15:10.197", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The HTML5 Video Player WordPress plugin before 2.5.27 does not sanitize and escape a parameter from a REST route before using it in a SQL statement, allowing unauthenticated users to perform SQL injection attacks" + }, + { + "lang": "es", + "value": "El complemento HTML5 Video Player de WordPress anterior a 2.5.27 no sanitiza ni escapa un par\u00e1metro de una ruta REST antes de usarlo en una declaraci\u00f3n SQL, lo que permite a usuarios no autenticados realizar ataques de inyecci\u00f3n SQL." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-55xx/CVE-2024-5533.json b/CVE-2024/CVE-2024-55xx/CVE-2024-5533.json index 54017c8f2ab..8364f2be891 100644 --- a/CVE-2024/CVE-2024-55xx/CVE-2024-5533.json +++ b/CVE-2024/CVE-2024-55xx/CVE-2024-5533.json @@ -2,12 +2,16 @@ "id": "CVE-2024-5533", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-18T08:15:50.723", - "lastModified": "2024-06-18T08:15:50.723", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "The Divi theme for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 4.25.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page." + }, + { + "lang": "es", + "value": "El tema Divi para WordPress es vulnerable a Cross-Site Scripting Almacenado en todas las versiones hasta la 4.25.1 incluida debido a una sanitizaci\u00f3n de entrada y un escape de salida insuficientes. Esto hace posible que atacantes autenticados, con acceso de nivel de autor y superior, inyecten scripts web arbitrarios en p\u00e1ginas que se ejecutar\u00e1n cada vez que un usuario acceda a una p\u00e1gina inyectada." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-55xx/CVE-2024-5541.json b/CVE-2024/CVE-2024-55xx/CVE-2024-5541.json index 80c2bacac6c..c2e095bf76d 100644 --- a/CVE-2024/CVE-2024-55xx/CVE-2024-5541.json +++ b/CVE-2024/CVE-2024-55xx/CVE-2024-5541.json @@ -2,12 +2,16 @@ "id": "CVE-2024-5541", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-18T03:15:10.020", - "lastModified": "2024-06-18T03:15:10.020", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "The Ibtana \u2013 WordPress Website Builder plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'ibtana_visual_editor_register_ajax_json_endpont' function in all versions up to, and including, 1.2.3.3. This makes it possible for unauthenticated attackers to update option values for reCAPTCHA keys on the WordPress site. This can be leveraged to bypass reCAPTCHA on the site." + }, + { + "lang": "es", + "value": "El complemento Ibtana \u2013 WordPress Website Builder para WordPress es vulnerable a modificaciones no autorizadas de datos debido a una falta de verificaci\u00f3n de capacidad en la funci\u00f3n 'ibtana_visual_editor_register_ajax_json_endpont' en todas las versiones hasta la 1.2.3.3 incluida. Esto hace posible que atacantes no autenticados actualicen los valores de las opciones para las claves reCAPTCHA en el sitio de WordPress. Esto se puede aprovechar para evitar reCAPTCHA en el sitio." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-55xx/CVE-2024-5574.json b/CVE-2024/CVE-2024-55xx/CVE-2024-5574.json index ebf05781a05..03a2c8dcb6d 100644 --- a/CVE-2024/CVE-2024-55xx/CVE-2024-5574.json +++ b/CVE-2024/CVE-2024-55xx/CVE-2024-5574.json @@ -2,12 +2,16 @@ "id": "CVE-2024-5574", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-19T06:15:11.993", - "lastModified": "2024-06-19T06:15:11.993", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The WP Magazine Modules Lite plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.1.2 via the 'blockLayout' parameter. This makes it possible for authenticated attackers, with Contributor-level access and above, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other \u201csafe\u201d file types can be uploaded and included." + }, + { + "lang": "es", + "value": "El complemento WP Magazine Modules Lite para WordPress es vulnerable a la inclusi\u00f3n de archivos locales en todas las versiones hasta la 1.1.2 incluida a trav\u00e9s del par\u00e1metro 'blockLayout'. Esto hace posible que atacantes autenticados, con acceso de nivel Colaborador y superior, incluyan y ejecuten archivos arbitrarios en el servidor, permitiendo la ejecuci\u00f3n de cualquier c\u00f3digo PHP en esos archivos. Esto se puede utilizar para eludir los controles de acceso, obtener datos confidenciales o lograr la ejecuci\u00f3n de c\u00f3digo en los casos en que se puedan cargar e incluir im\u00e1genes y otros tipos de archivos \"seguros\"." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-56xx/CVE-2024-5605.json b/CVE-2024/CVE-2024-56xx/CVE-2024-5605.json index f8fec8ea540..1023cb4bc68 100644 --- a/CVE-2024/CVE-2024-56xx/CVE-2024-5605.json +++ b/CVE-2024/CVE-2024-56xx/CVE-2024-5605.json @@ -2,12 +2,16 @@ "id": "CVE-2024-5605", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-20T04:15:18.590", - "lastModified": "2024-06-20T04:15:18.590", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "The Media Library Assistant plugin for WordPress is vulnerable to time-based SQL Injection via the \u2018order\u2019 parameter within the mla_tag_cloud Shortcode in all versions up to, and including, 3.16 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database." + }, + { + "lang": "es", + "value": "El complemento Media Library Assistant para WordPress es vulnerable a la inyecci\u00f3n SQL basada en tiempo a trav\u00e9s del par\u00e1metro 'order' dentro del c\u00f3digo corto mla_tag_cloud en todas las versiones hasta la 3.16 incluida debido a un escape insuficiente en el par\u00e1metro proporcionado por el usuario y a la falta de preparaci\u00f3n suficiente en la consulta SQL existente. Esto hace posible que los atacantes autenticados, con acceso de nivel de colaborador y superior, agreguen consultas SQL adicionales a consultas ya existentes que pueden usarse para extraer informaci\u00f3n confidencial de la base de datos." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-56xx/CVE-2024-5649.json b/CVE-2024/CVE-2024-56xx/CVE-2024-5649.json index 7d721b2e9f5..9f1a5e56efb 100644 --- a/CVE-2024/CVE-2024-56xx/CVE-2024-5649.json +++ b/CVE-2024/CVE-2024-56xx/CVE-2024-5649.json @@ -2,12 +2,16 @@ "id": "CVE-2024-5649", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-19T04:15:13.583", - "lastModified": "2024-06-19T04:15:13.583", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The Universal Slider plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.6.5 via deserialization of untrusted input 'fsl_get_gallery_value' function. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code." + }, + { + "lang": "es", + "value": "El complemento Universal Slider para WordPress es vulnerable a la inyecci\u00f3n de objetos PHP en todas las versiones hasta la 1.6.5 incluida a trav\u00e9s de la deserializaci\u00f3n de la funci\u00f3n 'fsl_get_gallery_value' de entrada no confiable. Esto hace posible que atacantes autenticados, con acceso de nivel de colaborador y superior, inyecten un objeto PHP. No hay ninguna cadena POP conocida presente en el software vulnerable. Si hay una cadena POP presente a trav\u00e9s de un complemento o tema adicional instalado en el sistema de destino, podr\u00eda permitir al atacante eliminar archivos arbitrarios, recuperar datos confidenciales o ejecutar c\u00f3digo." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-56xx/CVE-2024-5676.json b/CVE-2024/CVE-2024-56xx/CVE-2024-5676.json index 336ec092178..592afac1e4d 100644 --- a/CVE-2024/CVE-2024-56xx/CVE-2024-5676.json +++ b/CVE-2024/CVE-2024-56xx/CVE-2024-5676.json @@ -2,12 +2,16 @@ "id": "CVE-2024-5676", "sourceIdentifier": "1e3a9e0f-5156-4bf8-b8a3-cc311bfc0f4a", "published": "2024-06-19T10:15:10.740", - "lastModified": "2024-06-19T10:15:10.740", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The Paradox IP150 Internet Module in version 1.40.00 is vulnerable to Cross-Site Request Forgery (CSRF) attacks due to a lack of countermeasures and the use of the HTTP method `GET` to introduce changes in the system." + }, + { + "lang": "es", + "value": "El m\u00f3dulo de Internet Paradox IP150 en la versi\u00f3n 1.40.00 es vulnerable a ataques de Cross-Site Request Forgery (CSRF) debido a la falta de contramedidas y al uso del m\u00e9todo HTTP `GET` para introducir cambios en el sistema." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-56xx/CVE-2024-5686.json b/CVE-2024/CVE-2024-56xx/CVE-2024-5686.json index 91309b0249d..1ec1e776c4b 100644 --- a/CVE-2024/CVE-2024-56xx/CVE-2024-5686.json +++ b/CVE-2024/CVE-2024-56xx/CVE-2024-5686.json @@ -2,12 +2,16 @@ "id": "CVE-2024-5686", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-20T04:15:18.890", - "lastModified": "2024-06-20T04:15:18.890", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "The WPZOOM Addons for Elementor (Templates, Widgets) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the \u2018url\u2019 attribute within the plugin's Team Members widget in all versions up to, and including, 1.1.38 due to insufficient input sanitization and output escaping. 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." + }, + { + "lang": "es", + "value": "El complemento WPZOOM Addons for Elementor (Plantillas, Widgets) para WordPress es vulnerable a Cross-Site Scripting Almacenado a trav\u00e9s del atributo 'url' dentro del widget Miembros del equipo del complemento en todas las versiones hasta la 1.1.38 incluida debido a una sanitizaci\u00f3n de entrada insuficiente y el escape de salida. Esto hace posible que atacantes autenticados, con acceso de nivel de Colaborador y superior, inyecten scripts web arbitrarios en p\u00e1ginas que se ejecutar\u00e1n cada vez que un usuario acceda a una p\u00e1gina inyectada." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-57xx/CVE-2024-5724.json b/CVE-2024/CVE-2024-57xx/CVE-2024-5724.json index 029e10a858c..65c4f7329c6 100644 --- a/CVE-2024/CVE-2024-57xx/CVE-2024-5724.json +++ b/CVE-2024/CVE-2024-57xx/CVE-2024-5724.json @@ -2,12 +2,16 @@ "id": "CVE-2024-5724", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-19T04:15:13.860", - "lastModified": "2024-06-19T04:15:13.860", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The Photo Video Gallery Master plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.5.3 via deserialization of untrusted input 'PVGM_all_photos_details' parameter. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code." + }, + { + "lang": "es", + "value": "El complemento Photo Video Gallery Master para WordPress es vulnerable a la inyecci\u00f3n de objetos PHP en todas las versiones hasta la 1.5.3 incluida a trav\u00e9s de la deserializaci\u00f3n del par\u00e1metro de entrada no confiable 'PVGM_all_photos_details'. Esto hace posible que atacantes autenticados, con acceso de nivel de colaborador y superior, inyecten un objeto PHP. No hay ninguna cadena POP conocida presente en el software vulnerable. Si hay una cadena POP presente a trav\u00e9s de un complemento o tema adicional instalado en el sistema de destino, podr\u00eda permitir al atacante eliminar archivos arbitrarios, recuperar datos confidenciales o ejecutar c\u00f3digo." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-57xx/CVE-2024-5768.json b/CVE-2024/CVE-2024-57xx/CVE-2024-5768.json index 1c984e7e427..9f7a7569185 100644 --- a/CVE-2024/CVE-2024-57xx/CVE-2024-5768.json +++ b/CVE-2024/CVE-2024-57xx/CVE-2024-5768.json @@ -2,12 +2,16 @@ "id": "CVE-2024-5768", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-19T04:15:14.160", - "lastModified": "2024-06-19T04:15:14.160", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The MIMO Woocommerce Order Tracking plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'mimo_update_provider' function in all versions up to, and including, 1.0.2. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update shipping provider information, including adding stored cross-site scripting." + }, + { + "lang": "es", + "value": "El complemento MIMO Woocommerce Order Tracking para WordPress es vulnerable a modificaciones no autorizadas de datos debido a una falta de verificaci\u00f3n de capacidad en la funci\u00f3n 'mimo_update_provider' en todas las versiones hasta la 1.0.2 incluida. Esto hace posible que los atacantes autenticados, con acceso a nivel de suscriptor y superior, actualicen la informaci\u00f3n del proveedor de env\u00edo, incluida la adici\u00f3n de cross-site scripting almacenado." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-58xx/CVE-2024-5843.json b/CVE-2024/CVE-2024-58xx/CVE-2024-5843.json index 4354dc3f163..136effe042c 100644 --- a/CVE-2024/CVE-2024-58xx/CVE-2024-5843.json +++ b/CVE-2024/CVE-2024-58xx/CVE-2024-5843.json @@ -2,8 +2,8 @@ "id": "CVE-2024-5843", "sourceIdentifier": "chrome-cve-admin@google.com", "published": "2024-06-11T21:15:55.150", - "lastModified": "2024-06-14T06:15:17.170", - "vulnStatus": "Undergoing Analysis", + "lastModified": "2024-06-20T13:22:50.317", + "vulnStatus": "Analyzed", "descriptions": [ { "lang": "en", @@ -14,23 +14,108 @@ "value": "La implementaci\u00f3n inadecuada en Descargas en Google Chrome anterior a 126.0.6478.54 permiti\u00f3 a un atacante remoto ofuscar la interfaz de usuario de seguridad mediante un archivo malicioso. (Severidad de seguridad de Chromium: media)" } ], - "metrics": {}, + "metrics": { + "cvssMetricV31": [ + { + "source": "nvd@nist.gov", + "type": "Primary", + "cvssData": { + "version": "3.1", + "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N", + "attackVector": "NETWORK", + "attackComplexity": "LOW", + "privilegesRequired": "NONE", + "userInteraction": "REQUIRED", + "scope": "UNCHANGED", + "confidentialityImpact": "NONE", + "integrityImpact": "HIGH", + "availabilityImpact": "NONE", + "baseScore": 6.5, + "baseSeverity": "MEDIUM" + }, + "exploitabilityScore": 2.8, + "impactScore": 3.6 + } + ] + }, + "weaknesses": [ + { + "source": "nvd@nist.gov", + "type": "Primary", + "description": [ + { + "lang": "en", + "value": "NVD-CWE-noinfo" + } + ] + } + ], + "configurations": [ + { + "nodes": [ + { + "operator": "OR", + "negate": false, + "cpeMatch": [ + { + "vulnerable": true, + "criteria": "cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*", + "versionEndExcluding": "126.0.6478.54", + "matchCriteriaId": "28906E8E-9158-4473-8807-188F6DF15D13" + } + ] + } + ] + }, + { + "nodes": [ + { + "operator": "OR", + "negate": false, + "cpeMatch": [ + { + "vulnerable": true, + "criteria": "cpe:2.3:o:fedoraproject:fedora:39:*:*:*:*:*:*:*", + "matchCriteriaId": "B8EDB836-4E6A-4B71-B9B2-AA3E03E0F646" + }, + { + "vulnerable": true, + "criteria": "cpe:2.3:o:fedoraproject:fedora:40:*:*:*:*:*:*:*", + "matchCriteriaId": "CA277A6C-83EC-4536-9125-97B84C4FAF59" + } + ] + } + ] + } + ], "references": [ { "url": "https://chromereleases.googleblog.com/2024/06/stable-channel-update-for-desktop.html", - "source": "chrome-cve-admin@google.com" + "source": "chrome-cve-admin@google.com", + "tags": [ + "Third Party Advisory" + ] }, { "url": "https://issues.chromium.org/issues/333940412", - "source": "chrome-cve-admin@google.com" + "source": "chrome-cve-admin@google.com", + "tags": [ + "Permissions Required" + ] }, { "url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/7VXA32LXMNK3DSK3JBRLTBPFUH7LTODU/", - "source": "chrome-cve-admin@google.com" + "source": "chrome-cve-admin@google.com", + "tags": [ + "Third Party Advisory" + ] }, { "url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MPU7AB53QQVNTBPGRMJRY5SXJNYWW3FX/", - "source": "chrome-cve-admin@google.com" + "source": "chrome-cve-admin@google.com", + "tags": [ + "Third Party Advisory" + ] } ] } \ No newline at end of file diff --git a/CVE-2024/CVE-2024-58xx/CVE-2024-5844.json b/CVE-2024/CVE-2024-58xx/CVE-2024-5844.json index 92c3ca38370..77ca2b12a28 100644 --- a/CVE-2024/CVE-2024-58xx/CVE-2024-5844.json +++ b/CVE-2024/CVE-2024-58xx/CVE-2024-5844.json @@ -2,8 +2,8 @@ "id": "CVE-2024-5844", "sourceIdentifier": "chrome-cve-admin@google.com", "published": "2024-06-11T21:15:55.227", - "lastModified": "2024-06-14T06:15:17.517", - "vulnStatus": "Undergoing Analysis", + "lastModified": "2024-06-20T13:23:18.707", + "vulnStatus": "Analyzed", "descriptions": [ { "lang": "en", @@ -14,23 +14,108 @@ "value": "El desbordamiento del b\u00fafer de mont\u00f3n en Tab Strip en Google Chrome anterior a 126.0.6478.54 permit\u00eda a un atacante remoto realizar una lectura de memoria fuera de los l\u00edmites a trav\u00e9s de una p\u00e1gina HTML manipulada. (Severidad de seguridad de Chromium: media)" } ], - "metrics": {}, + "metrics": { + "cvssMetricV31": [ + { + "source": "nvd@nist.gov", + "type": "Primary", + "cvssData": { + "version": "3.1", + "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", + "attackVector": "NETWORK", + "attackComplexity": "LOW", + "privilegesRequired": "NONE", + "userInteraction": "REQUIRED", + "scope": "UNCHANGED", + "confidentialityImpact": "HIGH", + "integrityImpact": "HIGH", + "availabilityImpact": "HIGH", + "baseScore": 8.8, + "baseSeverity": "HIGH" + }, + "exploitabilityScore": 2.8, + "impactScore": 5.9 + } + ] + }, + "weaknesses": [ + { + "source": "nvd@nist.gov", + "type": "Primary", + "description": [ + { + "lang": "en", + "value": "CWE-787" + } + ] + } + ], + "configurations": [ + { + "nodes": [ + { + "operator": "OR", + "negate": false, + "cpeMatch": [ + { + "vulnerable": true, + "criteria": "cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*", + "versionEndExcluding": "126.0.6478.54", + "matchCriteriaId": "28906E8E-9158-4473-8807-188F6DF15D13" + } + ] + } + ] + }, + { + "nodes": [ + { + "operator": "OR", + "negate": false, + "cpeMatch": [ + { + "vulnerable": true, + "criteria": "cpe:2.3:o:fedoraproject:fedora:39:*:*:*:*:*:*:*", + "matchCriteriaId": "B8EDB836-4E6A-4B71-B9B2-AA3E03E0F646" + }, + { + "vulnerable": true, + "criteria": "cpe:2.3:o:fedoraproject:fedora:40:*:*:*:*:*:*:*", + "matchCriteriaId": "CA277A6C-83EC-4536-9125-97B84C4FAF59" + } + ] + } + ] + } + ], "references": [ { "url": "https://chromereleases.googleblog.com/2024/06/stable-channel-update-for-desktop.html", - "source": "chrome-cve-admin@google.com" + "source": "chrome-cve-admin@google.com", + "tags": [ + "Third Party Advisory" + ] }, { "url": "https://issues.chromium.org/issues/331960660", - "source": "chrome-cve-admin@google.com" + "source": "chrome-cve-admin@google.com", + "tags": [ + "Permissions Required" + ] }, { "url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/7VXA32LXMNK3DSK3JBRLTBPFUH7LTODU/", - "source": "chrome-cve-admin@google.com" + "source": "chrome-cve-admin@google.com", + "tags": [ + "Third Party Advisory" + ] }, { "url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MPU7AB53QQVNTBPGRMJRY5SXJNYWW3FX/", - "source": "chrome-cve-admin@google.com" + "source": "chrome-cve-admin@google.com", + "tags": [ + "Third Party Advisory" + ] } ] } \ No newline at end of file diff --git a/CVE-2024/CVE-2024-58xx/CVE-2024-5845.json b/CVE-2024/CVE-2024-58xx/CVE-2024-5845.json index 5b30f15f1a8..96f1c5a2a87 100644 --- a/CVE-2024/CVE-2024-58xx/CVE-2024-5845.json +++ b/CVE-2024/CVE-2024-58xx/CVE-2024-5845.json @@ -2,8 +2,8 @@ "id": "CVE-2024-5845", "sourceIdentifier": "chrome-cve-admin@google.com", "published": "2024-06-11T21:15:55.317", - "lastModified": "2024-06-14T06:15:17.790", - "vulnStatus": "Undergoing Analysis", + "lastModified": "2024-06-20T13:24:38.797", + "vulnStatus": "Analyzed", "descriptions": [ { "lang": "en", @@ -14,23 +14,108 @@ "value": "Use after free en Audio en Google Chrome anterior a 126.0.6478.54 permit\u00eda a un atacante remoto explotar potencialmente la corrupci\u00f3n del mont\u00f3n a trav\u00e9s de un archivo PDF manipulado. (Severidad de seguridad de Chromium: media)" } ], - "metrics": {}, + "metrics": { + "cvssMetricV31": [ + { + "source": "nvd@nist.gov", + "type": "Primary", + "cvssData": { + "version": "3.1", + "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", + "attackVector": "NETWORK", + "attackComplexity": "LOW", + "privilegesRequired": "NONE", + "userInteraction": "REQUIRED", + "scope": "UNCHANGED", + "confidentialityImpact": "HIGH", + "integrityImpact": "HIGH", + "availabilityImpact": "HIGH", + "baseScore": 8.8, + "baseSeverity": "HIGH" + }, + "exploitabilityScore": 2.8, + "impactScore": 5.9 + } + ] + }, + "weaknesses": [ + { + "source": "nvd@nist.gov", + "type": "Primary", + "description": [ + { + "lang": "en", + "value": "CWE-416" + } + ] + } + ], + "configurations": [ + { + "nodes": [ + { + "operator": "OR", + "negate": false, + "cpeMatch": [ + { + "vulnerable": true, + "criteria": "cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*", + "versionEndExcluding": "126.0.6478.54", + "matchCriteriaId": "28906E8E-9158-4473-8807-188F6DF15D13" + } + ] + } + ] + }, + { + "nodes": [ + { + "operator": "OR", + "negate": false, + "cpeMatch": [ + { + "vulnerable": true, + "criteria": "cpe:2.3:o:fedoraproject:fedora:39:*:*:*:*:*:*:*", + "matchCriteriaId": "B8EDB836-4E6A-4B71-B9B2-AA3E03E0F646" + }, + { + "vulnerable": true, + "criteria": "cpe:2.3:o:fedoraproject:fedora:40:*:*:*:*:*:*:*", + "matchCriteriaId": "CA277A6C-83EC-4536-9125-97B84C4FAF59" + } + ] + } + ] + } + ], "references": [ { "url": "https://chromereleases.googleblog.com/2024/06/stable-channel-update-for-desktop.html", - "source": "chrome-cve-admin@google.com" + "source": "chrome-cve-admin@google.com", + "tags": [ + "Third Party Advisory" + ] }, { "url": "https://issues.chromium.org/issues/340178596", - "source": "chrome-cve-admin@google.com" + "source": "chrome-cve-admin@google.com", + "tags": [ + "Permissions Required" + ] }, { "url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/7VXA32LXMNK3DSK3JBRLTBPFUH7LTODU/", - "source": "chrome-cve-admin@google.com" + "source": "chrome-cve-admin@google.com", + "tags": [ + "Third Party Advisory" + ] }, { "url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MPU7AB53QQVNTBPGRMJRY5SXJNYWW3FX/", - "source": "chrome-cve-admin@google.com" + "source": "chrome-cve-admin@google.com", + "tags": [ + "Third Party Advisory" + ] } ] } \ No newline at end of file diff --git a/CVE-2024/CVE-2024-58xx/CVE-2024-5846.json b/CVE-2024/CVE-2024-58xx/CVE-2024-5846.json index 44d6735bd9d..d10db69cf55 100644 --- a/CVE-2024/CVE-2024-58xx/CVE-2024-5846.json +++ b/CVE-2024/CVE-2024-58xx/CVE-2024-5846.json @@ -2,8 +2,8 @@ "id": "CVE-2024-5846", "sourceIdentifier": "chrome-cve-admin@google.com", "published": "2024-06-11T21:15:55.397", - "lastModified": "2024-06-14T06:15:18.070", - "vulnStatus": "Undergoing Analysis", + "lastModified": "2024-06-20T13:05:14.410", + "vulnStatus": "Analyzed", "descriptions": [ { "lang": "en", @@ -14,23 +14,108 @@ "value": "Use after free en PDFium en Google Chrome anterior a 126.0.6478.54 permit\u00eda a un atacante remoto explotar potencialmente la corrupci\u00f3n del mont\u00f3n a trav\u00e9s de un archivo PDF manipulado. (Severidad de seguridad de Chromium: media)" } ], - "metrics": {}, + "metrics": { + "cvssMetricV31": [ + { + "source": "nvd@nist.gov", + "type": "Primary", + "cvssData": { + "version": "3.1", + "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", + "attackVector": "NETWORK", + "attackComplexity": "LOW", + "privilegesRequired": "NONE", + "userInteraction": "REQUIRED", + "scope": "UNCHANGED", + "confidentialityImpact": "HIGH", + "integrityImpact": "HIGH", + "availabilityImpact": "HIGH", + "baseScore": 8.8, + "baseSeverity": "HIGH" + }, + "exploitabilityScore": 2.8, + "impactScore": 5.9 + } + ] + }, + "weaknesses": [ + { + "source": "nvd@nist.gov", + "type": "Primary", + "description": [ + { + "lang": "en", + "value": "CWE-416" + } + ] + } + ], + "configurations": [ + { + "nodes": [ + { + "operator": "OR", + "negate": false, + "cpeMatch": [ + { + "vulnerable": true, + "criteria": "cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*", + "versionEndExcluding": "126.0.6478.54", + "matchCriteriaId": "28906E8E-9158-4473-8807-188F6DF15D13" + } + ] + } + ] + }, + { + "nodes": [ + { + "operator": "OR", + "negate": false, + "cpeMatch": [ + { + "vulnerable": true, + "criteria": "cpe:2.3:o:fedoraproject:fedora:39:*:*:*:*:*:*:*", + "matchCriteriaId": "B8EDB836-4E6A-4B71-B9B2-AA3E03E0F646" + }, + { + "vulnerable": true, + "criteria": "cpe:2.3:o:fedoraproject:fedora:40:*:*:*:*:*:*:*", + "matchCriteriaId": "CA277A6C-83EC-4536-9125-97B84C4FAF59" + } + ] + } + ] + } + ], "references": [ { "url": "https://chromereleases.googleblog.com/2024/06/stable-channel-update-for-desktop.html", - "source": "chrome-cve-admin@google.com" + "source": "chrome-cve-admin@google.com", + "tags": [ + "Third Party Advisory" + ] }, { "url": "https://issues.chromium.org/issues/341095523", - "source": "chrome-cve-admin@google.com" + "source": "chrome-cve-admin@google.com", + "tags": [ + "Permissions Required" + ] }, { "url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/7VXA32LXMNK3DSK3JBRLTBPFUH7LTODU/", - "source": "chrome-cve-admin@google.com" + "source": "chrome-cve-admin@google.com", + "tags": [ + "Third Party Advisory" + ] }, { "url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MPU7AB53QQVNTBPGRMJRY5SXJNYWW3FX/", - "source": "chrome-cve-admin@google.com" + "source": "chrome-cve-admin@google.com", + "tags": [ + "Third Party Advisory" + ] } ] } \ No newline at end of file diff --git a/CVE-2024/CVE-2024-58xx/CVE-2024-5847.json b/CVE-2024/CVE-2024-58xx/CVE-2024-5847.json index a73318d2c00..7d274f94d23 100644 --- a/CVE-2024/CVE-2024-58xx/CVE-2024-5847.json +++ b/CVE-2024/CVE-2024-58xx/CVE-2024-5847.json @@ -2,8 +2,8 @@ "id": "CVE-2024-5847", "sourceIdentifier": "chrome-cve-admin@google.com", "published": "2024-06-11T21:15:55.500", - "lastModified": "2024-06-14T06:15:18.340", - "vulnStatus": "Undergoing Analysis", + "lastModified": "2024-06-20T13:05:43.187", + "vulnStatus": "Analyzed", "descriptions": [ { "lang": "en", @@ -14,23 +14,108 @@ "value": "Use after free en PDFium en Google Chrome anterior a 126.0.6478.54 permit\u00eda a un atacante remoto explotar potencialmente la corrupci\u00f3n del mont\u00f3n a trav\u00e9s de un archivo PDF manipulado. (Severidad de seguridad de Chromium: media)" } ], - "metrics": {}, + "metrics": { + "cvssMetricV31": [ + { + "source": "nvd@nist.gov", + "type": "Primary", + "cvssData": { + "version": "3.1", + "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", + "attackVector": "NETWORK", + "attackComplexity": "LOW", + "privilegesRequired": "NONE", + "userInteraction": "REQUIRED", + "scope": "UNCHANGED", + "confidentialityImpact": "HIGH", + "integrityImpact": "HIGH", + "availabilityImpact": "HIGH", + "baseScore": 8.8, + "baseSeverity": "HIGH" + }, + "exploitabilityScore": 2.8, + "impactScore": 5.9 + } + ] + }, + "weaknesses": [ + { + "source": "nvd@nist.gov", + "type": "Primary", + "description": [ + { + "lang": "en", + "value": "CWE-416" + } + ] + } + ], + "configurations": [ + { + "nodes": [ + { + "operator": "OR", + "negate": false, + "cpeMatch": [ + { + "vulnerable": true, + "criteria": "cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*", + "versionEndExcluding": "126.0.6478.54", + "matchCriteriaId": "28906E8E-9158-4473-8807-188F6DF15D13" + } + ] + } + ] + }, + { + "nodes": [ + { + "operator": "OR", + "negate": false, + "cpeMatch": [ + { + "vulnerable": true, + "criteria": "cpe:2.3:o:fedoraproject:fedora:39:*:*:*:*:*:*:*", + "matchCriteriaId": "B8EDB836-4E6A-4B71-B9B2-AA3E03E0F646" + }, + { + "vulnerable": true, + "criteria": "cpe:2.3:o:fedoraproject:fedora:40:*:*:*:*:*:*:*", + "matchCriteriaId": "CA277A6C-83EC-4536-9125-97B84C4FAF59" + } + ] + } + ] + } + ], "references": [ { "url": "https://chromereleases.googleblog.com/2024/06/stable-channel-update-for-desktop.html", - "source": "chrome-cve-admin@google.com" + "source": "chrome-cve-admin@google.com", + "tags": [ + "Third Party Advisory" + ] }, { "url": "https://issues.chromium.org/issues/341313077", - "source": "chrome-cve-admin@google.com" + "source": "chrome-cve-admin@google.com", + "tags": [ + "Permissions Required" + ] }, { "url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/7VXA32LXMNK3DSK3JBRLTBPFUH7LTODU/", - "source": "chrome-cve-admin@google.com" + "source": "chrome-cve-admin@google.com", + "tags": [ + "Third Party Advisory" + ] }, { "url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MPU7AB53QQVNTBPGRMJRY5SXJNYWW3FX/", - "source": "chrome-cve-admin@google.com" + "source": "chrome-cve-admin@google.com", + "tags": [ + "Third Party Advisory" + ] } ] } \ No newline at end of file diff --git a/CVE-2024/CVE-2024-58xx/CVE-2024-5853.json b/CVE-2024/CVE-2024-58xx/CVE-2024-5853.json index 091eec76955..8c68d248653 100644 --- a/CVE-2024/CVE-2024-58xx/CVE-2024-5853.json +++ b/CVE-2024/CVE-2024-58xx/CVE-2024-5853.json @@ -2,12 +2,16 @@ "id": "CVE-2024-5853", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-19T06:15:12.287", - "lastModified": "2024-06-19T06:15:12.287", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The Image Optimizer, Resizer and CDN \u2013 Sirv plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the sirv_upload_file_by_chanks AJAX action in all versions up to, and including, 7.2.6. This makes it possible for authenticated attackers, with Contributor-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible." + }, + { + "lang": "es", + "value": "El complemento Image Optimizer, Resizer y CDN \u2013 Sirv para WordPress es vulnerable a cargas de archivos arbitrarias debido a la falta de validaci\u00f3n del tipo de archivo en la acci\u00f3n AJAX sirv_upload_file_by_chanks en todas las versiones hasta la 7.2.6 incluida. Esto hace posible que atacantes autenticados, con acceso de nivel de colaborador y superior, carguen archivos arbitrarios en el servidor del sitio afectado, lo que puede hacer posible la ejecuci\u00f3n remota de c\u00f3digo." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-58xx/CVE-2024-5860.json b/CVE-2024/CVE-2024-58xx/CVE-2024-5860.json index 7f6656ecda6..cdb05bb9cc0 100644 --- a/CVE-2024/CVE-2024-58xx/CVE-2024-5860.json +++ b/CVE-2024/CVE-2024-58xx/CVE-2024-5860.json @@ -2,12 +2,16 @@ "id": "CVE-2024-5860", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-18T04:15:11.607", - "lastModified": "2024-06-18T04:15:11.607", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "The Tickera \u2013 WordPress Event Ticketing plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the tc_dl_delete_tickets AJAX action in all versions up to, and including, 3.5.2.8. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete all tickets associated with events." + }, + { + "lang": "es", + "value": "El complemento Tickera \u2013 WordPress Event Ticketing para WordPress es vulnerable a la p\u00e9rdida no autorizada de datos debido a una falta de verificaci\u00f3n de capacidad en la acci\u00f3n tc_dl_delete_tickets AJAX en todas las versiones hasta la 3.5.2.8 incluida. Esto hace posible que los atacantes autenticados, con acceso de nivel de suscriptor y superior, eliminen todos los tickets asociados con los eventos." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-58xx/CVE-2024-5899.json b/CVE-2024/CVE-2024-58xx/CVE-2024-5899.json index 1f6a81fb8ce..3bcfdc41e23 100644 --- a/CVE-2024/CVE-2024-58xx/CVE-2024-5899.json +++ b/CVE-2024/CVE-2024-58xx/CVE-2024-5899.json @@ -2,12 +2,16 @@ "id": "CVE-2024-5899", "sourceIdentifier": "cve-coordination@google.com", "published": "2024-06-18T09:15:09.767", - "lastModified": "2024-06-18T09:15:09.767", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "When Bazel Plugin in intellij imports a project (either using \"import project\" or \"Auto import\") the dialog for trusting the project is not displayed.\u00a0This comes from the fact that both call the method ProjectBuilder.createProject\u00a0which then calls ProjectManager.getInstance().createProject. This method, as its name suggests is intended to create a new project, not to import an existing one.\u00a0\nWe recommend upgrading to version 2024.06.04.0.2 or beyond for the IntelliJ, CLion and Android Studio Bazel plugins." + }, + { + "lang": "es", + "value": "Cuando Bazel Plugin en intellij importa un proyecto (ya sea usando \"importar proyecto\" o \"Importar autom\u00e1ticamente\"), no se muestra el cuadro de di\u00e1logo para confiar en el proyecto. Esto se debe al hecho de que ambos llaman al m\u00e9todo ProjectBuilder.createProject, que luego llama a ProjectManager.getInstance().createProject. Este m\u00e9todo, como su nombre indica, est\u00e1 destinado a crear un nuevo proyecto, no a importar uno existente. Recomendamos actualizar a la versi\u00f3n 2024.06.04.0.2 o posterior para los complementos IntelliJ, CLion y Android Studio Bazel." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-59xx/CVE-2024-5953.json b/CVE-2024/CVE-2024-59xx/CVE-2024-5953.json index ba40db88820..ec8a73901ad 100644 --- a/CVE-2024/CVE-2024-59xx/CVE-2024-5953.json +++ b/CVE-2024/CVE-2024-59xx/CVE-2024-5953.json @@ -2,8 +2,8 @@ "id": "CVE-2024-5953", "sourceIdentifier": "secalert@redhat.com", "published": "2024-06-18T10:15:11.170", - "lastModified": "2024-06-18T10:15:11.170", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", diff --git a/CVE-2024/CVE-2024-59xx/CVE-2024-5967.json b/CVE-2024/CVE-2024-59xx/CVE-2024-5967.json index 9ab66a6b4db..de170503e90 100644 --- a/CVE-2024/CVE-2024-59xx/CVE-2024-5967.json +++ b/CVE-2024/CVE-2024-59xx/CVE-2024-5967.json @@ -2,12 +2,16 @@ "id": "CVE-2024-5967", "sourceIdentifier": "secalert@redhat.com", "published": "2024-06-18T12:15:12.707", - "lastModified": "2024-06-18T12:15:12.707", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A vulnerability was found in Keycloak. The LDAP testing endpoint allows changing the Connection URL\u00a0 independently without re-entering the currently configured LDAP bind credentials. This flaw allows an attacker with admin\u00a0access (permission manage-realm) to change the LDAP host URL (\"Connection URL\") to a machine they control. The Keycloak server will connect to the attacker's host and try to authenticate with the configured credentials, thus leaking them to the attacker. As a consequence, an attacker who has compromised the admin console or compromised a user with sufficient privileges can leak domain credentials and attack the domain." + }, + { + "lang": "es", + "value": "Se encontr\u00f3 una vulnerabilidad en Keycloak. El endpoint de prueba LDAP permite cambiar la URL de conexi\u00f3n de forma independiente sin volver a ingresar las credenciales de enlace LDAP configuradas actualmente. Esta falla permite que un atacante con acceso de administrador (permiso de administraci\u00f3n de dominio) cambie la URL del host LDAP (\"URL de conexi\u00f3n\") a una m\u00e1quina que controla. El servidor Keycloak se conectar\u00e1 al host del atacante e intentar\u00e1 autenticarse con las credenciales configuradas, filtr\u00e1ndoselas as\u00ed al atacante. Como consecuencia, un atacante que haya comprometido la consola de administraci\u00f3n o haya comprometido a un usuario con privilegios suficientes puede filtrar las credenciales del dominio y atacar el dominio." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-59xx/CVE-2024-5970.json b/CVE-2024/CVE-2024-59xx/CVE-2024-5970.json index 2ad552b267c..164c2e0104f 100644 --- a/CVE-2024/CVE-2024-59xx/CVE-2024-5970.json +++ b/CVE-2024/CVE-2024-59xx/CVE-2024-5970.json @@ -2,12 +2,16 @@ "id": "CVE-2024-5970", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-18T22:15:09.487", - "lastModified": "2024-06-18T22:15:09.487", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The MaxGalleria plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's maxgallery_thumb shortcode in all versions up to, and including, 6.4.4 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." + }, + { + "lang": "es", + "value": "El complemento MaxGalleria para WordPress es vulnerable a cross-site scripting almacenado a trav\u00e9s del c\u00f3digo corto maxgallery_thumb del complemento en todas las versiones hasta la 6.4.4 incluida debido a una sanitizaci\u00f3n de entrada insuficiente y a un escape de salida en los atributos proporcionados por el usuario. Esto hace posible que atacantes autenticados, con acceso de nivel de colaborador y superior, inyecten scripts web arbitrarios en p\u00e1ginas que se ejecutar\u00e1n cada vez que un usuario acceda a una p\u00e1gina inyectada." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-60xx/CVE-2024-6055.json b/CVE-2024/CVE-2024-60xx/CVE-2024-6055.json index 4241a9c67ca..d1ab227ab66 100644 --- a/CVE-2024/CVE-2024-60xx/CVE-2024-6055.json +++ b/CVE-2024/CVE-2024-60xx/CVE-2024-6055.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6055", "sourceIdentifier": "security@devolutions.net", "published": "2024-06-17T13:15:53.697", - "lastModified": "2024-06-17T13:15:53.697", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Improper removal of sensitive information in data source export feature in Devolutions Remote Desktop Manager 2024.1.32.0 and earlier on Windows allows an attacker that obtains the exported settings to recover powershell credentials configured on the data source via stealing the configuration file." + }, + { + "lang": "es", + "value": "La eliminaci\u00f3n incorrecta de informaci\u00f3n confidencial en la funci\u00f3n de exportaci\u00f3n de fuentes de datos en Devolutions Remote Desktop Manager 2024.1.32.0 y versiones anteriores en Windows permite que un atacante que obtenga la configuraci\u00f3n exportada recupere las credenciales de PowerShell configuradas en la fuente de datos robando el archivo de configuraci\u00f3n." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-60xx/CVE-2024-6056.json b/CVE-2024/CVE-2024-60xx/CVE-2024-6056.json index 79c6855453e..99b69bcab73 100644 --- a/CVE-2024/CVE-2024-60xx/CVE-2024-6056.json +++ b/CVE-2024/CVE-2024-60xx/CVE-2024-6056.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6056", "sourceIdentifier": "cna@vuldb.com", "published": "2024-06-17T18:15:18.143", - "lastModified": "2024-06-17T18:15:18.143", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A vulnerability was found in nasirkhan Laravel Starter up to 11.8.0. It has been rated as problematic. Affected by this issue is some unknown functionality of the file /forgot-password of the component Password Reset Handler. The manipulation of the argument Email leads to observable response discrepancy. The attack may be launched remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-268784. NOTE: The vendor was contacted early about this disclosure but did not respond in any way." + }, + { + "lang": "es", + "value": "Se encontr\u00f3 una vulnerabilidad en nasirkhan Laravel Starter hasta 11.8.0. Ha sido calificada como problem\u00e1tica. Una funci\u00f3n desconocida del archivo /forgot-password del componente Password Reset Handler es afectada por esta vulnerabilidad. La manipulaci\u00f3n del argumento Correo electr\u00f3nico conduce a una discrepancia de respuesta observable. El ataque puede lanzarse de forma remota. La complejidad de un ataque es bastante alta. Se sabe que la explotaci\u00f3n es dif\u00edcil. El exploit ha sido divulgado al p\u00fablico y puede utilizarse. El identificador de esta vulnerabilidad es VDB-268784. NOTA: Se contact\u00f3 primeramente con el proveedor sobre esta divulgaci\u00f3n, pero no respondi\u00f3 de ninguna manera." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-60xx/CVE-2024-6057.json b/CVE-2024/CVE-2024-60xx/CVE-2024-6057.json index 07cd241f8cb..c6d8ee8d886 100644 --- a/CVE-2024/CVE-2024-60xx/CVE-2024-6057.json +++ b/CVE-2024/CVE-2024-60xx/CVE-2024-6057.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6057", "sourceIdentifier": "security@devolutions.net", "published": "2024-06-17T13:15:53.800", - "lastModified": "2024-06-17T13:15:53.800", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Improper authentication in the vault password feature in Devolutions Remote Desktop Manager 2024.1.31.0 and earlier allows an attacker that has compromised an access to an RDM instance to bypass the vault master password via the offline mode feature." + }, + { + "lang": "es", + "value": "La autenticaci\u00f3n incorrecta en la funci\u00f3n de contrase\u00f1a de la b\u00f3veda en Devolutions Remote Desktop Manager 2024.1.31.0 y versiones anteriores permite que un atacante que haya comprometido el acceso a una instancia de RDM omita la contrase\u00f1a maestra de la b\u00f3veda a trav\u00e9s de la funci\u00f3n del modo fuera de l\u00ednea." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-60xx/CVE-2024-6058.json b/CVE-2024/CVE-2024-60xx/CVE-2024-6058.json index 5c14ef27da4..09e630d2399 100644 --- a/CVE-2024/CVE-2024-60xx/CVE-2024-6058.json +++ b/CVE-2024/CVE-2024-60xx/CVE-2024-6058.json @@ -2,8 +2,8 @@ "id": "CVE-2024-6058", "sourceIdentifier": "cna@vuldb.com", "published": "2024-06-17T18:15:18.520", - "lastModified": "2024-06-18T16:15:10.860", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", diff --git a/CVE-2024/CVE-2024-60xx/CVE-2024-6059.json b/CVE-2024/CVE-2024-60xx/CVE-2024-6059.json index 47cb6bbdbd0..48cccb18beb 100644 --- a/CVE-2024/CVE-2024-60xx/CVE-2024-6059.json +++ b/CVE-2024/CVE-2024-60xx/CVE-2024-6059.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6059", "sourceIdentifier": "cna@vuldb.com", "published": "2024-06-17T19:15:59.467", - "lastModified": "2024-06-17T19:15:59.467", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A vulnerability, which was classified as problematic, has been found in Ingenico Estate Manager 2023. This issue affects some unknown processing of the file /emgui/rest/ums/messages of the component News Feed. The manipulation of the argument message leads to cross site scripting. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-268787. NOTE: The vendor was contacted early about this disclosure but did not respond in any way." + }, + { + "lang": "es", + "value": "Una vulnerabilidad clasificada como problem\u00e1tica fue encontrada en Ingenico Estate Manager 2023. Un procesamiento desconocido del archivo /emgui/rest/ums/messages del componente News Feed afecta a este problema. La manipulaci\u00f3n del mensaje de argumento conduce a cross site scripting. El ataque puede iniciarse de forma remota. El exploit ha sido divulgado al p\u00fablico y puede utilizarse. El identificador asociado de esta vulnerabilidad es VDB-268787. NOTA: Se contact\u00f3 primeramente con el proveedor sobre esta divulgaci\u00f3n, pero no respondi\u00f3 de ninguna manera." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-60xx/CVE-2024-6061.json b/CVE-2024/CVE-2024-60xx/CVE-2024-6061.json index 2f6e4506a81..6dc03e7e538 100644 --- a/CVE-2024/CVE-2024-60xx/CVE-2024-6061.json +++ b/CVE-2024/CVE-2024-60xx/CVE-2024-6061.json @@ -2,8 +2,8 @@ "id": "CVE-2024-6061", "sourceIdentifier": "cna@vuldb.com", "published": "2024-06-17T20:15:14.850", - "lastModified": "2024-06-18T14:15:11.533", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", diff --git a/CVE-2024/CVE-2024-60xx/CVE-2024-6062.json b/CVE-2024/CVE-2024-60xx/CVE-2024-6062.json index 16900528111..ddb779aa177 100644 --- a/CVE-2024/CVE-2024-60xx/CVE-2024-6062.json +++ b/CVE-2024/CVE-2024-60xx/CVE-2024-6062.json @@ -2,8 +2,8 @@ "id": "CVE-2024-6062", "sourceIdentifier": "cna@vuldb.com", "published": "2024-06-17T20:15:15.170", - "lastModified": "2024-06-18T14:15:11.670", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", diff --git a/CVE-2024/CVE-2024-60xx/CVE-2024-6063.json b/CVE-2024/CVE-2024-60xx/CVE-2024-6063.json index 4f892272809..f24113890bc 100644 --- a/CVE-2024/CVE-2024-60xx/CVE-2024-6063.json +++ b/CVE-2024/CVE-2024-60xx/CVE-2024-6063.json @@ -2,8 +2,8 @@ "id": "CVE-2024-6063", "sourceIdentifier": "cna@vuldb.com", "published": "2024-06-17T21:15:51.443", - "lastModified": "2024-06-18T14:15:11.787", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", diff --git a/CVE-2024/CVE-2024-60xx/CVE-2024-6064.json b/CVE-2024/CVE-2024-60xx/CVE-2024-6064.json index 303b52bad55..a86953717d9 100644 --- a/CVE-2024/CVE-2024-60xx/CVE-2024-6064.json +++ b/CVE-2024/CVE-2024-60xx/CVE-2024-6064.json @@ -2,8 +2,8 @@ "id": "CVE-2024-6064", "sourceIdentifier": "cna@vuldb.com", "published": "2024-06-17T21:15:51.727", - "lastModified": "2024-06-18T14:15:11.917", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:22.977", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", diff --git a/CVE-2024/CVE-2024-60xx/CVE-2024-6065.json b/CVE-2024/CVE-2024-60xx/CVE-2024-6065.json index df66faa6b55..b0c01c0889f 100644 --- a/CVE-2024/CVE-2024-60xx/CVE-2024-6065.json +++ b/CVE-2024/CVE-2024-60xx/CVE-2024-6065.json @@ -2,8 +2,8 @@ "id": "CVE-2024-6065", "sourceIdentifier": "cna@vuldb.com", "published": "2024-06-17T21:15:52.007", - "lastModified": "2024-06-18T14:15:12.040", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", diff --git a/CVE-2024/CVE-2024-60xx/CVE-2024-6066.json b/CVE-2024/CVE-2024-60xx/CVE-2024-6066.json index 1af3b3dc4c6..4a895925cc4 100644 --- a/CVE-2024/CVE-2024-60xx/CVE-2024-6066.json +++ b/CVE-2024/CVE-2024-60xx/CVE-2024-6066.json @@ -2,8 +2,8 @@ "id": "CVE-2024-6066", "sourceIdentifier": "cna@vuldb.com", "published": "2024-06-17T21:15:52.283", - "lastModified": "2024-06-18T14:15:12.183", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", diff --git a/CVE-2024/CVE-2024-60xx/CVE-2024-6067.json b/CVE-2024/CVE-2024-60xx/CVE-2024-6067.json index dff218480f3..e6e9d167106 100644 --- a/CVE-2024/CVE-2024-60xx/CVE-2024-6067.json +++ b/CVE-2024/CVE-2024-60xx/CVE-2024-6067.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6067", "sourceIdentifier": "cna@vuldb.com", "published": "2024-06-17T22:15:10.657", - "lastModified": "2024-06-17T22:15:10.657", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A vulnerability classified as critical was found in SourceCodester Music Class Enrollment System 1.0. Affected by this vulnerability is an unknown functionality of the file /mces/?p=class/view_class. The manipulation of the argument id leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-268795." + }, + { + "lang": "es", + "value": "Una vulnerabilidad fue encontrada en SourceCodester Music Class Enrollment System 1.0 y clasificada como cr\u00edtica. Una funcionalidad desconocida del archivo /mces/?p=class/view_class es afectada por esta vulnerabilidad. La manipulaci\u00f3n del argumento id conduce a la inyecci\u00f3n de SQL. El ataque se puede lanzar de forma remota. El exploit ha sido divulgado al p\u00fablico y puede utilizarse. El identificador asociado de esta vulnerabilidad es VDB-268795." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-60xx/CVE-2024-6080.json b/CVE-2024/CVE-2024-60xx/CVE-2024-6080.json index b7c37d180e3..8a16558eaac 100644 --- a/CVE-2024/CVE-2024-60xx/CVE-2024-6080.json +++ b/CVE-2024/CVE-2024-60xx/CVE-2024-6080.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6080", "sourceIdentifier": "cna@vuldb.com", "published": "2024-06-17T23:15:51.583", - "lastModified": "2024-06-17T23:15:51.583", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A vulnerability classified as critical was found in Intelbras InControl 2.21.56. This vulnerability affects unknown code. The manipulation leads to unquoted search path. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. VDB-268822 is the identifier assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way." + }, + { + "lang": "es", + "value": "Una vulnerabilidad fue encontrada en Intelbras InControl 2.21.56 y clasificada como cr\u00edtica. Esta vulnerabilidad afecta a c\u00f3digo desconocido. La manipulaci\u00f3n conduce a una ruta de b\u00fasqueda sin comillas. Se requiere acceso local para abordar este ataque. El exploit ha sido divulgado al p\u00fablico y puede utilizarse. VDB-268822 es el identificador asignado a esta vulnerabilidad. NOTA: Se contact\u00f3 primeramente con el proveedor sobre esta divulgaci\u00f3n, pero no respondi\u00f3 de ninguna manera." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-60xx/CVE-2024-6082.json b/CVE-2024/CVE-2024-60xx/CVE-2024-6082.json index b3a93d12cc4..3623aa17b40 100644 --- a/CVE-2024/CVE-2024-60xx/CVE-2024-6082.json +++ b/CVE-2024/CVE-2024-60xx/CVE-2024-6082.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6082", "sourceIdentifier": "cna@vuldb.com", "published": "2024-06-17T23:15:51.920", - "lastModified": "2024-06-17T23:15:51.920", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A vulnerability, which was classified as problematic, has been found in PHPVibe 11.0.46. This issue affects some unknown processing of the file functionalities.global.php of the component Global Options Page. The manipulation of the argument site-logo-text leads to cross site scripting. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-268823. NOTE: The vendor was contacted early about this disclosure but did not respond in any way." + }, + { + "lang": "es", + "value": "Una vulnerabilidad fue encontrada en PHPVibe 11.0.46 y clasificada como problem\u00e1tica. Este problema afecta un procesamiento desconocido del archivo functionalities.global.php del componente P\u00e1gina de opciones globales. La manipulaci\u00f3n del argumento sitio-logotipo-texto conduce a cross site scripting. El ataque puede iniciarse de forma remota. El exploit ha sido divulgado al p\u00fablico y puede utilizarse. El identificador asociado de esta vulnerabilidad es VDB-268823. NOTA: Se contact\u00f3 primeramente con el proveedor sobre esta divulgaci\u00f3n, pero no respondi\u00f3 de ninguna manera." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-60xx/CVE-2024-6083.json b/CVE-2024/CVE-2024-60xx/CVE-2024-6083.json index 33559329567..45c854f49ef 100644 --- a/CVE-2024/CVE-2024-60xx/CVE-2024-6083.json +++ b/CVE-2024/CVE-2024-60xx/CVE-2024-6083.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6083", "sourceIdentifier": "cna@vuldb.com", "published": "2024-06-18T00:15:09.853", - "lastModified": "2024-06-18T00:15:09.853", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A vulnerability, which was classified as critical, was found in PHPVibe 11.0.46. Affected is an unknown function of the file /app/uploading/upload-mp3.php of the component Media Upload Page. The manipulation of the argument file leads to unrestricted upload. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-268824. NOTE: The vendor was contacted early about this disclosure but did not respond in any way." + }, + { + "lang": "es", + "value": "Una vulnerabilidad fue encontrada en PHPVibe 11.0.46 y clasificada como cr\u00edtica. Una funci\u00f3n desconocida del archivo /app/uploading/upload-mp3.php del componente Media Upload Page es afectada por esta vulnerabilidad. La manipulaci\u00f3n del archivo de argumentos conduce a una carga sin restricciones. Es posible lanzar el ataque de forma remota. El exploit ha sido divulgado al p\u00fablico y puede utilizarse. El identificador de esta vulnerabilidad es VDB-268824. NOTA: Se contact\u00f3 primeramente con el proveedor sobre esta divulgaci\u00f3n, pero no respondi\u00f3 de ninguna manera." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-60xx/CVE-2024-6084.json b/CVE-2024/CVE-2024-60xx/CVE-2024-6084.json index 85660ca8865..d7f5b82a09e 100644 --- a/CVE-2024/CVE-2024-60xx/CVE-2024-6084.json +++ b/CVE-2024/CVE-2024-60xx/CVE-2024-6084.json @@ -2,8 +2,8 @@ "id": "CVE-2024-6084", "sourceIdentifier": "cna@vuldb.com", "published": "2024-06-18T01:15:20.333", - "lastModified": "2024-06-18T14:15:12.317", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6100.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6100.json index 248e58a9734..27128b3bc81 100644 --- a/CVE-2024/CVE-2024-61xx/CVE-2024-6100.json +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6100.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6100", "sourceIdentifier": "chrome-cve-admin@google.com", "published": "2024-06-20T00:15:09.810", - "lastModified": "2024-06-20T00:15:09.810", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "Type Confusion in V8 in Google Chrome prior to 126.0.6478.114 allowed a remote attacker to execute arbitrary code via a crafted HTML page. (Chromium security severity: High)" + }, + { + "lang": "es", + "value": "Type Confusion en V8 en Google Chrome anterior a 126.0.6478.114 permit\u00eda a un atacante remoto ejecutar c\u00f3digo arbitrario a trav\u00e9s de una p\u00e1gina HTML manipulada. (Severidad de seguridad de Chrome: alta)" } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6101.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6101.json index 05f15cee00f..7f7db8eb8b4 100644 --- a/CVE-2024/CVE-2024-61xx/CVE-2024-6101.json +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6101.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6101", "sourceIdentifier": "chrome-cve-admin@google.com", "published": "2024-06-20T00:15:09.967", - "lastModified": "2024-06-20T00:15:09.967", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "Inappropriate implementation in V8 in Google Chrome prior to 126.0.6478.114 allowed a remote attacker to perform out of bounds memory access via a crafted HTML page. (Chromium security severity: High)" + }, + { + "lang": "es", + "value": "La implementaci\u00f3n inapropiada en V8 en Google Chrome anterior a 126.0.6478.114 permiti\u00f3 a un atacante remoto realizar acceso a la memoria fuera de los l\u00edmites a trav\u00e9s de una p\u00e1gina HTML manipulada. (Severidad de seguridad de Chrome: alta)" } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6102.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6102.json index a6c8c890171..d4179541081 100644 --- a/CVE-2024/CVE-2024-61xx/CVE-2024-6102.json +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6102.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6102", "sourceIdentifier": "chrome-cve-admin@google.com", "published": "2024-06-20T00:15:10.053", - "lastModified": "2024-06-20T00:15:10.053", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "Out of bounds memory access in Dawn in Google Chrome prior to 126.0.6478.114 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)" + }, + { + "lang": "es", + "value": "El acceso a memoria fuera de los l\u00edmites en Dawn en Google Chrome anterior a 126.0.6478.114 permit\u00eda a un atacante remoto explotar potencialmente la corrupci\u00f3n del mont\u00f3n a trav\u00e9s de una p\u00e1gina HTML manipulada. (Severidad de seguridad de Chrome: alta)" } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6103.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6103.json index 2343ee57906..8dbb92dde88 100644 --- a/CVE-2024/CVE-2024-61xx/CVE-2024-6103.json +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6103.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6103", "sourceIdentifier": "chrome-cve-admin@google.com", "published": "2024-06-20T00:15:10.133", - "lastModified": "2024-06-20T00:15:10.133", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "Use after free in Dawn in Google Chrome prior to 126.0.6478.114 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)" + }, + { + "lang": "es", + "value": "Use after free en Dawn en Google Chrome anterior a 126.0.6478.114 permit\u00eda a un atacante remoto explotar potencialmente la corrupci\u00f3n del mont\u00f3n a trav\u00e9s de una p\u00e1gina HTML manipulada. (Severidad de seguridad de Chrome: alta)" } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6108.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6108.json index b6e2e70010f..d770dc23b57 100644 --- a/CVE-2024/CVE-2024-61xx/CVE-2024-6108.json +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6108.json @@ -2,8 +2,8 @@ "id": "CVE-2024-6108", "sourceIdentifier": "cna@vuldb.com", "published": "2024-06-18T10:15:11.653", - "lastModified": "2024-06-18T10:15:11.653", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6109.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6109.json index 444f50821c5..410a78033d4 100644 --- a/CVE-2024/CVE-2024-61xx/CVE-2024-6109.json +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6109.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6109", "sourceIdentifier": "cna@vuldb.com", "published": "2024-06-18T12:15:12.987", - "lastModified": "2024-06-18T12:15:12.987", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A vulnerability was found in itsourcecode Tailoring Management System 1.0. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file addmeasurement.php. The manipulation of the argument id leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-268855." + }, + { + "lang": "es", + "value": "Se encontr\u00f3 una vulnerabilidad en itsourcecode Tailoring Management System 1.0. Ha sido declarada cr\u00edtica. Una funci\u00f3n desconocida del archivo addmeasurement.php es afectada por esta vulnerabilidad. La manipulaci\u00f3n del argumento id conduce a la inyecci\u00f3n de SQL. El ataque se puede lanzar de forma remota. El exploit ha sido divulgado al p\u00fablico y puede utilizarse. El identificador asociado de esta vulnerabilidad es VDB-268855." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6110.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6110.json index 0804bed1892..83e2dad0ecf 100644 --- a/CVE-2024/CVE-2024-61xx/CVE-2024-6110.json +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6110.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6110", "sourceIdentifier": "cna@vuldb.com", "published": "2024-06-18T12:15:13.290", - "lastModified": "2024-06-18T12:15:13.290", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A vulnerability was found in itsourcecode Magbanua Beach Resort Online Reservation System up to 1.0. It has been rated as critical. Affected by this issue is some unknown functionality of the file controller.php. The manipulation of the argument image leads to unrestricted upload. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-268856." + }, + { + "lang": "es", + "value": "Se encontr\u00f3 una vulnerabilidad en itsourcecode Magbanua Beach Resort Online Reservation System hasta 1.0. Ha sido calificada como cr\u00edtica. Una funci\u00f3n desconocida del archivo controller.php es afectada por esta vulnerabilidad. La manipulaci\u00f3n de la imagen del argumento conduce a una carga sin restricciones. El ataque puede lanzarse de forma remota. El exploit ha sido divulgado al p\u00fablico y puede utilizarse. El identificador de esta vulnerabilidad es VDB-268856. " } ], "metrics": { diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6111.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6111.json index 878eaf1dce1..f8bd8093922 100644 --- a/CVE-2024/CVE-2024-61xx/CVE-2024-6111.json +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6111.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6111", "sourceIdentifier": "cna@vuldb.com", "published": "2024-06-18T13:15:52.193", - "lastModified": "2024-06-18T15:15:52.873", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A vulnerability classified as critical has been found in itsourcecode Pool of Bethesda Online Reservation System 1.0. This affects an unknown part of the file login.php. The manipulation of the argument email leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-268857 was assigned to this vulnerability." + }, + { + "lang": "es", + "value": "Una vulnerabilidad ha sido encontrada en itsourcecode Pool of Bethesda Online Reservation System 1.0 y clasificada como cr\u00edtica. Una parte desconocida del archivo login.php afecta a esta vulnerabilidad. La manipulaci\u00f3n del argumento email conduce a la inyecci\u00f3n de SQL. Es posible iniciar el ataque de forma remota. El exploit ha sido divulgado al p\u00fablico y puede utilizarse. A esta vulnerabilidad se le asign\u00f3 el identificador VDB-268857." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6112.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6112.json index 8f51ad9fcc8..1ff6a5fe036 100644 --- a/CVE-2024/CVE-2024-61xx/CVE-2024-6112.json +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6112.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6112", "sourceIdentifier": "cna@vuldb.com", "published": "2024-06-18T13:15:52.550", - "lastModified": "2024-06-18T15:15:52.993", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A vulnerability classified as critical was found in itsourcecode Pool of Bethesda Online Reservation System 1.0. This vulnerability affects unknown code of the file index.php. The manipulation of the argument log_email leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. VDB-268858 is the identifier assigned to this vulnerability." + }, + { + "lang": "es", + "value": "Una vulnerabilidad fue encontrada en itsourcecode Pool of Bethesda Online Reservation System 1.0 y clasificada como cr\u00edtica. Esta vulnerabilidad afecta a un c\u00f3digo desconocido del archivo index.php. La manipulaci\u00f3n del argumento log_email conduce a la inyecci\u00f3n de SQL. El ataque se puede iniciar de forma remota. El exploit ha sido divulgado al p\u00fablico y puede utilizarse. VDB-268858 es el identificador asignado a esta vulnerabilidad." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6113.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6113.json index ebf7e3a259e..cf164debb6b 100644 --- a/CVE-2024/CVE-2024-61xx/CVE-2024-6113.json +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6113.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6113", "sourceIdentifier": "cna@vuldb.com", "published": "2024-06-20T06:15:10.310", - "lastModified": "2024-06-20T06:15:10.310", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A vulnerability was found in itsourcecode Monbela Tourist Inn Online Reservation System 1.0. It has been rated as critical. This issue affects some unknown processing of the file login.php. The manipulation of the argument email leads to sql injection. The attack may be initiated remotely. The identifier VDB-268865 was assigned to this vulnerability." + }, + { + "lang": "es", + "value": "Se encontr\u00f3 una vulnerabilidad en itsourcecode Monbela Tourist Inn Online Reservation System 1.0. Ha sido calificada como cr\u00edtica. Este problema afecta un procesamiento desconocido del archivo login.php. La manipulaci\u00f3n del argumento email conduce a la inyecci\u00f3n de SQL. El ataque puede iniciarse de forma remota. A esta vulnerabilidad se le asign\u00f3 el identificador VDB-268865." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6114.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6114.json index 19988af1353..6d0c632ddd8 100644 --- a/CVE-2024/CVE-2024-61xx/CVE-2024-6114.json +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6114.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6114", "sourceIdentifier": "cna@vuldb.com", "published": "2024-06-18T13:15:52.897", - "lastModified": "2024-06-18T13:15:52.897", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A vulnerability classified as critical has been found in itsourcecode Monbela Tourist Inn Online Reservation System up to 1.0. Affected is an unknown function of the file controller.php. The manipulation of the argument image leads to unrestricted upload. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. VDB-268866 is the identifier assigned to this vulnerability." + }, + { + "lang": "es", + "value": "Una vulnerabilidad ha sido encontrada en itsourcecode Monbela Tourist Inn Online Reservation System y clasificada como cr\u00edtica. Una funci\u00f3n desconocida del archivo controller.php es afectada por esta vulnerabilidad. La manipulaci\u00f3n de la imagen del argumento conduce a una carga sin restricciones. Es posible lanzar el ataque de forma remota. El exploit ha sido divulgado al p\u00fablico y puede utilizarse. VDB-268866 es el identificador asignado a esta vulnerabilidad." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6115.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6115.json index 4c0f8ad9a72..df847b0ecba 100644 --- a/CVE-2024/CVE-2024-61xx/CVE-2024-6115.json +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6115.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6115", "sourceIdentifier": "cna@vuldb.com", "published": "2024-06-18T13:15:53.267", - "lastModified": "2024-06-18T13:15:53.267", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A vulnerability classified as critical was found in itsourcecode Simple Online Hotel Reservation System 1.0. Affected by this vulnerability is an unknown functionality of the file add_room.php. The manipulation of the argument photo leads to unrestricted upload. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-268867." + }, + { + "lang": "es", + "value": "Una vulnerabilidad fue encontrada en itsourcecode Simple Online Hotel Reservation System 1.0 y clasificada como cr\u00edtica. Una funci\u00f3n desconocida del archivo add_room.php es afectada por esta vulnerabilidad. La manipulaci\u00f3n de la foto del argumento da lugar a una subida sin restricciones. El ataque se puede lanzar de forma remota. El exploit ha sido divulgado al p\u00fablico y puede utilizarse. El identificador asociado de esta vulnerabilidad es VDB-268867." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6116.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6116.json index f4364e56743..bc2f39187a8 100644 --- a/CVE-2024/CVE-2024-61xx/CVE-2024-6116.json +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6116.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6116", "sourceIdentifier": "cna@vuldb.com", "published": "2024-06-18T14:15:12.440", - "lastModified": "2024-06-18T16:15:10.983", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A vulnerability, which was classified as critical, has been found in itsourcecode Simple Online Hotel Reservation System 1.0. Affected by this issue is some unknown functionality of the file edit_room.php. The manipulation of the argument photo leads to unrestricted upload. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-268868." + }, + { + "lang": "es", + "value": "Una vulnerabilidad fue encontrada en itsourcecode Simple Online Hotel Reservation System 1.0 y clasificada como cr\u00edtica. Una funci\u00f3n desconocida del archivo edit_room.php es afectada por esta vulnerabilidad. La manipulaci\u00f3n de la foto del argumento da lugar a una subida sin restricciones. El ataque puede lanzarse de forma remota. El exploit ha sido divulgado al p\u00fablico y puede utilizarse. El identificador de esta vulnerabilidad es VDB-268868." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6125.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6125.json index a45fbd3000e..f46922f12b5 100644 --- a/CVE-2024/CVE-2024-61xx/CVE-2024-6125.json +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6125.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6125", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-19T02:15:09.873", - "lastModified": "2024-06-19T02:15:09.873", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The Login with phone number plugin for WordPress is vulnerable to unauthorized password resets in versions up to, and including 1.7.34. This is due to the plugin generating too weak a reset code, and the code used to reset the password has no attempt or time limit. This makes it possible for unauthenticated attackers to reset the password of arbitrary users by guessing a 6-digit numeric reset code." + }, + { + "lang": "es", + "value": "El complemento Login with phone number para WordPress es vulnerable a restablecimientos de contrase\u00f1a no autorizados en versiones hasta la 1.7.34 incluida. Esto se debe a que el complemento genera un c\u00f3digo de restablecimiento demasiado d\u00e9bil y el c\u00f3digo utilizado para restablecer la contrase\u00f1a no tiene l\u00edmite de intento ni de tiempo. Esto hace posible que atacantes no autenticados restablezcan la contrase\u00f1a de usuarios arbitrarios adivinando un c\u00f3digo de restablecimiento num\u00e9rico de 6 d\u00edgitos." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6128.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6128.json index da4273aaf4d..43810787943 100644 --- a/CVE-2024/CVE-2024-61xx/CVE-2024-6128.json +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6128.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6128", "sourceIdentifier": "cna@vuldb.com", "published": "2024-06-18T21:15:56.877", - "lastModified": "2024-06-18T21:15:56.877", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A vulnerability, which was classified as problematic, has been found in spa-cartcms 1.9.0.6. This issue affects some unknown processing of the file /checkout of the component Checkout Page. The manipulation of the argument quantity with the input -10 leads to enforcement of behavioral workflow. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-268895." + }, + { + "lang": "es", + "value": "Una vulnerabilidad fue encontrada en spa-cartcms 1.9.0.6 y clasificada como problem\u00e1tica. Este problema afecta un procesamiento desconocido del archivo /checkout de la p\u00e1gina de pago del componente. La manipulaci\u00f3n del argumento cantidad con la entrada -10 conduce a la aplicaci\u00f3n del flujo de trabajo conductual. El ataque puede iniciarse de forma remota. El exploit ha sido divulgado al p\u00fablico y puede utilizarse. El identificador asociado de esta vulnerabilidad es VDB-268895." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6129.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6129.json index 833ae7d1ff3..f0a5c4f2b1e 100644 --- a/CVE-2024/CVE-2024-61xx/CVE-2024-6129.json +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6129.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6129", "sourceIdentifier": "cna@vuldb.com", "published": "2024-06-18T21:15:57.217", - "lastModified": "2024-06-18T21:15:57.217", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A vulnerability, which was classified as problematic, was found in spa-cartcms 1.9.0.6. Affected is an unknown function of the file /login of the component Username Handler. The manipulation of the argument email leads to observable behavioral discrepancy. It is possible to launch the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-268896." + }, + { + "lang": "es", + "value": "Una vulnerabilidad fue encontrada en spa-cartcms 1.9.0.6 y clasificada como problem\u00e1tica. Una funci\u00f3n desconocida del archivo /login del componente Username Handler es afectada por esta vulnerabilidad. La manipulaci\u00f3n del argumento del correo electr\u00f3nico conduce a una discrepancia de comportamiento observable. Es posible lanzar el ataque de forma remota. La complejidad de un ataque es bastante alta. Se dice que la explotabilidad es dif\u00edcil. El exploit ha sido divulgado al p\u00fablico y puede utilizarse. El identificador de esta vulnerabilidad es VDB-268896." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6132.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6132.json index de71f6c0a89..2b76bb4f3ce 100644 --- a/CVE-2024/CVE-2024-61xx/CVE-2024-6132.json +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6132.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6132", "sourceIdentifier": "security@wordfence.com", "published": "2024-06-19T06:15:12.520", - "lastModified": "2024-06-19T06:15:12.520", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "The Pexels: Free Stock Photos plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the 'pexels_fsp_images_options_validate' function in all versions up to, and including, 1.2.2. This makes it possible for authenticated attackers, with contributor-level and above permissions, to upload arbitrary files on the affected site's server which may make remote code execution possible." + }, + { + "lang": "es", + "value": "El complemento Pexels: Free Stock Photos para WordPress es vulnerable a la carga de archivos arbitrarios debido a la falta de validaci\u00f3n del tipo de archivo en la funci\u00f3n 'pexels_fsp_images_options_validate' en todas las versiones hasta la 1.2.2 incluida. Esto hace posible que atacantes autenticados, con permisos de nivel de colaborador y superiores, carguen archivos arbitrarios en el servidor del sitio afectado, lo que puede hacer posible la ejecuci\u00f3n remota de c\u00f3digo." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6142.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6142.json index cf1a33221f9..52239d8610f 100644 --- a/CVE-2024/CVE-2024-61xx/CVE-2024-6142.json +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6142.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6142", "sourceIdentifier": "zdi-disclosures@trendmicro.com", "published": "2024-06-19T00:15:49.580", - "lastModified": "2024-06-19T00:15:49.580", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Actiontec WCB6200Q uh_tcp_recv_content Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Actiontec WCB6200Q routers. Authentication is not required to exploit this vulnerability.\n\nThe specific flaw exists within the HTTP server. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length buffer. An attacker can leverage this vulnerability to execute code in the context of the HTTP server. Was ZDI-CAN-21410." + }, + { + "lang": "es", + "value": "Vulnerabilidad de ejecuci\u00f3n remota de c\u00f3digo por desbordamiento del b\u00fafer en Actiontec WCB6200Q uh_tcp_recv_content. Esta vulnerabilidad permite a atacantes adyacentes a la red ejecutar c\u00f3digo arbitrario en instalaciones afectadas de enrutadores Actiontec WCB6200Q. No se requiere autenticaci\u00f3n para aprovechar esta vulnerabilidad. La falla espec\u00edfica existe dentro del servidor HTTP. El problema se debe a la falta de una validaci\u00f3n adecuada de la longitud de los datos proporcionados por el usuario antes de copiarlos en un b\u00fafer de longitud fija. Un atacante puede aprovechar esta vulnerabilidad para ejecutar c\u00f3digo en el contexto del servidor HTTP. Era ZDI-CAN-21410." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6143.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6143.json index c91f782028c..d7929c9fdca 100644 --- a/CVE-2024/CVE-2024-61xx/CVE-2024-6143.json +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6143.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6143", "sourceIdentifier": "zdi-disclosures@trendmicro.com", "published": "2024-06-19T00:15:49.847", - "lastModified": "2024-06-19T00:15:49.847", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Actiontec WCB6200Q uh_tcp_recv_header Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Actiontec WCB6200Q routers. Authentication is not required to exploit this vulnerability.\n\nThe specific flaw exists within the HTTP server. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length buffer. An attacker can leverage this vulnerability to execute code in the context of the HTTP server. Was ZDI-CAN-21414." + }, + { + "lang": "es", + "value": "Vulnerabilidad de ejecuci\u00f3n remota de c\u00f3digo por desbordamiento del b\u00fafer en Actiontec WCB6200Q uh_tcp_recv_header. Esta vulnerabilidad permite a atacantes adyacentes a la red ejecutar c\u00f3digo arbitrario en instalaciones afectadas de enrutadores Actiontec WCB6200Q. No se requiere autenticaci\u00f3n para aprovechar esta vulnerabilidad. La falla espec\u00edfica existe dentro del servidor HTTP. El problema se debe a la falta de una validaci\u00f3n adecuada de la longitud de los datos proporcionados por el usuario antes de copiarlos en un b\u00fafer de longitud fija. Un atacante puede aprovechar esta vulnerabilidad para ejecutar c\u00f3digo en el contexto del servidor HTTP. Era ZDI-CAN-21414." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6144.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6144.json index 6268691634a..5285e8aff0c 100644 --- a/CVE-2024/CVE-2024-61xx/CVE-2024-6144.json +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6144.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6144", "sourceIdentifier": "zdi-disclosures@trendmicro.com", "published": "2024-06-19T00:15:50.133", - "lastModified": "2024-06-19T00:15:50.133", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Actiontec WCB6200Q Multipart Boundary Stack-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Actiontec WCB6200Q routers. Authentication is not required to exploit this vulnerability.\n\nThe specific flaw exists within the HTTP server. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of the HTTP server. Was ZDI-CAN-21416." + }, + { + "lang": "es", + "value": "Vulnerabilidad de ejecuci\u00f3n remota de c\u00f3digo de desbordamiento de b\u00fafer basado en pila de los l\u00edmites multiparte Actiontec WCB6200Q. Esta vulnerabilidad permite a atacantes adyacentes a la red ejecutar c\u00f3digo arbitrario en instalaciones afectadas de enrutadores Actiontec WCB6200Q. No se requiere autenticaci\u00f3n para aprovechar esta vulnerabilidad. La falla espec\u00edfica existe dentro del servidor HTTP. El problema se debe a la falta de una validaci\u00f3n adecuada de la longitud de los datos proporcionados por el usuario antes de copiarlos en un b\u00fafer basado en pila de longitud fija. Un atacante puede aprovechar esta vulnerabilidad para ejecutar c\u00f3digo en el contexto del servidor HTTP. Era ZDI-CAN-21416." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6145.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6145.json index b2e23be003e..f3d6c29785c 100644 --- a/CVE-2024/CVE-2024-61xx/CVE-2024-6145.json +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6145.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6145", "sourceIdentifier": "zdi-disclosures@trendmicro.com", "published": "2024-06-19T00:15:50.413", - "lastModified": "2024-06-19T00:15:50.413", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Actiontec WCB6200Q Cookie Format String Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Actiontec WCB6200Q routers. Authentication is not required to exploit this vulnerability.\n\nThe specific flaw exists within the HTTP server. A crafted Cookie header in an HTTP request can trigger the use of a format specifier from a user-supplied string. An attacker can leverage this vulnerability to execute code in the context of the HTTP server. Was ZDI-CAN-21417." + }, + { + "lang": "es", + "value": "Vulnerabilidad de ejecuci\u00f3n remota de c\u00f3digo de cadena de formato de cookie Actiontec WCB6200Q. Esta vulnerabilidad permite a atacantes adyacentes a la red ejecutar c\u00f3digo arbitrario en instalaciones afectadas de enrutadores Actiontec WCB6200Q. No se requiere autenticaci\u00f3n para aprovechar esta vulnerabilidad. La falla espec\u00edfica existe dentro del servidor HTTP. Un encabezado de cookie manipulado en una solicitud HTTP puede desencadenar el uso de un especificador de formato a partir de una cadena proporcionada por el usuario. Un atacante puede aprovechar esta vulnerabilidad para ejecutar c\u00f3digo en el contexto del servidor HTTP. Era ZDI-CAN-21417." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6146.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6146.json index 0de91dd8f31..fd4b700f83c 100644 --- a/CVE-2024/CVE-2024-61xx/CVE-2024-6146.json +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6146.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6146", "sourceIdentifier": "zdi-disclosures@trendmicro.com", "published": "2024-06-19T00:15:50.703", - "lastModified": "2024-06-19T00:15:50.703", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:44:01.637", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Actiontec WCB6200Q uh_get_postdata_withupload Stack-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Actiontec WCB6200Q routers. Authentication is not required to exploit this vulnerability.\n\nThe specific flaw exists within the HTTP server. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of the HTTP server. Was ZDI-CAN-21418." + }, + { + "lang": "es", + "value": "Vulnerabilidad de ejecuci\u00f3n remota de c\u00f3digo de desbordamiento de b\u00fafer basado en pila en Actiontec WCB6200Q uh_get_postdata_withupload. Esta vulnerabilidad permite a atacantes adyacentes a la red ejecutar c\u00f3digo arbitrario en instalaciones afectadas de enrutadores Actiontec WCB6200Q. No se requiere autenticaci\u00f3n para aprovechar esta vulnerabilidad. La falla espec\u00edfica existe dentro del servidor HTTP. El problema se debe a la falta de una validaci\u00f3n adecuada de la longitud de los datos proporcionados por el usuario antes de copiarlos en un b\u00fafer basado en pila de longitud fija. Un atacante puede aprovechar esta vulnerabilidad para ejecutar c\u00f3digo en el contexto del servidor HTTP. Era ZDI-CAN-21418." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6176.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6176.json index 9cd9c8d0974..eee1492391c 100644 --- a/CVE-2024/CVE-2024-61xx/CVE-2024-6176.json +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6176.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6176", "sourceIdentifier": "product.security@lge.com", "published": "2024-06-20T01:15:49.023", - "lastModified": "2024-06-20T01:15:49.023", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "Allocation of Resources Without Limits or Throttling vulnerability in LG Electronics LG SuperSign CMS allows Port Scanning.This issue affects LG SuperSign CMS: from 4.1.3 before < 4.3.1." + }, + { + "lang": "es", + "value": "Asignaci\u00f3n de recursos sin l\u00edmites o vulnerabilidad de limitaci\u00f3n en LG Electronics LG SuperSign CMS permite el escaneo de puertos. Este problema afecta a LG SuperSign CMS: desde 4.1.3 antes < 4.3.1." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6177.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6177.json index 6f287c15d11..013c1d81c17 100644 --- a/CVE-2024/CVE-2024-61xx/CVE-2024-6177.json +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6177.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6177", "sourceIdentifier": "product.security@lge.com", "published": "2024-06-20T02:15:11.980", - "lastModified": "2024-06-20T02:15:11.980", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in LG Electronics SuperSign CMS allows Reflected XSS.\u00a0This issue affects SuperSign CMS: from 4.1.3 before < 4.3.1." + }, + { + "lang": "es", + "value": "La vulnerabilidad de neutralizaci\u00f3n inadecuada de la entrada durante la generaci\u00f3n de p\u00e1ginas web (XSS o 'Cross-site Scripting') en LG Electronics SuperSign CMS permite XSS Reflejado. Este problema afecta a SuperSign CMS: desde 4.1.3 antes < 4.3.1." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6178.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6178.json index e67f525b5cb..4e9f1337308 100644 --- a/CVE-2024/CVE-2024-61xx/CVE-2024-6178.json +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6178.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6178", "sourceIdentifier": "product.security@lge.com", "published": "2024-06-20T02:15:12.123", - "lastModified": "2024-06-20T02:15:12.123", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in LG Electronics SuperSign CMS allows Reflected XSS.\u00a0This issue affects SuperSign CMS: from 4.1.3 before < 4.3.1." + }, + { + "lang": "es", + "value": "La vulnerabilidad de neutralizaci\u00f3n inadecuada de la entrada durante la generaci\u00f3n de p\u00e1ginas web ('cross-site Scripting') en LG Electronics SuperSign CMS permite XSS Reflejado. Este problema afecta a SuperSign CMS: desde 4.1.3 antes < 4.3.1." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6179.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6179.json index 7d51833c4f7..3fbfbfd8ef4 100644 --- a/CVE-2024/CVE-2024-61xx/CVE-2024-6179.json +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6179.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6179", "sourceIdentifier": "product.security@lge.com", "published": "2024-06-20T02:15:12.257", - "lastModified": "2024-06-20T02:15:12.257", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Undergoing Analysis", "descriptions": [ { "lang": "en", "value": "Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in LG Electronics SuperSign CMS allows Reflected XSS.\u00a0This issue affects SuperSign CMS: from 4.1.3 before < 4.3.1." + }, + { + "lang": "es", + "value": "La vulnerabilidad de neutralizaci\u00f3n inadecuada de la entrada durante la generaci\u00f3n de p\u00e1ginas web ('cross-site Scripting') en LG Electronics SuperSign CMS permite XSS Reflejado. Este problema afecta a SuperSign CMS: desde 4.1.3 antes < 4.3.1." } ], "metrics": {}, diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6181.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6181.json index a68683722bf..f420f041f03 100644 --- a/CVE-2024/CVE-2024-61xx/CVE-2024-6181.json +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6181.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6181", "sourceIdentifier": "cna@vuldb.com", "published": "2024-06-20T11:15:56.723", - "lastModified": "2024-06-20T11:15:56.723", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A vulnerability was found in LabVantage LIMS 2017. It has been declared as problematic. This vulnerability affects unknown code of the file /labvantage/rc?command=file&file=WEB-CORE/elements/files/filesembedded.jsp&size=32. The manipulation of the argument height/width leads to cross site scripting. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-269152. NOTE: The vendor was contacted early about this disclosure but did not respond in any way." + }, + { + "lang": "es", + "value": "Una vulnerabilidad fue encontrada en LabVantage LIMS 2017 y ha sido declarada problem\u00e1tica. Esta vulnerabilidad afecta a c\u00f3digo desconocido del archivo /labvantage/rc?command=file&file=WEB-CORE/elements/files/filesembedded.jsp&size=32. La manipulaci\u00f3n del argumento alto/ancho conduce a cross site scripting. El ataque se puede iniciar de forma remota. El exploit ha sido divulgado al p\u00fablico y puede utilizarse. El identificador de esta vulnerabilidad es VDB-269152. NOTA: Se contact\u00f3 primeramente con el proveedor sobre esta divulgaci\u00f3n, pero no respondi\u00f3 de ninguna manera." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6182.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6182.json index f9b5489a07b..f3bd2ad5bf9 100644 --- a/CVE-2024/CVE-2024-61xx/CVE-2024-6182.json +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6182.json @@ -2,12 +2,16 @@ "id": "CVE-2024-6182", "sourceIdentifier": "cna@vuldb.com", "published": "2024-06-20T11:15:57.117", - "lastModified": "2024-06-20T11:15:57.117", - "vulnStatus": "Received", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", "descriptions": [ { "lang": "en", "value": "A vulnerability was found in LabVantage LIMS 2017. It has been rated as problematic. This issue affects some unknown processing of the file /labvantage/rc?command=page&page=LV_ViewSampleSpec&oosonly=Y&_sdialog=Y. The manipulation of the argument sdcid/keyid1 leads to cross site scripting. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-269153 was assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way." + }, + { + "lang": "es", + "value": "Se encontr\u00f3 una vulnerabilidad en LabVantage LIMS 2017. Se calific\u00f3 como problem\u00e1tica. Este problema afecta un procesamiento desconocido del archivo /labvantage/rc?command=page&page=LV_ViewSampleSpec&oosonly=Y&_sdialog=Y. La manipulaci\u00f3n del argumento sdcid/keyid1 conduce a cross site scripting. El ataque puede iniciarse de forma remota. El exploit ha sido divulgado al p\u00fablico y puede utilizarse. A esta vulnerabilidad se le asign\u00f3 el identificador VDB-269153. NOTA: Se contact\u00f3 primeramente con el proveedor sobre esta divulgaci\u00f3n, pero no respondi\u00f3 de ninguna manera." } ], "metrics": { diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6183.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6183.json new file mode 100644 index 00000000000..e493d6b0494 --- /dev/null +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6183.json @@ -0,0 +1,88 @@ +{ + "id": "CVE-2024-6183", + "sourceIdentifier": "cna@vuldb.com", + "published": "2024-06-20T12:15:15.233", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "A vulnerability classified as problematic has been found in EZ-Suite EZ-Partner 5. Affected is an unknown function of the component Forgot Password Handler. The manipulation leads to basic cross site scripting. It is possible to launch the attack remotely. VDB-269154 is the identifier assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way." + } + ], + "metrics": { + "cvssMetricV31": [ + { + "source": "cna@vuldb.com", + "type": "Secondary", + "cvssData": { + "version": "3.1", + "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N", + "attackVector": "NETWORK", + "attackComplexity": "LOW", + "privilegesRequired": "NONE", + "userInteraction": "REQUIRED", + "scope": "UNCHANGED", + "confidentialityImpact": "NONE", + "integrityImpact": "LOW", + "availabilityImpact": "NONE", + "baseScore": 4.3, + "baseSeverity": "MEDIUM" + }, + "exploitabilityScore": 2.8, + "impactScore": 1.4 + } + ], + "cvssMetricV2": [ + { + "source": "cna@vuldb.com", + "type": "Secondary", + "cvssData": { + "version": "2.0", + "vectorString": "AV:N/AC:L/Au:N/C:N/I:P/A:N", + "accessVector": "NETWORK", + "accessComplexity": "LOW", + "authentication": "NONE", + "confidentialityImpact": "NONE", + "integrityImpact": "PARTIAL", + "availabilityImpact": "NONE", + "baseScore": 5.0 + }, + "baseSeverity": "MEDIUM", + "exploitabilityScore": 10.0, + "impactScore": 2.9, + "acInsufInfo": false, + "obtainAllPrivilege": false, + "obtainUserPrivilege": false, + "obtainOtherPrivilege": false, + "userInteractionRequired": false + } + ] + }, + "weaknesses": [ + { + "source": "cna@vuldb.com", + "type": "Primary", + "description": [ + { + "lang": "en", + "value": "CWE-80" + } + ] + } + ], + "references": [ + { + "url": "https://vuldb.com/?ctiid.269154", + "source": "cna@vuldb.com" + }, + { + "url": "https://vuldb.com/?id.269154", + "source": "cna@vuldb.com" + }, + { + "url": "https://vuldb.com/?submit.353713", + "source": "cna@vuldb.com" + } + ] +} \ No newline at end of file diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6184.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6184.json new file mode 100644 index 00000000000..75795af2be6 --- /dev/null +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6184.json @@ -0,0 +1,92 @@ +{ + "id": "CVE-2024-6184", + "sourceIdentifier": "cna@vuldb.com", + "published": "2024-06-20T12:15:15.560", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "A vulnerability classified as critical was found in Ruijie RG-UAC 1.0. Affected by this vulnerability is an unknown functionality of the file /view/systemConfig/reboot/reboot_commit.php. The manipulation of the argument servicename leads to os command injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-269155. NOTE: The vendor was contacted early about this disclosure but did not respond in any way." + } + ], + "metrics": { + "cvssMetricV31": [ + { + "source": "cna@vuldb.com", + "type": "Secondary", + "cvssData": { + "version": "3.1", + "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L", + "attackVector": "NETWORK", + "attackComplexity": "LOW", + "privilegesRequired": "LOW", + "userInteraction": "NONE", + "scope": "UNCHANGED", + "confidentialityImpact": "LOW", + "integrityImpact": "LOW", + "availabilityImpact": "LOW", + "baseScore": 6.3, + "baseSeverity": "MEDIUM" + }, + "exploitabilityScore": 2.8, + "impactScore": 3.4 + } + ], + "cvssMetricV2": [ + { + "source": "cna@vuldb.com", + "type": "Secondary", + "cvssData": { + "version": "2.0", + "vectorString": "AV:N/AC:L/Au:S/C:P/I:P/A:P", + "accessVector": "NETWORK", + "accessComplexity": "LOW", + "authentication": "SINGLE", + "confidentialityImpact": "PARTIAL", + "integrityImpact": "PARTIAL", + "availabilityImpact": "PARTIAL", + "baseScore": 6.5 + }, + "baseSeverity": "MEDIUM", + "exploitabilityScore": 8.0, + "impactScore": 6.4, + "acInsufInfo": false, + "obtainAllPrivilege": false, + "obtainUserPrivilege": false, + "obtainOtherPrivilege": false, + "userInteractionRequired": false + } + ] + }, + "weaknesses": [ + { + "source": "cna@vuldb.com", + "type": "Primary", + "description": [ + { + "lang": "en", + "value": "CWE-78" + } + ] + } + ], + "references": [ + { + "url": "https://github.com/L1OudFd8cl09/CVE/blob/main/11_06_2024_a.md", + "source": "cna@vuldb.com" + }, + { + "url": "https://vuldb.com/?ctiid.269155", + "source": "cna@vuldb.com" + }, + { + "url": "https://vuldb.com/?id.269155", + "source": "cna@vuldb.com" + }, + { + "url": "https://vuldb.com/?submit.354119", + "source": "cna@vuldb.com" + } + ] +} \ No newline at end of file diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6185.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6185.json new file mode 100644 index 00000000000..eb85c6b1b0d --- /dev/null +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6185.json @@ -0,0 +1,92 @@ +{ + "id": "CVE-2024-6185", + "sourceIdentifier": "cna@vuldb.com", + "published": "2024-06-20T12:15:15.873", + "lastModified": "2024-06-20T12:43:25.663", + "vulnStatus": "Awaiting Analysis", + "descriptions": [ + { + "lang": "en", + "value": "A vulnerability, which was classified as critical, has been found in Ruijie RG-UAC 1.0. Affected by this issue is the function get_ip_addr_details of the file /view/dhcp/dhcpConfig/commit.php. The manipulation of the argument ethname leads to os command injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-269156. NOTE: The vendor was contacted early about this disclosure but did not respond in any way." + } + ], + "metrics": { + "cvssMetricV31": [ + { + "source": "cna@vuldb.com", + "type": "Secondary", + "cvssData": { + "version": "3.1", + "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L", + "attackVector": "NETWORK", + "attackComplexity": "LOW", + "privilegesRequired": "LOW", + "userInteraction": "NONE", + "scope": "UNCHANGED", + "confidentialityImpact": "LOW", + "integrityImpact": "LOW", + "availabilityImpact": "LOW", + "baseScore": 6.3, + "baseSeverity": "MEDIUM" + }, + "exploitabilityScore": 2.8, + "impactScore": 3.4 + } + ], + "cvssMetricV2": [ + { + "source": "cna@vuldb.com", + "type": "Secondary", + "cvssData": { + "version": "2.0", + "vectorString": "AV:N/AC:L/Au:S/C:P/I:P/A:P", + "accessVector": "NETWORK", + "accessComplexity": "LOW", + "authentication": "SINGLE", + "confidentialityImpact": "PARTIAL", + "integrityImpact": "PARTIAL", + "availabilityImpact": "PARTIAL", + "baseScore": 6.5 + }, + "baseSeverity": "MEDIUM", + "exploitabilityScore": 8.0, + "impactScore": 6.4, + "acInsufInfo": false, + "obtainAllPrivilege": false, + "obtainUserPrivilege": false, + "obtainOtherPrivilege": false, + "userInteractionRequired": false + } + ] + }, + "weaknesses": [ + { + "source": "cna@vuldb.com", + "type": "Primary", + "description": [ + { + "lang": "en", + "value": "CWE-78" + } + ] + } + ], + "references": [ + { + "url": "https://github.com/L1OudFd8cl09/CVE/blob/main/11_06_2024_b.md", + "source": "cna@vuldb.com" + }, + { + "url": "https://vuldb.com/?ctiid.269156", + "source": "cna@vuldb.com" + }, + { + "url": "https://vuldb.com/?id.269156", + "source": "cna@vuldb.com" + }, + { + "url": "https://vuldb.com/?submit.354121", + "source": "cna@vuldb.com" + } + ] +} \ No newline at end of file diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6186.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6186.json new file mode 100644 index 00000000000..ba57d6dd405 --- /dev/null +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6186.json @@ -0,0 +1,92 @@ +{ + "id": "CVE-2024-6186", + "sourceIdentifier": "cna@vuldb.com", + "published": "2024-06-20T13:15:50.007", + "lastModified": "2024-06-20T13:15:50.007", + "vulnStatus": "Received", + "descriptions": [ + { + "lang": "en", + "value": "A vulnerability, which was classified as critical, was found in Ruijie RG-UAC 1.0. This affects an unknown part of the file /view/userAuthentication/SSO/commit.php. The manipulation of the argument ad_log_name leads to os command injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-269157 was assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way." + } + ], + "metrics": { + "cvssMetricV31": [ + { + "source": "cna@vuldb.com", + "type": "Secondary", + "cvssData": { + "version": "3.1", + "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L", + "attackVector": "NETWORK", + "attackComplexity": "LOW", + "privilegesRequired": "LOW", + "userInteraction": "NONE", + "scope": "UNCHANGED", + "confidentialityImpact": "LOW", + "integrityImpact": "LOW", + "availabilityImpact": "LOW", + "baseScore": 6.3, + "baseSeverity": "MEDIUM" + }, + "exploitabilityScore": 2.8, + "impactScore": 3.4 + } + ], + "cvssMetricV2": [ + { + "source": "cna@vuldb.com", + "type": "Secondary", + "cvssData": { + "version": "2.0", + "vectorString": "AV:N/AC:L/Au:S/C:P/I:P/A:P", + "accessVector": "NETWORK", + "accessComplexity": "LOW", + "authentication": "SINGLE", + "confidentialityImpact": "PARTIAL", + "integrityImpact": "PARTIAL", + "availabilityImpact": "PARTIAL", + "baseScore": 6.5 + }, + "baseSeverity": "MEDIUM", + "exploitabilityScore": 8.0, + "impactScore": 6.4, + "acInsufInfo": false, + "obtainAllPrivilege": false, + "obtainUserPrivilege": false, + "obtainOtherPrivilege": false, + "userInteractionRequired": false + } + ] + }, + "weaknesses": [ + { + "source": "cna@vuldb.com", + "type": "Primary", + "description": [ + { + "lang": "en", + "value": "CWE-78" + } + ] + } + ], + "references": [ + { + "url": "https://github.com/L1OudFd8cl09/CVE/blob/main/11_06_2024_c.md", + "source": "cna@vuldb.com" + }, + { + "url": "https://vuldb.com/?ctiid.269157", + "source": "cna@vuldb.com" + }, + { + "url": "https://vuldb.com/?id.269157", + "source": "cna@vuldb.com" + }, + { + "url": "https://vuldb.com/?submit.354122", + "source": "cna@vuldb.com" + } + ] +} \ No newline at end of file diff --git a/CVE-2024/CVE-2024-61xx/CVE-2024-6187.json b/CVE-2024/CVE-2024-61xx/CVE-2024-6187.json new file mode 100644 index 00000000000..3099e649b73 --- /dev/null +++ b/CVE-2024/CVE-2024-61xx/CVE-2024-6187.json @@ -0,0 +1,92 @@ +{ + "id": "CVE-2024-6187", + "sourceIdentifier": "cna@vuldb.com", + "published": "2024-06-20T13:15:50.320", + "lastModified": "2024-06-20T13:15:50.320", + "vulnStatus": "Received", + "descriptions": [ + { + "lang": "en", + "value": "A vulnerability has been found in Ruijie RG-UAC 1.0 and classified as critical. This vulnerability affects unknown code of the file /view/vpn/autovpn/sub_commit.php. The manipulation of the argument key leads to os command injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. VDB-269158 is the identifier assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way." + } + ], + "metrics": { + "cvssMetricV31": [ + { + "source": "cna@vuldb.com", + "type": "Secondary", + "cvssData": { + "version": "3.1", + "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L", + "attackVector": "NETWORK", + "attackComplexity": "LOW", + "privilegesRequired": "LOW", + "userInteraction": "NONE", + "scope": "UNCHANGED", + "confidentialityImpact": "LOW", + "integrityImpact": "LOW", + "availabilityImpact": "LOW", + "baseScore": 6.3, + "baseSeverity": "MEDIUM" + }, + "exploitabilityScore": 2.8, + "impactScore": 3.4 + } + ], + "cvssMetricV2": [ + { + "source": "cna@vuldb.com", + "type": "Secondary", + "cvssData": { + "version": "2.0", + "vectorString": "AV:N/AC:L/Au:S/C:P/I:P/A:P", + "accessVector": "NETWORK", + "accessComplexity": "LOW", + "authentication": "SINGLE", + "confidentialityImpact": "PARTIAL", + "integrityImpact": "PARTIAL", + "availabilityImpact": "PARTIAL", + "baseScore": 6.5 + }, + "baseSeverity": "MEDIUM", + "exploitabilityScore": 8.0, + "impactScore": 6.4, + "acInsufInfo": false, + "obtainAllPrivilege": false, + "obtainUserPrivilege": false, + "obtainOtherPrivilege": false, + "userInteractionRequired": false + } + ] + }, + "weaknesses": [ + { + "source": "cna@vuldb.com", + "type": "Secondary", + "description": [ + { + "lang": "en", + "value": "CWE-78" + } + ] + } + ], + "references": [ + { + "url": "https://github.com/L1OudFd8cl09/CVE/blob/main/11_06_2024_d.md", + "source": "cna@vuldb.com" + }, + { + "url": "https://vuldb.com/?ctiid.269158", + "source": "cna@vuldb.com" + }, + { + "url": "https://vuldb.com/?id.269158", + "source": "cna@vuldb.com" + }, + { + "url": "https://vuldb.com/?submit.354125", + "source": "cna@vuldb.com" + } + ] +} \ No newline at end of file diff --git a/README.md b/README.md index da192a91c66..5b88fec14da 100644 --- a/README.md +++ b/README.md @@ -13,13 +13,13 @@ Repository synchronizes with the NVD every 2 hours. ### Last Repository Update ```plain -2024-06-20T12:00:18.799054+00:00 +2024-06-20T14:00:20.555063+00:00 ``` ### Most recent CVE Modification Timestamp synchronized with NVD ```plain -2024-06-20T11:15:57.117000+00:00 +2024-06-20T13:24:38.797000+00:00 ``` ### Last Data Feed Release @@ -33,43 +33,69 @@ Download and Changelog: [Click](https://github.com/fkie-cad/nvd-json-data-feeds/ ### Total Number of included CVEs ```plain -254671 +254730 ``` ### CVEs added in the last Commit -Recently added CVEs: `22` +Recently added CVEs: `59` -- [CVE-2021-47617](CVE-2021/CVE-2021-476xx/CVE-2021-47617.json) (`2024-06-20T11:15:54.317`) -- [CVE-2021-47618](CVE-2021/CVE-2021-476xx/CVE-2021-47618.json) (`2024-06-20T11:15:54.477`) -- [CVE-2021-47619](CVE-2021/CVE-2021-476xx/CVE-2021-47619.json) (`2024-06-20T11:15:54.560`) -- [CVE-2021-47620](CVE-2021/CVE-2021-476xx/CVE-2021-47620.json) (`2024-06-20T11:15:54.653`) -- [CVE-2022-48711](CVE-2022/CVE-2022-487xx/CVE-2022-48711.json) (`2024-06-20T11:15:54.793`) -- [CVE-2022-48712](CVE-2022/CVE-2022-487xx/CVE-2022-48712.json) (`2024-06-20T11:15:54.880`) -- [CVE-2022-48713](CVE-2022/CVE-2022-487xx/CVE-2022-48713.json) (`2024-06-20T11:15:54.960`) -- [CVE-2022-48714](CVE-2022/CVE-2022-487xx/CVE-2022-48714.json) (`2024-06-20T11:15:55.033`) -- [CVE-2022-48715](CVE-2022/CVE-2022-487xx/CVE-2022-48715.json) (`2024-06-20T11:15:55.110`) -- [CVE-2022-48716](CVE-2022/CVE-2022-487xx/CVE-2022-48716.json) (`2024-06-20T11:15:55.207`) -- [CVE-2022-48717](CVE-2022/CVE-2022-487xx/CVE-2022-48717.json) (`2024-06-20T11:15:55.287`) -- [CVE-2022-48718](CVE-2022/CVE-2022-487xx/CVE-2022-48718.json) (`2024-06-20T11:15:55.373`) -- [CVE-2022-48719](CVE-2022/CVE-2022-487xx/CVE-2022-48719.json) (`2024-06-20T11:15:55.470`) -- [CVE-2022-48720](CVE-2022/CVE-2022-487xx/CVE-2022-48720.json) (`2024-06-20T11:15:55.547`) -- [CVE-2022-48721](CVE-2022/CVE-2022-487xx/CVE-2022-48721.json) (`2024-06-20T11:15:55.620`) -- [CVE-2022-48722](CVE-2022/CVE-2022-487xx/CVE-2022-48722.json) (`2024-06-20T11:15:55.733`) -- [CVE-2022-48723](CVE-2022/CVE-2022-487xx/CVE-2022-48723.json) (`2024-06-20T11:15:55.820`) -- [CVE-2024-28147](CVE-2024/CVE-2024-281xx/CVE-2024-28147.json) (`2024-06-20T11:15:55.913`) -- [CVE-2024-5036](CVE-2024/CVE-2024-50xx/CVE-2024-5036.json) (`2024-06-20T11:15:56.273`) -- [CVE-2024-5886](CVE-2024/CVE-2024-58xx/CVE-2024-5886.json) (`2024-06-20T11:15:56.580`) -- [CVE-2024-6181](CVE-2024/CVE-2024-61xx/CVE-2024-6181.json) (`2024-06-20T11:15:56.723`) -- [CVE-2024-6182](CVE-2024/CVE-2024-61xx/CVE-2024-6182.json) (`2024-06-20T11:15:57.117`) +- [CVE-2022-48757](CVE-2022/CVE-2022-487xx/CVE-2022-48757.json) (`2024-06-20T12:15:13.823`) +- [CVE-2022-48758](CVE-2022/CVE-2022-487xx/CVE-2022-48758.json) (`2024-06-20T12:15:13.927`) +- [CVE-2022-48759](CVE-2022/CVE-2022-487xx/CVE-2022-48759.json) (`2024-06-20T12:15:14.023`) +- [CVE-2022-48760](CVE-2022/CVE-2022-487xx/CVE-2022-48760.json) (`2024-06-20T12:15:14.110`) +- [CVE-2022-48761](CVE-2022/CVE-2022-487xx/CVE-2022-48761.json) (`2024-06-20T12:15:14.203`) +- [CVE-2022-48762](CVE-2022/CVE-2022-487xx/CVE-2022-48762.json) (`2024-06-20T12:15:14.287`) +- [CVE-2022-48763](CVE-2022/CVE-2022-487xx/CVE-2022-48763.json) (`2024-06-20T12:15:14.363`) +- [CVE-2022-48764](CVE-2022/CVE-2022-487xx/CVE-2022-48764.json) (`2024-06-20T12:15:14.450`) +- [CVE-2022-48765](CVE-2022/CVE-2022-487xx/CVE-2022-48765.json) (`2024-06-20T12:15:14.530`) +- [CVE-2022-48766](CVE-2022/CVE-2022-487xx/CVE-2022-48766.json) (`2024-06-20T12:15:14.617`) +- [CVE-2022-48767](CVE-2022/CVE-2022-487xx/CVE-2022-48767.json) (`2024-06-20T12:15:14.703`) +- [CVE-2022-48768](CVE-2022/CVE-2022-487xx/CVE-2022-48768.json) (`2024-06-20T12:15:14.783`) +- [CVE-2022-48769](CVE-2022/CVE-2022-487xx/CVE-2022-48769.json) (`2024-06-20T12:15:14.870`) +- [CVE-2022-48770](CVE-2022/CVE-2022-487xx/CVE-2022-48770.json) (`2024-06-20T12:15:14.953`) +- [CVE-2022-48771](CVE-2022/CVE-2022-487xx/CVE-2022-48771.json) (`2024-06-20T12:15:15.043`) +- [CVE-2023-49110](CVE-2023/CVE-2023-491xx/CVE-2023-49110.json) (`2024-06-20T13:15:49.250`) +- [CVE-2023-49111](CVE-2023/CVE-2023-491xx/CVE-2023-49111.json) (`2024-06-20T13:15:49.380`) +- [CVE-2023-49112](CVE-2023/CVE-2023-491xx/CVE-2023-49112.json) (`2024-06-20T13:15:49.480`) +- [CVE-2023-49113](CVE-2023/CVE-2023-491xx/CVE-2023-49113.json) (`2024-06-20T13:15:49.560`) +- [CVE-2023-52883](CVE-2023/CVE-2023-528xx/CVE-2023-52883.json) (`2024-06-20T12:15:15.140`) +- [CVE-2024-6183](CVE-2024/CVE-2024-61xx/CVE-2024-6183.json) (`2024-06-20T12:15:15.233`) +- [CVE-2024-6184](CVE-2024/CVE-2024-61xx/CVE-2024-6184.json) (`2024-06-20T12:15:15.560`) +- [CVE-2024-6185](CVE-2024/CVE-2024-61xx/CVE-2024-6185.json) (`2024-06-20T12:15:15.873`) +- [CVE-2024-6186](CVE-2024/CVE-2024-61xx/CVE-2024-6186.json) (`2024-06-20T13:15:50.007`) +- [CVE-2024-6187](CVE-2024/CVE-2024-61xx/CVE-2024-6187.json) (`2024-06-20T13:15:50.320`) ### CVEs modified in the last Commit -Recently modified CVEs: `2` +Recently modified CVEs: `408` -- [CVE-2024-26807](CVE-2024/CVE-2024-268xx/CVE-2024-26807.json) (`2024-06-20T10:15:09.303`) -- [CVE-2024-34693](CVE-2024/CVE-2024-346xx/CVE-2024-34693.json) (`2024-06-20T11:15:56.090`) +- [CVE-2024-6103](CVE-2024/CVE-2024-61xx/CVE-2024-6103.json) (`2024-06-20T12:43:25.663`) +- [CVE-2024-6108](CVE-2024/CVE-2024-61xx/CVE-2024-6108.json) (`2024-06-20T12:44:01.637`) +- [CVE-2024-6109](CVE-2024/CVE-2024-61xx/CVE-2024-6109.json) (`2024-06-20T12:44:01.637`) +- [CVE-2024-6110](CVE-2024/CVE-2024-61xx/CVE-2024-6110.json) (`2024-06-20T12:44:01.637`) +- [CVE-2024-6111](CVE-2024/CVE-2024-61xx/CVE-2024-6111.json) (`2024-06-20T12:44:01.637`) +- [CVE-2024-6112](CVE-2024/CVE-2024-61xx/CVE-2024-6112.json) (`2024-06-20T12:44:01.637`) +- [CVE-2024-6113](CVE-2024/CVE-2024-61xx/CVE-2024-6113.json) (`2024-06-20T12:43:25.663`) +- [CVE-2024-6114](CVE-2024/CVE-2024-61xx/CVE-2024-6114.json) (`2024-06-20T12:44:01.637`) +- [CVE-2024-6115](CVE-2024/CVE-2024-61xx/CVE-2024-6115.json) (`2024-06-20T12:44:01.637`) +- [CVE-2024-6116](CVE-2024/CVE-2024-61xx/CVE-2024-6116.json) (`2024-06-20T12:44:01.637`) +- [CVE-2024-6125](CVE-2024/CVE-2024-61xx/CVE-2024-6125.json) (`2024-06-20T12:44:01.637`) +- [CVE-2024-6128](CVE-2024/CVE-2024-61xx/CVE-2024-6128.json) (`2024-06-20T12:44:01.637`) +- [CVE-2024-6129](CVE-2024/CVE-2024-61xx/CVE-2024-6129.json) (`2024-06-20T12:44:01.637`) +- [CVE-2024-6132](CVE-2024/CVE-2024-61xx/CVE-2024-6132.json) (`2024-06-20T12:44:01.637`) +- [CVE-2024-6142](CVE-2024/CVE-2024-61xx/CVE-2024-6142.json) (`2024-06-20T12:44:01.637`) +- [CVE-2024-6143](CVE-2024/CVE-2024-61xx/CVE-2024-6143.json) (`2024-06-20T12:44:01.637`) +- [CVE-2024-6144](CVE-2024/CVE-2024-61xx/CVE-2024-6144.json) (`2024-06-20T12:44:01.637`) +- [CVE-2024-6145](CVE-2024/CVE-2024-61xx/CVE-2024-6145.json) (`2024-06-20T12:44:01.637`) +- [CVE-2024-6146](CVE-2024/CVE-2024-61xx/CVE-2024-6146.json) (`2024-06-20T12:44:01.637`) +- [CVE-2024-6176](CVE-2024/CVE-2024-61xx/CVE-2024-6176.json) (`2024-06-20T12:43:25.663`) +- [CVE-2024-6177](CVE-2024/CVE-2024-61xx/CVE-2024-6177.json) (`2024-06-20T12:43:25.663`) +- [CVE-2024-6178](CVE-2024/CVE-2024-61xx/CVE-2024-6178.json) (`2024-06-20T12:43:25.663`) +- [CVE-2024-6179](CVE-2024/CVE-2024-61xx/CVE-2024-6179.json) (`2024-06-20T12:43:25.663`) +- [CVE-2024-6181](CVE-2024/CVE-2024-61xx/CVE-2024-6181.json) (`2024-06-20T12:43:25.663`) +- [CVE-2024-6182](CVE-2024/CVE-2024-61xx/CVE-2024-6182.json) (`2024-06-20T12:43:25.663`) ## Download and Usage diff --git a/_state.csv b/_state.csv index a6c5bf4e82b..b072886c567 100644 --- a/_state.csv +++ b/_state.csv @@ -121379,7 +121379,7 @@ CVE-2018-25098,0,0,fcae82fd425e45c0b5170e1d16175026afcc4282c8c2d036ab7934ed74d6d CVE-2018-25099,0,0,4477c16cb5a3503e957873dbddbd3b50ffb7092ffd27acf2a352c93f686dfb7f,2024-03-18T12:38:25.490000 CVE-2018-25100,0,0,26375a09020100e722ed36e37b25c669512cdaa2d61a780ec73480ee78db5d6b,2024-03-25T01:51:01.223000 CVE-2018-25101,0,0,b04dde640afba29853f504e83596fe419f66817bb46aeb488be7718ce77d287c,2024-06-04T19:16:57.060000 -CVE-2018-25103,0,0,1c9793e149655d3528332820a08b1745b5751a38cb908688b2059c830f89f510,2024-06-18T15:15:51.310000 +CVE-2018-25103,0,1,cbeb7183ee8d2abcf399d0a65ec2e2339a740557f606406f70279bfefd9ef633,2024-06-20T12:44:22.977000 CVE-2018-2515,0,0,158f882e4275a7485a2b9ce17e7e57c4ea22cf74c55a78a9900c73a4caa327c0,2023-11-07T02:57:57.887000 CVE-2018-2560,0,0,0bb1a26d6c05fddeb488697adb0bbe667a3dd77c1a5bc7af495c8721df5b1197,2020-08-24T17:37:01.140000 CVE-2018-2561,0,0,b76feaa260e2f54fc8eeb8d50d578ffdd22b603f486ac4f8f5b3bc42df22fa45,2018-01-25T13:53:15.120000 @@ -185102,6 +185102,7 @@ CVE-2021-44386,0,0,00b8287f5b7c8a0747d8a12a95e435e01f2ac023c2e2f7bb0cd135101e1fd CVE-2021-44387,0,0,dfbd399dfe4aab86157245acc012cb1b1bfc10fb32244c27f85df5caefe95d0f,2022-10-25T17:43:35.947000 CVE-2021-44388,0,0,692d769bf87e59c4f8b9ec249bebb3797906bc0f1d54c058758ce1b152846394,2022-10-25T17:43:28.293000 CVE-2021-44389,0,0,972f0b2428493ae5619d8eb80be95c08a07977fc039b3e1c367adfc82e19d7ca,2022-10-25T17:43:23.320000 +CVE-2021-4439,1,1,2544489b78a48b854f4a23708ab37ff8005d2bb7ad7840ec572b35d1bce0f30d,2024-06-20T12:43:25.663000 CVE-2021-44390,0,0,0aa2f3646bdd7e43769b5f7853edead41d341761f0cafbdd4062c99c97770e8d,2022-10-25T17:43:18.373000 CVE-2021-44391,0,0,389164038b7d6ca4cd7789c19cb1f37843d3d1fbc271016d800f6f8808241155,2022-10-25T17:43:13.387000 CVE-2021-44392,0,0,78841eb432530d6d24d4b0855b9b6e2a59cf15e0bf55e0bb2ad4459ae9a795cd,2022-10-25T17:43:02.037000 @@ -187374,51 +187375,51 @@ CVE-2021-47572,0,0,55c6e98268ccff9a12ecfcf7346b412b0260b19f4dd297c4a5d7a5ddb50f3 CVE-2021-47573,0,0,77f17ceffef01ed1235383fa8b9d660bd9e97f9957ddf89f7588fecd6de7f3ee,2024-06-20T09:15:10.660000 CVE-2021-47574,0,0,391863034eab59403fe143d15df40f1956c3dc69dca88c34541f90e4de440ed8,2024-06-20T09:15:10.850000 CVE-2021-47575,0,0,722357c96fabd9dcaa94e25f2d6c3827cc0d9ffea8340b657e2489a7b6bb493c,2024-06-20T09:15:10.953000 -CVE-2021-47576,0,0,529ff2838ef76d7619d5bef41c4412385193d0388581dc3389cc34ad5cb3392b,2024-06-19T15:15:52.117000 -CVE-2021-47577,0,0,2e716ba915bf347483c8366b86986fd4bc924c2188585127b0346a76083dca64,2024-06-19T15:15:52.223000 -CVE-2021-47578,0,0,b6cdd7cb71f065232f349708162f254a0436579d12bb1d2af1930716fd430722,2024-06-19T15:15:52.320000 -CVE-2021-47579,0,0,bacd9b18ea2cec453f67aac72823401bb7e8ad56778087942ea94693446c2239,2024-06-19T15:15:52.427000 -CVE-2021-47580,0,0,9d0dcf903250aa86955d83dd6f1490d35c7ce8feed681a55869b2ec26c204660,2024-06-19T15:15:52.537000 +CVE-2021-47576,0,1,69da014fbbc3f0b45c3145c4428c9eb7fd2605f6899eeb538841444654bbc7c2,2024-06-20T12:43:25.663000 +CVE-2021-47577,0,1,7fd8b9c48493a66d71ca3c86af2f0a2d9a9405883a0b1520ec50134ee4322ff7,2024-06-20T12:43:25.663000 +CVE-2021-47578,0,1,0d33797a02100a7695b700be3f92a3255ef0ab01bfa896746c8d613d9c14be1e,2024-06-20T12:43:25.663000 +CVE-2021-47579,0,1,cafaed068b7957bcdd661c186014562a1bb1b6ccd2b7a1f4499162f9481bf1e1,2024-06-20T12:43:25.663000 +CVE-2021-47580,0,1,e2a56c1083e5d1a375ac73a33b53d312695450476fbec5790b78690aa91218e6,2024-06-20T12:43:25.663000 CVE-2021-47581,0,0,17ec8f4e133d40e0db5079fe03b869ad7ee16e0e079fffc51fd025ed4a3f9521,2024-06-20T09:15:11.057000 -CVE-2021-47582,0,0,c9a1f9b44372a9f249b03729be5db788d3c9b94e5e60e99cb74bd75151e295d6,2024-06-19T15:15:52.743000 -CVE-2021-47583,0,0,6e348f5d1cee71355f4561877aa842e4099a5c563bcd5b01e8d3e5ff3a090cb9,2024-06-19T15:15:52.843000 -CVE-2021-47584,0,0,9fb73020197e21e2348918b425a736b526ca64cbfa5f5cb286809e6fb7fff65f,2024-06-19T15:15:52.947000 -CVE-2021-47585,0,0,45316e91c8bea316ee92b587c9319286686c3cd208f2af95f7d79d74efa8ffd7,2024-06-19T15:15:53.057000 -CVE-2021-47586,0,0,d331ab70c5bfde6c6665a76a3373a2e64c6c37aa6352a470c13c641107e0c358,2024-06-19T15:15:53.160000 -CVE-2021-47587,0,0,2d2423a7ab89a33b0d87880d69b9b6b4fc703b6d128c2553722952faa3021e10,2024-06-19T15:15:53.260000 -CVE-2021-47588,0,0,a0e1bbbf740ff002ca82b37c4b49dacf27e336198f81a7076a7a5293fdb6a1a6,2024-06-19T15:15:53.383000 -CVE-2021-47589,0,0,ac56294b81875646123649f94dd75ef2c6ac35510c3e137c15ab4cc9e6fd349f,2024-06-19T15:15:53.490000 -CVE-2021-47590,0,0,d929e2531a2ced2f00e7f6243856f459305d3b4a19388f9ad1dd32efc2ec8b88,2024-06-19T15:15:53.610000 -CVE-2021-47591,0,0,40905f7938dd7d861f006374ae1e07e2e7616091bd890434dbf0c4bad8f94157,2024-06-19T15:15:53.700000 -CVE-2021-47592,0,0,55b1818f44c50557b85aa84c23ab657b7b5f7952aafa89f635699705894e1acf,2024-06-19T15:15:53.793000 -CVE-2021-47593,0,0,2453e95f6bd69abf1aec24bb3f114d84b2bc68032117ce680e2144e38191f0b1,2024-06-19T15:15:53.890000 -CVE-2021-47594,0,0,b90ad310a01b0c7879387647b604e8a1251800522fd6f69713ee95b3e39c2426,2024-06-19T15:15:53.983000 -CVE-2021-47595,0,0,f8c8ae07336519cdffb88074b494617598d5645d3fac9e03dd860051b38e77b5,2024-06-19T15:15:54.097000 -CVE-2021-47596,0,0,3054e693ed0ec446db6a8d07adf32a25d995a4321e1df9f7a5f30cbe1dd2570d,2024-06-19T15:15:54.197000 -CVE-2021-47597,0,0,970bf402ceb007f313ab6d1c1de95f83c878be2765c685526cd8bc61745162c3,2024-06-19T15:15:54.290000 -CVE-2021-47598,0,0,10e9b631f62d5dd155c284e1a4264c46944800aef0fc6e20bf943547635c4285,2024-06-19T15:15:54.383000 -CVE-2021-47599,0,0,7b22220e915c7bf61ea16fd29285bd681e8b631551be6f299685c28134c39cbe,2024-06-19T15:15:54.483000 -CVE-2021-47600,0,0,949a4794b9506ccac32bece1703014ccc2b77800ebf22c4e09fd471744f42723,2024-06-19T15:15:54.567000 -CVE-2021-47601,0,0,0a9d4a311496e8de19a5d5c979a1426d978d0b10291daba87e3e4c766d30a4b8,2024-06-19T15:15:54.670000 -CVE-2021-47602,0,0,e4574c13b0123e4010b66b76d9a44833f03b46bf8e5c09d1abd3e2705c8ea272,2024-06-19T15:15:54.760000 -CVE-2021-47603,0,0,2ad9052737362c6b5172a2abe95f90af2d8d5ffd97c7816da47ab256dadb2047,2024-06-19T15:15:54.863000 -CVE-2021-47604,0,0,bc72b30cf885dbeafd7535e63523ebff0868cb25a8e8d38f480a4e05549e0d6b,2024-06-19T15:15:54.973000 -CVE-2021-47605,0,0,7ec7ca061cca4e71e0679c949aea70d7170cec588808089067e88abddd03decc,2024-06-19T15:15:55.067000 -CVE-2021-47606,0,0,a5e1c1cd7fe01dc0b105b86ec55ab2a38b951e78149b5089b2adc353b78aa637,2024-06-19T15:15:55.153000 -CVE-2021-47607,0,0,52ab34c0feaad1601b5cfe5aa54e3ae1d1de2d58071bddaa0829129a5aeeb045,2024-06-19T15:15:55.263000 -CVE-2021-47608,0,0,8cc039d5ee1ab5c49e65d2dfe554ce96e00e3eac284c725b2be1d63afeec6d02,2024-06-19T15:15:55.360000 -CVE-2021-47609,0,0,03cf69f7c079cb1616c73477e252d0a4d7e87730e984962822f2c016d45b00d2,2024-06-19T15:15:55.457000 -CVE-2021-47610,0,0,152cd74c8bcddca2efcb72b95ed04991da184bc105f42dfebfbc52f249605cf0,2024-06-19T15:15:55.557000 -CVE-2021-47611,0,0,0ce7546358236451fca730ea48bf4015b4bd73e34e31f0c0af1b5acc823fb72c,2024-06-19T15:15:55.650000 -CVE-2021-47612,0,0,06e0ba7e76d8835532f3d09276c16e68ad04f9731d78802db0b8e8a9aa1a80e6,2024-06-19T15:15:55.750000 -CVE-2021-47613,0,0,440b155bc5e528cbfc86f311f0754e1fcc83a2837cf27d9be9e9e63280c5e4d5,2024-06-19T15:15:55.850000 -CVE-2021-47614,0,0,57fdd5a971b374efd6ca12ff9eaebc4ae1382cf48de669e8b347571bad23008b,2024-06-19T15:15:55.943000 -CVE-2021-47615,0,0,e6972818866c037db26a5c1b369f5391f820afda8212e98d624ae9e2f749949f,2024-06-19T15:15:56.030000 -CVE-2021-47616,0,0,613e0fc659a08a1fbd2d33e67d7334b1808c6952236b73a03143db70ef545f3b,2024-06-19T15:15:56.130000 -CVE-2021-47617,1,1,6a4cc525a053ed7724deb39d26fa648531dc0eff60b7caf36150ce513b8655c1,2024-06-20T11:15:54.317000 -CVE-2021-47618,1,1,a92457db77c57329a98818642a3c4c8ae8cec64ad75299e63477d87c5d954e28,2024-06-20T11:15:54.477000 -CVE-2021-47619,1,1,a587964b82f28c3f37c4aed7e2edae5cbf64b8705b16826678522954d17cce89,2024-06-20T11:15:54.560000 -CVE-2021-47620,1,1,66fde7a024dfe345b80aff0598fe94f6ddbf6b5afcdcee7d050eee6605cd5f9e,2024-06-20T11:15:54.653000 +CVE-2021-47582,0,1,2ce9440ba1c9bfa4fce1eb9f2a968e9bc20efa09fbaf77bbb876f9900c96b2c7,2024-06-20T12:43:25.663000 +CVE-2021-47583,0,1,71356b902fbeb2a7776e143f0558c2a21afa193a7877d36978558eb4ad0c8da2,2024-06-20T12:43:25.663000 +CVE-2021-47584,0,1,f95da46e379be35effbdbebd9c6dde440fb79cefcfd0cac47c33424036e8bc62,2024-06-20T12:43:25.663000 +CVE-2021-47585,0,1,bbaab35a282507692a0e9407f1122cd2043f21129de9b01fb025cb4462f32c58,2024-06-20T12:43:25.663000 +CVE-2021-47586,0,1,7bd2ad125ca602813d13a31c32d4d88514df9199698b5df7e1b5536013378fc6,2024-06-20T12:43:25.663000 +CVE-2021-47587,0,1,fa5cb28cf70ca95dc26ec4c09cc77bfd665285ce3c772fcd3808b6fd3d20fbf0,2024-06-20T12:43:25.663000 +CVE-2021-47588,0,1,c08c3b4d8b14513f30d473c1f08b7308f5086c05ad9135336496a653214077ac,2024-06-20T12:43:25.663000 +CVE-2021-47589,0,1,4149af2da59a86f91b3e41a07765832c87ebf4b81bee8efe27a599bbee03fbd4,2024-06-20T12:43:25.663000 +CVE-2021-47590,0,1,46019cde9584f97d54394fc4ee145b503d0296d0389b392c5c6223f39c8f81f1,2024-06-20T12:43:25.663000 +CVE-2021-47591,0,1,22a3295891acf003ed83637df36f0a611a83a6a728ad6afda476e618e30c986f,2024-06-20T12:43:25.663000 +CVE-2021-47592,0,1,e69d53dcf9de1614f4129a90a6185726bc2c1d70a29511d5af7055d21076c976,2024-06-20T12:43:25.663000 +CVE-2021-47593,0,1,7614c0fed2ecd23230a311cda188df3e1965ff3f59feb35abf735c03887049f5,2024-06-20T12:43:25.663000 +CVE-2021-47594,0,1,c7e9363b4434f962806801144b990c611279a29f93d2277cb9ac621baa3ec378,2024-06-20T12:43:25.663000 +CVE-2021-47595,0,1,73e61ed227b7033617a11b6a31d49a770eecaf530e54b5a99decc3177a1aa6e9,2024-06-20T12:43:25.663000 +CVE-2021-47596,0,1,54466e35fcc7b4fd918a7864adde5666ec5aa9ad2961e19bc966ec9b26d7da2a,2024-06-20T12:43:25.663000 +CVE-2021-47597,0,1,7e049faffb70c93759295f6613a586d774dbce6a2158ee8260f38de3cf69acf0,2024-06-20T12:43:25.663000 +CVE-2021-47598,0,1,7d08decb40948f6d18a07c93e51811e3c17fce48a4295245bbfa70405a018778,2024-06-20T12:43:25.663000 +CVE-2021-47599,0,1,8faba8cae4b735d55de5d89733622aad87684d523bd71e4f8fb5efb7d71e7d58,2024-06-20T12:43:25.663000 +CVE-2021-47600,0,1,c6d7e7dcdf054fe1b5b8c2fe42c086a7f37275c037307f376357a27d927a9831,2024-06-20T12:43:25.663000 +CVE-2021-47601,0,1,8c4d7c6bd3b2868e41676d60ee8fad43cf804b5f0a45c1f7b496f1559cfec485,2024-06-20T12:43:25.663000 +CVE-2021-47602,0,1,f6ce2a29a0b8d4554d22fef7e45947e51dd070204d64f8a618fbe06354ae66ad,2024-06-20T12:43:25.663000 +CVE-2021-47603,0,1,f2fe13ff0c5b88f661217b83dd4ea609ded75b67e3d565cb3efb4513c9b572e7,2024-06-20T12:43:25.663000 +CVE-2021-47604,0,1,af6ce714a1ccf981a96749ffac35eb88359f032d44e40df1924cf12020b09c8f,2024-06-20T12:43:25.663000 +CVE-2021-47605,0,1,9ee3ba2a85ed461faeaf9c596b199fc0d0c61dc6850275ec64ff29ea3b9c6230,2024-06-20T12:43:25.663000 +CVE-2021-47606,0,1,6bf505b867ddb13e6fe6e89211c8cd171fb10dae1f05e10b0a1ff6c5cc956415,2024-06-20T12:43:25.663000 +CVE-2021-47607,0,1,bd322627e14ea5b8be6fa194a30630dd4fd4c062e3444a6a7404e2b75083c222,2024-06-20T12:43:25.663000 +CVE-2021-47608,0,1,8e8fe721bed8087573bd35b85b7fe475baa9a0814dd0e243002673cd0bb32e80,2024-06-20T12:43:25.663000 +CVE-2021-47609,0,1,cb351e2182f8af4401367b049d3992adaddb8d65a99ccd4120c216f2f95d11bb,2024-06-20T12:43:25.663000 +CVE-2021-47610,0,1,d4129914d18bd88de8b29910184d54a643e40072e13d0ed0730cb009c611c487,2024-06-20T12:43:25.663000 +CVE-2021-47611,0,1,b66ad8907c4cb2d60b3e5053c399e843e54103f69104a7e9456e06c6427fd66b,2024-06-20T12:43:25.663000 +CVE-2021-47612,0,1,4e1f3d03e6c20c1854b67779c93a42fe6fd9231686f3f0049dfe838e28f89ebc,2024-06-20T12:43:25.663000 +CVE-2021-47613,0,1,bc8bba3adaea2744612e3bb876918de8cab29f2327e161762b6ca2a3bfc1a20a,2024-06-20T12:43:25.663000 +CVE-2021-47614,0,1,ed3def4cccc85a3cbb4f0669fe350e9f5fab7ef1e7c9050374510b42c7a74048,2024-06-20T12:43:25.663000 +CVE-2021-47615,0,1,1addb8f71f26916d1d224ff476cc7f6ad7554a4362c8dd703f62a1fa7cda97b8,2024-06-20T12:43:25.663000 +CVE-2021-47616,0,1,37f14c5b14baef5b576c72848fbce2540668a8a383c371c6b0c686d4539cee1b,2024-06-20T12:43:25.663000 +CVE-2021-47617,0,1,c75ea148262644d2451cc32f9ac6a576f11ecd918bf4d639f9086efef6274ed0,2024-06-20T12:43:25.663000 +CVE-2021-47618,0,1,004dbd6a5570da1020b0f1fc8155ace5bc5ad55c9e9bff794bd0575093dc19e8,2024-06-20T12:43:25.663000 +CVE-2021-47619,0,1,7075a99f4658b089c7f3d0c4c534ac3351773dda04b0f30c836651289a39c588,2024-06-20T12:43:25.663000 +CVE-2021-47620,0,1,db713823bd4c3a3e771ff08218ed032dfba438253d23ae1b17ef4540d9c59c2c,2024-06-20T12:43:25.663000 CVE-2022-0001,0,0,d8fdf66a3692474461fa30afb4569bb8513a7a0b04c6840c7e2c146df6b5709c,2024-04-09T15:15:26.797000 CVE-2022-0002,0,0,4ba989879ca817729e7cddc36d35dc20834fb13fd71d0cce189890fe2defbd53,2022-08-19T12:28:50.667000 CVE-2022-0004,0,0,49c52ff3575738b86482113493a7c3a40cb78eb0fdff68408b97beece4f065c8,2022-06-10T20:52:37.810000 @@ -192895,7 +192896,7 @@ CVE-2022-23823,0,0,543205417da41a7b23737ae28dfd6b48a01af447795df0eab749f3118890c CVE-2022-23824,0,0,ccd6ba4761e785496e815e01d778ed56a7a0aebd4af317b6ddb698ba2961992f,2024-02-04T08:15:09.267000 CVE-2022-23825,0,0,2af3a11ccdd36ac86315e3cdbef8a887a77bff7b370308e0ced38caca54e198b,2024-02-04T08:15:09.697000 CVE-2022-23827,0,0,1444b375ab1491026eb4e24244dad8d0425773cb96f57cc0c6e41e6dd6f59722,2023-11-07T03:44:19.730000 -CVE-2022-23829,0,0,128e019faa0724fc5df75d67211c49df157f895445e78ae9557338866a3c6d59,2024-06-18T19:15:56.957000 +CVE-2022-23829,0,1,8dab5325492d7a9882fbbe0746b61917c5553160656f2b1ffe7a43b7ef7eb48d,2024-06-20T12:44:01.637000 CVE-2022-2383,0,0,6a74b85765b833043c39ed7b8365ebe6a9e252a3a2869dea68d6c13221cafab9,2022-08-25T02:49:09.237000 CVE-2022-23830,0,0,70da6603b4344b03f3bd562a1c805ef75796a5f34e14c9c6b1536e6cf6362a43,2024-06-18T19:15:57.180000 CVE-2022-23831,0,0,6805afe132da57bf9f47c00f58e96b270f4475fce0826f65e9e50d7f2f489e9b,2023-11-07T03:44:19.953000 @@ -210136,7 +210137,7 @@ CVE-2022-45828,0,0,0ac26eeca266e43c3fcde13e17ae0e2dda9aa05d64c6fa4e153285331db94 CVE-2022-45829,0,0,a2e2c96a4213101118cbfac481594693b47838684fb966e14d5eedce11ed9940,2023-11-07T03:54:52.460000 CVE-2022-4583,0,0,0717c108862b8a17f76e123f61dd50261def94b340c6ad4fcde62f1e4c59859f,2023-01-03T17:57:58.537000 CVE-2022-45831,0,0,5bf1ea1a9fb07efb466a01fa61782dca0361cda3a807354097c34f25a4794539,2023-11-07T03:54:52.583000 -CVE-2022-45832,0,0,ecc92e7d19ea60cf07d3aab50b3bae46a41785fda7faa482f3bc0dee4876b08e,2024-06-19T15:15:56.223000 +CVE-2022-45832,0,1,fce313160ae8ce6f2e2b21a9946ed4bd376ace6bd670b83b3fcc374b42397273,2024-06-20T12:43:25.663000 CVE-2022-45833,0,0,ce3210fdb7e5ac590ae61ec6565c154a68f9cfc0e1c385e47b8b104ec555ef94,2022-12-08T14:47:14.997000 CVE-2022-45835,0,0,93921aa866ce04138f0b83703837a3843805d7859fc17e4ad02381d870466854,2023-11-16T21:42:28.520000 CVE-2022-45836,0,0,a0a3a245065fa220a82de090f4229c47ebedf02dc5caefdc811997129e51ba8b,2023-04-27T12:51:19.200000 @@ -212095,25 +212096,73 @@ CVE-2022-48708,0,0,b35378a7467337cab7b1eef08420fd20c82e6434d74596d1198a41e477871 CVE-2022-48709,0,0,6baa1cc0021e923f3b33081043dd7a305091b7d2d8afafa75c06c12c76f323ea,2024-05-21T16:53:56.550000 CVE-2022-4871,0,0,7274992495dd67388b392e338389fdefa8e3ed34b55ba94bae27cb8f3908886f,2024-05-17T02:17:00.160000 CVE-2022-48710,0,0,fe0ec196b9ae5f3f56372f7ec69d70930c0b30ebf7231710388167bc4a2cc6ec,2024-05-21T16:53:56.550000 -CVE-2022-48711,1,1,437bfedf93ccc6707dd66d2a73f2aa01c86f5b3cc60900eb635a56ff1b8fb994,2024-06-20T11:15:54.793000 -CVE-2022-48712,1,1,3b64a6878c99556d2e8e53df3e3fbe560123c9b9235d2d0be81373221ade16df,2024-06-20T11:15:54.880000 -CVE-2022-48713,1,1,fa6c1284746f0ff8d418439a3365df6be246ac2e056745ec75dadf6029a4d3df,2024-06-20T11:15:54.960000 -CVE-2022-48714,1,1,5832f54243f2c8c4414082f2dbd8e585d701954280f2cee014511c0c990981b9,2024-06-20T11:15:55.033000 -CVE-2022-48715,1,1,7fcf7dc38c54f89b9d6be4a75e3e3a0cd868f2fbae230c145239cc82fb11749a,2024-06-20T11:15:55.110000 -CVE-2022-48716,1,1,a314667ccf1ddd96185d9e439ee406446167e8467c58c7c9636a0c88f6814902,2024-06-20T11:15:55.207000 -CVE-2022-48717,1,1,f3c1926626a63f7d8b90d2e8783cdf40a49918a488fafb83e0667538d260dc99,2024-06-20T11:15:55.287000 -CVE-2022-48718,1,1,53dc35066ea404dcf93f0fc63cade45f4682d57233698f55434e98eacfd19e9f,2024-06-20T11:15:55.373000 -CVE-2022-48719,1,1,1c36a8e83830e4e1040d7eee7644b403859159a8bc6f32997b566312ca63c2c1,2024-06-20T11:15:55.470000 +CVE-2022-48711,0,1,f4e9873b2429e7681a6cd94493ae62279d1a7478c234665de8612a07705645df,2024-06-20T12:43:25.663000 +CVE-2022-48712,0,1,7f76c44302869b6f00ed94de5892f7f01970a82d79ccd50eee5da4bea7bc86d8,2024-06-20T12:43:25.663000 +CVE-2022-48713,0,1,e0e0549ab59879cbb734327af4fdc9f7b6dd1cd6bd79e091f961b99d45f15c0e,2024-06-20T12:43:25.663000 +CVE-2022-48714,0,1,db2f69cc1e312e4177f489724ad4fa9c96e69547444a07fce0d7dc3a499eb388,2024-06-20T12:43:25.663000 +CVE-2022-48715,0,1,a6ec305f45a9ee598bf1b4b4f7f7299343393213f1103818a96d6e9c196ae7cf,2024-06-20T12:43:25.663000 +CVE-2022-48716,0,1,ba2cb258cc1f70e325254de9984fc84cebf37c0c8041603174e7f633bd3dfd1c,2024-06-20T12:43:25.663000 +CVE-2022-48717,0,1,6910aeac97ea8633bf534a324a43bbd67a89fcdac70e84d7a71bbb491b133562,2024-06-20T12:43:25.663000 +CVE-2022-48718,0,1,88ae2a5bf302e27d45701b50405269347ec972ac17f70c3a964aa6083259d576,2024-06-20T12:43:25.663000 +CVE-2022-48719,0,1,b73c2b7473ad37217e5d14f9c429cb8ecb28d51a7f3db8c97f81f5bc54e2d8ae,2024-06-20T12:43:25.663000 CVE-2022-4872,0,0,56b13c17402299c2fa4e0cba1279535195f7b441f30ccd3fba7ade7900a2723a,2023-11-07T03:59:09.100000 -CVE-2022-48720,1,1,5355e4977fe0aabca30364968e4f6773c27b05d2f607d1765071807a2155d700,2024-06-20T11:15:55.547000 -CVE-2022-48721,1,1,affb9a56241bf14c4a2e76d875def26a80d3bf7fe26fd7f7b5962f6dcc1ed0d6,2024-06-20T11:15:55.620000 -CVE-2022-48722,1,1,301c149709267b18d6a69a788abdf48c64545944c994bfb3e7ce5c8a236d2b3d,2024-06-20T11:15:55.733000 -CVE-2022-48723,1,1,402f89299bed574bf0f7166b0c6a56854c8a51670cc02ba25a437096b01cbeb7,2024-06-20T11:15:55.820000 +CVE-2022-48720,0,1,86756482c12f5ceb7b3cdb8085037f3204a541f40838287baf071171cbb21758,2024-06-20T12:43:25.663000 +CVE-2022-48721,0,1,061b50fa1038dbbfb042dc3ee9438cf10a67e7fff91c7b47d78ad354eb5e825b,2024-06-20T12:43:25.663000 +CVE-2022-48722,0,1,489bec40085ce454bc0452dac5ed29c096b0ec77f081b344b0c5bdbf9d7680c8,2024-06-20T12:43:25.663000 +CVE-2022-48723,0,1,a2c62823835d5292cf2bd42b61101a88411e6034a74afb3c9983bd6e8889957b,2024-06-20T12:43:25.663000 +CVE-2022-48724,1,1,f60aee937a903f4f13d47737e5ff24c2d7519059a629208c53503294040cbe61,2024-06-20T12:43:25.663000 +CVE-2022-48725,1,1,c6960aeabc3e7948fa2b8dfe13703f5ff3d303726e41701ad5ef41986fd7f920,2024-06-20T12:43:25.663000 +CVE-2022-48726,1,1,6337f282af23dc7cf4364b2d71476e93241a193c9b21f54b264d9b8b38b3bd1a,2024-06-20T12:43:25.663000 +CVE-2022-48727,1,1,4c6d5fa1863754a5723a42f5fb8faefb542d382881ce540d08e41b1ef5fcc746,2024-06-20T12:43:25.663000 +CVE-2022-48728,1,1,3affb9a9805bdd25a7156c0310564b8e1ab2e05afb18c2553aa16452d43f3e64,2024-06-20T12:43:25.663000 +CVE-2022-48729,1,1,d4eb61f64c4c5da71e7aa8fdbed39b719900d6f9b0f030fe7fd1d7bf7b3936b4,2024-06-20T12:43:25.663000 CVE-2022-4873,0,0,563a199763d37b536a31c01788923286fc1b28eed585d04a99495c2e08b4d4db,2023-11-07T03:59:09.310000 +CVE-2022-48730,1,1,25b2af5a963551f6596039a5096d90bb24678bad12a71416dd890fa111bdf28d,2024-06-20T12:43:25.663000 +CVE-2022-48731,1,1,1c32f8b3384cb7bedc404e9005f479f8c520809ccb664096f0692b79b7bf0790,2024-06-20T12:43:25.663000 +CVE-2022-48732,1,1,a9d4a4f5984607762d30c6895e79cf620b0b37499121d70344e06aff81126931,2024-06-20T12:43:25.663000 +CVE-2022-48733,1,1,0961f1ee379590392e13f692644ecdf8e86b70e8294c57f9d69509799c830a92,2024-06-20T12:43:25.663000 +CVE-2022-48734,1,1,410ac40cde5ea83225f6df7239839dbbba13359e0c1cdcaa00328abff5cd0860,2024-06-20T12:43:25.663000 +CVE-2022-48735,1,1,38123e18773427d4b2743f4dab98d36825a131341650151e394fc37cb2a5ba3d,2024-06-20T12:43:25.663000 +CVE-2022-48736,1,1,ee49716c40468d7d5d7138c89f94edeec4ee0849e5b37595e0282a435b91787d,2024-06-20T12:43:25.663000 +CVE-2022-48737,1,1,0c92627e1e3d48e57566517ec8438a4e13707a2c370f8a39c709308dec02dca9,2024-06-20T12:43:25.663000 +CVE-2022-48738,1,1,b8253a7cf38cc1862912a6bb21627b8f7c0bdc327005a4e407e135cb227b651e,2024-06-20T12:43:25.663000 +CVE-2022-48739,1,1,bcdc582d0f8e6bdb336b784c1034abfab8d23293788f50a02490d94b7f49935b,2024-06-20T12:43:25.663000 CVE-2022-4874,0,0,11bc171fda6fc861e0708d150c2ec522d2356e3420b85bbff8eb41cec9dc83eb,2023-11-07T03:59:09.523000 +CVE-2022-48740,1,1,ae1cf3cddf159ffe81e770691c5781bcb4c58f8dc33cc121912f0f2c9902d8de,2024-06-20T12:43:25.663000 +CVE-2022-48741,1,1,346b915984fe755d6e3867f148c9ef642b32cc987f98644517e3015af6f4b950,2024-06-20T12:43:25.663000 +CVE-2022-48742,1,1,ebf0d4c1c05d6865f2ee5e1324931debdbedaab9f855a23a268609342b499300,2024-06-20T12:43:25.663000 +CVE-2022-48743,1,1,224e8eecd97805b2f9ed3a1a7a106c45f401d3117d0f950c673ae6520cc3fd91,2024-06-20T12:43:25.663000 +CVE-2022-48744,1,1,d2c05955465e3b8e9415925d07607f60549adac7e3d69c42ff9aca7a08f31833,2024-06-20T12:43:25.663000 +CVE-2022-48745,1,1,fc8f7e9be39a16e544db23aa6e671605c0afa8849222ec4f65ef1ab4b57e6ef6,2024-06-20T12:43:25.663000 +CVE-2022-48746,1,1,4c2c8a0183eaa1f7e85f6d29e59aac11b767fc453d74f18ef197b869b8276657,2024-06-20T12:43:25.663000 +CVE-2022-48747,1,1,282a49a9c34b5f4731795689579b98650d519d40e42eaedb4f8f848134106aa4,2024-06-20T12:43:25.663000 +CVE-2022-48748,1,1,4532e8ccdca0ff0b39a222470540fed238d7867797e2fccef2fbc88ef0cf7465,2024-06-20T12:43:25.663000 +CVE-2022-48749,1,1,761352292034513a5608df0f864268c681cfef00532bb0c89c6c6daca4c3cf0a,2024-06-20T12:43:25.663000 CVE-2022-4875,0,0,17c44f8ed61133d49317ef236aeaa7add57a954975b984861ea8fa8f275ad9d2,2024-05-17T02:17:00.353000 +CVE-2022-48750,1,1,36c18a6254e7b61145a8485b80dc6b53669ace1e353c5efaba0b163acd8d0a30,2024-06-20T12:43:25.663000 +CVE-2022-48751,1,1,ccbe45a6f46ea478f6d2103d0c462b7b927be5c05a337aad0597f6ed69e6258f,2024-06-20T12:43:25.663000 +CVE-2022-48752,1,1,9d9a185802f3eb156cd507d10d389a1da8eb659638fb3fdf21cc2b4309cd38b5,2024-06-20T12:43:25.663000 +CVE-2022-48753,1,1,a394b42b6cf3cc352557e3c8140aa4d7c71463c650867404c296d9fb853db470,2024-06-20T12:43:25.663000 +CVE-2022-48754,1,1,337f3449be64113aaf24de412d4655db674450d28f7fcca4bbf2e4f2d29c93e6,2024-06-20T12:43:25.663000 +CVE-2022-48755,1,1,e043097107c305ab62672804380f87fe8e1823a16a03476e7a3b134acdab4e4b,2024-06-20T12:43:25.663000 +CVE-2022-48756,1,1,106be3f391c228d430dde34032e5497a387c6774288b1de150fa82711b5332d1,2024-06-20T12:43:25.663000 +CVE-2022-48757,1,1,14bc9d85b6d03c1c26df1d21dd635873063f0f4981d5674745a75becadb9420b,2024-06-20T12:43:25.663000 +CVE-2022-48758,1,1,8e9439eef26e99683aa8ef637d1df2b97f04a51944af5867b592609c8d1f6a8f,2024-06-20T12:43:25.663000 +CVE-2022-48759,1,1,6f5acb09cb5d8c130e18eb258f2888ddba89c8f2ce34c26a9097aaa875335b9b,2024-06-20T12:43:25.663000 CVE-2022-4876,0,0,f22defc481c82d0ef8aa9b99337c513083691d5b26717971a48e0daed3671d7d,2024-05-17T02:17:00.467000 +CVE-2022-48760,1,1,35a382c887535f06ed4b0f44a39f0b4fcd801f99ddee52a67d9923a3380d30a7,2024-06-20T12:43:25.663000 +CVE-2022-48761,1,1,47201253d6e5eb2e1d9700e4c6bb415a80ca7686e6d9c32590ee526c730807b7,2024-06-20T12:43:25.663000 +CVE-2022-48762,1,1,b93e233bd1dee47aa734aecf960c6634e3a106130fd1ec168defc0f44e4d8063,2024-06-20T12:43:25.663000 +CVE-2022-48763,1,1,bcd35ffa8dae062f1c8cb4af1864513b281461fe4310c0b2b732dadf855ce794,2024-06-20T12:43:25.663000 +CVE-2022-48764,1,1,99658f93faf14a16fc5b015d0dccac376bfbdbfdaea6b04b9b969126f896c1c1,2024-06-20T12:43:25.663000 +CVE-2022-48765,1,1,8229f32d622e7ba39615da31a4e14b0965ef73ec5cada4738af5d688d4d14794,2024-06-20T12:43:25.663000 +CVE-2022-48766,1,1,a4f5e0ef6d893f2769f6bdf16637a1ee2dc6aa56561610ced3bfb4d2e5229683,2024-06-20T12:43:25.663000 +CVE-2022-48767,1,1,cc9a5bb61bae55195a1c204317f2caa0ace88b7acfd745a88717b8bde9533e14,2024-06-20T12:43:25.663000 +CVE-2022-48768,1,1,d459f886cfa8819e4350955d9ed38ea7ecbf5d5800186dede3f35eb656fd270d,2024-06-20T12:43:25.663000 +CVE-2022-48769,1,1,27b5120a87877ba853c1455f914c416ae47403f4b6d090dbd219594e5b8fafb9,2024-06-20T12:43:25.663000 CVE-2022-4877,0,0,f2130ce984ecc4a7ab39ad237fb93ed91ee6583213d9752d5a3b6539de11f505,2024-05-17T02:17:00.577000 +CVE-2022-48770,1,1,52d395c3ce3348def67b3c2809ebc128aea32b0caddb38d5ae355145904c04e7,2024-06-20T12:43:25.663000 +CVE-2022-48771,1,1,c1ee1a730f7494234f4416c7d25e97319c057b5255e732e344bf5b1ef1c45f34,2024-06-20T12:43:25.663000 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 @@ -218750,7 +218799,7 @@ CVE-2023-25642,0,0,54cd3d92e51620fed76245134bc60afc7ae3e51e41fa4d6885ef8ef3472c8 CVE-2023-25643,0,0,6662e13f25246c83f148ea47e66b39f4bc11afce3dc84d7bc5d608fa8055f158,2023-12-18T20:09:13.630000 CVE-2023-25644,0,0,52583b69aeb656c73951a90f18c2035417d95e92cacdcefce04a1a56e3b20ff8,2023-12-18T20:08:39.477000 CVE-2023-25645,0,0,9cc2e48dedbeb9a73ae5d33a7b379d30567e4edf38b0cfb37087eb2bd6ba43a6,2023-06-26T22:19:11.390000 -CVE-2023-25646,0,0,0a90e80f06d479da65164144e1bda8d0bf9fd2057032fcd8540359018ed233b7,2024-06-20T07:15:41.340000 +CVE-2023-25646,0,1,e8fcb0f8a3ed94a7fff283cbf83fc68b5ab4d2acc3335024cabb9b1a5214549a,2024-06-20T12:43:25.663000 CVE-2023-25647,0,0,4c06370cd769277d2f1f2a309d8262dd5189ad19b7b62c9c9e0a79a6d67ec360,2023-08-24T16:20:12.140000 CVE-2023-25648,0,0,6b8f2a5d4f2290c9906f74dab886ae48b0efc0769734b2e0d0a39bf46259d5d1,2023-12-19T19:25:23.710000 CVE-2023-25649,0,0,7fdca89abb02c0a04c1a8d8d1c0be240d887fa7c73c6b501606d77250afdc458,2023-08-31T16:22:56.523000 @@ -218802,7 +218851,7 @@ CVE-2023-25693,0,0,10cd608fed2e9e6e440c687d4ef96717f4cda5e6a7df0e1af342a026a4c74 CVE-2023-25694,0,0,464fbfa1d242a161fe16a05493e4128187914fbebbfb66670b87d547dab2aa3e,2023-11-07T04:09:07.633000 CVE-2023-25695,0,0,805cd0fad03b555a8d2a5cc86a4d7b464432242abc01326d0bcaf21acbc7c9f0,2023-11-07T04:09:08.003000 CVE-2023-25696,0,0,1bb1165e4898e93d7416616267d6610e54960f7875002590c410faf3219754d8,2023-11-07T04:09:08.073000 -CVE-2023-25697,0,0,faa2455a58d11e86ea0ee126a623f876fa600f84073632edba31e4ad2e99e338,2024-06-19T15:15:56.513000 +CVE-2023-25697,0,1,a1632c14680b55cd04a6a1632fb23434faed93d45acfe21b741ab6ca592bb246,2024-06-20T12:43:25.663000 CVE-2023-25698,0,0,e56b7d935093bd493ce30761a0a46812c945e926647573c5d416569d592987ee,2023-05-25T16:27:29.670000 CVE-2023-25699,0,0,69ad2c3d02852f2448b1d027ab440c5fe2e8c73f73f1fb38c5427e091c552fe0,2024-04-03T17:24:18.150000 CVE-2023-2570,0,0,8663252ec671c3b7a42e9d7664ba3c00e3ca93661a5d1c12b4a7aea331483c3b,2023-06-21T21:03:56.260000 @@ -223621,7 +223670,7 @@ CVE-2023-32035,0,0,f9817d32cead9a5ff84a9ea55b3d6f38d1338b8f97fa149fd6e8271fd0147 CVE-2023-32037,0,0,5812c20945775e76d4c23f4f209d094253668c628184a75a4434c38317c5a314,2024-05-29T03:15:40.027000 CVE-2023-32038,0,0,de6d98a0b125713c23a8b3afa233e1e74ff95a0fd20d416693aa965e8d6abfcd,2024-05-29T03:15:40.210000 CVE-2023-32039,0,0,9b411f39ff333ad234f11449bd59a0cfe751618de7aa8a63af2d3143b02135d5,2024-05-29T03:15:40.413000 -CVE-2023-3204,0,0,ab4c1a4387e947ba69afd56664e48bb9797efbfb1be3a2ee16b53bb32ac39a49,2024-06-20T02:15:09.147000 +CVE-2023-3204,0,1,4b2137aec9ddb3ee366bbbac1711fc4f49f6b7dae4a85d785e8925642b431afa,2024-06-20T12:43:25.663000 CVE-2023-32040,0,0,dc7d053c3177127d571a31983f41f8acd819b60e1d358a856abddc6682d6927e,2024-05-29T03:15:40.580000 CVE-2023-32041,0,0,ad091a32826d0af26a7c8fabf43d50cb6532b1a9ff516f399d08d56d750de3b0,2024-05-29T03:15:40.770000 CVE-2023-32042,0,0,4bcb20c5e1a80a7bd4085078de801bc55a175e599f7c46a0788dd056524f905f,2024-05-29T03:15:41.073000 @@ -225978,9 +226027,9 @@ CVE-2023-35044,0,0,45f40e6694e87ced74b4deadebb9273be310310ac0e25d08dc42d598488e5 CVE-2023-35045,0,0,3e0898030a2ca96054a5df91444ec92a3f690fd05e2b3fb35d819fabf05ecb66,2024-06-17T12:43:31.090000 CVE-2023-35047,0,0,fe258d6ee26c0233b2874679788145dd4bac851e1c7fa70cf5bc84fadfb5902f,2023-07-18T18:21:45.713000 CVE-2023-35048,0,0,02fe97c0093e1429567a43693606b005b52f707cb13aeaf4d21f056707a3b606,2023-06-28T07:24:45.533000 -CVE-2023-35049,0,0,415335f883852864836437a0122dc0b83062f4c375ddf49001988a0b9374129c,2024-06-19T13:15:52.287000 +CVE-2023-35049,0,1,5f8f7db41f16cc359c592622a9ab751a212b9aa2188f29a73f9b6ca6ba31aacd,2024-06-20T12:44:01.637000 CVE-2023-3505,0,0,bb7ccef8f4e641467252849d80f7cc74c51a53533d6b1dc48cac00a4fe605528,2024-05-17T02:27:32.733000 -CVE-2023-35050,0,0,3aadfe28590616c1a43d85f89cae08fdbda13408f8368f778494949559074599,2024-06-19T13:15:52.600000 +CVE-2023-35050,0,1,078413ca3d09be1e6cf7fbc4d4708743ad806eaab64bdf4ccfe0cffea5f8eac3,2024-06-20T12:44:01.637000 CVE-2023-35053,0,0,fa117709b8b0a3319db6b9d5ce8991c4b2f96594544c75bfe0f563df5f5ae04c,2023-06-16T18:35:52.327000 CVE-2023-35054,0,0,6ea2e3d4dae37d0ba3feac710d37275483a443ef6c7e7e24276cdefc65530ceb,2023-06-16T18:36:30.947000 CVE-2023-35055,0,0,a34093fdd4506cfcec353abaebf1b9fea4aa8c8b0870507dcf07f15db18e3f52,2023-10-12T22:47:39.863000 @@ -226937,11 +226986,11 @@ CVE-2023-36507,0,0,29af67b33727cb340afdb79364b7fbb36daaca24d9a8770d1fda55dfa024a CVE-2023-36508,0,0,6a82ccd114f0b0b6a677dcb4ee79ade31dd64cf63b48057227930f2fe1db578f,2023-11-08T18:47:51.157000 CVE-2023-3651,0,0,00dc1b21ce394780de31ec43237c48e6a900f7c85fd3660a516d41c5ebdf2ced,2023-08-15T00:20:26.703000 CVE-2023-36511,0,0,3d1348cfdaf9d07719f33c9e556d55ecb3502e0c156b199144fba62410afab9d,2023-07-27T03:48:59.503000 -CVE-2023-36512,0,0,ee34496fb502c4d0a1e4145300ad504e3064c9eb6e57657c62c73b2d9a7fce69,2024-06-19T13:15:52.893000 +CVE-2023-36512,0,1,1627e361cae1074a212194fee2bde8798734cbae52fde791e7466457bece4109,2024-06-20T12:44:01.637000 CVE-2023-36513,0,0,51598f21ede69a971d1f95df698e21e169619da78593d0591e76e21b0cefb65d,2023-07-27T03:46:51.797000 CVE-2023-36514,0,0,d6e99b34cf850003e62aa2cd7a43a30ce011f371e25280dcc8826b7c1ad83e3a,2023-07-27T03:47:07.827000 -CVE-2023-36515,0,0,645a52bf8abb6fb3f4190f5fa2e6f4b58d57ad8bcafbf4ec49fcd08aeb109edd,2024-06-19T15:15:56.847000 -CVE-2023-36516,0,0,3a0559844943057f3246efbc17f02eb82e27d47c3f952fc50b6d37b51a81c7e2,2024-06-19T15:15:57.133000 +CVE-2023-36515,0,1,c7ba28cc7b1dc363c1c15737fbc873bdfd92377e98a60b8d5706c9736670c138,2024-06-20T12:43:25.663000 +CVE-2023-36516,0,1,80d8cbab73721395a5dcf7857f77f28be411bb087b4321f6cfd1e58d0d84b477,2024-06-20T12:43:25.663000 CVE-2023-36517,0,0,d3fb4f6ec9cfd59946d7bd8e1222a2901d7c1e37c450eee02a4394ed7bcad366,2023-07-18T15:57:59.233000 CVE-2023-3652,0,0,fafd49efb9094f945fb261cf514df28216606a420f77434ee91077f2b777c2d7,2023-08-15T00:23:23.923000 CVE-2023-36520,0,0,9979adb56a94ad064e1777a896a1d11c5a6eae27de6a4fa16498385e0ea0c3bf,2023-12-28T20:18:22.997000 @@ -227087,14 +227136,14 @@ CVE-2023-36672,0,0,ef7babe93497c23b650a4a832ce992d12e9928fdd3aeaeb154672f42f32ff CVE-2023-36673,0,0,332d850bf4edd394544e69b255d65e3121ed55281ce36b65bc370c19b97542eb,2023-10-31T09:15:08.337000 CVE-2023-36674,0,0,037c0f4f8e0421fbf60f517b960991d5db75e9a7a959de6ad2198427b5ac0421,2023-11-07T04:16:41.150000 CVE-2023-36675,0,0,ef783a7579e6012c2ebc6fc64eaba660a4b8768812f41b1c9c2bad33fe1c8a8e,2023-11-07T04:16:42.083000 -CVE-2023-36676,0,0,17fd48cee25d2901400130155e1105b9ca95040b881cb2dcfaa152baacfe67bb,2024-06-19T14:15:11.867000 +CVE-2023-36676,0,1,03bf6f5ad3eca7d5851e4fd95b03c40426de341c36699ebb5ced169876b77031,2024-06-20T12:44:01.637000 CVE-2023-36677,0,0,5dc376964c9be5b3c855d9a3ee454c31d832734cef7300cda71cef8e44b5bbd4,2023-11-09T20:31:09.167000 CVE-2023-36678,0,0,dccb2309cc1666cfa17ba7895c8a8afb4ad464318bd565abdb02e0315d5b72ff,2023-08-09T16:25:04.920000 CVE-2023-36679,0,0,1c4c7fe6224269b649e68919a16fb4fe28ac83f214ee8df5dbe68585f6236b95,2024-03-28T12:42:56.150000 CVE-2023-3668,0,0,2f69278a5e0e75a6f4eded7459b4fc4e72af610cebaa3a1e009861b8db796613,2023-07-27T12:17:44.780000 CVE-2023-36682,0,0,950c7203a686ef8c30c2f969ba98adf910b90a0726d776fb7d9d586837292a56,2023-12-05T19:57:34.747000 -CVE-2023-36683,0,0,427efe65dd0f5aca64d840da22a3031193a87e6c4966fd42d84999de48abcd22,2024-06-19T14:15:12.137000 -CVE-2023-36684,0,0,a086fec9231fd0dda0e97eaa80609ea102b5f784ef05e35da0dd695858159d58,2024-06-19T14:15:12.380000 +CVE-2023-36683,0,1,adeabcbda0cea3c81999ad1152ba7712cfd8c34d3d767ed3b2ce76eb2a9900b7,2024-06-20T12:44:01.637000 +CVE-2023-36684,0,1,9dbf3dc783192490dcc95f61811b70e0470f306376b2b391e4b29a25b8e812e6,2024-06-20T12:44:01.637000 CVE-2023-36685,0,0,4fcfd1d410431355a7ddaa6f00e3c4e8b3302d440b3477251b93474ca31fbdbb,2023-12-05T20:44:13.570000 CVE-2023-36686,0,0,fd421ae4d279aff60804cb36f471f2a34c49cec2319f4e52f3ac3e31d28f76c5,2023-08-09T18:01:02.050000 CVE-2023-36687,0,0,524f73e45d06e76b95c2e25fe13e81ccfa4350a4f0bdc1625b37eee106114daf,2023-07-18T18:21:13.220000 @@ -227368,8 +227417,8 @@ CVE-2023-3703,0,0,76f02181cf5d80b7f612caff5073f455db91d34ac29ea7817245c12bf8efc7 CVE-2023-3704,0,0,0b7c69bc28e7afdd5dcf10d8a79e926f269c85852f7d6befc01c8a1d3a76f806,2023-09-01T17:12:08.027000 CVE-2023-37049,0,0,4a710d2494270e65f82c9c7a56bded47f634b44df6e778149a2d19ec0778c27d,2023-07-31T18:12:44.960000 CVE-2023-3705,0,0,8c79d499f4e32027bc4150fd363eda1f383550d9e90e93d841777af54adc58f7,2023-08-31T00:37:27.440000 -CVE-2023-37057,0,0,58de6d15bbd15b1584a74442f183982523f5d7e7982a5eba81571241c832f712,2024-06-17T21:15:50.380000 -CVE-2023-37058,0,0,cefa1996e1157324212d1dd6d54dbf4556fbe37ae2ff2cba33a7cf48cdc49924,2024-06-17T21:15:50.503000 +CVE-2023-37057,0,1,cd023ee94b75134222ab5c4bb1044768463ceb0a498cd67c1403064feed0ed55,2024-06-20T12:44:22.977000 +CVE-2023-37058,0,1,636eb2ae68c7933ac1c46d0381f4bf470e2c04a0a3fd6f1a4e0652ebcf077f8e,2024-06-20T12:44:22.977000 CVE-2023-3706,0,0,d1d24339f524babb3c5d468291861ac849afd345e41ad883606273b20a797f16,2023-11-07T04:19:25.570000 CVE-2023-37061,0,0,7caa8b5c6907e4b61cbed31197e8664c90d669fbc2f478d5af9b346f52feb24b,2023-07-12T20:58:22.373000 CVE-2023-37062,0,0,915c2f5b9c7526d6273035bd201fe818387382f5f9119c439e8c7256d48d5151,2023-07-12T20:50:55.603000 @@ -227963,11 +228012,11 @@ CVE-2023-37865,0,0,7808da64efc63821bbc221aebad88e1b25561871a0b7fb2ea12990cc7a375 CVE-2023-37866,0,0,426d941681477d72dba31cb1af5d0017cbfdc7b4ed2b5bcac4188ace27277b6b,2024-05-17T18:36:05.263000 CVE-2023-37867,0,0,5b40f88535a21a5fc1741e0bf848180b66100f4c8511a8360b3352760b2647b2,2023-12-05T19:42:52.137000 CVE-2023-37868,0,0,3dca24f48f5ab0c03afb5b3ef0954996b6ef75d5ce37dfa7001aa80a5f36ec9f,2023-12-05T22:24:37.173000 -CVE-2023-37869,0,0,e4559e919562aed8e201f7b6daa3f9362e6a02d850732ee1d117d78d94bc3a3f,2024-06-19T14:15:12.617000 +CVE-2023-37869,0,1,c49ae145ebf8f053ed9a1fd9c26b9216ee163f2857f3621fb4d81040ef0d5082,2024-06-20T12:44:01.637000 CVE-2023-3787,0,0,2fe735f6094dd23347385a4409bf18497974a7329e90c23a0f88e563720410e2,2024-05-17T02:27:47.670000 -CVE-2023-37870,0,0,9ffc2ea886de47df6e8d61e4737aad6eb275b46f58047f9a68086cde5e458e83,2024-06-19T13:15:53.163000 +CVE-2023-37870,0,1,ebb5d7a54d8a644e0d3849951b7dcbc840497599f3e2db4f2c1c87511d1073cd,2024-06-20T12:44:01.637000 CVE-2023-37871,0,0,4932a65d4ba8ab90a315798cbe7c320caa4014febc8ff5e37d43893207d278a5,2023-12-28T20:01:03.433000 -CVE-2023-37872,0,0,e14e2e8d7cd4c84454b97f12c68f3fdf63fc8406dc1dc5abc02b1913dcc5781b,2024-06-19T14:15:12.853000 +CVE-2023-37872,0,1,4e24eb7469e3d80fd344b45264dda6160ddef0a12c5a02e177f5e749bea5623a,2024-06-20T12:44:01.637000 CVE-2023-37873,0,0,4e198482f7aaad698302c7eb8e2cc05de5942e2b3c717373ac245778acbaf7c1,2023-08-09T16:24:22.127000 CVE-2023-37874,0,0,17996ec7a8c0fe208a2fbc0054bb1dc196238e7df6f997e6fc1b3130216fb25a,2023-08-09T16:22:20.317000 CVE-2023-37875,0,0,a2a07a96902f43f7bcd09ed9a486e735eaea5eb937e4f93d7b2bd7e20e48e086,2023-09-14T18:32:08.477000 @@ -228435,15 +228484,15 @@ CVE-2023-38380,0,0,edb3d0fa0dd181ca6ebfed37566e0ba2696ff1b9252d5924c6f5dc2a96634 CVE-2023-38381,0,0,580e87b333e058d175503c85ff5b2c721d6b8ea39eca9d994a48ef8de7325d1d,2023-10-04T19:53:28.377000 CVE-2023-38382,0,0,95233def5985e85c0df5206014d24c06949c4b4bc39503e9f9d91f0c02293126,2023-11-10T04:19:37.937000 CVE-2023-38384,0,0,54f2c7b3d2818effaffa8b8e84e243e8a49ddce49dfea166f8b7f7dfa5cc206c,2023-08-10T03:49:13.217000 -CVE-2023-38386,0,0,c012702bab6dcbf5187c6361e36abff85c35c138cdf704994a47498a3f7368fd,2024-06-19T13:15:53.440000 +CVE-2023-38386,0,1,aaae6685ce584abebd33b1f049d0c1581b4aef9e84b8c60a1d7578f2dd26a7ee,2024-06-20T12:44:01.637000 CVE-2023-38387,0,0,18b9581624e43501a4cb80726cbad939a2ac6adef341936b040bdb0338ce921d,2023-09-08T14:39:10.543000 CVE-2023-38388,0,0,a65eaf4e5dca56ffeb23eee28b5715af13e19c46768ad084c3f42d56caf3d77f,2024-03-27T12:29:30.307000 CVE-2023-3839,0,0,5ff9aa1532a46eccdb92ce1ebbb2619dbcddface6d60c3cddbbbed157e6b500e,2024-05-17T02:27:52.343000 CVE-2023-38390,0,0,a8ddb08e6640474b7c20c14af215057166b935398c10611e08cf7ad2b1521ce6,2023-10-04T19:58:33.723000 CVE-2023-38391,0,0,344147f660134030bcbbaa890dae6516b557e6ede35f44154d334296e9591473,2023-11-09T20:07:33.613000 CVE-2023-38392,0,0,7efefe02027d57cb14a0cfe9309a9a9ee4f710dcb294c8b4a9368d9d3b173021,2023-08-09T18:01:11.383000 -CVE-2023-38393,0,0,350400d1d06f0acd852c90cfd7d5f9e6786f2141b5bf821432d381d91bf3f97a,2024-06-19T15:15:57.420000 -CVE-2023-38394,0,0,ad077fb2250f264f948c642628665d8b213b664296dc1a7f84510f5aa2cd156e,2024-06-19T15:15:57.710000 +CVE-2023-38393,0,1,9c72acca6d1a49bd78fe1970f6857693d9857c1788fb08f9adbfb7238bd5366f,2024-06-20T12:43:25.663000 +CVE-2023-38394,0,1,a0733141b01a25e83f8ea8637cac93c922eef77dc235dc9f8237961672d96e82,2024-06-20T12:43:25.663000 CVE-2023-38395,0,0,88c0100c2bef76697d17833db410c8784defa8193b1b2a48a188de7572d988b8,2024-06-13T18:36:09.010000 CVE-2023-38396,0,0,6f57eebc70de82e5a15efc514f000a4b45edbd824e1f80d31df289d03d664799,2023-10-04T19:58:23.093000 CVE-2023-38397,0,0,9812e0124da566ab9c4e149579bbf6e7b3020263ad5728b0e6e7a41e1f24c128,2023-08-15T13:31:29.753000 @@ -229169,9 +229218,9 @@ CVE-2023-39306,0,0,6fdea6e755ad3c897f08918d9c1d51ddc69d961346f27f39c6f47d3188ca8 CVE-2023-39307,0,0,7acef3cec93184c51474f9c31e2a1c837088af3bbc58f21a5e50dcf1d40254e9,2024-03-27T12:29:30.307000 CVE-2023-39308,0,0,0a6368135905c51e4bfc8658e86115693ae2beb292d59faa84b5dcfe3424348f,2023-10-02T19:36:52.837000 CVE-2023-39309,0,0,776d200f69f611571cece78c512f425a9f8dd72edf61eebb304dc1c432652d31,2024-03-28T12:42:56.150000 -CVE-2023-39310,0,0,93b9075bda2fc7595605de4cafe1b99ed77649ac3b7510381ab2aa5c979b480f,2024-06-19T14:15:13.100000 +CVE-2023-39310,0,1,66e4583f9f6fb3502012ed493583896f1bd82b9de792512e6925ffb5f1a64c5b,2024-06-20T12:44:01.637000 CVE-2023-39311,0,0,35b98bd091be9b4292392bddd965647b3fc75e1122944a9a0eb1d1fb42675d02,2024-03-27T15:49:41.437000 -CVE-2023-39312,0,0,654aa2d71308baa46b83db9c5483a71fe5e31d0899066e30ea25e728af16b485,2024-06-19T15:15:58.020000 +CVE-2023-39312,0,1,9a3a1444fca5d771049f885e19f1b89d1d868303bddd2dfe5d1a4a8b82266ecf,2024-06-20T12:43:25.663000 CVE-2023-39313,0,0,86939a25b53e6bb018a0256d87a7dad3e18b77d3660d1f63d82e3c7b7810614e,2024-03-28T12:42:56.150000 CVE-2023-39314,0,0,ea740e75552d6dc1c0cf1f6c4b3f96de5bf219ab1a6cac778aaf3dfb58fa2dc3,2023-08-15T00:14:54.643000 CVE-2023-39316,0,0,417d7dff8ab68b3fe9ff8334ccfc3e9c0c5bd2443eb2c38c70d45524e9296788,2024-04-09T21:15:15.350000 @@ -229590,7 +229639,7 @@ CVE-2023-39918,0,0,d88deb02ff7f439bf3e0bfb3e7a92f394a111cd023c5544039e6158c862f5 CVE-2023-39919,0,0,d7fe9b154c690aa5082f08104d08f1845c941ef61be197c404249df501c1686b,2023-09-06T22:25:35.907000 CVE-2023-3992,0,0,fe4298680658618fb7caf316a4f18a0291464ffc626e1d0cb092abb0f373c12c,2023-11-07T04:20:05.730000 CVE-2023-39921,0,0,1611a99c67962c018d6b1fee5fb13ad22dbfebee693e5a122d7c57a8053f2c24,2023-12-06T00:40:06.827000 -CVE-2023-39922,0,0,61b2d77e699952aae85eaa8fd8f1a2347ecb57b54219173760c9438f3457e70c,2024-06-19T13:15:53.700000 +CVE-2023-39922,0,1,9cff80590d1efec73731ab622ca7ac6b233a015b16eb8d0e628954af2a66dc23,2024-06-20T12:44:01.637000 CVE-2023-39923,0,0,6b48aedd4dddb610ced99c309f04ee370eecaf7f5cc8d964ba2411a2576db718,2023-10-05T15:50:28.930000 CVE-2023-39924,0,0,412b3d116668f2a8f11b4bfb79e1523804fb2580a1b51a02b5a0cabfc9df8dfd,2023-10-31T18:11:01.040000 CVE-2023-39925,0,0,5279f6a46ae1cece069d87ad5fcbf8c6a733679f5cae33522f5279279031045c,2023-11-27T21:37:20.403000 @@ -229658,16 +229707,16 @@ CVE-2023-39987,0,0,338865d9620cb667158779ee18ddd612f499e5842029b2f7342cf8aaf84e1 CVE-2023-39988,0,0,a66fbdcab65ea27ed84a033de7e90af2e53857a5af0bd25d098af11215a8e33b,2023-11-07T04:17:44.050000 CVE-2023-39989,0,0,558d5a69f0e96ea9472d20fe19e0c75c24de7a5fc408983ff6ead4de194ee4dc,2023-10-05T16:22:06.307000 CVE-2023-3999,0,0,e956e4531a12f134c42307f8770cea5b99de3c2ae9b6c40e4e02de23b59ca80a,2023-11-07T04:20:06.417000 -CVE-2023-39990,0,0,3a3aefe908acd8d81995d9ba9d44083da1e45efc1003b6ccd35899b0b2179781,2024-06-19T13:15:54.157000 +CVE-2023-39990,0,1,c1313bbf1d356c9572f36ba2bfeb6b1bb5112047fcc436dc4507b4faaf7ada02,2024-06-20T12:44:01.637000 CVE-2023-39991,0,0,0340b8efa37bc605092d9c1759b9c813cca0680f0f84b2ea2bf227d0125a7656,2023-09-08T14:05:34.107000 CVE-2023-39992,0,0,fcaf02bda213dd1f17ad161f01bd711a5d2c373d3063a8bcb7d8975ad8f37032,2023-09-06T22:32:25.333000 -CVE-2023-39993,0,0,5be2e4031ff17c989188b303d808d372ef8461824d3e62a6032b112105810f84,2024-06-19T13:15:54.400000 -CVE-2023-39998,0,0,b599782a6614a9a65a7916fe71a329ac589c5536bba7bb72bfd44520b87ad767,2024-06-19T13:15:54.633000 +CVE-2023-39993,0,1,06c5df2569dbc6851a31849ec7f40221e3a1a156de6b9d32d25c9f7a75c03fc0,2024-06-20T12:44:01.637000 +CVE-2023-39998,0,1,8e1f35fb388823000afb4a9d1160d57a9e3477e1f28147ccdca19cbd07d67849,2024-06-20T12:44:01.637000 CVE-2023-39999,0,0,7f36dc8514fc357e5e6fee23d3ff01e508ba90292e4f9f40fa57c31fd1bfe82c,2024-02-16T17:16:07.967000 CVE-2023-4000,0,0,1005d71e397cb341faeaa4134970e8dfeabc1e1fe3dee59b82c3690ab56614da,2023-11-07T04:22:02.303000 CVE-2023-40000,0,0,0a46baa03399be7288f9a123a2aaf5c1cef3f042af61f3aca5a1f07043895449,2024-04-17T12:48:31.863000 CVE-2023-40002,0,0,df96ef52ab4b7398a777e2a5595f079d9584908dd83efc246d0dcd480e04e895,2023-11-28T20:50:44.160000 -CVE-2023-40004,0,0,464f44c03781c8c002f46136a8174c1d69d8c7ab38a7b4903e678e4d01f1d48d,2024-06-19T12:15:09.687000 +CVE-2023-40004,0,1,bb7f6e5d7bc316a2b21af3a2a1ce1074b1c0dcd43a0206ecf11cb30602af13bb,2024-06-20T12:44:01.637000 CVE-2023-40007,0,0,3d365fc27f53117c77aaf78c7b2029831bb830f090bc89a5ba9063d789b28996,2023-09-08T21:27:24.257000 CVE-2023-40008,0,0,b73dbe806c28edbf5665a2cfc6c564be712f9ba5e3900757e8716b96b2d9cb60,2023-10-10T14:54:19.977000 CVE-2023-40009,0,0,b9c4a8c2e88ab2f5591a4482256b6ed6297416390634db13e8ebf215e9ee36d9,2023-10-06T15:38:27.297000 @@ -230214,7 +230263,7 @@ CVE-2023-40604,0,0,79a17a1d4274a0cb608e96a1b3a85d23f1191f3072ff20419d725abb704a0 CVE-2023-40605,0,0,2870d5caeafea811a8688cc4ebe593a2899aa4182d76bf6c58458aad1fa6dbc3,2023-09-28T13:29:56.727000 CVE-2023-40606,0,0,ffb711cb04281288071061d7def36f503f557af42461712b94950a307d1ff338,2024-01-04T21:21:52.873000 CVE-2023-40607,0,0,af752a33c16ae4679d7f5f8ca560448e87fc8989147a67e2310ec2b22b888d7e,2023-10-06T20:36:59.623000 -CVE-2023-40608,0,0,74e7e346b643278c62c4819fd1f4c11118119b799aa401ddf3c2f1a20f3cf080,2024-06-19T12:15:09.960000 +CVE-2023-40608,0,1,e673411f6e4217d3bbd2571457ad12fd193e2ed66cda6207f3df3b271b85522b,2024-06-20T12:44:01.637000 CVE-2023-40609,0,0,a03dad6fa33a7763c35fe0f8b93fdbeab8ed4b63a1b0dcea2c8448ba0019f4c0,2023-11-10T04:18:14.100000 CVE-2023-4061,0,0,351052f8120c348fe87611174379e5011c5fca1c5515d153506d3b1076d8d658,2023-11-16T16:03:43.037000 CVE-2023-40610,0,0,faae2e7f774c4944be8a38cc901cdd61407b0527c3017264f4a119c24211a469,2024-01-10T17:15:08.717000 @@ -231077,7 +231126,7 @@ CVE-2023-4180,0,0,794c72c24f6a51c39d32c63ff47c1b56220088a34f275c97a4635d56a1896a CVE-2023-41800,0,0,f2e6bab98958fe853159c31025d8202c7a9f0690863a6943e127869980df6544,2023-10-04T13:24:01.053000 CVE-2023-41801,0,0,4a19d3eaec4bb8865b1b213e065db80117cf5d5b13d1b3d7cf5e3c52a5736f7f,2023-10-10T20:53:59.430000 CVE-2023-41804,0,0,a090e3b00adb5da944db2569d715ad0da764341a562b21b3ec3281031c2e4d8e,2023-12-12T16:59:18.847000 -CVE-2023-41805,0,0,37fd10b7badba650a546fa1fe117acd402202778c4b440ccee4677b8f48e1f1f,2024-06-19T13:15:55.360000 +CVE-2023-41805,0,1,dee771bb29bcc87968449fcb1e19e6377c8d5592f3b31b9e4bd0b97c8ea631d5,2024-06-20T12:44:01.637000 CVE-2023-41806,0,0,4a82d1e32231a8d9c2ccc2fec0bb323e601413bcead97e21ec96a22edd3f73ca,2023-11-29T20:57:54.670000 CVE-2023-41807,0,0,9061411f084c3f889a1bb5d0663923b9bad0b84b77571ec1def28b0c80e2b996,2023-11-29T20:56:44.663000 CVE-2023-41808,0,0,06cba953d6c10768ca2477c3816355e6dd2654c9617f7d8e6c077482b6e57472,2023-11-29T20:56:06.170000 @@ -232673,10 +232722,10 @@ CVE-2023-44143,0,0,f1d5f0377e07daf0451a71636fd8955c937d8957a0ee772d4baf38d05c3c4 CVE-2023-44144,0,0,689646f7341e425ac19392a71f90bd674ca3a5d7e3d1804275adf98293701380,2023-10-04T02:25:54.813000 CVE-2023-44145,0,0,11f935b4b116a5c4c7de5bf418b782f9b4696dcbd955965c3b5d3459b02c7bd8,2023-10-04T02:29:04.490000 CVE-2023-44146,0,0,6f47968c96fd55cfc1521752a1ec9121e450bddf6e0b7c5bb5f55c71ce3e8b90,2023-10-10T20:49:38.620000 -CVE-2023-44148,0,0,1c3208436d9f983d02c3a35de95b305a59ea6733d555b0607a4c3bfc499cb14d,2024-06-19T12:15:10.200000 +CVE-2023-44148,0,1,1caea623e47b9c5df2fcb83199c7419583782b8996d9cedfe29d71c312ee2e5d,2024-06-20T12:44:01.637000 CVE-2023-4415,0,0,963cc884aa7f06306fba2f06482391b3a59e4bddc7877f4aa74dd24e348d6d8b,2024-05-17T02:31:32.947000 CVE-2023-44150,0,0,f65c9645d95090761f4dfa38fe7afda2dc4230ab46cc1ae84cfa7487a950b56c,2023-12-06T01:44:26.800000 -CVE-2023-44151,0,0,2ac437d789af1745b4ea03cbbd9a4e9a510805918ea7aad7393db01d95f7d6af,2024-06-19T12:15:10.437000 +CVE-2023-44151,0,1,d0b38794ce77ff074c8a2e662795a17562e05b1a79ef631557d16cf30399a678,2024-06-20T12:44:01.637000 CVE-2023-44152,0,0,76b8bf7903d93fb32a9e46e47c4e438d2d6daadfa149981380cb6e3852c06077,2023-09-28T01:22:12.437000 CVE-2023-44153,0,0,06e6fa5e06852c51fda2470c124002fc49e6a78290f55514dd41fe50765d657b,2023-09-28T01:23:03.267000 CVE-2023-44154,0,0,c9503975191edb3af7415d8967ae7208b37549abdd9b755873ba6c61fea69928,2023-10-26T20:08:48.693000 @@ -233584,7 +233633,7 @@ CVE-2023-45654,0,0,14e88a4b5268c9d4c04bc136c1aabbb60d4c48be7be5d19bf745091c19b77 CVE-2023-45655,0,0,6785178d3d55fb51b982f0e19603e95453ea23c9e1a432e183fc7017b86c8616,2023-10-19T17:56:36.927000 CVE-2023-45656,0,0,beae919604cbafd35071359ecf061180af2310bb67d901f15649334601696555,2023-10-19T18:07:45.763000 CVE-2023-45657,0,0,d5392a553549ed4acba93de28da1e59d04b4cd4b0548feffbb9b92af25c6bea3,2023-11-14T15:28:24.893000 -CVE-2023-45658,0,0,c518ff9e7385a6e14ee704e9637f496af3de10a4ecf5c7bb6ea3c88932c7bae3,2024-06-19T12:15:10.677000 +CVE-2023-45658,0,1,35b68a74d7074a9a8b6de12c4bdca94a2b55625bac2a7c59481973f3ea286b76,2024-06-20T12:44:01.637000 CVE-2023-45659,0,0,25c6be157f984807fbec6c97aa486bc8669d999ad43f22ff2341a10cb01b9e85,2023-10-30T18:03:57.393000 CVE-2023-4566,0,0,0aafd35fdd476b37a62e71e5699a6387a834e08583c3dbce7d659628897b8bc5,2024-01-19T16:12:13.313000 CVE-2023-45660,0,0,f88b088da208d3f3e3daa806fd7326ab1fdbedfb3cbaa0253c1bd9c3e88f22bc,2023-10-20T12:18:07.003000 @@ -233953,9 +234002,9 @@ CVE-2023-46142,0,0,eeeba665a55a4c38f43ab994435d3b748d7594d6de9a74dc8c0028479749d CVE-2023-46143,0,0,25bb9c16ccfca7530cd488db3d1da3e1721e11c1f85ba98f540871c4296e6262,2023-12-21T17:15:46.577000 CVE-2023-46144,0,0,c42def9ab73ddd702574473b1d854b708c78aff77837daf04a7e63505abf2916,2023-12-21T17:16:11.880000 CVE-2023-46145,0,0,23e8cf44f4d98725eb072fd71f37372dcbf6b28b96e7faccec1e2d2205e23417,2024-05-17T18:36:05.263000 -CVE-2023-46146,0,0,5b41126b845692d54a3c7d525d1569d33e7a41c9e45530907c61ab4ab61fae83,2024-06-19T12:15:10.930000 +CVE-2023-46146,0,1,5a989b14578d061ec870177c00da704ba94e35508500af82acf2085fc13e4e27,2024-06-20T12:44:01.637000 CVE-2023-46147,0,0,c26e36737b6c1ff20521a85c1e9e2b22fe6d487b63d4cc598b5cf78d09ff94fc,2023-12-28T20:04:49.337000 -CVE-2023-46148,0,0,dc7d10f4d6e2de0b228853ddd301e7818956187393f2c80b2cbdb7ef6f2b012c,2024-06-19T12:15:11.160000 +CVE-2023-46148,0,1,d38799448fd678267b2351dde0fb8e25a84aa29c46f078d7c3386c4f006f3251,2024-06-20T12:44:01.637000 CVE-2023-46149,0,0,9c86dc35a2f27029ab17b861a2fb6b193a2728a00adf9640c3dc56830e66e26e,2023-12-28T13:44:32.593000 CVE-2023-4615,0,0,0d33e2796458b011ab0a9d487405a989f5de3989db0de38c0c7d53c54bcdaa35,2023-09-08T14:14:45.633000 CVE-2023-46150,0,0,8f2475c86fd2f6d6c924a3361711385b74ed44ab1606e36daf35b48ab39526f5,2023-11-01T17:34:25.380000 @@ -235072,7 +235121,7 @@ CVE-2023-47678,0,0,bda9ec5da3a75993b01e519fd6af148f2c4398b7dbe8f7b4635a0c4c3b51f CVE-2023-47679,0,0,6a7281ce75d88db73ee4644105ec6a35308c3adb3e0a17e43a1be4e968fc5b2b,2024-05-17T18:36:05.263000 CVE-2023-4768,0,0,4a45b9a26a63dda75c659ff661d20422bc870280687842f9433a1cb52a94b57e,2023-11-13T18:28:18.260000 CVE-2023-47680,0,0,92ee1efbc9cf057b2aac6bfa02d096a8847a00df5987488cef44359cea582925,2023-11-17T14:50:40.710000 -CVE-2023-47681,0,0,41b2e6132af73b28f95e135ba9a4c143874074c2650913c4e69ac31e4ed8144f,2024-06-19T12:15:11.393000 +CVE-2023-47681,0,1,6de396065372e96a43cad9a1bb18ef303fc5c6cc640d33fcfb1bd64894fd9339,2024-06-20T12:44:01.637000 CVE-2023-47682,0,0,9838e3056fdb7cc28e6ca8a0657d36a441007939654eac5af295516c7e0c18e6,2024-05-17T18:36:05.263000 CVE-2023-47683,0,0,3d5f96cc9cab2a210e4a8ebb1bb403bbb08cf399c7fb1c0e676ed3c73cb54822,2024-05-17T18:36:05.263000 CVE-2023-47684,0,0,344355a4110d06a3a3634ba5cda34986b5edbf49247188a19d364543c2e16afd,2023-11-17T14:12:47.883000 @@ -235108,7 +235157,7 @@ CVE-2023-47717,0,0,27c384bb2da2247b75e1e97dd81158a4a3f5ec676660f195bcf845b18701a CVE-2023-47718,0,0,c741441681738efc3979d67da4409868f353d29cc92314f5037f92d0809304bd,2024-01-24T21:23:15.540000 CVE-2023-4772,0,0,2771ff64adbe1ba6f7dfdd5d8e8af50d5674985cd4bd14f9ff6d841da9878bd5,2023-11-07T04:22:57.827000 CVE-2023-47722,0,0,5f2ccb67ee0472008868026b0561431d013bb25eb62913fd40686172191b4bbe,2023-12-12T21:04:18.177000 -CVE-2023-47726,0,0,79f6b824922e6bea28adef2f4c43e3eeb3e5389d93758235f1c785aa2fea7522,2024-06-18T14:15:10.317000 +CVE-2023-47726,0,1,f0748b3c3567bc3b48d1521e7ea7008ab8e5119f1245c016e2d4cfd25bc66861,2024-06-20T12:44:01.637000 CVE-2023-47727,0,0,93638cf13767af0fd87f1a8887a0e85470c71bd37710b8f5a091f8483530bff2,2024-05-02T18:00:37.360000 CVE-2023-4773,0,0,46809a7c239cdb033db621dca5a458d470c07362dae46adc2ff34854ee8e494c,2023-11-07T04:22:57.903000 CVE-2023-47731,0,0,590a1016c4a04e7897213078a5a094bed41ef8ae124e51eb0de721543408fccd,2024-04-24T13:39:42.883000 @@ -235131,8 +235180,8 @@ CVE-2023-47767,0,0,d83e27c39cbb312ccf0217c3b2c5d4f56f6e2b810766abaf5e7fcfbee9251 CVE-2023-47768,0,0,9cefbe9c9b382b54c5ee099fb76d85e1fd42d31125fbe85625df2f10a347f516,2023-11-28T19:22:41.277000 CVE-2023-47769,0,0,e0360b140aacc1b1f1e4221e9405f057d834bc8c3c83aa2423b973eec9d4be19,2024-06-04T16:57:41.053000 CVE-2023-4777,0,0,2285f3b3937f1b6ee7b5013a1072c08eed965f2b904b03b7b4184647f26697b4,2023-09-13T12:54:59.283000 -CVE-2023-47770,0,0,d6452c9f973388dd6be4371eeca43470036fbf6acbbee3c0fb187c7993b517f0,2024-06-19T12:15:11.630000 -CVE-2023-47771,0,0,de8d080bd5869fcdaa485394cffa1f7b23905695858b9eeb60c4c1525d7b1cb7,2024-06-19T11:15:49.640000 +CVE-2023-47770,0,1,9c018860f255970f741d236a4f5863c3465b2f727c200baa319eacbfe97bd1b7,2024-06-20T12:44:01.637000 +CVE-2023-47771,0,1,c6536e817890a1161d9e6b1110bb0868e925caf8b845a39f212db443829830ce,2024-06-20T12:44:01.637000 CVE-2023-47772,0,0,7713bada3e93d580185e7757a00736557df9fbba8e32d5584ac0aaf5b9527567,2023-11-27T20:23:44.047000 CVE-2023-47773,0,0,298e58c18c603d342f120209e3a04b3e42e7e1fc100c9336741efc054d287705,2023-11-30T04:55:31.483000 CVE-2023-47774,0,0,ceca4bae52bfd9b55cbed928f86f07d46ff9838dc2b5bfce08587ed5108eeac9,2024-04-24T17:16:50.397000 @@ -235142,12 +235191,12 @@ CVE-2023-47779,0,0,e33b31dee126d69530344f86a60a47d5dbf814838ea8214bf0cd86723f480 CVE-2023-4778,0,0,e65fab7481708587195b5e350d3f009b8640975d4929f3b2e66e02fe1dda1fbb,2023-09-07T19:34:34.170000 CVE-2023-47781,0,0,16866f547dc98b65098b773d73122eee723050e0e14ea3d1c9c2badc6ca9763f,2024-02-06T13:15:08.093000 CVE-2023-47782,0,0,15a6458772a74a0240babf0abc7861fc3aaff4017c22982e7b06decc1920abd4,2024-05-17T18:36:05.263000 -CVE-2023-47783,0,0,d37d16e47e6ea1e51e19ccfe48a402d5ea0188bf7889ae8543024a3a3d1bcac4,2024-06-19T11:15:49.933000 +CVE-2023-47783,0,1,dac8cca06085ceb517e778a206b073792c79e3850dc4f3717a8f143963ce5ab8,2024-06-20T12:44:01.637000 CVE-2023-47784,0,0,44747aae2dc814d1ef6b101b6ae809ce116e4131b48b9709891d91491260f95f,2023-12-27T20:05:27.610000 CVE-2023-47785,0,0,c9c8d82d65cd6e3171f1f40377c08c985db93e6d2b2b25315d6f39f19ddcbd11,2023-11-27T21:37:43.020000 CVE-2023-47786,0,0,bff92b3ebcc6fa82dc70f2726260d0ae6c85084d9db8e923406bc718d8bbced7,2023-11-30T04:55:18.567000 CVE-2023-47787,0,0,53d60a4bdf49ff8a9e528743a92ddf930723664d6bba4949a586b5509a08c5a0,2023-12-22T14:32:43.010000 -CVE-2023-47788,0,0,daafb0d5fabc8100900e8a41d18c5edb1d5de2f8c6ce3f5905989f952320c196,2024-06-19T11:15:50.177000 +CVE-2023-47788,0,1,99ef28bdfee4220bbe1bf62bd2d23295bb0843747c7dbe5e6ad0f9d7197414f4,2024-06-20T12:44:01.637000 CVE-2023-47789,0,0,bb74177ff87de323f66d07a1aa236f57551efb6b57aaf72481f5da74ae57318e,2023-12-22T14:31:39.947000 CVE-2023-4779,0,0,e82ca2bffb80c11a18e02f3bf3998c2d5266c28801d2604bc8e372bd39af236e,2023-11-07T04:22:58.437000 CVE-2023-47790,0,0,d4a73ac558a654b30b0f70c13efbcba87f7c84c9c01fede107dfc594b4bc495e,2023-11-28T20:39:17.157000 @@ -235892,10 +235941,10 @@ CVE-2023-48754,0,0,0569193cd78a4efadd60bf838471661ca63bd091c9aeb68b7a8fe14fbc81d CVE-2023-48755,0,0,89f1a2b9527257064e17a247159ee4cc7befcc939c8ab5a8c446ef85da2287a4,2023-12-20T21:09:32.063000 CVE-2023-48756,0,0,8c30dc5020c654f585a0d5dd735951cb2629fc1084a1290d46751808b441b84a,2023-12-18T19:06:14.257000 CVE-2023-48757,0,0,0a1bae3080ea3d20f69cecd47279b5f2b2591faaeeab4e0a423414356101153c,2024-05-17T18:36:05.263000 -CVE-2023-48759,0,0,459a765be3a03c21b9cfa31b99a232aff959e4aa846543a8daee1b7a6e934877,2024-06-19T11:15:50.407000 +CVE-2023-48759,0,1,4def6c05c44ba10f2e3b266f75ba3b00ee39a9efbaad226894047a95d4c0f4ee,2024-06-20T12:44:01.637000 CVE-2023-4876,0,0,f9eb648217df9ea8ed21ac789d432af1f675ced46338af1975413764e6a6289a,2023-09-13T13:36:42.887000 -CVE-2023-48760,0,0,b680ad5d71df8b0a46a4e681724328dde1649642d4a4a0de093b74309cbaf388,2024-06-19T11:15:50.647000 -CVE-2023-48761,0,0,bf4710193a272a4aad05d99d01a042d258c5325ec7e89966779c4693f572872d,2024-06-19T11:15:50.877000 +CVE-2023-48760,0,1,31a27383d13919f2262801d5ef2f583c38b50eac4e442d4631fad4dfdaf11828,2024-06-20T12:44:01.637000 +CVE-2023-48761,0,1,f25e1d37f0682a2728a22336f19544fb4171e99c575c8f69a42ca1178a00fbcc,2024-06-20T12:44:01.637000 CVE-2023-48762,0,0,18f0655500b77fe229f0c05382318285d69aa564e93bd9e38484c2464ac06f2c,2023-12-20T04:17:13.577000 CVE-2023-48763,0,0,9db41c6ca700a44d4c80c503f3741328ff596bfaa13c55f7f62ae0d5eb3dc389,2024-04-24T17:16:50.397000 CVE-2023-48764,0,0,34547c93d3452db8ea2222360cd8fa73e88a9573b62ab35d0a19faf06f341b66,2023-12-28T17:25:33.493000 @@ -236102,6 +236151,10 @@ CVE-2023-49107,0,0,0e9af909d621a9c4570185530fdb9aef197de445657f00c33192f11bd7858 CVE-2023-49108,0,0,8b448f813b7f2ff64556bb633e06c1db82194a485a83298972e379416108c845,2023-12-07T17:52:39.950000 CVE-2023-49109,0,0,3bb373d6db941540f9b57f78839d3b030348e834d02ede0d650edc70819635fb,2024-02-20T19:50:53.960000 CVE-2023-4911,0,0,0380760292e65955859c1ea2fd6467a51435ec5fc89240e3b7268906c4542c20,2024-02-22T20:18:58.020000 +CVE-2023-49110,1,1,2e1a7658b29d2ab135bc49a0b41f7eea96bafe10c3c43f4cea395faf509b8fc7,2024-06-20T13:15:49.250000 +CVE-2023-49111,1,1,79f1f236135ac9989ecba27964afee012e805d031223442f228ce1195eda4cf2,2024-06-20T13:15:49.380000 +CVE-2023-49112,1,1,554d977a08477a090174e8ce62db1194421ee3d8137bf112dae81efef5aab121,2024-06-20T13:15:49.480000 +CVE-2023-49113,1,1,c101c62a00ad1ce02194a1c155c928156d0d46c3f36f7f7d88aead6535a54d90,2024-06-20T13:15:49.560000 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-49117,0,0,532b60b363b961206673339ea571d1dbd7872affd35f7cb4f7e7a5be2e8191ec,2024-01-04T02:42:06.503000 @@ -237205,7 +237258,7 @@ CVE-2023-50895,0,0,983bb9264ba2c8683f575e79001c719a5d1f72b56ef941db6ead73b118a4d CVE-2023-50896,0,0,32a10544fdac61db8a171df746dccf1d232f13684a47de05af905306e155cf06,2024-01-05T17:32:59.937000 CVE-2023-50898,0,0,8aff62c643d7aeddc95a67a99b868adeecf42b7f0720ae7af339a4744e3e221f,2024-03-15T16:26:49.320000 CVE-2023-5090,0,0,44061d9c807e6cb4b7365388d7e67b561f84f0eadd74068d4d9f7ddde12f8fbd,2024-06-12T10:15:28.920000 -CVE-2023-50900,0,0,4bcee2dde492da93c4e6039cc9532167efd69173c18cf57e3fce2febeeca490c,2024-06-19T10:15:09.683000 +CVE-2023-50900,0,1,d20000b011b3912839a1e3e9a3d806a35dbcfc59ee224e38266be4fc064bc4cc,2024-06-20T12:44:01.637000 CVE-2023-50901,0,0,fa1245dfad58609576f971f16b5ea532f1ca81c051130c99f667ea1205d37921,2024-01-05T17:34:07.947000 CVE-2023-50902,0,0,1513c647ffec3bccc364b057fe7be8ad3f21264b604f6b5475cb44c0c9074864,2024-01-05T16:21:34.563000 CVE-2023-50905,0,0,c0b30a24d3473e2350b628f1856fc1c117d2f8592d3dde08d565e83b22838670,2024-02-29T13:49:29.390000 @@ -238729,6 +238782,7 @@ CVE-2023-5288,0,0,0738994bddf6db9f0b825ffb89279f9130371f293c5b8f6550deac482c5ff7 CVE-2023-52880,0,0,482c2c5065430f7d7892683cda8d1764232771aae78850c90bbe4e8ec77770ac,2024-05-24T18:09:20.027000 CVE-2023-52881,0,0,6f27b572b3e64428644bdda7520544f8cd90fee86a13f8f6a714c131a849a56d,2024-05-29T13:02:09.280000 CVE-2023-52882,0,0,798470a64b56f744c8b04faf053b4d16c03d86b55db554772e204dd8af8cb938,2024-05-30T18:19:11.743000 +CVE-2023-52883,1,1,0abe994929823aed4581478ee993b71d052a0474b1f5d0383c9ccbd022898409,2024-06-20T12:43:25.663000 CVE-2023-5289,0,0,e99a2312fffac7e548d9067401ea1735cab5340b5825bd2426e3171dd9b0909d,2023-10-02T18:13:04.227000 CVE-2023-52890,0,0,a0eebe139551581f49cfd3b7f68f49883daf2a40bfb5a3949932cb006cd09360,2024-06-13T18:36:09.010000 CVE-2023-5290,0,0,755547461c1ffe140ccfa395ab853f280b1d991be6ac36b66243260a063192cc,2023-11-07T04:23:48.727000 @@ -238950,7 +239004,7 @@ CVE-2023-5522,0,0,200b029bc6315b4c24f78beb3576c8cf0e70aa48d6544a311895a1f5f320b8 CVE-2023-5523,0,0,858bfcb9b8b859c1e5e3b5cdda6c9a832c20f4c69fab01b89e601eadb13a78b0,2023-10-28T03:34:59.010000 CVE-2023-5524,0,0,60c4edc5359992a03a016444dd9c65cc1602054742d468c0525c274cd41b7955,2023-10-30T13:50:35.243000 CVE-2023-5525,0,0,63929e1ce8f1d5189c7faff2086e71c27952b4083e8f4067b96b81b17be9f23f,2023-11-30T20:15:18.223000 -CVE-2023-5527,0,0,6f7fdc58bc486a7d8a3b57756c6fb01677092a0f1871f015badb7916e24104b2,2024-06-18T06:15:10.243000 +CVE-2023-5527,0,1,be0af34d6710517f4d222d42524f6b483873db1064095a012996fbc0dbf4ab59,2024-06-20T12:44:01.637000 CVE-2023-5528,0,0,07643a0fa5c4c83910aea8e973f4b5e61f85acbc3ccb794a69dcca174f582695,2024-01-19T16:15:10.280000 CVE-2023-5530,0,0,85f2c031460358f0272c3f9642016eae1f670f983b42376966541a1349ead6e6,2023-11-14T15:31:50.170000 CVE-2023-5531,0,0,1abed91bb44bd2026d176943054fb17b827d8e897b0a4f10a1006ab7b9fd072e,2023-11-07T04:24:07.297000 @@ -239820,7 +239874,7 @@ CVE-2023-6491,0,0,cdf7c06784d4d39eba71b6fb1604eda595538e62c28add78cc43a71a5a4b75 CVE-2023-6492,0,0,202ca7b5bc9878cc8ce748874f3e7b02ae4737632c455777af5a1838eccbc49d,2024-06-17T12:43:31.090000 CVE-2023-6493,0,0,f1b44774d19dee2dde0db6057c1c8da6a9052c466b0c843005cf7e84e74e5bad,2024-01-10T15:10:40.807000 CVE-2023-6494,0,0,e84577867db064082c4fbb5b749302fb02213f52d6d8e07c0caef285009cb8e8,2024-04-15T13:15:31.997000 -CVE-2023-6495,0,0,0fcfb1d0058bf9394898cdd31ad37abb020e87e791467b5ac9e17b20412e5797,2024-06-19T09:15:10.433000 +CVE-2023-6495,0,1,1666fb84290d79451fa115e60c1f7722eb45964f03f7f090509d5d4ec773b462,2024-06-20T12:44:01.637000 CVE-2023-6496,0,0,87b56518aaf4afd4545cd371dac346e93b19b056714958fa1a42154914cf88c5,2024-01-17T20:24:42.663000 CVE-2023-6497,0,0,5c328723b0d6eb2b6ecefa341ec54fae28ffb5f772896759b50e3e0ea4100eb7,2024-02-01T04:14:30.527000 CVE-2023-6498,0,0,9f7d3ecac1b2f6231548f9f23508f6f54f57fff8c183129d647c8665a44041de,2024-01-10T16:53:30.670000 @@ -239982,7 +240036,7 @@ CVE-2023-6688,0,0,d261de4de637dc0e80af432f70bd6cacdd348e8805fcc1ab5b8afb55a49ce5 CVE-2023-6689,0,0,94832909555ff59b567516253441b2d84f7ab3411369d6764bc6cdff465466c7,2023-12-29T19:29:33.807000 CVE-2023-6690,0,0,4a0a71b1ead07e18f281fc4661b8ad9c1c5894485cf3fc449f0f62ac342ca884,2023-12-29T19:21:45.180000 CVE-2023-6691,0,0,a11890938c81fde945a58f158b8b20210e60d65408972177cf95e97613dae836,2023-12-28T18:28:00.493000 -CVE-2023-6692,0,0,bf557c3ebfee6750ae6b7c1bb3c2f168b22fd88b4a864917ada31e91e29ece8a,2024-06-19T06:15:10.873000 +CVE-2023-6692,0,1,65d04d6b86520ce07a071d903bf0f4874de865e41ea84cb12f6da17cd0992d9d,2024-06-20T12:44:01.637000 CVE-2023-6693,0,0,cf628307c1964a00995a1e6a5134d1eb338281166ebf99b3dd57917a16a1b948,2024-05-22T17:16:09.817000 CVE-2023-6694,0,0,74888c6061f5995c1ece9e256c949c745db7a28c9fae546822fe2bdd37077360,2024-04-10T13:24:00.070000 CVE-2023-6695,0,0,c350585c288709484fa2c4ed5afca55376ce388211fecd421637a541eb8ceb4d,2024-04-10T13:24:00.070000 @@ -240525,7 +240579,7 @@ CVE-2024-0054,0,0,987efaa1857469d87adfaae38079aee4e9c660539b169f0b4c9210a0c7eb43 CVE-2024-0055,0,0,7cea323e5f22231f34a966995c2bb8e831665aebf4714879a2fd8ff073c52f27,2024-03-19T13:26:46 CVE-2024-0056,0,0,c373cef1ac1f17bedc37db496b454d4c90ecce450755088b205c5d2e159e7855,2024-05-29T00:15:10.920000 CVE-2024-0057,0,0,e226ddd9c506eaf915ae1c1f549242a9ee67c0c5d995f910e37ad62c332a9c20,2024-05-29T00:15:11.080000 -CVE-2024-0066,0,0,86098a415c5a4dbb1dda6bec1be48be0fe2c72320f6c360d42e650f19f1beda3,2024-06-18T06:15:10.723000 +CVE-2024-0066,0,1,984e199a92876310e1da8446d07f9645f6d44887a90649ef7f3944d6821ce76a,2024-06-20T12:44:01.637000 CVE-2024-0068,0,0,29054351872f671ffd0afada76da136d48518b88acaefb639ccc6c169ead07a3,2024-03-01T14:04:26.010000 CVE-2024-0069,0,0,fcda9c827a68481a563f617244a09b1d788f56c62c31734c572fbfe1a75ea718,2023-11-28T00:15:07.140000 CVE-2024-0070,0,0,f5edfa828dbd64ca40da0463d8d67355f807a2f6d8ea2e049578dd15434f1821,2023-11-28T00:15:07.183000 @@ -240764,7 +240818,7 @@ CVE-2024-0379,0,0,174da64b305b0263e8906a1d5cc2f6215dd55f09aa0a9c8b5bda9bf88e026e CVE-2024-0380,0,0,3f3894f5083e9ad8feafa10eee28775174e246729c7af4fbf8093c7f92398568,2024-02-07T23:31:49.193000 CVE-2024-0381,0,0,cc404e9ab60526f4cfd2cba8d7ea8cb6a7e1eef465808eab04f8e02e2e2ed4df,2024-01-24T20:48:35.827000 CVE-2024-0382,0,0,ab33ccbf2aeb6736aa9a498513aba9dba3b237c3d9fe3e776d686fd399098525,2024-02-07T23:32:02.143000 -CVE-2024-0383,0,0,215abb7aab32104a87b9ae087214ce501913e96ac0f0c849c8f5e2a1c125fce0,2024-06-19T09:15:10.807000 +CVE-2024-0383,0,1,aeffa21f78a36c9c0d84808a117a6697ed2e3cc64ce939a7fc0d16c9926aeaca,2024-06-20T12:44:01.637000 CVE-2024-0384,0,0,5eba97ede5e4794d92f0b763409403bdfcbde410a2df433510faaeddc85a4fb3,2024-02-07T23:32:14.717000 CVE-2024-0385,0,0,7385b238cbf21556b1f0a069144cfd049b570a4bd6587b69c231f70bb76258d5,2024-03-13T18:16:18.563000 CVE-2024-0386,0,0,8d804ee9a3a51d016220166b449c94366950fc2260124c0222047bc30a6e9571,2024-03-13T12:33:51.697000 @@ -240775,7 +240829,7 @@ CVE-2024-0393,0,0,8881de5088bee2f43467b73941f684354c9bcdccfa7386a7827d4a78a7e8f3 CVE-2024-0394,0,0,132997f5a0f39575e52ab364803d29384d542a557e73a32dea0a249b2357dfb2,2024-04-03T17:24:18.150000 CVE-2024-0395,0,0,9697a8ac3bbf759d0c2ea19b7ab0aa903676619b1d5a607c85b8d090a4e44ee7,2024-01-10T14:15:44.970000 CVE-2024-0396,0,0,106628bcb832aae2e274e4e91fdb5add809827efe4c459066d3102ffe0249334,2024-01-29T15:22:40.317000 -CVE-2024-0397,0,0,fb8a60d96b18ded5a4df325ab5f16c2a3f8bca756e992bf0a8b459da554ad30b,2024-06-17T18:15:14.767000 +CVE-2024-0397,0,1,f559bd631e9ad345a230e622ff58736383b6d20f916da29823b9431f2d24f22c,2024-06-20T12:44:22.977000 CVE-2024-0399,0,0,f9efd00d0c28d2f5fd7844014ccf20e6de83c83ab3d0467105e159f94efa805f,2024-04-15T13:15:31.997000 CVE-2024-0400,0,0,18035b4484267a537c15645ebee53285fc55ae5559f980b5f9795ec2795f24dd,2024-03-27T12:29:30.307000 CVE-2024-0401,0,0,eb06da8d7bba1b4b23b9513633128fc89991a02e4c0b59d538b76f5796878a05,2024-05-20T19:34:58.277000 @@ -241145,7 +241199,7 @@ CVE-2024-0783,0,0,1ca97ec97b21e037fbe3b601983e1e1e9bc541d42b5f2afcead0eafaa8735d CVE-2024-0784,0,0,fb77306878a2fdb06d9bdbd4ba344dc651326b28a94bc0ba964a8aeed9016a75,2024-05-17T02:34:58.123000 CVE-2024-0786,0,0,cdb83bc39f946cc0a2d3b9c4f5ab4e00db9f2e81c4656498c18c3f17deb6a8f9,2024-02-28T14:06:45.783000 CVE-2024-0788,0,0,75f5d622b7c1e57503efb87108b55174eee69d541c9f6d15cace8392d8e80e64,2024-02-08T16:42:27.363000 -CVE-2024-0789,0,0,24ca500d54123d7a5ebbbc50242dfcbb35a3d2c3142214ae02e47aa86496d3d5,2024-06-19T08:15:48.873000 +CVE-2024-0789,0,1,474b3e1e2c322fe24e7f69e63d7f3d8a0ef03362e244735019c027d8afc25b9f,2024-06-20T12:44:01.637000 CVE-2024-0790,0,0,b67fc3cf82e5ad01ef4ce78b4d2e35b81bb71c4dae26e3e273cbdb15fcd5e9e6,2024-02-13T19:42:38.757000 CVE-2024-0791,0,0,7827d7eb3cda60385ca8701c37bf1a6aa6a95c3c08714f3192e95831d3b99ccc,2024-02-13T19:42:31.100000 CVE-2024-0792,0,0,dcdf8778bbc427621cd1ba232124bc6bd9e3711d49fe90c505fd2c1a800268ca,2024-02-29T13:49:29.390000 @@ -241199,7 +241253,7 @@ CVE-2024-0840,0,0,a29fd729ffdb30a11acea1b506301229e907e8ea6ce7fdfdd44e196863c898 CVE-2024-0841,0,0,9e65cbfff7725abca8b3bb8d47238fadc1759ba27b260df301bbf9206f25aa46,2024-05-22T17:16:11.667000 CVE-2024-0842,0,0,2d4febcc0a5bd3f6b5f6eeeb222e1bdadfd7499df5c95fd0f9cc7e2a10a87dbd,2024-02-15T19:11:14.253000 CVE-2024-0844,0,0,9b0ede7ee0379ed34aa516e6f2cba464e96d05ae45278d47c03f7b0b4baaf7d5,2024-02-08T16:15:39.903000 -CVE-2024-0845,0,0,f5157ada9c80be62143fc3b476b2c597f2f65b6c0952aac15a121512f61d89f1,2024-06-18T03:15:09.330000 +CVE-2024-0845,0,1,b3845c04fb1425367077ee7558db960e855add222c71be6945e3f94db1c736df,2024-06-20T12:44:01.637000 CVE-2024-0847,0,0,2423a45a83c68ee77ea1657795a6b4f742f1b905ef7ab47fbb7c37fbc6c3b67d,2024-05-02T18:00:37.360000 CVE-2024-0848,0,0,31e58640f306446653f67bc78198fcff39c93c6b22a4398146342d7991ad8c6a,2024-05-02T18:00:37.360000 CVE-2024-0849,0,0,ab143b9a0b5d37d266faac9cd54f50fee666b57f962e8e1bec5db73357a455f9,2024-02-13T19:16:30.810000 @@ -241491,7 +241545,7 @@ CVE-2024-1164,0,0,8ceb95fcba553c0447a63d8e5e80c1481416a7a28be670b34d68b7bc77538c CVE-2024-1165,0,0,09d0c48437e50305f6b70b9aab3bb8805a9bc240d0fb341de398e33a6ad98f02,2024-02-26T16:32:25.577000 CVE-2024-1166,0,0,cbc50c0645991c69523344b23f8a84819598bdfdeb24c5f4ba7570f86b9c6398,2024-05-14T16:13:02.773000 CVE-2024-1167,0,0,646f860ad24a5198d530bba39bcdba3b9fb385431091cfa90a0190891cfad025,2024-02-09T20:20:51.900000 -CVE-2024-1168,0,0,10134d5551957bcbcc4f441efcc5d053e0b12f7b3f77d1d637b73305d119cebb,2024-06-20T02:15:09.420000 +CVE-2024-1168,0,1,d18ecbe4ee5e6ae3c4099f948aaa0721b128f082b8c3c3b9f401f76315dbe9be,2024-06-20T12:43:25.663000 CVE-2024-1169,0,0,f519c7f99749582bebe013a87c95bdf3b84f2eaee24ddc4513116c225a8401a2,2024-03-07T13:52:27.110000 CVE-2024-1170,0,0,8c5173edd657df97640022e14408ad562874ba7f628f780dfa1960fdbf90e9a7,2024-03-07T13:52:27.110000 CVE-2024-1171,0,0,6b87cc518b4ec22739c7ae66eda5d8c3cdf1db30d4dec8967ce2f3257f9601bb,2024-02-29T13:49:29.390000 @@ -241713,7 +241767,7 @@ CVE-2024-1403,0,0,52ae0be80e56bab12c9eb7614c5934d9c3f91ac3ecccfb883ba911d569f9ab CVE-2024-1404,0,0,2bdd0ef1975c09eeeb8becea825068c858d5996650f8e796b4187f1653127afa,2024-05-17T02:35:25.647000 CVE-2024-1405,0,0,ae5bd42b76973a8b425282db98078aed6f04c4313708f5d3fdc8ebee3587232f,2024-05-17T02:35:25.767000 CVE-2024-1406,0,0,6550a87d634c803bc250747d6e95d1a92b844be0a4dfe16d71b011bf743baf19,2024-05-17T02:35:25.870000 -CVE-2024-1407,0,0,9f22b2bfa162de69df26546e39352ee255207027c27596afcb6f6195f2f56136,2024-06-19T07:15:45.730000 +CVE-2024-1407,0,1,b3bf8f2b728ef0b4a1a62fa8c247a0dfb09f43f9867c02e41c2ba0a5e7511808,2024-06-20T12:44:01.637000 CVE-2024-1408,0,0,459282e673d0895d08ca66f1f5c00497d34216acebf7f722a72b076c4d3b2a9a,2024-02-29T13:49:29.390000 CVE-2024-1409,0,0,d0e45009fed6fac81d0d180ff2fcd57cf5cd35a7a048fa6351f7a4a4461a1319,2024-03-13T18:15:58.530000 CVE-2024-1410,0,0,535308bfcb5b14b9cf6546577fa611ecf7473e04ab146e149a1b5e72425241fd,2024-03-13T12:33:51.697000 @@ -241904,7 +241958,7 @@ CVE-2024-1630,0,0,b3e63ab3fca2f57c425774ec83616f21b44473c1f5570d1282d02bf599e377 CVE-2024-1631,0,0,fc2893d5d84aff0551fae290d2fe3cfb3246f815cc3e85e7be8cb7a443e59ea9,2024-02-22T19:07:37.840000 CVE-2024-1632,0,0,6e1c47780d96ad6fcb59ec0ca790b51a445b7ba6bfe735fc687e801fa4e9fa24,2024-02-28T14:06:45.783000 CVE-2024-1633,0,0,38fdaaa081cb72684e8a3a7c24003a4981094738f4cb62580982692842e12368,2024-02-20T19:50:53.960000 -CVE-2024-1634,0,0,78175d9e4bf293beda410596616055bfefd86fe734d011e12eb7dad6e0525eeb,2024-06-18T03:15:09.580000 +CVE-2024-1634,0,1,8a4331c682c530826a465024c2bf21e94118c5d10878ce0aa5b8784561850a13,2024-06-20T12:44:01.637000 CVE-2024-1635,0,0,df1dd81e97ec5df9995721a1f269c745906d52047fd48e8691457cab01d3dbf8,2024-04-17T16:15:07.720000 CVE-2024-1636,0,0,110561fc2d8220a09cd098605d5d9c82332c44e2266859d6f751e2ed66576fc3,2024-02-28T14:06:45.783000 CVE-2024-1637,0,0,ad9b5ab8aa7d33952d11bf9f2ca328427186899a35864ba9221fa2bbd849dc16,2024-04-10T13:24:00.070000 @@ -243232,7 +243286,7 @@ CVE-2024-21678,0,0,a74398aed7f752b8a4413bad434f2adf6ab8a95bc47028b48620e299957a5 CVE-2024-2168,0,0,b854878eddfae20c7bf7090b800e5793dbeb1896e489304f1c2dd8d4439ad998,2024-05-17T02:38:05.397000 CVE-2024-21682,0,0,6b4858b4700d4b6ec3ad8145ec0ece417db20d31f4042e4246bb7ce7db07ab15,2024-02-20T19:50:53.960000 CVE-2024-21683,0,0,4606a78c4030c676b13be131298ac67504c74d2a7960f7e607518276fc67bc44,2024-06-10T18:15:25.363000 -CVE-2024-21685,0,0,a38e15416bd51e29641aebf7a624b8ba280501b2512be5bc40b3341055e57418,2024-06-18T17:15:51.243000 +CVE-2024-21685,0,1,e2cb496c7456474dc422afe7a0ecdd1596dce839e094299685a35eed8de7809e,2024-06-20T12:44:01.637000 CVE-2024-2169,0,0,151ccb2c8e1a2ae0c1ec7f646f803cafe134a2f43c3cebd718a131296f39d84d,2024-03-20T13:00:16.367000 CVE-2024-2170,0,0,ecb9a4c8858b9f58e40341aa169d3b7c37f3c5e40f6e92367b411525d123f7bf,2024-03-26T12:55:05.010000 CVE-2024-2171,0,0,97513686f796b3a7e6724a3e799700f71cc4419429b47ff47103ef11ceb3a9b5,2024-06-07T14:56:05.647000 @@ -243393,7 +243447,7 @@ CVE-2024-21989,0,0,ff0faa596af54ed5ae8099ba628458de998e57d9e93fbba155c9de7f27b73 CVE-2024-2199,0,0,9bdc0d33f3824756fa8001c75623dfa1e96bf87c8561083782f2f0022d53b57c,2024-06-12T10:15:30.623000 CVE-2024-21990,0,0,0b4ba6f896ec2fdb9c7522d6449f5c0166971932fa2ba6c5f18beb5ae9a5b96a,2024-04-18T13:04:28.900000 CVE-2024-2200,0,0,c95251fe62e0a963b7f86da5338bcf7f5fe53157d94fd1e09dd2c48a41fbdf10,2024-04-10T13:23:38.787000 -CVE-2024-22002,0,0,b66c32288fd0801f6f752802c14c34701abe503f0ac2f3aa6c3311513815e974,2024-06-18T19:15:59.397000 +CVE-2024-22002,0,1,414e0abb0991bcf1056e17651b74f77477e56f14822643d1fad03b790e5a58fd,2024-06-20T12:44:01.637000 CVE-2024-22004,0,0,722cf9801f459066afdd85850c725b2e967fa83ca93b6dee72900667c46a5b4a,2024-04-08T18:49:25.863000 CVE-2024-22005,0,0,313b9bc6d7138eced2900a2388d6d58fcc17e9d91231c0517d2cb0e3e82b9d0d,2024-03-15T20:15:07.527000 CVE-2024-22006,0,0,4c7c420bbb6e62588c7a1f4eb632b3e6efe7a61ff08393b9055a3796f498bb2e,2024-03-15T20:15:07.573000 @@ -243600,7 +243654,7 @@ CVE-2024-22259,0,0,dce7d33f8caf96926ed38e47ae4f4d2a0e606a3507b6c30493d6119b160a2 CVE-2024-2226,0,0,ee8f1ca60db458688b285f09c24138ba2af43e7eda48e7abf64d7861f3a6fd0e,2024-04-10T13:23:38.787000 CVE-2024-22261,0,0,becda971f9fe2bc0796e849a1ca6efcee98df6406cf540f6a7792c4f11b5b746,2024-06-11T13:54:12.057000 CVE-2024-22262,0,0,f19b1c11ec8069ac727f7996014f3456fd5a6417d431b01d11ac200419a9bbec,2024-06-10T18:15:25.940000 -CVE-2024-22263,0,0,7b07d6e622f65dc045484a9e766df4fed78061c76f2e5d56b996ef553b89f686,2024-06-19T15:15:58.327000 +CVE-2024-22263,0,1,05e1e7315e7f035b5eed904b4ce84da90b832cc34c42840059ea59ce5d4610d0,2024-06-20T12:43:25.663000 CVE-2024-22264,0,0,96bdae8486634c5f71f7c0824f656da1157e383d5f4bd5d08e042b1398b50bf7,2024-05-08T13:15:00.690000 CVE-2024-22266,0,0,00ca0b0bb686e5de0808c372a0dca387ad248949c8bb90b3dfb3008d90a00e7f,2024-05-08T13:15:00.690000 CVE-2024-22267,0,0,727e40be0aa0227d7b476a6c5d7d557ff3749d3281a0273fd0cde6d1d2dc7d37,2024-05-14T19:18:31.490000 @@ -244238,7 +244292,7 @@ CVE-2024-2344,0,0,9cae69222ac86b797893a236952e2b67d0f04fb96cc74f0182a6b9bc4a4c1d CVE-2024-23440,0,0,9dd065aa3db280abdb31ad5cddbf9a0771593c407067e49d6917c21b3390f15a,2024-02-13T15:16:05.223000 CVE-2024-23441,0,0,de32eb33b55d8738bd8a9d16a7a81a54994489d7a2b6a46fb774fdf5c385031e,2024-02-05T18:41:43.547000 CVE-2024-23442,0,0,c936cb1ec228e56a170ab994be2774df3ba381de2e907bc730c280a37402960c,2024-06-17T12:42:04.623000 -CVE-2024-23443,0,0,2f72e7e1c510a8d98457109ae4b3b18e61c0a9ec31d30bdf6870ee977215eb0e,2024-06-19T14:15:13.360000 +CVE-2024-23443,0,1,837475d1d65bd0bbec9098faf22d629e6ca14f95f5424cf6c98ff1abe05947b1,2024-06-20T12:44:01.637000 CVE-2024-23445,0,0,6f9abb167952921adf9b985cc5d276de406aa3f6103c7695809c16eab313f2c4,2024-06-13T18:36:09.010000 CVE-2024-23446,0,0,250d55c97e03f858281f4b571f5417bd7430f2eb75d812ec1a5460363cd232aa,2024-02-14T20:10:24.323000 CVE-2024-23447,0,0,d914699914a1032e2f26c2be4fcf7737ff60c4d99dbe7a58145b0312508d8818,2024-02-14T20:02:00.753000 @@ -244516,7 +244570,7 @@ CVE-2024-23806,0,0,3c7dd05f0d84cb4b37bdcdbac4571706a903d21147ebee955315287ef797b CVE-2024-23807,0,0,df12edcc395b0843ea97d6f3fbf434aff9cef06784aae4873fcae58a24a3d141,2024-02-29T13:49:29.390000 CVE-2024-23808,0,0,5be188e2ed229b6d1c42bb6f499af717d633f551dde12260911eb0c8cbdc2703,2024-05-07T13:39:32.710000 CVE-2024-23809,0,0,e4465b9152c477fa0b8b9ba353cffba5c3ae3843ad0f849fa715a6b77d4c4ae7,2024-04-02T15:15:53.217000 -CVE-2024-2381,0,0,5b4f25b2819bc5e7db1eda51927485116ef40752aa9c15fb49d606d5004c1828,2024-06-19T04:15:10.753000 +CVE-2024-2381,0,1,4d413232e398fb26cf5464ef20fd7ffc85489d082a339146ee14f7f5c730f171,2024-06-20T12:44:01.637000 CVE-2024-23810,0,0,fcc523095813c9aa174bae9d5d18aa598f3c0429a0b756712e53ba2ee896842a,2024-02-13T14:01:00.987000 CVE-2024-23811,0,0,626bc7786e498ad37af14e3917801ad7d39c61c22419a48d031d889eeb5a7ea3,2024-02-13T14:01:00.987000 CVE-2024-23812,0,0,33a1b186208ff08c53ff4ffae26bc7a3ad9f21f666e95388037d51e55c6fc5f0,2024-02-13T14:01:00.987000 @@ -246441,7 +246495,7 @@ CVE-2024-26803,0,0,bf4f15eac5d42d9d48acabce36c3d482be8797731b77e5ce1483231d6ff82 CVE-2024-26804,0,0,d8c422436039e8386ad66c3fbd170d47519ecd5b9715a009f99e3fe84af8acd2,2024-04-04T12:48:22.650000 CVE-2024-26805,0,0,b675ea9a7857f11cb50873972316476c87ff8c6cc3e58590a96a92123fc9f992,2024-04-04T12:48:22.650000 CVE-2024-26806,0,0,015091e390b260dd882093bed966879e94cc206771d1bfbc34aebfbaafa6ae89,2024-04-04T12:48:22.650000 -CVE-2024-26807,0,1,66efaa56e935b770d7f99b196cd5f7a3f19f58a0e206f379b919ed6ff2ab6c69,2024-06-20T10:15:09.303000 +CVE-2024-26807,0,0,66efaa56e935b770d7f99b196cd5f7a3f19f58a0e206f379b919ed6ff2ab6c69,2024-06-20T10:15:09.303000 CVE-2024-26808,0,0,4f31bc304a07232a3baf91061957b820ea1892642e797b2566eb9414b09af675,2024-04-04T12:48:22.650000 CVE-2024-26809,0,0,9fe73261a4fc78e6c4eacdd5a51592c430457963a39614d59847053f3066f6fb,2024-04-04T12:48:22.650000 CVE-2024-2681,0,0,9e6fd5b2f5bd242307a3b06bd8306c1385de8ff11e4127aa515eaf95df4ceb50,2024-05-17T02:38:25.007000 @@ -247479,7 +247533,7 @@ CVE-2024-28135,0,0,96abb3119d7c130b3351ae6e19b7b28266b27d62a615bb8abd63702b97f6d CVE-2024-28136,0,0,f26be5bb0ac176918932bfafcc2f2c6a92b6e2dab79b908804e6e26c391cb054,2024-05-14T19:18:31.490000 CVE-2024-28137,0,0,8b6624ffab52051587006e3eecdec06d044231b46bf2ab3d1e0aef29724296f2,2024-05-14T19:18:31.490000 CVE-2024-2814,0,0,982339f1e31e31b47a86b07569eeaf2f5813f3d3dd621dc9984c4993bd7b494b,2024-05-17T02:38:31.880000 -CVE-2024-28147,1,1,f3827b7b7e265af2adf0f447b9e9e3377810e8e92f7852202d72cda9c13ed838,2024-06-20T11:15:55.913000 +CVE-2024-28147,0,1,aab0bc6dbe7ef76ad0286e1a843686a19f861519d57fe0ceb776aac3cbc4f1e7,2024-06-20T12:43:25.663000 CVE-2024-28148,0,0,dae8adaa9a9f352e6ec75654d798899599fff5056d36885fb288ef42e72a3322,2024-05-08T09:15:08.620000 CVE-2024-28149,0,0,41104aad52a41f735bff830317158bdc9ba92207034c216d3619939dc1f50d3c,2024-05-01T18:15:16.697000 CVE-2024-2815,0,0,ae30a9b38d7ddc3e74b46ed02c6cc6dfaac22a9e2f338b709b798eea6b5488d0,2024-05-17T02:38:31.990000 @@ -247931,8 +247985,8 @@ CVE-2024-29009,0,0,64d623a5e5091ece3a08216e60fd84baa7c5e2c60d17197a481a7a00a1fb5 CVE-2024-2901,0,0,df536d591427828a51852a2b88694908334d7c53f764c9038fd3774c5ac19973,2024-05-17T02:38:36.427000 CVE-2024-29010,0,0,1e3d8487ff712a2c650beb70061bccfe6dbcb9db93046ccef5c4aba76b5791d4,2024-05-01T19:50:25.633000 CVE-2024-29011,0,0,87d4656d77d891e8470b880f5feac00db31649e777019df201e1d135e5a0d7dd,2024-05-01T19:50:25.633000 -CVE-2024-29012,0,0,999b9b770baa8dc2cef8f5b8f9692cc2067265ac052b62a4dd1d34ebdf9cff96,2024-06-20T09:15:11.347000 -CVE-2024-29013,0,0,038e0a8a864d3094bd5ac1441f00f2be35b07bed2f90be66b3c0a13dda6e32a2,2024-06-20T09:15:11.543000 +CVE-2024-29012,0,1,a9953065f42e3ba6102cc6d89882db25a8face697a139977e2894e4eb091522b,2024-06-20T12:43:25.663000 +CVE-2024-29013,0,1,99c75c70296973c86f385480f959e000867cb2264e65f4781def620ef38a1b1f,2024-06-20T12:43:25.663000 CVE-2024-29018,0,0,a31ea156ee4a30b6d7535cfe30928ed9f90e655143b9cf9c902aa0e59ea88865,2024-03-21T12:58:51.093000 CVE-2024-29019,0,0,fe2de4afc3940e547c647135fa914dde2bc9fce5b46dec96e6b4c47b6599bdc4,2024-04-11T12:47:44.137000 CVE-2024-2902,0,0,38f24f885a94a37a841618e1d20810a0ee756f93a05006f5b6341ee4af4d3b21,2024-05-17T02:38:36.520000 @@ -249878,7 +249932,7 @@ CVE-2024-32027,0,0,5f3c09d170bbd26a1e397a298c9a92805316ba30164f013dc8cd02f515dcd CVE-2024-32028,0,0,a16d36bcfaa5cccbb6282aecd03e18b80c66f8151e3c2f08a8edd43b521f9227,2024-04-15T13:15:31.997000 CVE-2024-32029,0,0,1e834dc3a71ee261fc468b623f57a7d125b56bad8bd02c617d5a0b814be0d9b3,2024-05-30T16:15:10.050000 CVE-2024-3203,0,0,5eb7ad499de8259c7320c0effe5b5c52900c8ef3ec49c4b6655249cca33556b2,2024-05-17T02:39:46.670000 -CVE-2024-32030,0,0,fd0b78de9a3262b9c8f29bead6cae209f5e2258b9ecfd9525e4f9a70cbf64a74,2024-06-19T17:15:57.863000 +CVE-2024-32030,0,1,4e025f5e63849da604e7386b9f0f2214ecc24f2a5dc26c5230dedb3be0f16c86,2024-06-20T12:43:25.663000 CVE-2024-32035,0,0,9f9419e7b7ca688ca6c807b99c4196d3fdd26d305c290e1d723cf412a79167b9,2024-04-16T13:24:07.103000 CVE-2024-32036,0,0,4358f457ff05e2fb3005eccdac6fca8cb869be3ffa209c190e441f2c4aed7dbe,2024-04-16T23:15:09.173000 CVE-2024-32038,0,0,02c9bf2213ac1ff691fd8ed35a9ee3f7c3440196b5d0ceb851835e775a533fbd,2024-04-19T16:19:49.043000 @@ -250010,7 +250064,7 @@ CVE-2024-32285,0,0,9529431b83da151fb9b96ef61a6f52d78979021395b253d357cca57331ad8 CVE-2024-32286,0,0,0446ae8cfeed3b6b428f38f3c2f4e35d46b31c54a9ccc231877126a8c050363b,2024-04-17T15:31:50.160000 CVE-2024-32287,0,0,26a016a9b3c6a7e85e2e0f642b43856dadb05faacb97686d986a0222c93b67a8,2024-04-17T15:31:50.160000 CVE-2024-32288,0,0,d6ad7a62d4bac5355131f6aa48a68ab7356e2aec6915f40a12433efb5f544350,2024-04-17T15:31:50.160000 -CVE-2024-3229,0,0,db852c9f4971c0df49e941b99aca10d64b9cfebf3e3dcfc895d6e72972f14531,2024-06-19T05:15:52.067000 +CVE-2024-3229,0,1,6db44865bc549d81d248c9ff4567189d0e265f2d9666ac3a1b2d3d9f5ef83f57,2024-06-20T12:44:01.637000 CVE-2024-32290,0,0,800e7992739d5b0400ed8c63993183d656650d0e339040a86ad028fc9cfdd76c,2024-04-17T15:31:50.160000 CVE-2024-32291,0,0,b7153c4f84f4dcdc9674c2de97a60dfcb3c6ccd76dc3087e39499a1f30a8221c,2024-04-17T15:31:50.160000 CVE-2024-32292,0,0,28e836ab012ba26ce6370aa637128c082a6104370d01202934f29fd84d4444bd,2024-04-17T15:31:50.160000 @@ -250390,7 +250444,7 @@ CVE-2024-32745,0,0,7c7ddc449e8c742cc889f2211c73cf5b3fd566001a852588319e29620ec00 CVE-2024-32746,0,0,15529f833c25b7b5b5022877593c49d5afec10018bbf65b56334a694e0bc455a,2024-04-18T13:04:28.900000 CVE-2024-3275,0,0,911ea91aef7f88befc82f4227a09867c3c1d7c5e1f1eaf9e7dcf15d1eb26a443,2024-05-02T18:00:37.360000 CVE-2024-32752,0,0,397ccf54ed3571b7d395be8ff9092e3859eac6f23898bbdd1a86af941d776e4c,2024-06-07T14:56:05.647000 -CVE-2024-3276,0,0,019f3963d34678902425ffe181c8b429b9a4c37c1c98b718108e0e70bcea0fec,2024-06-18T06:15:12.270000 +CVE-2024-3276,0,1,b9bc05998c576f7ede7b358eceadf281580f2a31856045bde52e20100a737365,2024-06-20T12:44:01.637000 CVE-2024-32760,0,0,67074d2cb149a548f5ca201a895261189c469e9d7c384fe074a8d7f159cb359a,2024-06-10T18:15:34.203000 CVE-2024-32761,0,0,ce6e18957362490cfabf91767930741349195476d374863f1eaf0c6108afcfd0,2024-05-08T17:05:24.083000 CVE-2024-32764,0,0,bc3d072b957e003e653de0b420ab306da82665736b4d7b512b364e6134049d7c,2024-04-26T15:32:22.523000 @@ -250864,8 +250918,8 @@ CVE-2024-3361,0,0,6cfe4bd1ffaf7a5293c549afc24c2e11b0c1549d161c12ff1c08a5c10aa339 CVE-2024-33612,0,0,0425b598952d370f8a45e51ed1855ee3ad8884230e79284f598bf766f7d5da62,2024-05-08T17:05:24.083000 CVE-2024-33615,0,0,41b28b8b67e3206017b00ab76deab87329a0ebd842ccfa49e74f1fc56f1b83a8,2024-05-16T13:03:05.353000 CVE-2024-3362,0,0,e9a5faf7bef6a2614d0c56b437a13ad3b5f4daaa51a5a3fb10813056115fcca4,2024-05-17T02:39:52.720000 -CVE-2024-33620,0,0,738c2331f034191a2882555c968823f743046d0abce76371d8c47735c97fb401,2024-06-18T06:15:11.053000 -CVE-2024-33622,0,0,5ed611c3f3f7684fbb3271f5298a5566bdc9a7da0a1d248b0cf1b094d3ecc417,2024-06-18T06:15:11.163000 +CVE-2024-33620,0,1,0ae5b4e98ac837c69d26781384b9c5cec226adf786c29c4574ab9d5cf7e0dfc4,2024-06-20T12:44:01.637000 +CVE-2024-33622,0,1,e421546b7fd8afb11c5a88c4ead6cba43a6425c1c0fd110949d5051c73c4260d,2024-06-20T12:44:01.637000 CVE-2024-33625,0,0,a7a653e26a738155ef4ac75e4b2ab045de169bb09a26b4098fd362fd9fccf1a6,2024-05-16T13:03:05.353000 CVE-2024-33627,0,0,46d1ca344f6adedbf698f1c5642ffd1e81c65d9ee122179e4726e5c233352e37,2024-04-29T12:42:03.667000 CVE-2024-33628,0,0,bd593525183e782eba9ed1d53c2c68cab7cced5143364e77f1a2ec527b353c41,2024-06-04T16:57:41.053000 @@ -250987,7 +251041,7 @@ CVE-2024-33830,0,0,4bec17a1ace431d40129f86a3decff5923e7758432d69e3320d95a816eb74 CVE-2024-33831,0,0,98c1e02fb52cc885fef491b04fbf31cf74b7566005400cd91ab0d4a14f98e6eb,2024-04-30T19:35:36.960000 CVE-2024-33832,0,0,e7d2cac687a99961b7eaca7437c17155c2c3f6529821c095b09e5161bda8425f,2024-04-30T19:35:36.960000 CVE-2024-33835,0,0,b7a1ddab44d53e7f09c5ad58cb148033d556cb74ed3d7a19809aa297e0382c78,2024-05-01T13:01:51.263000 -CVE-2024-33836,0,0,5e3480fa82212040508d6d08eb0e0a60833210b602c0a8e357d7b52cffc1e40d,2024-06-19T21:15:56.920000 +CVE-2024-33836,0,1,56a0960aeb8039f6a242dc79de612ac8aaa2ca95d4d1f5ad6698e412435b641e,2024-06-20T12:43:25.663000 CVE-2024-3384,0,0,f1db02aa38b819888be52a421a922174001b5f3c9e0abe3ab9082a168503f129,2024-04-10T19:49:51.183000 CVE-2024-33844,0,0,921cf446ac356d2881e6613aac60d162eae136862d065184d9b1201e02e62333,2024-06-10T18:45:09.903000 CVE-2024-33849,0,0,3b4368a52b5ddf8a3c305c2346a67c77b86eca45d334812e664f6d20b43a32e6,2024-05-28T17:11:47.007000 @@ -251089,7 +251143,7 @@ CVE-2024-34011,0,0,4e2e0fb5d64e6e75da5ff3561c6f86ff1f891a3646e890e015512c561d328 CVE-2024-34012,0,0,f1411ce42e8800b234994197ea4049bb546138b11d36384d7fb2107e804a3455,2024-06-17T12:42:04.623000 CVE-2024-3402,0,0,e994f4abb2ec0efc27de74bd789f4b69dd0341c920e8e4136eb625b5fd69d8ce,2024-06-07T14:56:05.647000 CVE-2024-34020,0,0,9d9b11f4db84c3770acd92b1150bad9b802c58de4fce781bba37a89c232e029f,2024-04-30T13:11:16.690000 -CVE-2024-34024,0,0,93bb3ceb24bf0689f7d5f8052b7b5dd95c2c2998faca112540e44d8667114cc3,2024-06-18T06:15:11.257000 +CVE-2024-34024,0,1,10e33d292073b520b667747f9d1f0728699da6905036151d86e343d924c712be,2024-06-20T12:44:01.637000 CVE-2024-34025,0,0,7910ed3f49f27cc3d6e29efd0456c14b8fa97ed1ac57b4183c41d497d3215ba0,2024-05-16T13:03:05.353000 CVE-2024-34029,0,0,4169ae74794d01d0e86a2d5b95da9173d7cd134e14e2c2e7fdcc6668ef8aab4e,2024-05-28T12:39:28.377000 CVE-2024-3403,0,0,351b7361a62b75fa01065ca2b4d00dead5236a2356f9f11be8885ee6cd82884b,2024-05-16T13:03:05.353000 @@ -251354,8 +251408,8 @@ CVE-2024-3444,0,0,3fed8f12f167e44fb217920a0e1abb084d18b4e359c74e2e2177b70a7af8a2 CVE-2024-34440,0,0,b35781b3e55750c4237f59d181884e306cdb8e92ede962cf40ae2ebd986a22e4,2024-05-14T16:12:23.490000 CVE-2024-34441,0,0,30a4318e62907426b3ab700c3b20e4f834f59441ac7ba3bdfe737a2f9987193b,2024-05-14T16:12:23.490000 CVE-2024-34442,0,0,d86ee0854d1f1a110f21775a8445a4cc7e3a4ab9e79237857eaed80c40028752,2024-06-13T18:36:45.417000 -CVE-2024-34443,0,0,c8d27d71371da9ed7347a58533f6552e6a4f18d8b798e7a17a55296db1ce3099,2024-06-19T15:15:59.230000 -CVE-2024-34444,0,0,6f01d8da5657bac812a99cdcbdf145b0dad4bbdfa9509d61fbfdce1a2f01e3a5,2024-06-19T15:15:59.530000 +CVE-2024-34443,0,1,94fd127b0fe85b2ba6e687043146fd73f267c48e5ad98af3e9dd0af73b63547c,2024-06-20T12:43:25.663000 +CVE-2024-34444,0,1,28f30ad6485250fac26047f41862d5e60bf1cf8b217c3355fa8d3b3620ebb4d5,2024-06-20T12:43:25.663000 CVE-2024-34445,0,0,5ae9c8efe1aaf47848c5b15a6687968aa01604c93efb870985c96be2737d2fc7,2024-05-14T16:12:23.490000 CVE-2024-34446,0,0,b445bdbcee2357cb0b4db1ab10e64a435c89bc8ae1d2fa2a306f3117c07625d0,2024-05-03T15:32:19.637000 CVE-2024-34447,0,0,6838a7a92bb676f1940cdd14d99cd1fb2165891227a7272db6bf0dd16c72b880,2024-06-14T13:15:51.950000 @@ -251467,7 +251521,7 @@ CVE-2024-34688,0,0,66fff955b629aa6883569d950a703da0f073f684f77574846b0584730e15d CVE-2024-3469,0,0,89a04cf68ae33ee1037c8a13e9431c4d00d2106abb2ae6d7191ba817489a1fcd,2024-06-13T19:36:21.350000 CVE-2024-34690,0,0,823a2e1ae33b55e0d3769be79c59e7f42483b5ff6dba621f60a0402d90d83ba8,2024-06-11T13:54:12.057000 CVE-2024-34691,0,0,827395ff4b0bf99f2642a5cd3134d1fe0effa60012a62490a349f26f4db25abb,2024-06-11T13:54:12.057000 -CVE-2024-34693,0,1,73980ddc4f5fa7a9a503f5fb0dc903aae671bf22b5815306056581c355d21186,2024-06-20T11:15:56.090000 +CVE-2024-34693,0,1,6da431cb088539cdedaef048562e52acae68c24a7fe449888c5724e281a42b04,2024-06-20T12:43:25.663000 CVE-2024-34694,0,0,c52b0ddd7913e7b99d778e62e2419069bd9d8eb90d9108e75c7e8088bb5608e8,2024-06-17T12:42:04.623000 CVE-2024-34695,0,0,d5ed5d99c8f0d08b73ea3cb249327295e787f14594542dd2f27279ab9312830c,2024-05-14T16:12:23.490000 CVE-2024-34697,0,0,95295a45851b4a50f600527e364638272a5d24a08a1ec02edb19abea712755b2,2024-05-14T16:12:23.490000 @@ -251564,7 +251618,7 @@ CVE-2024-34827,0,0,967f2d32afb0b2dfaa20d1f45e0df3e21389d96466bc0e3abad227fc206b4 CVE-2024-34828,0,0,7605aa3bedb5fc5d707a6b481c1cc91c79f17545427a53b88cbe66a14822c076,2024-05-14T16:12:23.490000 CVE-2024-3483,0,0,f497cc0f9f7ed97ac693fa9f9e6ee9a3d8c1c00c57913a6c4140ae3ca9834d87,2024-05-15T18:35:11.453000 CVE-2024-34832,0,0,5450d25a8a2a2c18ec1f13cea90692cbdaa88c98ad37b2d242e0d647addbb9b2,2024-06-07T14:56:05.647000 -CVE-2024-34833,0,0,72fbe58e3e01f562fee66fe89dd0dd0ae6fe5f1a36770a101e92430749016e59,2024-06-17T21:15:50.783000 +CVE-2024-34833,0,1,789f0a35216c1be50ffd360aabd943414abb12c109dbba03663b97841c399d00,2024-06-20T12:44:22.977000 CVE-2024-3484,0,0,77b96fc6faa401f39469e2fe8fb49203604ce091be4caf53c785afcea370dbf3,2024-05-15T18:35:11.453000 CVE-2024-3485,0,0,e8641b5678d7bfcdabd6408cac9c77af492485e4b29f63fc9dc56af18234e19a,2024-05-15T18:35:11.453000 CVE-2024-34852,0,0,a2b46166918037a96ec96511b7428ab937c28a5b7c34beca90d286eb089cfe06,2024-05-29T13:02:09.280000 @@ -251621,9 +251675,9 @@ CVE-2024-3498,0,0,5a88bde38eadc03f84603569fdec38fe83a6606de78277714e78faa80a5569 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-3499,0,0,38e1f3a6ce5aff826b19a73a4f796b980cc1161eaf58f8fada2f6f87e54573a4,2024-05-02T18:00:37.360000 -CVE-2024-34990,0,0,13ccab59c2424db60c7b433cf56fbf860b9c9b8e04719321b68e5b62c442f80f,2024-06-19T21:15:57.023000 -CVE-2024-34993,0,0,c85954a771357ba0ecc33a52666c32e422f90f8939758fd997c93a31f43d78c7,2024-06-19T20:15:11.053000 -CVE-2024-34994,0,0,f9367d66e327433fabf526300a6d5445a40e06ad7a614c7f91486a5c6960c652,2024-06-19T21:15:57.130000 +CVE-2024-34990,0,1,954e9cad148d93781e06727d2db5247f2f552d787151dbf2d18611cf67a55aa3,2024-06-20T12:43:25.663000 +CVE-2024-34993,0,1,88520e58b3968956ee44832ef9bca602378dea4f2524d5113c2eaf5052b0d026,2024-06-20T12:43:25.663000 +CVE-2024-34994,0,1,2d37bfb277f5e0193ed8c82676312446b855d68532288e194c45848265ea0e23,2024-06-20T12:43:25.663000 CVE-2024-34995,0,0,ff7295f94bdc66d877986c97deb7981eb83c3e840f72ac7a8ee7543b9685ad7b,2024-05-24T18:09:20.027000 CVE-2024-34997,0,0,cee044c4ccffe504e44bd95724dd0befc01681debe6525e4c247f664c7f74ef5,2024-06-17T14:15:09.950000 CVE-2024-3500,0,0,bd83544d3c8c82359104dcd5b032a6095cbae3178ec9c9c56ddfe242d28462ee,2024-05-02T18:00:37.360000 @@ -251755,7 +251809,7 @@ CVE-2024-3529,0,0,a5064dfdb29cc291d331e7cb349f1ad4d7941de74c2bc68b73712d362eb350 CVE-2024-35291,0,0,0cd9908c687150a1cb92a20a0728ae0d78713e0c1f8545554484da4694fb3024,2024-05-28T12:39:28.377000 CVE-2024-35292,0,0,d7611392c0d965ffc3c4722e15c98d7b6e4fb149df8eeccb24ddc9ca3fe05c9e,2024-06-11T13:54:12.057000 CVE-2024-35297,0,0,77081ae230c63fb48dd5900682a9571bd14346ef9951f53b02ff7fc86a100e83,2024-05-28T12:39:28.377000 -CVE-2024-35298,0,0,c7dc34c21e5926904863afa75e79d893b4c1f54d8405029e7ad9b38d088d427c,2024-06-19T05:15:51.907000 +CVE-2024-35298,0,1,4a93465b73521a13629db05b4a86a28e218b8bbd2011f61a842e94ebba15980e,2024-06-20T12:44:01.637000 CVE-2024-35299,0,0,3e4e645ea2334a2d70a8ac0e5a235ab378675ad9f04d95540b17d9c98a4ac10a,2024-05-16T13:03:05.353000 CVE-2024-3530,0,0,e12d930d34076470c73bc5005c248ade707b9149f13bae62cf727f0aa959148f,2024-05-17T02:39:59.340000 CVE-2024-35300,0,0,c9948d6a23b607dc905f5cedb43ddb5e762c784721f0ec88d5b26fbba2ccfab0,2024-05-16T13:03:05.353000 @@ -251874,7 +251928,7 @@ CVE-2024-35571,0,0,dcefc26d9b657207625437e63a7ceff75cf8ace6d5c78cee94aa9e811570b CVE-2024-35576,0,0,6fd29acfb903a2443f8d00c4cda4f5ba191f77d5b0b1351e41a5877536c1ac12,2024-05-20T19:34:58.277000 CVE-2024-35578,0,0,11eb62338421587fed66b0ca7ef3560bcd4370552307bc4119662b3c0deaaac8,2024-05-20T19:34:58.277000 CVE-2024-35579,0,0,271374c19e13bccc58e82fc2a49bd5a4d9e26c3bbc49d82078ba3c56ef3686b3,2024-05-20T19:34:58.277000 -CVE-2024-3558,0,0,aee6f96f049a15f414529e8404cedf675915f8c43ce91717273c55ce6036e8cd,2024-06-20T02:15:09.663000 +CVE-2024-3558,0,1,f9fa8295ef1bb8e06bc2bd8d49a335a6d7c8b402023b1332ede6212c7f0d5778,2024-06-20T12:43:25.663000 CVE-2024-35580,0,0,0345a89b9d1b0b2bc3648b28bbf695e495afdf532600f33365cca04a56d5d3d5,2024-05-20T19:34:58.277000 CVE-2024-35581,0,0,0251a3e87b13757c3a03e890126d433466629cf50c68351c4c02a6208e1e9c23,2024-05-29T13:02:09.280000 CVE-2024-35582,0,0,e476c64ba51d10b24dcb30010c383cdc2c74fb3a3a57489cdf68eb2dbeda37c9,2024-05-29T13:02:09.280000 @@ -251885,9 +251939,9 @@ CVE-2024-35592,0,0,8f6a7fbbc655181061e6850b1df1cfc42aef549b106dc16a322109a72795d CVE-2024-35593,0,0,ac49e872b55e54f210318d86332baa52d20d8879f1cd298d8a19635900c842e2,2024-05-24T18:09:20.027000 CVE-2024-35595,0,0,309ff184e92dd2b3f270cd8670573cca3fd077dcdf3378b4aa602096b5697fba,2024-05-24T18:09:20.027000 CVE-2024-3560,0,0,66c1a96b1f1d19ab8c2a91f30bb939a8ccde028ecd6951f27029cb1628de4d35,2024-04-19T13:10:25.637000 -CVE-2024-3561,0,0,7965e3bd9afcd5e625055c0d215c14fa20cb25eba48adecb93064d75fe9ec4a9,2024-06-20T02:15:09.920000 +CVE-2024-3561,0,1,87332a7f44d79f38ac016e43146b6eab96b23fbdf4b6276fc649f5d695c1c6a5,2024-06-20T12:43:25.663000 CVE-2024-35618,0,0,fc2572e9e8823eb6313bf2bb54c527fc11c4117d0d0837dc8f8794515acd3b77,2024-05-24T18:09:20.027000 -CVE-2024-3562,0,0,6a7d7b5a1f2611d38f61bd061ce33826074aaaaa2a34a86aa73a1948947295a3,2024-06-20T02:15:10.140000 +CVE-2024-3562,0,1,2c433f38634ac971df5298204e01a5cfcb61fa234d5652d870b5515296a5f914,2024-06-20T12:43:25.663000 CVE-2024-35621,0,0,eff37f6109cc46dfb019de6bac1c1e4ffe46087d96bb684a690c4e1a8342c7d1,2024-05-28T17:11:47.007000 CVE-2024-35627,0,0,152f6a140367536a1e62d9a33b0213a3c0edb39ccbba33db112f0915411e954b,2024-05-24T01:15:30.977000 CVE-2024-35628,0,0,e05989fc65de82e8f7f616462cd9eeb8a5a0a479a9823d124fa71f478b90d503,2024-06-13T18:36:45.417000 @@ -252027,8 +252081,8 @@ CVE-2024-35754,0,0,aa65be108fb30993f3885ae8163c97598c773dba7e2b2fc6fa84875158e74 CVE-2024-35755,0,0,172ec26a252feca7396ffdbe59736e2cc07ceb58de6059045747b33d7fb06a33,2024-06-10T02:52:08.267000 CVE-2024-35756,0,0,26709156d92c0e268ef7cbecfe5b4508148e493e88bdf919829cd3fadab67b01,2024-06-10T02:52:08.267000 CVE-2024-3576,0,0,da3479f65547a923ac9b6fc5d4e01aab352d357f2ab0f89f14bd434e8562f642,2024-05-07T09:15:38.747000 -CVE-2024-35765,0,0,deb6dfcc3ba9a0ce3a73fecb507dcf23f2342eb09beb256895023c89d68654c0,2024-06-19T11:15:51.117000 -CVE-2024-35780,0,0,9a822fa356e4ebfdfe077ed4c7eb74f60a0195815ac65ee5ffcc528f96b123d9,2024-06-19T11:15:51.370000 +CVE-2024-35765,0,1,2b4b05960266dffe197f924005c89655c3d35c1a3b09e1011c3ba498aa784944,2024-06-20T12:44:01.637000 +CVE-2024-35780,0,1,0cb83863c03783254bdbb259245f43349fceaa55402150e68b96501fc1a18c7e,2024-06-20T12:44:01.637000 CVE-2024-35782,0,0,1a0373b5f1f7deeeedd7f390a32d36b4e5b6a7fa2bc73f703a0a9b8d71fdc6f1,2024-06-05T19:50:20.463000 CVE-2024-35784,0,0,777c9d07d4e578c087e7dca5451415bcc43ec9a1a18957eb76a5068c9b97dba4,2024-05-17T18:35:35.070000 CVE-2024-35785,0,0,2d190f92b1b0e8f457adf5fad73410cb0f4e785e27759c42f1852e8078e97e76,2024-05-17T18:35:35.070000 @@ -252229,7 +252283,7 @@ CVE-2024-35966,0,0,c5fe47d4bcd9271f5e602a237b487a254165526cb77cec4c5b3e9d6030961 CVE-2024-35967,0,0,bb3ff79041a63b72013c8e6fdadf5992d4071019718c97182c4796281f76705f,2024-05-20T13:00:04.957000 CVE-2024-35968,0,0,a78badb5439f85aa8efb4a9cdf528d05f2c802d5a327056a2636c278abe68375,2024-05-20T13:00:04.957000 CVE-2024-35969,0,0,f72d3b48ca1d088451c0875483e2ba33d5a31cccef78ceaedc36918359206c4f,2024-05-20T13:00:04.957000 -CVE-2024-3597,0,0,640564eea7f6156724d73d5a0cfe16383f9b118bcd1fe7c2e5e2a524d17354f9,2024-06-20T02:15:10.363000 +CVE-2024-3597,0,1,61db435ecdadb6c970a4dc16fc28877bfa4b9d331964319c3be4ca6f562d7128,2024-06-20T12:43:25.663000 CVE-2024-35970,0,0,6dc1144434a50796750071e0c3d32f1adfe548b8c17aaa45ca8711be6b4aea01,2024-05-20T13:00:04.957000 CVE-2024-35971,0,0,789d8533d8a5b9480a46b5c467b61e45b7f385d5215ba9c26c6a1dfe1f86553e,2024-06-10T18:15:35.383000 CVE-2024-35972,0,0,8fcf39d4ace4f1fcc0a244e6329df0b275111c4ac22e4ce79dcba8599cd853de,2024-05-23T21:04:02.433000 @@ -252284,7 +252338,7 @@ CVE-2024-36016,0,0,4cba6e6a75f627dee0859835e4746e030cdfcba67d3294485222008ad5f51 CVE-2024-36017,0,0,06b3fa4d5fc5124fbcb85f162223c7c3aac5c8e863443f7f4e826cb80c4f6854,2024-05-30T13:40:12.593000 CVE-2024-36018,0,0,3a8206a02c5adfc67a2a516b8b16f0711b57e1035b88218c63b323725b6cdf46,2024-05-30T18:19:11.743000 CVE-2024-36019,0,0,cbde2a6e185dae769cb5f8294d3446f38fd341f16f132fc23455025199fad60c,2024-05-30T18:19:11.743000 -CVE-2024-3602,0,0,973d9791c8041d94ee624935706a459dce9d0fa1d56f51c81acd345a82fcc68c,2024-06-20T02:15:10.590000 +CVE-2024-3602,0,1,94acaf9dc68464912ead419350d2fd489a81a9c3c12dd5ae8393cf11facf309c,2024-06-20T12:43:25.663000 CVE-2024-36020,0,0,d1532c8fb5d7b7afa7aea5593f1a6ab29599f87f13e46423cba38d38e702b7e0,2024-05-30T18:19:11.743000 CVE-2024-36021,0,0,94f9365ed1db16f5cf54c6394739d97158e9ef58d8893123ecd517ca9b226174,2024-05-30T18:19:11.743000 CVE-2024-36022,0,0,20f730e70cbf9f258d0a4f7215eac5cd45435a01501c51da7968f945b5992211,2024-05-30T18:19:11.743000 @@ -252306,7 +252360,7 @@ CVE-2024-36042,0,0,2ba301066fcf3b5e2098ddfbb2759b29cc55ab5a805cf9edc9ebe22e6b436 CVE-2024-36043,0,0,a692d077d358c1feb0a509deb9a8e16caf647bf207b7ab7a4cd103038bbab39e,2024-05-20T13:00:04.957000 CVE-2024-36048,0,0,28009f5c9c89d66914a954a3622c5cc8d7b761845f43a58d1b9db13955c9fa8c,2024-06-10T17:16:32.167000 CVE-2024-36049,0,0,3a7a1da30d4597dad4c167032717d4ea0f9bb4c5d5396bc121febaf5ae683a7e,2024-05-24T18:09:20.027000 -CVE-2024-3605,0,0,da2c81fa30bf94940472a93d78752d6912620435c83e9734ff6d129391208ceb,2024-06-20T02:15:10.817000 +CVE-2024-3605,0,1,c493df18d7bb5f847e1a975a6e775c5f6fae79bc93247baa5bb2cc57f81ebc95,2024-06-20T12:43:25.663000 CVE-2024-36050,0,0,4c307008c713c918a6e3b84da1e5e49b2b2247354b7102850872f2f1076c6edc,2024-05-22T16:15:10.777000 CVE-2024-36052,0,0,8db219128822e3b435341a720fec4da51967df08eb27bb5fb0af45f420ce346c,2024-05-22T12:46:53.887000 CVE-2024-36053,0,0,672a3b34a9bdb19210396687438a3a5963248f4f357ce5db05db5d249614922b,2024-05-20T13:00:04.957000 @@ -252335,9 +252389,9 @@ CVE-2024-3611,0,0,b6a9e7e031fc264aaf6cc25eb2de4637a54a3c74ff1ad6ab29710fbea0fb99 CVE-2024-36110,0,0,60de6d063a43c2488fb7938eb212a9d443b4f1b9215af12070cdde5c64f618d1,2024-05-29T13:02:09.280000 CVE-2024-36112,0,0,fd8205b7c79aea233d5b23b835a6806c74e0d450d4ed81f7488de46ba99ce9ca,2024-05-29T13:02:09.280000 CVE-2024-36114,0,0,cd6667af901bf4e55598a9890cfbf772045b36365134bac1827f2ee46e0e9bfd,2024-05-30T13:15:41.297000 -CVE-2024-36115,0,0,77ffb340facd4eb973eac52381e2f6a69c57f16112d9a1e9c8a11631b93721bf,2024-06-19T18:15:10.597000 -CVE-2024-36116,0,0,97d02985e00df6f7d772ee84aa2631c7ca3d05edfa8f47e4715c606bf2662bd4,2024-06-19T18:15:10.910000 -CVE-2024-36117,0,0,3a38fcb17cdffee17f9ebc04549ce42d49dd9d7c61932ea40dda2b103f15627b,2024-06-19T18:15:11.220000 +CVE-2024-36115,0,1,b311a15fd16028af807263ed1142ace2563c92e7aaefec86b4b1542690ee4e98,2024-06-20T12:43:25.663000 +CVE-2024-36116,0,1,ef7ea8f740c41e3dd566d13df65930830eeb67957abd08ff59d80e7230ed23a9,2024-06-20T12:43:25.663000 +CVE-2024-36117,0,1,5e2b3c2a14f6a225849e1587377f2330efe991455c2be4361777e86aa5bf79bd,2024-06-20T12:43:25.663000 CVE-2024-36118,0,0,33d8fbf029e8489b5c9f0a8940761bdd6087754b4000c59931582a52c8a8908f,2024-05-30T18:18:58.870000 CVE-2024-36119,0,0,df322ac6443fcc8a013c93b7e5a35f3678792028e0c0bb1f44fa863251664f98,2024-05-31T13:01:46.727000 CVE-2024-3612,0,0,d6528427cbb589467c111cbd40a18dd09640d3302d8baf887860f351407e958e,2024-05-17T02:40:01.520000 @@ -252459,7 +252513,7 @@ CVE-2024-3624,0,0,e0ac19607b4c8d1214127703973418b820b7283270ffca198194137ef8f419 CVE-2024-36241,0,0,ec13df73bdae0daae51b14875ab9159491333aae8ecd7b32e3b3849163ae270e,2024-05-28T12:39:28.377000 CVE-2024-36246,0,0,50338f85842e71924c1397e2b0a309f647146226696bf59a5411ba0e6e468e33,2024-05-31T13:01:46.727000 CVE-2024-3625,0,0,bb7fa72c43d725aef9f66641f31c3359a614ed8ba414acf9f05b8e44148cef81,2024-04-26T12:58:17.720000 -CVE-2024-36252,0,0,caa82c94f4afcf99a4e6f98775aab93f1094ac4d77c179067af7f3989e090454,2024-06-19T07:15:46.200000 +CVE-2024-36252,0,1,15f198f9d24050d47b4b65c7729189d555592843e3d7c2313de650ff4411e911,2024-06-20T12:44:01.637000 CVE-2024-36255,0,0,22b21684452ad4563618ad5cee66dc719af723b04c8a1647fe9cf6d970347f9a,2024-05-28T12:39:28.377000 CVE-2024-3626,0,0,668faec6d18ac8a7c33197af94901aaf7ddac1dec4c77c1d646fba224d5f8541,2024-05-24T01:15:30.977000 CVE-2024-36263,0,0,8fc77ae12c809e003508687bca8ef69500efdb9e489f26efe8ffb68dd267fd3b,2024-06-13T18:36:09.010000 @@ -252467,7 +252521,7 @@ CVE-2024-36264,0,0,3852f3a1f0d8a2d4f62090f3b6254d16b37a584c2a4799814e318aea1f241 CVE-2024-36265,0,0,00a9e362e8a489eb7027d68fd71b14b08824e37d9652a79a38b01c7bc61baef1,2024-06-13T21:15:57.170000 CVE-2024-36266,0,0,251ca14083666637d83281029e46640454efd455680ea38b3c5a664d41d8a836,2024-06-11T13:54:12.057000 CVE-2024-36267,0,0,5b402628b4c430b8eab614a5b3330f6f2d186537f83ff9a60bb1a91e4b3c3cac,2024-05-30T13:15:41.297000 -CVE-2024-3627,0,0,27cc7dbcd171ebd08dba9b8d84497f559c447113f2a8152b6630981255d91d23,2024-06-20T02:15:11.040000 +CVE-2024-3627,0,1,f5c20db254155e1980cc0c244f583a6a1536d3adf64c11755694648c0d5e1776,2024-06-20T12:43:25.663000 CVE-2024-36277,0,0,20d47326e280adb94d9059aa48d208d3f478f327ce890b8688aef81aa91e0089,2024-06-17T12:42:04.623000 CVE-2024-36279,0,0,3325b8af913fac0d163d5be9a8802e9f76dc63912c8cffea0ae3040270976e9f,2024-06-17T12:42:04.623000 CVE-2024-3628,0,0,ad2a38a3d431944b5239dd67ace3bcd2603e3057c8d0a04d847db45516b0c9ea,2024-05-07T13:39:32.710000 @@ -252552,7 +252606,7 @@ CVE-2024-36471,0,0,7bfc01a91f1334cb206068a1dfaffdf29e68b3bf2783355d50e083ff5a6a3 CVE-2024-36472,0,0,9bfd7afc4b2e800059c7e7a1cc84b36bb079950920b1605d92cfb4dcf501fc09,2024-05-28T17:11:47.007000 CVE-2024-36473,0,0,fdab9cfd1652fb2a67390d3a8e49efbc4911425ddf31224888be2ea2f102443c,2024-06-11T13:54:12.057000 CVE-2024-3648,0,0,347cd63bf86e6b194279224a49f79f49cff1705e1f9b364650443227c716e8b1,2024-05-24T01:15:30.977000 -CVE-2024-36480,0,0,53bc541f89f157ad3d204acbf1cf503ba51c7a7167474a19ec18c0fd6e59f6d7,2024-06-19T07:15:46.340000 +CVE-2024-36480,0,1,e44d83876d2dae748412d2e7075759ad0769387e9cfa4e370e78d4e4f59fcc0e,2024-06-20T12:44:01.637000 CVE-2024-3649,0,0,969867829e20da4acc88ade671a27808c021dddbe3e27e051d2004e683670e61,2024-05-02T18:00:37.360000 CVE-2024-36499,0,0,077c5caf8d301ff2d1947e18a01670bc02e5c0dd9fda48352816e5be2251d0eb,2024-06-17T12:42:04.623000 CVE-2024-3650,0,0,e078ac649d7d0d133fe9598e10336739bc9d365236ed72d408805e3868c3d439,2024-05-02T18:00:37.360000 @@ -252562,11 +252616,11 @@ CVE-2024-36502,0,0,af0ea55ba6dbd08cf23c5f8732d2aeb0cf79fdfab13bdf5e07cadc4434254 CVE-2024-36503,0,0,3aef981902bcd0cfa43896ed1ada7c9ec64d59690838f1ba35c268bf26e5218a,2024-06-17T12:42:04.623000 CVE-2024-3652,0,0,455dabb71414a7592172807b25da69c5818ecc78456d9f87c63904d4c0988a33,2024-05-01T17:15:37.793000 CVE-2024-36523,0,0,779ff20f3e54c54b68fa38cf8a73a6874fca821f18024ef38fb974b398395dd0,2024-06-13T18:36:09.010000 -CVE-2024-36527,0,0,2b0ce26462ddf4094a9f42ea54b908cbb2586dcbcfee6531e1c43b55113e0148,2024-06-17T18:15:16.767000 +CVE-2024-36527,0,1,78d7584b160535d1351b569ab12493248c714d50ee4dfafee49cf0501ef01071,2024-06-20T12:44:22.977000 CVE-2024-36528,0,0,f25edd031c479e2eb08ab34031d71804f3bb9f2a7bd4f1a1d0b25d391d002135,2024-06-10T18:06:22.600000 CVE-2024-36531,0,0,991b1a5a568679e84b92f85516ddb5ed86f9e4a97046e45c71aa818ce6df4847,2024-06-10T18:06:22.600000 CVE-2024-3654,0,0,954800a828ed246c147def14a6599156bd18a3e2cc72072dd62b0ab02b4bbf53,2024-04-19T16:19:49.043000 -CVE-2024-36543,0,0,d296ac07647444738f564112c0fbd0f6cdc70c839f2aad61af43a607bcbd5052,2024-06-17T19:15:58.353000 +CVE-2024-36543,0,1,96dadbfc1ecb488523e1445b9cca4f88005d70a44d460cd8a195bc76559786cc,2024-06-20T12:44:22.977000 CVE-2024-36547,0,0,6660ddee6e567c7988e43d4b24008e0896770307b9894b7b829c762e8a195005,2024-06-06T15:16:11.897000 CVE-2024-36548,0,0,9d28d8e8972db5bd27a8a65faaafcca56f3bdf2175ddc670e3a757d6c577d105,2024-06-06T15:24:02.577000 CVE-2024-36549,0,0,ede738893685493385854bf4f5b6680c7d976cf01bd2e0f64b85833020e8a996,2024-06-06T15:24:35.210000 @@ -252574,16 +252628,16 @@ CVE-2024-36550,0,0,affd201d52525b08fe9dc0ac43cf536ec50f780fc23bf861db62d86c798cf CVE-2024-36568,0,0,f6757785c01c43727d227a9340ded7869db334138c1e07644080e388c657d4de,2024-06-03T14:46:24.250000 CVE-2024-36569,0,0,cc62a3b4fb5fe5cf7891883c6e12ba14de517f9765eb42867751af3c3e50f0ad,2024-06-03T14:46:24.250000 CVE-2024-3657,0,0,e0e9aa98b4bfe8d4d80395efd4c4293865e72a7d88d35e61376b8312bdae8c3e,2024-06-12T10:15:31.447000 -CVE-2024-36573,0,0,750ebe45272a4f2bbd917f456a069d3e63271e35a219c08d85bf8093c0a0b6e5,2024-06-17T16:15:14.947000 -CVE-2024-36574,0,0,64bd9cd44e2422837b446ec1e39651bbbef09e30ab3a39b8f1b8b0361052792b,2024-06-17T16:15:15.040000 -CVE-2024-36575,0,0,ed36a3dda7699a6151615dd0f4a8ba608593c659559e706aa039085e6ab6425e,2024-06-17T16:15:15.140000 -CVE-2024-36577,0,0,701237de0aa421f725f50cae5349a1b7b236344f940da970bc8c4371b26d1374,2024-06-17T16:15:15.233000 -CVE-2024-36578,0,0,54d498d91b0b299bd1280e0e84877cbb031dddd415152caf68b05edc849f7e06,2024-06-17T16:15:15.333000 +CVE-2024-36573,0,1,fe17576bb75552079566dd5d6c7a5851d1d43b2b8ea1d59b23b3fc0b98ec48b6,2024-06-20T12:44:22.977000 +CVE-2024-36574,0,1,0848b880836181907f2f643113be33bf38b0f27e048a009439c6d54141479ec7,2024-06-20T12:44:22.977000 +CVE-2024-36575,0,1,5088cc8230af34a6553ab5b03d7ac65d8e6dd090c538b3da6412c983cb2c9c3d,2024-06-20T12:44:22.977000 +CVE-2024-36577,0,1,0a24527bd7e0655c846a00acea63f64354529ccbe7e2b776a57bb2f876d338b0,2024-06-20T12:44:22.977000 +CVE-2024-36578,0,1,5f9a4c402bba76c7557cd8e724384718288c5ac61b96cd4155ceb9c4cfd58bcb,2024-06-20T12:44:22.977000 CVE-2024-3658,0,0,788a6c57a5cc1d17a8f73184ec3f2bfe6dae89c54b4197447e7e87a36bebe3cf,2024-05-28T15:15:09.703000 -CVE-2024-36580,0,0,982f3c6e1a409feccad1e6cb4897a8a8d95dbec5c8d00651e139725a763f9359,2024-06-17T14:15:10.227000 -CVE-2024-36581,0,0,b0b55ea5afa036e7fb18c148b1b9ee7a2c8d7dd817cbe56e30c27abf908e433f,2024-06-17T15:15:51.130000 -CVE-2024-36582,0,0,cd975f5489e3afb4887de7292d56befb6ee6fe1867e756ee11a14f65cfd00746,2024-06-17T15:15:51.243000 -CVE-2024-36583,0,0,df878686601707220f20331c39cf545bdf859668e3801b689232bee9d5ed1b83,2024-06-17T14:15:10.330000 +CVE-2024-36580,0,1,d5906284499fdb7c595238f9ae8dcc879081c712e4783aa05752ed465a0ab190,2024-06-20T12:44:22.977000 +CVE-2024-36581,0,1,c413c68ea18d4a2466915c4cf84a760fdc7347d8011360e27296b6648f443897,2024-06-20T12:44:22.977000 +CVE-2024-36582,0,1,45f87142f9a5e9e5e5696a5ee24e464582757274df8404620787ffbabef5ee66,2024-06-20T12:44:22.977000 +CVE-2024-36583,0,1,4ed35952c0aa0ce8a7976492a381da1363e45eef5c87a4eb5e0be4b43b47803c,2024-06-20T12:44:22.977000 CVE-2024-36586,0,0,302fd67d5bf11292556b5a817ae025f56479dee1787f148e919beea3947496ec,2024-06-17T12:43:31.090000 CVE-2024-36587,0,0,906aafdc070e7118cc2f1e5d5e49e8746361ad3b3c3a10318730a2cccba4b3ea,2024-06-17T12:43:31.090000 CVE-2024-36588,0,0,041c855a0e5ca096dd16030ca52f4146f7b727baaf22aa52e219f4870ac0578a,2024-06-17T12:43:31.090000 @@ -252611,12 +252665,12 @@ CVE-2024-36670,0,0,fdafe9c66140e5a2018ce6b3a330b135107007226ee1c746bda0de7803753 CVE-2024-36673,0,0,c3fdb493385fd7349af8a7f0f647aa65a0c25320dc90b659d1425197d89ce5bd,2024-06-11T18:27:20.950000 CVE-2024-36674,0,0,80518ec37aaca3163e2f2a38f2de20c8dedbcb7f0e795fb382e532f1b66ca868,2024-06-03T19:23:17.807000 CVE-2024-36675,0,0,d8b3bb8705c0d8b166e699377141fb97d9735e483700819521a5fc1573c26a90,2024-06-11T16:49:10.457000 -CVE-2024-36677,0,0,93c22664235a2af49937c6fc169e3dce04c8914727d28c9438d6cea425acd789,2024-06-19T21:15:57.257000 -CVE-2024-36678,0,0,57eba006cdb8a72766df2b7b61cd7cd0ab7a4a69f11d5e1e237eda7b4e0b84a7,2024-06-19T21:15:57.363000 -CVE-2024-36679,0,0,58af4cab32f0095f9b3f92c7e0c895f2f34213c0eadfbb8fd8a338d56130861d,2024-06-19T21:15:57.470000 +CVE-2024-36677,0,1,9f75570545ecba2b72703a8b10ef48a3072dcad0b0da2c3a9395d1cde3c4cf06,2024-06-20T12:43:25.663000 +CVE-2024-36678,0,1,b40bcef505929051186338018132624ab6cbb572787979182cd8c6d26989404a,2024-06-20T12:43:25.663000 +CVE-2024-36679,0,1,8821e4eea3e4aeed8d65a516b06861a5717cd50e7124b3274b0fd92bade0c86c,2024-06-20T12:43:25.663000 CVE-2024-3668,0,0,49d55bc0cfb418bcfc9437877f4056373badba24215047598ce2c0a1a6dfb761,2024-06-10T02:52:08.267000 -CVE-2024-36680,0,0,a2785cd07a34b06766cbf6cc40d21f8414f9fa61543ff95041c99981f6d966d4,2024-06-19T21:15:57.577000 -CVE-2024-36684,0,0,2cb04fa49b7499bc6667d7d1d4a5491f6ca6eda601e1477df9f1d513e4c0124f,2024-06-19T21:15:57.680000 +CVE-2024-36680,0,1,d0d5945762cb2164a2282b055a60546e9c27ff729e4565b5f8f11eb263a62624,2024-06-20T12:43:25.663000 +CVE-2024-36684,0,1,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 CVE-2024-3670,0,0,c82d0130c8edc16344a78447d1514c5ffe18d421cd344e5799606a7730bedf8c,2024-05-02T18:00:37.360000 @@ -252776,13 +252830,13 @@ CVE-2024-3697,0,0,600d9314ffac8217c56b5ddb9a6dd8f383edc3a52ae15aefe26cd04d9d92b6 CVE-2024-36970,0,0,7821872f33932cd23581e3f08933e1120512f95b8bffb9a221042f6e182c4c03,2024-06-10T02:52:08.267000 CVE-2024-36971,0,0,7baf68ba8d6177e5c800107eb44bfd99f2323f2978ed8bf3a29a9bc948d8cb2e,2024-06-16T13:15:52.820000 CVE-2024-36972,0,0,c8949e99c51cdd06e16d761976785fb3e8ba887f5070dbd12308139f2998e944,2024-06-16T13:15:52.947000 -CVE-2024-36973,0,0,aaf9d958c8593ac07f0f724040e3aeb13ad0df1753e4f68e9b0d677119862905,2024-06-17T18:15:17.043000 -CVE-2024-36974,0,0,523b92247cf66f6361db9b7c957ef5cd9ba0f981d05a3392398bdf9da78a3660,2024-06-18T20:15:13.257000 -CVE-2024-36975,0,0,83243f7768f45e89c82022b7e0d47c20c8e71e87e1ebb54d3fc69837c26fa479,2024-06-18T20:15:13.340000 -CVE-2024-36976,0,0,1a806a37074af8f0890b0e258ce8f1566b67951e049fb8c5dfd1a1cd88f441a6,2024-06-18T20:15:13.437000 -CVE-2024-36977,0,0,ecdf5cde1ffeedc1b1b2928831c6b77a75e30b55c998a79df5a8fc5f4517fd8c,2024-06-18T20:15:13.517000 -CVE-2024-36978,0,0,075fd6eb1f84e32876f8b1032a0d8079dde4060e45e3db25cca04364dfac60a7,2024-06-19T07:15:46.437000 -CVE-2024-36979,0,0,5191c81ea8cab7061235fec3d42d83ac1364ca147ec4c691a315c2daf9cb1a95,2024-06-19T14:15:13.620000 +CVE-2024-36973,0,1,387c9e38d212abc65afd4ded901a91456257cc0fef43ab9c83516046c7bf0296,2024-06-20T12:44:22.977000 +CVE-2024-36974,0,1,2b24f5ce54c274e894e2ad84676869cf1c4b33386be349e999367511afd70adb,2024-06-20T12:44:01.637000 +CVE-2024-36975,0,1,fec62453d9d139bbf281f7602593c857ec33f10da19c238179e6eeabc562fa45,2024-06-20T12:44:01.637000 +CVE-2024-36976,0,1,eb6b0d3dacc448944abcbdb8dd18e68e059e9c13cf8dbd6d40a9f9c53333ef58,2024-06-20T12:44:01.637000 +CVE-2024-36977,0,1,211593e58fc9135f9893829a9f2e1a8571662349bd4f1f6e872c0294a0b0ded4,2024-06-20T12:44:01.637000 +CVE-2024-36978,0,1,3d3bc88bdce6dcade3539b03f34f96eb9f26455b40c5b7e059adf0af155437a1,2024-06-20T12:44:01.637000 +CVE-2024-36979,0,1,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-3700,0,0,f1913b84964a9a87ca4f78bbad55a262819a35385e2c066c91eaa7c4a1891262,2024-06-12T17:51:52.710000 @@ -252820,12 +252874,12 @@ 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-37079,0,0,46a9554a9ef2eb3870709d6f231ffe9e1b00d960bc980453a2ef4953cc9360b2,2024-06-18T06:15:11.350000 +CVE-2024-37079,0,1,9bbd76d5444005ceb39d0ac68b0b4e335d82d5da3fc1107a95914993fa985b9a,2024-06-20T12:44:01.637000 CVE-2024-3708,0,0,09132fb1644ebf0c808002aa8ac15b19f13ae71d0beb378f7a9664a5ae685f9a,2024-05-24T01:15:30.977000 -CVE-2024-37080,0,0,10e295609ce11c4b9f8de83bc5c9d03a60a3c7fddf058d2fd3d7811220f833e1,2024-06-18T06:15:11.640000 -CVE-2024-37081,0,0,a260f8619b104800ca02613b64e1047ee007ff0595cf7675b1372a3d57029c23,2024-06-18T06:15:11.900000 +CVE-2024-37080,0,1,c953e426661198e9665c742ef09fb44af751efb40a1f491b02b9f5389b1d3d21,2024-06-20T12:44:01.637000 +CVE-2024-37081,0,1,462e18659ef5f7f4965b221966912e397932217f36959496e3a505bf8400d835,2024-06-20T12:44:01.637000 CVE-2024-3711,0,0,00ee502ae0ae8bdc802cd38eb1ec1e1356c10e1c18d766a4effd20297a066f55,2024-05-24T01:15:30.977000 -CVE-2024-37124,0,0,241b9f17ed119afd87ddb25cb7a5c08f2fcd12bc3731c8b59dc823a1ccc5f950,2024-06-19T07:15:46.547000 +CVE-2024-37124,0,1,bdb1c2622a72a7efb103c3f5603bc06acb88520168a2b939ad78f62d410bde2b,2024-06-20T12:44:01.637000 CVE-2024-37130,0,0,e0f79c9f14be5102570781fc06be35c79666eecf04eb579171e468c9a760aecc,2024-06-11T13:54:12.057000 CVE-2024-37131,0,0,9d8793df78437fefb0a970a364558bdad589a0c15e132432497cef4b2151f46f,2024-06-13T18:35:19.777000 CVE-2024-3714,0,0,29d3de80cc1f6e0ff07b09e17d8d58f6e17e5f0164ed94da7b2235ed17131c18,2024-05-20T13:00:34.807000 @@ -252835,8 +252889,8 @@ CVE-2024-37152,0,0,d5beb8b2bc90de99efc40fac5a89948f3b2a0d50610a65220e35a91d41ce9 CVE-2024-37153,0,0,61a2831c55890f9a410cc075d806b38e60c3b9609259f6ca16f7a060d646905b,2024-06-07T14:56:05.647000 CVE-2024-37154,0,0,58669c60bd370ee58122b9f7af67de36a61a42702559484c7a8e000321217599,2024-06-07T14:56:05.647000 CVE-2024-37156,0,0,7e333f2d85e8aebcd8a0c3a0c10b32f6169582c9ae7ef770c4979e919256c1f4,2024-06-07T14:56:05.647000 -CVE-2024-37158,0,0,5348c4c38275397f3520772b12ec38e3c593ac69b019bca4b488d2a1b249386c,2024-06-17T14:15:10.430000 -CVE-2024-37159,0,0,d344d7501c8b30ba12ac270cde5ae0c0a3bba069f84ba8f18f004f87a5111c3f,2024-06-17T14:15:10.693000 +CVE-2024-37158,0,1,8ac0d3bf9c6c192639a5d4d9fb3db17c299ecb245abca350c3fea5ab3509483c,2024-06-20T12:44:22.977000 +CVE-2024-37159,0,1,9e5b9e265ca524a89ed21134c1c7f4fe52ca92049373907e8a27961a87de80db,2024-06-20T12:44:22.977000 CVE-2024-3716,0,0,cd48c9d9385d749e7f6a760222e7bd3c34be9d8579ea908584dc3532500bc083,2024-06-18T18:53:28.927000 CVE-2024-37160,0,0,76b6b47acfcb84ecfe47e9095986f2ff3f5ea200ba6d7cfb795a680bd69b22ef,2024-06-11T18:22:50.097000 CVE-2024-37161,0,0,9c5192d6b3269f1f004ac7a8938b555cac9b29a8a4452c22b7bb7bb22e8cfd15,2024-06-13T18:36:45.417000 @@ -252876,7 +252930,7 @@ CVE-2024-3730,0,0,a30960de1676c855ee35b61976bc4581959cd1a98a7ba3127a461fb7fc9551 CVE-2024-37300,0,0,7a8b0144b5518f42a2503b23de88b2ac1dd643d024476f6cf726712d7722e352,2024-06-13T18:36:09.010000 CVE-2024-37301,0,0,450b2bcc32537519af2d171a1a4f4dec398481df24494eefa7c4bfacafd1cdd4,2024-06-13T18:36:09.013000 CVE-2024-37304,0,0,58f0056f03946090c8e002d0e9ba0984fa448eb3acaa7f846a712c694162376b,2024-06-13T18:36:09.010000 -CVE-2024-37305,0,0,756a91f02283d9df256d9a54b14b0910f6d0e8069b80da21c581159e3dda387e,2024-06-17T20:15:12.880000 +CVE-2024-37305,0,1,1e31554b34fe1e9e35aa717c906566f811d2254318b33f2cb1b7f9c22a7dba75,2024-06-20T12:44:22.977000 CVE-2024-37306,0,0,c42be228ed7af3d19c55f98cc69863314df6372a103fb19662ff1ada5ea07223,2024-06-13T18:35:19.777000 CVE-2024-37307,0,0,307a9077f465a844bb3929ae05a1dcebcb701d8b2ae344b6539171566dfccac0,2024-06-13T18:35:19.777000 CVE-2024-37308,0,0,789ac1ee79bf50a380c8842b793e1f03cbcea96755a8db8c09ad817d1922f353,2024-06-13T18:35:19.777000 @@ -252903,7 +252957,7 @@ CVE-2024-3738,0,0,0968d9618a10c036b25eaa390531466819e491a5c992bcf4c715af4b591b91 CVE-2024-37383,0,0,c0362d3d95fe11bdc30f3c36377b27485de734d675fe1b90f60703cfe5051656,2024-06-17T15:15:51.517000 CVE-2024-37384,0,0,2bdb7db18773042dbfcf7b4442179738e059134c1a70f1a6d09b92e8cfe2872e,2024-06-17T15:15:51.640000 CVE-2024-37385,0,0,ab67b8a0f073ce7f5c28ca11584627dbf70b59e11b1337a1068ce1887aeb0943,2024-06-07T14:56:05.647000 -CVE-2024-37387,0,0,0f25007f9cfc5b749d503760fb293573c0590167d96792567102a081a7a4b4c8,2024-06-19T07:15:46.647000 +CVE-2024-37387,0,1,b989b6f9a9181325e6202ffc64af4007cc6f76345f94702c71f04fd2017fece5,2024-06-20T12:44:01.637000 CVE-2024-37388,0,0,78091082c96da1cca6d1b3a881a45160af8428a4ada3a4ba554597b78ade9a76,2024-06-07T19:24:09.243000 CVE-2024-3739,0,0,18ca969c974b63c6d16494fbcc2d63756747cacc5947332fefb20d9c592537e4,2024-05-17T02:40:06.067000 CVE-2024-37393,0,0,adb4710ef8d4e8e5b898aa80bff6a41a92b599e232f1db44a8b62c91938837ef,2024-06-12T17:56:23.390000 @@ -252932,14 +252986,14 @@ CVE-2024-37570,0,0,a374041c2622c9ba66d2048315fc9e015af6a8717cce4f8beb5b598003986 CVE-2024-3758,0,0,3ea9ecbea279ca1eb1159e542db09b1cab2d2435be79c6a6a563dc4d73ca4285,2024-05-07T13:39:32.710000 CVE-2024-3759,0,0,20211226ea875c33805e71e9c0afa18c7ce1ad112702c8859afd48ee84347f62,2024-05-07T13:39:32.710000 CVE-2024-3761,0,0,c0af44e486388b5bef077e784125f415f33c54c3c3a8677d0ab80af1f3e8df6c,2024-05-20T13:00:04.957000 -CVE-2024-37619,0,0,aff15bb57076d686e36cfc0cbea640138a4be0bdf788157c911222ef6978e0ee,2024-06-17T14:15:10.943000 +CVE-2024-37619,0,1,fb18acad5ba1a8224fdd33f26f78349bad39bb24158d07ebb826ee85065e8012,2024-06-20T12:44:22.977000 CVE-2024-3762,0,0,3a4d7121b46153c733feea020bbdc2b15c8dd6dac7706d18d5d6cc6fdd5731da,2024-05-17T02:40:06.647000 -CVE-2024-37620,0,0,65c8cbdb666c9b6e45cbb7ae81638f154dcd51e35de72d38e7d6f00aa2f65ae2,2024-06-17T14:15:11.047000 -CVE-2024-37621,0,0,c1bdf46db7eb64b6e9a6e3de8cd799d018a10d4ff1e8435f986b6d06b3cd47a0,2024-06-17T14:15:11.153000 -CVE-2024-37622,0,0,78aeca349bc14588eda44bd7a4c78d1fbcbed8a48b4d83a986c688922d0df66c,2024-06-17T14:15:11.480000 -CVE-2024-37623,0,0,944d49b0a57aeaa4709234137d8a429fd4f7fb0faadea303b4a9712cde94e38b,2024-06-17T14:15:11.580000 -CVE-2024-37624,0,0,0ea6fd2180eb9e22efaefdbb14b9e7e8f8ad410e2d99091c575d83f933d07fd4,2024-06-17T14:15:11.680000 -CVE-2024-37625,0,0,4fa37387021ef2e30a5489f0ba675157dbc50507f786d9f4806574acc51cbd40,2024-06-17T14:15:11.790000 +CVE-2024-37620,0,1,37467c263f3a10bfc6b745e644b5a43ae65b50bb4f2457ed19a0f152bb8e9d4a,2024-06-20T12:44:22.977000 +CVE-2024-37621,0,1,5130c0bcc2cba29b045247f3ea9bd16107f039194b4374647a532239a8d33439,2024-06-20T12:44:22.977000 +CVE-2024-37622,0,1,c5ce5e55072739c990e174478f39d68c083974ab6129554da5a4e33caf326895,2024-06-20T12:44:22.977000 +CVE-2024-37623,0,1,d8395bc9979b8438bd8a5fcda64469a56ed1c7b2c754f62d69464aad225f7a8d,2024-06-20T12:44:22.977000 +CVE-2024-37624,0,1,c67dc5f200fd7bd4558aaa3dba0b70e30788e7a5243808acd6e7683dc3c78ae7,2024-06-20T12:44:22.977000 +CVE-2024-37625,0,1,a02e4bb7abe01fe5f5451064a7b8497a50e5fc7fa5bd1988eae82c585b3c68a7,2024-06-20T12:44:22.977000 CVE-2024-37629,0,0,1d00756a2a17c559759065d32584e34ded12669fdde5bf74562dbb03b1828152,2024-06-13T18:36:09.010000 CVE-2024-3763,0,0,d4a43b988d4f5ccf2146c95730aa308ab303229339c58dc3a72b2fdabbe91a36,2024-06-05T20:15:13.530000 CVE-2024-37630,0,0,bf66b2030be40d35050885498117395fd763796c76fee3b35b96849113224fa0,2024-06-13T18:35:19.777000 @@ -252959,10 +253013,10 @@ CVE-2024-37644,0,0,5f7f97e28e218e3fb348230aa8347ee3b0354d72853f4d6c2591e151f0231 CVE-2024-37645,0,0,1f2d6a8f87fac13d3d11d6cbec3b695ad44ed6f32f14768d5b077122546347a3,2024-06-17T12:42:04.623000 CVE-2024-3765,0,0,4fdba2eb80818b350bc57cc64ca06a70a8e5d2cec5cc9e99a6b5fff1df632742,2024-05-17T02:40:06.923000 CVE-2024-3766,0,0,539824cbdfccc4276f1fd794b326f898c89140cb76877e5ae113fb2f5031330d,2024-05-17T02:40:07.027000 -CVE-2024-37661,0,0,8bc6987d1055de55d8b7876bf221b6ce9ec043a5b4bf1c22473fe955a3ac5ac2,2024-06-17T18:15:17.463000 -CVE-2024-37662,0,0,4ba16f654108e1192bd8fb8e8e02e50d6a91573173d812e9064b0a305d10e19b,2024-06-17T18:15:17.560000 -CVE-2024-37663,0,0,c85121604649b2156315c207a5ca6621b999521337716b02c686139e1ebe6456,2024-06-17T18:15:17.653000 -CVE-2024-37664,0,0,b106b1d8d5f840cb17425c36d7f75fda90045b9146be03e27cd1d2e215bc155f,2024-06-17T18:15:17.743000 +CVE-2024-37661,0,1,81e23698cd648834aff1e39e66ffecdc62f564b919dc4643e362915df5fa1b2a,2024-06-20T12:44:22.977000 +CVE-2024-37662,0,1,2581d16ac0c1e64ed9489a4956fd58fc745c5ab4cf8c43694c38d8d5ee60569c,2024-06-20T12:44:22.977000 +CVE-2024-37663,0,1,461ef2b627ebaf037724a15235d82a1820114435949dedc6f8dbf4f5fc8f77a4,2024-06-20T12:44:22.977000 +CVE-2024-37664,0,1,d12e16fb3db0b4b5d59f6bea6df277ad2fce6c983f4f02a9c54b534ba9c1963c,2024-06-20T12:44:22.977000 CVE-2024-37665,0,0,65120387c81349907f7a4a053373f743b497b218da3e8528d2288dae639dbb17,2024-06-13T18:36:09.010000 CVE-2024-3767,0,0,8ba3fcd8961d67ee2d120eabc736772a73aa38bca02250a44c8bb4877d64b7d4,2024-06-05T20:15:13.643000 CVE-2024-3768,0,0,778d3eea8bf87c1f80239f04628ed71cfd577dabb0ce88459344c4cd4d61bb16,2024-05-17T02:40:07.203000 @@ -252975,24 +253029,24 @@ CVE-2024-3775,0,0,a79253f4f0c7633f40fa5e33903553d0137ff03b4a2d8425a028bb5ddf1c6b 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 -CVE-2024-37791,0,0,9254412ba904deaac695ba08c21b6b53b1e1ea7fd3dd34c8aed412f3931c084c,2024-06-18T19:16:00.120000 -CVE-2024-37794,0,0,b0474f9a1e34d4ce4f5843135972ccb449b5684509f30c70025ad198d2cbac13,2024-06-17T18:15:17.853000 -CVE-2024-37795,0,0,b55a1de597f46e87ebb5846214283b41513b4351794622c586104759dffc0de0,2024-06-17T18:15:17.953000 -CVE-2024-37798,0,0,d647646e0be03e8cb80db3b744ccd6eb5c597c1119aa65d17a2032b22c4f2175,2024-06-17T21:15:51.180000 -CVE-2024-37799,0,0,ba7564e3c329f90a0f1d9af54c2a266851e2959c6b686a7ecbb76d586b851b9a,2024-06-18T17:15:51.910000 +CVE-2024-37791,0,1,aac0a75365a73d05a49838e7a7b1ba90a794339affdf6e30eec1aa9fd749c48e,2024-06-20T12:44:01.637000 +CVE-2024-37794,0,1,4c3366c949c3a00b5985b55e086ea5fd5a3c04859d2613f1e28f09c9c53bc4e0,2024-06-20T12:44:22.977000 +CVE-2024-37795,0,1,0ff1ea38e854ef97fef5a9769f3bd2bd99f2e5335a31299021a2afe28c37fb4b,2024-06-20T12:44:22.977000 +CVE-2024-37798,0,1,a36d4ce942da740a820483c71ea27d50cf1c83d3b81c54ef74a42f4ebeb4a079,2024-06-20T12:44:22.977000 +CVE-2024-37799,0,1,0232ea2090a0e592209e0a68f751a4a7bae4888199b9a0222e19baa8b6f85802,2024-06-20T12:44:01.637000 CVE-2024-3780,0,0,d5287c65230cff026fcb8162b9ad15d2c7a6ec9085a2f226aaf7f4b5c5cee424,2024-04-15T13:15:31.997000 -CVE-2024-37800,0,0,1a897896ca9af5f5cbe5808439ac4b85e5c6849a88c84ef80e98d78dc5fffb9d,2024-06-18T17:15:52.027000 -CVE-2024-37802,0,0,114b6d3756f45058fec6cbf8def89155874091d6f45a5ddb47f4ebaf496b9d4c,2024-06-18T17:15:52.133000 -CVE-2024-37803,0,0,070a255a36570e3d4988acb1df23ef134492850f901ae6824c2cffe792e06a29,2024-06-18T17:15:52.237000 +CVE-2024-37800,0,1,36eed506d2f5ce9d6b2834586124ecf9a503dd8108d250049c63e00ddb7167c7,2024-06-20T12:44:01.637000 +CVE-2024-37802,0,1,81dd912a99a788ace360667b22054f8192c4e36f358a19747d18c874d2ebd289,2024-06-20T12:44:01.637000 +CVE-2024-37803,0,1,4f3db0375a36967be1dadee84c3c9799655c3891ffc2301c21194d9aedc22218,2024-06-20T12:44:01.637000 CVE-2024-3781,0,0,bf710215509c2fb5fefd67fb85930537c2ce3a67160738297841ece3c75d6fc6,2024-04-15T19:12:25.887000 CVE-2024-3782,0,0,c95ea596dccb3636dd3691321b5a7a48aa3ee2b08cd07f6f17f6b9ebb6c70325,2024-04-15T19:12:25.887000 -CVE-2024-37821,0,0,ee08a2daaf5ec61b8cfc17f85f39257e5e1760ddecbc43483464a5d1a3b09f4f,2024-06-18T20:15:13.640000 -CVE-2024-37828,0,0,088eef7d3d9d5b4384684055d9dd088b2ead6321f489994eca7630f1ebe32ff9,2024-06-17T21:15:51.280000 +CVE-2024-37821,0,1,69c8b0f219772ac85c00d152695d2a6db130f2920e14ec06f202587157691baf,2024-06-20T12:44:01.637000 +CVE-2024-37828,0,1,1aec682223533f9f2174345c4486cdc5644002780b6ea2a3830079cc11688c3e,2024-06-20T12:44:22.977000 CVE-2024-3783,0,0,f916980cd1e532a7d588efc898e3b89c6684234f9d5fc7d911dee2ee73ce3295,2024-04-15T19:12:25.887000 CVE-2024-37831,0,0,5e7eb1d81cbc03e5a6cb7a0c776550184a7e580655a65f67804199e93112edb2,2024-06-17T12:42:04.623000 CVE-2024-3784,0,0,c3548262a5dd94ab612636409a3bf8cd74017da9deb24debb2f77536fe274623,2024-04-15T19:12:25.887000 -CVE-2024-37840,0,0,8453d99efeccde0568a082a5c426e56d812bc51b13eebf910ea641df056335c3,2024-06-17T19:15:58.470000 -CVE-2024-37848,0,0,88fe14869b9db882d345d58a87ca35c6cced9fdb08d49352f54bce8a27f6744a,2024-06-17T14:15:11.890000 +CVE-2024-37840,0,1,145ee429ed53f53bee37478d13303757e3c9a9f24e63bc7b6c2abc99adf58711,2024-06-20T12:44:22.977000 +CVE-2024-37848,0,1,14bb88bc5c67311edd5b3500e695fbbed1a5f0a2c4a3e7baecfb228770826b1a,2024-06-20T12:44:22.977000 CVE-2024-37849,0,0,1c3bd85b42f72006ddc00210dee95fa2aec60a18f1d79fbfdd90f35c19fff4ef,2024-06-13T18:35:19.777000 CVE-2024-3785,0,0,fc93f2e321d044bf7a0ccc45f351722880d9f0bf94368b28b702ab59c5cb3144,2024-04-15T19:12:25.887000 CVE-2024-3786,0,0,e7dff42d10ea5f51aefb5b7728f1b7d65e7bf6f944a436f82b5cbbe6bdc82c9e,2024-04-15T19:12:25.887000 @@ -253001,7 +253055,7 @@ CVE-2024-37877,0,0,977bdb17b02ee563e354d32709be15b353932c13f2b0db17e57c208cd7c3a CVE-2024-37878,0,0,6ab5285f65d3836bfce4373eeb59284bc38e780244a86b2dd9df8f43f28d93d7,2024-06-13T18:36:09.010000 CVE-2024-3788,0,0,746d07fda684df68d3fb292ada95a2bfbbf82c49ef53e13b55d1c7f158f32ee7,2024-05-14T16:11:39.510000 CVE-2024-37880,0,0,8fc2a7037c003cd05c8204143fd08c5c781310cbac1dbb1e80c2c17a0b28d4e3,2024-06-12T16:30:15.053000 -CVE-2024-37881,0,0,0c34bac75a31e8239bea59eac9a2abcc08657e589ece924dbfaddce6dc9308c2,2024-06-19T07:15:46.743000 +CVE-2024-37881,0,1,e735a099778aac0066c6fabcd8760b1183bff4f7ac584775b8d8c0b91d543346,2024-06-20T12:44:01.637000 CVE-2024-37882,0,0,45ca9932bf3d21ce548b08e090d9ac3d0e382ca97b4400acdf6ea5776d1f3c08,2024-06-17T12:42:04.623000 CVE-2024-37883,0,0,c888822acb2129cd70ebdf11385d4592fadef6856c52c29e59a2fa7e7237e972,2024-06-17T12:42:04.623000 CVE-2024-37884,0,0,b707a0f87446700c352d589d1b4076085e4d7ec94492a1b6b776af09951cf2b4,2024-06-17T12:42:04.623000 @@ -253011,14 +253065,14 @@ CVE-2024-37887,0,0,0467ece977566b214676eb0db2203ccad3333f72a527f3986a8c1fbfb2fc1 CVE-2024-37888,0,0,a9672782b19886e33249fc75bc18c4a8c4010f9132fe10364f8659932ef364bf,2024-06-17T12:42:04.623000 CVE-2024-37889,0,0,daa8873bf696328586ad7ac5c8ae18378b96ec85219f7a263344af70c2ad0bbd,2024-06-17T12:42:04.623000 CVE-2024-3789,0,0,63d455d46acf2815a86f3b9bf286e732f6c1d2d557d093772c64f0c37d315365,2024-05-14T16:11:39.510000 -CVE-2024-37890,0,0,5a51aaf9ddba68dcc4fb851d8d8c2104191ec0f76492414a4202b6704653dbaa,2024-06-17T20:15:13.203000 -CVE-2024-37891,0,0,1596db18091d20a666dec5f247a44722389e3ddb81693324abbe091c2732aef3,2024-06-17T20:15:13.450000 -CVE-2024-37893,0,0,1776a40c4bb7f6b3a47eef65f2923177a81d35e324abf140661a4de06104507d,2024-06-17T20:15:13.700000 -CVE-2024-37895,0,0,f41259f66b42700e5e06aae6e334284d38fc67ec67f409e007cedbe6b28f32e4,2024-06-17T20:15:13.970000 -CVE-2024-37896,0,0,5112ee551bccf3f0184159c2912eb6d43ad52672ea31b9947c140c0e6a0ee36f,2024-06-17T20:15:14.213000 +CVE-2024-37890,0,1,64919ef90d7e50e30ea881a6670fbfc5d82541a664dbdfbc52673f8c72279c2d,2024-06-20T12:44:22.977000 +CVE-2024-37891,0,1,7f699fe1f8c4a3ec8703a81c424d14c0900900ca3b4179e40a6b3b715e3f33f7,2024-06-20T12:44:22.977000 +CVE-2024-37893,0,1,41d25d093dc6fff20a6eda85ded9c0383f2159fafb609c8080b75906fa502b74,2024-06-20T12:44:22.977000 +CVE-2024-37895,0,1,5a205f11ced3309e1f825afc55d41c5d514e9d7238b82fe13249e658f1877f11,2024-06-20T12:44:22.977000 +CVE-2024-37896,0,1,85ccee04f37e2b1a04ceeddd19a029b9400fb1a43ccfa07a1fe5a65adbb32b4e,2024-06-20T12:44:22.977000 CVE-2024-3790,0,0,ea62135e66a6e7a74daddc8d443b8b9750f000d596c0e5f30e202f53e21ec40b,2024-05-14T16:11:39.510000 -CVE-2024-37902,0,0,ac13ed252f83085121ab0ea73c36602edd534bb1985c378bf0890d4d70316b15,2024-06-17T20:15:14.463000 -CVE-2024-37904,0,0,3b21218e989ba1226f49cc96119afb46fbea49434a93cccbf4f238306631c992,2024-06-18T17:15:52.337000 +CVE-2024-37902,0,1,64cca10e7e3ace20e9d59c9293b434dbb2c9acda55554e640303530aeeaef0aa,2024-06-20T12:44:22.977000 +CVE-2024-37904,0,1,7359ae18b288eca288056e2ff119b59a0b9c9bbf3f0e5a23aea1f27fd550dd3f,2024-06-20T12:44:01.637000 CVE-2024-3791,0,0,9bc6cec70e672f5f7f9ccdb1c0603c19b269c41965293930113b85d0de980142,2024-05-14T16:11:39.510000 CVE-2024-3792,0,0,cf023b5179bed164faad65630e21cc1d1811b19d16667a2b08c63260eab0a5be,2024-05-14T16:11:39.510000 CVE-2024-3793,0,0,ee3137e362c58246aa5051457614bdcb92cca84e4e50c79d141ea28f09937fab,2024-05-14T16:11:39.510000 @@ -253049,11 +253103,11 @@ CVE-2024-3822,0,0,fc2c97d17f172eec9f94cdc5060f4aab438cbcb9ae5ff2766add603f099f29 CVE-2024-3823,0,0,cd28ea160a68276fdd70271b0ec926d19fdc3598e922bafa9bf05d9fdd41ea0b,2024-05-15T16:40:19.330000 CVE-2024-3824,0,0,8545575d3e734e1433cd4d7c91c77cd29907e6f5ee87d4739239efdf13c20f26,2024-05-15T16:40:19.330000 CVE-2024-3825,0,0,f398f78dcc905612b8b1fff020bcc62d405b80ffdf3a9053d9f90f163c40baa7,2024-04-17T15:31:50.160000 -CVE-2024-38273,0,0,62d7ce68ddedc4582258408542c188caa41ea672bb373508a235b2ed37068d3b,2024-06-18T20:15:13.740000 -CVE-2024-38274,0,0,9fee77a15773e6270d50f4c0cc54bc440d02f2e3c8f15ddf6c923c51f399021f,2024-06-18T20:15:13.860000 -CVE-2024-38275,0,0,ca7af18bb911c3ecc6697fd231fd0ef74fcf3743a5e6b3ff8e57e025cbaf9ed3,2024-06-18T20:15:13.970000 -CVE-2024-38276,0,0,1fea523b6b0dead5925809d17fa6ede432a1aff37d79d37d7dc8e2da7c51754a,2024-06-18T20:15:14.093000 -CVE-2024-38277,0,0,fecc2a0eade732af4e448f8410bc8ac7a2c28feed714ba711353870833fbf5ca,2024-06-18T20:15:14.210000 +CVE-2024-38273,0,1,3b666b885fd4335027619e91e0284f1b470234dde00130d091638fa968cbd8f0,2024-06-20T12:44:01.637000 +CVE-2024-38274,0,1,e3c858d3a34ac2077869b60b80cac2603994a6b6470a6d640dd39358edb35041,2024-06-20T12:44:01.637000 +CVE-2024-38275,0,1,474fed95f690c9f90f55ff4b7ea783e35914740c4a353e11aabbb10d602de3d4,2024-06-20T12:44:01.637000 +CVE-2024-38276,0,1,61201684c0144d531701138f68e3981b54ff88c196047ee68b15ac4e852406bc,2024-06-20T12:44:01.637000 +CVE-2024-38277,0,1,861f863e7bdcbe6e008f894a715056c3f25fc74dc86e0f050002e71eb59644e4,2024-06-20T12:44:01.637000 CVE-2024-38279,0,0,8e0d752edd2b7f1cef81ab1eeb42304ca3458652fd02e5f15b8a704f935f8c5e,2024-06-13T18:35:19.777000 CVE-2024-3828,0,0,57a9b409ca1cac39bc20af9eb7a4e7dcc3bae1882e9b3a8ca25cdf22dad097ef,2024-05-14T16:11:39.510000 CVE-2024-38280,0,0,bcbf7defab925fd2529b59f3634dae6b192845ba506dcf676efe40b15061269c,2024-06-13T18:35:19.777000 @@ -253070,17 +253124,17 @@ CVE-2024-3831,0,0,28fa4e2fb2524144138a610966fa5501c7b19e1083bb04e4062bd6679bbd2a CVE-2024-38312,0,0,a025bc282a0932c71cb95ccc5342a2a383a8f77cb388790ae2ac3d82d89cfc0a,2024-06-17T12:43:31.090000 CVE-2024-38313,0,0,1c234fe7a87659718d48f2a88e14944f64c41ea923fa0d6325e8d4b1e192fda1,2024-06-17T12:43:31.090000 CVE-2024-3832,0,0,1075b96952121645fbb81b228e0c3813e39db7e21c4c9aa1fc24c30b61618c13,2024-04-23T18:15:15.187000 -CVE-2024-38329,0,0,cca922ce5b3f3309c0b1b52bed62408c80803caeffd81b99d1b9a93f59f2d802,2024-06-19T14:15:13.723000 +CVE-2024-38329,0,1,6a4543a55a7780ada6e17c79a82dd0a8355d271b676150df85f00b992a580a6b,2024-06-20T12:44:01.637000 CVE-2024-3833,0,0,ba630503495cf2aaf1fce7ce704a30930ed35eb1665a53e19102e8c18f607a36,2024-05-03T03:16:28.940000 CVE-2024-3834,0,0,a6e69ceb5a64ba9dfba23cdfa4c02e2549bf746772815229f9a627159689f77e,2024-05-03T04:15:09.043000 -CVE-2024-38347,0,0,1db5df6f7760b01b56d52993df383797c5f4798c0cdb9cb68f64a4daf639125b,2024-06-18T17:15:52.583000 -CVE-2024-38348,0,0,94cbfe55a7243d30de59c6d5a0b267d7b83aa88d8592807a6edbb2ea3d15f4b0,2024-06-18T17:15:52.677000 -CVE-2024-38351,0,0,e713168365103b037ea0e97b0ff1c8370226a2ff3430694f8a53a77f591bce4f,2024-06-18T17:15:52.777000 +CVE-2024-38347,0,1,4d613454dc1780690a10a13a7c4d0d38fa70bfa9e6afa8cdcbdd33d7a9b439c3,2024-06-20T12:44:01.637000 +CVE-2024-38348,0,1,08a2029befc8d2a1e1aac0c0f86516a41bff44ffe308cc482b357e94f4d80ebd,2024-06-20T12:44:01.637000 +CVE-2024-38351,0,1,fc316049b1243ceecf4f16bb932622b3d32a9ec242887e0258f3f20fe77446f1,2024-06-20T12:44:01.637000 CVE-2024-38352,0,0,13a6e81e4d4d40a0591843c161ee638c75aac348990bf4d2603a4c2fb8cf2a30,2024-06-19T18:15:11.507000 -CVE-2024-38355,0,0,278543c69fed17838c464fd75fdfae5cc583fde89bdf573040918981a86265a1,2024-06-19T20:15:11.180000 -CVE-2024-38356,0,0,b087ab52a4a6f9850eaa03fd1740cd30dbab7b1e2cef201f002582eaa58d07bf,2024-06-19T20:15:11.453000 -CVE-2024-38357,0,0,1e04483f65eff96a043cf58a7aa17669e01ba401e8032d34860eb347d04bc131,2024-06-19T20:15:11.727000 -CVE-2024-38358,0,0,4942d1e00758f0ba19862200c342e18c5bdd69c37ff3fc43be42b8eb75873261,2024-06-19T20:15:11.990000 +CVE-2024-38355,0,1,548f855fd76fea3ae91cbde1441c70071a7c7d1a3d657b48a4999a1a744b1672,2024-06-20T12:43:25.663000 +CVE-2024-38356,0,1,4d5684a2a5b21833c79b0d8355427fc3daf538540dd8f7d1cfa341630e75ced1,2024-06-20T12:43:25.663000 +CVE-2024-38357,0,1,db932e7bd44b2292bed66681b7d77a847d541a79cdeb9df0d08a424975405801,2024-06-20T12:43:25.663000 +CVE-2024-38358,0,1,d7fa4473d29cbfc514ec5a6118f6b700b95e48744d7580b8a99541a6dd9bac5b,2024-06-20T12:43:25.663000 CVE-2024-3837,0,0,5046b04f6fff161407832d91f839d6c01f3dcf30bcf75f620bfd7221b5de1c27,2024-05-03T03:16:29.010000 CVE-2024-3838,0,0,bd55ca068ebe4472845bce1f3d037932d27279da54b129864c942318cbf6c399,2024-04-23T18:15:15.410000 CVE-2024-3839,0,0,5078cfd1c7c68c41b30fd8b0c9c6a095120ec81bc8166ccecb75ba3c8be530b5,2024-05-03T04:15:09.127000 @@ -253098,7 +253152,7 @@ CVE-2024-38440,0,0,81c16272bce02d8f590661e69377efd9d4a75b6b13fedd48324b80c4cc1b2 CVE-2024-38441,0,0,8774b6986ddfd4d93147ecf78ef7ec770ec6154755fdfb7857334702b7a334c6,2024-06-19T15:16:00.040000 CVE-2024-38443,0,0,1d75cfa177cf692b67a12f7bd5c673225dc4008379121d75b6d5d0686ab9a220,2024-06-17T12:42:04.623000 CVE-2024-38448,0,0,66ae408cb06bbe5b04615772f5468e0f5bb5c8f2d46df318fd238e60dfb550e8,2024-06-17T12:42:04.623000 -CVE-2024-38449,0,0,bfe3d44cc91ccbcb53fd85e23fea8d11b89236c24e32b2201e2a397ac6ed1755,2024-06-17T19:15:58.567000 +CVE-2024-38449,0,1,d69089b504731433d7b543e10e4b6e57d1623551f30ae8f192ba71fc59819634,2024-06-20T12:44:22.977000 CVE-2024-3845,0,0,0eb4004f99da1c2122444a8d1de5d3db39129e713bf386d7b60bb455af744c00,2024-05-03T03:16:29.210000 CVE-2024-38454,0,0,9e16cbeba5810d367094a131b56862641aa42d77b0ed4c90d4e4d7e92bb854dc,2024-06-17T12:42:04.623000 CVE-2024-38457,0,0,c77550a7e2a9252924a4646a20696a029639d1882dc30abb38808d48a175ba0c,2024-06-17T12:42:04.623000 @@ -253112,111 +253166,111 @@ CVE-2024-38465,0,0,ce0d9866ad6b3f19ec6c77095c1dbcaa6c5f45b9afb927f8abe6499d7e02e CVE-2024-38466,0,0,5d1c6c536bd1417b5b67342ab1c487e0c966acabfa2718a6effebf26cfa8c7cc,2024-06-17T12:42:04.623000 CVE-2024-38467,0,0,b57435625cbeac6544b6507d14e1fc98d3d5fa7f2ffbeb94aa6418d1e331de50,2024-06-17T12:42:04.623000 CVE-2024-38468,0,0,d4c6d48d530a65ce7d90662f3fd07d6f0801b061b80f57001958e3c05da71f26,2024-06-17T12:42:04.623000 -CVE-2024-38469,0,0,140a77be01186206a15069da16c61bcef6024a72a74fbb4c0ff60bdd71d5b1f6,2024-06-17T14:15:12.070000 +CVE-2024-38469,0,1,61f8d4e00b8eb0d7cc440bb61aa54e448e7d0cf937bc39055bad05a42163dd83,2024-06-20T12:44:22.977000 CVE-2024-3847,0,0,a2146e655749d60cf9631f855db42a3d44cf07cd9a542fd1035e46bb9a6304c5,2024-05-03T03:16:29.293000 -CVE-2024-38470,0,0,72fd619cad47e9609a3b66bd344e6e0cff51bf41c439520887f75ce5743ccfa9,2024-06-17T14:15:12.183000 +CVE-2024-38470,0,1,4c268a4f5b43704204ee0794f0d14b8ed1a9214a7b71a5011526bcfa496d0f17,2024-06-20T12:44:22.977000 CVE-2024-3848,0,0,cff2d1cd97f0b1f2183f9bb4edcf4fc45d9e2b8ab251b9953f6af6105249c0ec,2024-05-16T13:03:05.353000 CVE-2024-3849,0,0,d4181d6192aab2f4a2b324451fbda7660fbd9621eb95f5f54a642a6a3d1e7d46,2024-05-02T18:00:37.360000 CVE-2024-3850,0,0,bbe49076d39470df53cdf5186eea91a2b4a40256492f588a1ab86bd1ba5244b0,2024-06-12T18:12:56.413000 -CVE-2024-38504,0,0,723c2c420862a936fd41d275c0985222db47b2d9ca77b454b39db26128f3cbfd,2024-06-18T11:15:51.467000 -CVE-2024-38505,0,0,368605ff3cf07dbe3cca2fed2dc47582b754d29e7d2c044d0a65ba1d0bae5b6e,2024-06-18T11:15:51.733000 -CVE-2024-38506,0,0,caa6d49f29866115f27bdd878f862855f9f5372966a6341bed1e9122088bbdeb,2024-06-18T11:15:52.030000 -CVE-2024-38507,0,0,685485b35ef3638082340806528733cf965a1abe52bfb88503b678c53e8d2242,2024-06-18T11:15:52.267000 +CVE-2024-38504,0,1,1e5426a2fc921f282b30067463f89deeb7f3dcc78ec818fa823270612233ac4d,2024-06-20T12:44:01.637000 +CVE-2024-38505,0,1,be5aaa1dcdfd8c2aa334d5f57235bcc4cc51742ebd9414669481e2364aff48b8,2024-06-20T12:44:01.637000 +CVE-2024-38506,0,1,f0cad7be1bf66b2843860132c4a1c6f7d61e84c638e965683ddee0cfb22e3838,2024-06-20T12:44:01.637000 +CVE-2024-38507,0,1,a0f746b2efdaa14b7b3a19b053b62c389c989bd3db7005a96c00e53930c09585,2024-06-20T12:44:01.637000 CVE-2024-3851,0,0,16bcb9f87255ebcf1aad2856af6894b1b0c36049b98621e173e693ad3a900330,2024-05-16T13:03:05.353000 CVE-2024-3852,0,0,3038e46972183e994310b2b410f139aaace8bd74e7e7e979d336a57b5feba459,2024-04-22T10:15:07.430000 CVE-2024-3853,0,0,da9bcb4a065926b49732a0dd79b2f07a12fd9777c9341906bc363e07df8725cf,2024-04-17T12:48:31.863000 -CVE-2024-38538,0,0,9d673c7f4bad027d5ee2629a2f2d2b94a4949b2c02a2b9961611d8fbc25d7709,2024-06-19T14:15:14.107000 -CVE-2024-38539,0,0,4744ffe22ed2868a96e9e04c9ce3f742dd4faf477777760d33575b2b5a09b04a,2024-06-19T14:15:14.193000 +CVE-2024-38538,0,1,fd8d0c414421b9d83404be9e58919f8d1c04c080d100c149e46c3a374cade8e2,2024-06-20T12:44:01.637000 +CVE-2024-38539,0,1,bb07b10cb8e27f63a4ad4d8d9f4efc546da28e9a77992ff13895f8e8066ae4a7,2024-06-20T12:44:01.637000 CVE-2024-3854,0,0,1fc25728bc86cd277ba270d144040c69a89e438f315d3ebf85291cac5fb28ebb,2024-04-22T10:15:07.470000 -CVE-2024-38540,0,0,8764a5184bd3b6b94167acad5b955473b7f698d269cde47803a9c0e26fd2955d,2024-06-19T14:15:14.290000 -CVE-2024-38541,0,0,8a402c5645416539ba9bcbcfde334458a0476a8e9190f023d33909e2558b99b5,2024-06-19T14:15:14.383000 -CVE-2024-38542,0,0,590cae0d139adff23872ac3076661151c6d6f5024a83b3cf303e788f4ff38d30,2024-06-19T14:15:14.487000 -CVE-2024-38543,0,0,eabb458b565c009ff430056d744d0b9c912571783af9cd0b8305dd64fd2799fc,2024-06-19T14:15:14.587000 -CVE-2024-38544,0,0,f8455ab9a078d10aada3bcb6a7d52989b4ae72a474d428845d91be524c78e540,2024-06-19T14:15:14.687000 -CVE-2024-38545,0,0,03976ac4b43760b8f9bc5875d5c0d9ecce60ceaf2ccc54bb39d25b90228d0d57,2024-06-19T14:15:14.787000 -CVE-2024-38546,0,0,35753d5102159c31de2dc28ec708cba2c44e886d7b6d5a0a7f34a57fa3b95bab,2024-06-19T14:15:14.877000 -CVE-2024-38547,0,0,e2a6aa700250acbd7f157a5e08f65fde57cff5c5111db97f46b86664bb6be120,2024-06-19T14:15:14.973000 -CVE-2024-38548,0,0,e0e7b1e33ab42e29221e3f5cd8d4369961595ee0c662c6132886e7356068446f,2024-06-19T14:15:15.063000 -CVE-2024-38549,0,0,b76024aa04c5e5c3abfb2db769b6499b43621fef3444283cb05dab442ded8047,2024-06-19T14:15:15.163000 +CVE-2024-38540,0,1,e7b3803cf99e050c270c726ab274e7affefcb94f7141fbd6c0b0de4357820faf,2024-06-20T12:44:01.637000 +CVE-2024-38541,0,1,1065fa7d8a4cfd5436e04c18db5d69054ab11f4091c3b7b1134ec020405979bc,2024-06-20T12:44:01.637000 +CVE-2024-38542,0,1,2d3206d3acbc6296896c679abb34821c47c48d8547928a1903930404e39399fb,2024-06-20T12:44:01.637000 +CVE-2024-38543,0,1,749d163234bfa43b2a7a6d5ddb464425e98a7fa6417113dfa2e269c4435d43de,2024-06-20T12:44:01.637000 +CVE-2024-38544,0,1,5697b7121dc116d7dcef1239b61c622e0f4cc69a3755f90752a511f7e74eea0c,2024-06-20T12:44:01.637000 +CVE-2024-38545,0,1,e19534fd73a94af20a1fb344dbf36ffdeca4febea6b2756e17c399f613e5bd81,2024-06-20T12:44:01.637000 +CVE-2024-38546,0,1,06ab8e5395b6ea64dcfc3d0291c1a4cede82de3c6adf9a35f972579209480dff,2024-06-20T12:44:01.637000 +CVE-2024-38547,0,1,6d094da35ceeec072de822b532aacf8e22808edceb46187f6ef18b7c87947a6c,2024-06-20T12:44:01.637000 +CVE-2024-38548,0,1,226b2ec59cd0e8bc5ac9ab89d5a58dbce46f44f8de3bdb71de5c8cff8c4bd0b1,2024-06-20T12:44:01.637000 +CVE-2024-38549,0,1,bf11d8cbded1b174766f461f785ead27d74681fc4984905e8cbcc5a5dcfd77f9,2024-06-20T12:44:01.637000 CVE-2024-3855,0,0,72f9965b46480d1ef50ed2a1799389235938182cc86dc8ecd73fd2cc29210cf3,2024-04-17T12:48:31.863000 -CVE-2024-38550,0,0,0e86aef73ba74451066b4ba304736696dafd0dd519df95646245ccfa66e155f6,2024-06-19T14:15:15.270000 -CVE-2024-38551,0,0,7e74b94a918577951efd6c2b36af8fd9a160963e4969a8fcfb87c866e69e7bf5,2024-06-19T14:15:15.357000 -CVE-2024-38552,0,0,17c88eb1fd0a69a3250a38cf812396f17eb7e51b2e3a41eb0b6e0f3d5acf500b,2024-06-19T14:15:15.450000 -CVE-2024-38553,0,0,771c817308556a0b35640331d7b5eb54a917ebde99858dca4e5f904d84073c23,2024-06-19T14:15:15.550000 -CVE-2024-38554,0,0,235837b68ad52b33174e384e1a479a3d7f7fe3624ea749f9709aa9e375145c19,2024-06-19T14:15:15.627000 -CVE-2024-38555,0,0,349d05bcd7ebf675b40523004fcb6589963b7bdaa054fd5df0bb2dcdc2ece7ba,2024-06-19T14:15:15.720000 -CVE-2024-38556,0,0,e1a6289d444b73575115cc035f66060d09356b9d832b0642b1e4ed2d3daafd70,2024-06-19T14:15:15.810000 -CVE-2024-38557,0,0,68ed9cf803253aa5bbc3f834d3ba7491cd98ce6948d30f09e3a60d6bc5532f77,2024-06-19T14:15:15.900000 -CVE-2024-38558,0,0,af4833fb6bb18bf8bfb094f3a9482fd36a807de308fae35f230c2d02c3b15e1a,2024-06-19T14:15:15.983000 -CVE-2024-38559,0,0,f42af1a9e1079a7cce7c729473e8590da6cc8bae5c473d66528f1a8c868dc00d,2024-06-19T14:15:16.077000 +CVE-2024-38550,0,1,12c1f7faf6d391bda45153650ece532f5927f00b8db4353fe4f9877957dc88b7,2024-06-20T12:44:01.637000 +CVE-2024-38551,0,1,994bdc4b2bbd91b836307a9355447db2c53145ee9caa85e9ac226f8e6e77bac5,2024-06-20T12:44:01.637000 +CVE-2024-38552,0,1,01c171b993c98ea9691fcb9c0132239a0403ae52a92e72087b20089fe28a56aa,2024-06-20T12:44:01.637000 +CVE-2024-38553,0,1,286ac07f37ead0233ff53087fe6bb725f02540170c59cfcee7e11483334cd294,2024-06-20T12:44:01.637000 +CVE-2024-38554,0,1,5e74e3d53ddd7d96294d8c3ac43d22e24d94eb7441250ec59441112cd0cf92b5,2024-06-20T12:44:01.637000 +CVE-2024-38555,0,1,1325a5873db06d0a5896cedfaafadbba06050b8903042fceca1b4e19fed51c2a,2024-06-20T12:44:01.637000 +CVE-2024-38556,0,1,e0e81ab8190bcbd6bb796b6590adf60b73006915d9ddc86cfd7468742ef0c269,2024-06-20T12:44:01.637000 +CVE-2024-38557,0,1,5d307d93744b50df3585e73b748fbc1dea70a105ccbf6e4e87a827fc2aa9e43d,2024-06-20T12:44:01.637000 +CVE-2024-38558,0,1,d215af1f9dc6f1871afb6785a3eacc6cbeb466c2538fba6d795011157de1355b,2024-06-20T12:44:01.637000 +CVE-2024-38559,0,1,43590e9bb6ef9bc4a860e0dbb4ea57c00d36c2723dfdefcc54f8e589b22ece61,2024-06-20T12:44:01.637000 CVE-2024-3856,0,0,b4145bd7b493b073ad7b7090cd52428765d0c24799c3bf5af1fe7594a342c2dd,2024-04-17T12:48:31.863000 -CVE-2024-38560,0,0,62ff65dda09b037e32f4690de5b519bf207f28ef5720c20008b934b7e9954bf9,2024-06-19T14:15:16.187000 -CVE-2024-38561,0,0,9bc38ae2bfee4c0cca370e12e75ab92fcfdc47987981271a6cd04a4e9432f21c,2024-06-19T14:15:16.313000 -CVE-2024-38562,0,0,798c1af58063c18745db485841ce53dcf759c6e88afcd0f2429db7fc4e7113ff,2024-06-19T14:15:16.393000 -CVE-2024-38563,0,0,c863b51d8f0068b4f278240da9bd03cdac5d264188500b458fd69a2ec92c8f5c,2024-06-19T14:15:16.480000 -CVE-2024-38564,0,0,debc1fca0e40e36833428e7783db48efde03bda1f05ea2cdedc8220fe9f2f5d6,2024-06-19T14:15:16.560000 -CVE-2024-38565,0,0,c5695469bcd30f894ebdb62b4d46371f128fb936a7dc4799a2182e1bfaca4736,2024-06-19T14:15:16.667000 -CVE-2024-38566,0,0,859e2ebefe75cc064292568a973dd7b2571127448d3a4e6c89ffb6345f4f64fe,2024-06-19T14:15:16.767000 -CVE-2024-38567,0,0,e5e05b24c41f210bbd1c74c2ae7e5bfc3e76225a2d0482424d4aee320c2705b4,2024-06-19T14:15:16.850000 -CVE-2024-38568,0,0,7aec1407a46e340eb826903a8e05a30010842466f1fcc28439f2c78063799aa8,2024-06-19T14:15:16.950000 -CVE-2024-38569,0,0,c72d716b868ea6d3d6e650c2e282e662149189cf5913854eb8479682e0ae6075,2024-06-19T14:15:17.060000 +CVE-2024-38560,0,1,dd3d7759ae511a11426b1402e0e3263d5bd5a72be09156ff201562649ec75b00,2024-06-20T12:44:01.637000 +CVE-2024-38561,0,1,93a736f54ad24f57f3b35f5e4686025c04c00aee6e32e522a0d99bae472a5b47,2024-06-20T12:44:01.637000 +CVE-2024-38562,0,1,95e049daa82ebc8bb7fd09103982cb4b2704355000dbaf388cb8a15eba1e5c55,2024-06-20T12:44:01.637000 +CVE-2024-38563,0,1,be99db486d5a22c61fa099cfd73d538d2c8a8ad8c800fa69baa108ab15267146,2024-06-20T12:44:01.637000 +CVE-2024-38564,0,1,f30b6e5454fdc56fe2ed5cf62ff8068acbd0868113a623cceeac8c222d27e863,2024-06-20T12:44:01.637000 +CVE-2024-38565,0,1,255aa3d89cd8844b96cc6af713f9899010a19ca82da38a82497b82b9f85c00c8,2024-06-20T12:44:01.637000 +CVE-2024-38566,0,1,cbf9595bc7c6a3a8392b2f29aa06e360a055ceee2b59f6b396c4b12b30d6a84f,2024-06-20T12:44:01.637000 +CVE-2024-38567,0,1,747343b02008a17ee1415397b21e5405c1c0a77c4613a0f8f2d08ea83aec2fc0,2024-06-20T12:44:01.637000 +CVE-2024-38568,0,1,ebc26ecb554f4a117e56a2b7595b19c2bb6870e5fe6ec7da1db88f1843088b19,2024-06-20T12:44:01.637000 +CVE-2024-38569,0,1,43b2e24bb95b5b0c5ed869e83948d4db63ec0f5a8a8fbb28319ca0915c7949cf,2024-06-20T12:44:01.637000 CVE-2024-3857,0,0,759e3e6356edbe4b757e6defb2865ff9079af79daa39f4b5313863a09852808f,2024-04-22T10:15:07.520000 -CVE-2024-38570,0,0,3756edceffaccca01e7c297f3d6cc6e66b402cc7b00d02fddb6fc5304ef909f8,2024-06-19T14:15:17.153000 -CVE-2024-38571,0,0,0b8c31b7122128cb4cd2b6c7306b8dc70ad56d3c410bec3993198d6b550379ad,2024-06-19T14:15:17.250000 -CVE-2024-38572,0,0,3537ac5d6712b552508d8498fe223124a0d3260120780b4639f7f22c9bade129,2024-06-19T14:15:17.333000 -CVE-2024-38573,0,0,f2440822cd9d6e108271497fe3006dabd9faa13e66951b922275f9f17ab19ec3,2024-06-19T14:15:17.420000 -CVE-2024-38574,0,0,d5b53f8bc863fb358ad3ec3b938ab36e67bc4ef80c756367d360cc83a0978862,2024-06-19T14:15:17.520000 -CVE-2024-38575,0,0,e7b1457c475ed43ac7d010abe92ece974b37ad7056379e23ba90336fbf9c41b5,2024-06-19T14:15:17.603000 -CVE-2024-38576,0,0,30432eec6bb81595219f09751a58ae4dd0c33916f7b4b2f1cb8a1aa9d0bee39f,2024-06-19T14:15:17.700000 -CVE-2024-38577,0,0,b2a2990e48be05e576ccd07893752478e64deb8551e76430efd2ccbe60470e12,2024-06-19T14:15:17.787000 -CVE-2024-38578,0,0,db7c295e7edeeb49dc0ea00f9bc1ff74ad94bd41b0b627cd258c3b5ea0d6d987,2024-06-19T14:15:17.870000 -CVE-2024-38579,0,0,4837ef17323b3ca3f026a6ffe01a8b1cfa6ff191f2913a223e30d5c6c0365ba0,2024-06-19T14:15:17.960000 +CVE-2024-38570,0,1,7ec182f6fa5f3c0d1a4f19f2759b6f5e1c5a221db963b42f1c92abd85c45cdce,2024-06-20T12:44:01.637000 +CVE-2024-38571,0,1,a8ac066d75001a7a7c7d08cd5467b743b181e3ae1b62ab3328c7b56658888fcf,2024-06-20T12:44:01.637000 +CVE-2024-38572,0,1,aacf13e691ed59e8d1f0037d7039807cd50bf7233bf63dc7df8936b4d7a148b7,2024-06-20T12:44:01.637000 +CVE-2024-38573,0,1,bc38939d625e4d50426892be0c285949a4fdf5b8010cff55bd177a21e81e979b,2024-06-20T12:44:01.637000 +CVE-2024-38574,0,1,c9bbb608bc0fb4fd78471e471f67157db9c46f296b9cebdbf2a9eaa112c2b05c,2024-06-20T12:44:01.637000 +CVE-2024-38575,0,1,706823464dd777ddf38fceba51b63345567e0ce58208e92b648866b8c461ddcf,2024-06-20T12:44:01.637000 +CVE-2024-38576,0,1,5f2c362a1b20fb6644f41270cb49cdc5fa151e9181a4765c6f2c4b80f8fd5ce5,2024-06-20T12:44:01.637000 +CVE-2024-38577,0,1,aab783e562369ba736289de53b41b9b9e9e5bce44bf13dc1d8e2f816a558ee31,2024-06-20T12:44:01.637000 +CVE-2024-38578,0,1,59a6f376e54bbaf5df61ec2e73020ae35b8f027f6cff8284302abd972222ea0c,2024-06-20T12:44:01.637000 +CVE-2024-38579,0,1,19bad89d8508334ab376a57e76d0349363cf011713f6d20c00dcae216a9c77bb,2024-06-20T12:44:01.637000 CVE-2024-3858,0,0,7909cba96f3e3d206ccbb308cd394c2dd55ea5480740c25fa8316d0bc5650abe,2024-04-17T12:48:31.863000 -CVE-2024-38580,0,0,b8616ad94e4058d9aac53ac083cc2faa8d54f78d6bed5ee3c66ae42ac88244e1,2024-06-19T14:15:18.057000 -CVE-2024-38581,0,0,4ca46e6e718af04ea5d298d8391cf3bfc8358235ec9c963732884bd37e22418b,2024-06-19T14:15:18.150000 -CVE-2024-38582,0,0,e5c0bc80e5ccb3e0f3b0899a1b55afdf417a9415e1a1ad9a717c89eb283b4f4d,2024-06-19T14:15:18.273000 -CVE-2024-38583,0,0,4aabaa9945a8170bb6cb2c9f75add872f399e5dea27906d70ebf692dd06424dc,2024-06-19T14:15:18.397000 -CVE-2024-38584,0,0,b7e5d8057261ca79112fc246485509a03c2ad8b474aa4df872915347f5e028a5,2024-06-19T14:15:18.530000 -CVE-2024-38585,0,0,f7baa7dc21eb3c03a1a55d1c836857015fde16f357dc0552f78d0560285a8a20,2024-06-19T14:15:18.610000 -CVE-2024-38586,0,0,dee4eded8916812b4923dc2351d1a2650dbca4ddea721275fd441156371d5b05,2024-06-19T14:15:18.700000 -CVE-2024-38587,0,0,50a187338193144887a870eaede9bee6fb2e067220c406c87892b357fb301810,2024-06-19T14:15:18.800000 -CVE-2024-38588,0,0,4f51d80a67bdd789f4aad4872515abbae5338cd99c23b6305880067ddad7e90b,2024-06-19T14:15:18.907000 -CVE-2024-38589,0,0,7ca7644c5af5f4acf075c19471d0d9a27e54c0da319f329e0c2fb60b80df485d,2024-06-19T14:15:19 +CVE-2024-38580,0,1,38a9a9672fdcd3a26951ddb1fa5b0b6a344f0f6809bbcc0c9be0b904caf7e8c4,2024-06-20T12:44:01.637000 +CVE-2024-38581,0,1,d26f4100a5534742e5b1c060f48168274a9f8ba7a3a144ed1f5a68fa7a64c8c5,2024-06-20T12:44:01.637000 +CVE-2024-38582,0,1,41e3d47345cfc6f7a622b4174be023717be773cc77952929809d13f2b3e76a1f,2024-06-20T12:44:01.637000 +CVE-2024-38583,0,1,b155bb53501a56a625151deea2027414759fdeb68090c9c88843bd07655e6b56,2024-06-20T12:44:01.637000 +CVE-2024-38584,0,1,a86dd4bec97afdd294218b4d2cb90c2a2236e3f932e80b46504435534c4b8163,2024-06-20T12:44:01.637000 +CVE-2024-38585,0,1,88b0887377392aa1b176806491a5ec82610e5a3bcc11262f1287e63162efa57d,2024-06-20T12:44:01.637000 +CVE-2024-38586,0,1,44e39521bc8b7aff0d13b8bdb8eb57c475e755967082646c98b31056f074bddb,2024-06-20T12:44:01.637000 +CVE-2024-38587,0,1,fa7838f440b65e8fdfadad72d3e22feb5c6758bd575bc3d58bbdf3179ae6b561,2024-06-20T12:44:01.637000 +CVE-2024-38588,0,1,63377d15d615a89cc502e82cc0b4d98dd3570175273284e854a555b603cb2164,2024-06-20T12:44:01.637000 +CVE-2024-38589,0,1,c22349a35c5125a3c03e12aeb5f0a5d0cb90d1ff19f30f4f1e992cb88ffb9b6c,2024-06-20T12:44:01.637000 CVE-2024-3859,0,0,3065404677b844c907170ea43348d98daf159eda29192d0f8b013c98cba7e7cc,2024-04-22T10:15:07.573000 -CVE-2024-38590,0,0,99bbb8a40160ddb11baa872222f7720258ecdfe58375b58d2b3bc3ce24751287,2024-06-19T14:15:19.113000 -CVE-2024-38591,0,0,66be3095ef5227d07938f9b78b8305ccff090ea0163127c5ba15920f929ec3cf,2024-06-19T14:15:19.207000 -CVE-2024-38592,0,0,807d9e77327ba353370fabeb446d8696713185cfaa2d7f13dc3478cb2b22e271,2024-06-19T14:15:19.297000 -CVE-2024-38593,0,0,310d7ab3542b025a5b066575c3c95d1911562382a9e082240e76ade76a4b27db,2024-06-19T14:15:19.387000 -CVE-2024-38594,0,0,a86cafa698850a501a3830677c7f869ed574f9c5ee695029d20070a1e106ecfc,2024-06-19T14:15:19.467000 -CVE-2024-38595,0,0,9203c37c08c2e51d3c926a4a1fc184bcc65493c46d6368911d4b9c02e62a74c6,2024-06-19T14:15:19.550000 -CVE-2024-38596,0,0,d8b348722bc9635b7bc071e699eee26e440c2b3f93821d426890b8f63a877815,2024-06-19T14:15:19.640000 -CVE-2024-38597,0,0,ffdbb0d63c69add2f6ffb55c2ab1843b73fbcbf7ab99ae23d34bc16aa4e66f07,2024-06-19T14:15:19.730000 -CVE-2024-38598,0,0,b1b877a528d458d15ef62f5493508ef27ec096890066a3a3f007f90fe61b3c1e,2024-06-19T14:15:19.813000 -CVE-2024-38599,0,0,3886ec2a15aa3b7cd7368b71dcc52642968017517114ab25ba1e9d8cbe2b7c3e,2024-06-19T14:15:19.903000 +CVE-2024-38590,0,1,1fde351792af11094df547ca6039c92dd4040f95fbccbb26deb2074af9ba3491,2024-06-20T12:44:01.637000 +CVE-2024-38591,0,1,a87a6cf3381321fae2571d6b3d74f06358c9ae85b011ec7304b3632eb3677c62,2024-06-20T12:44:01.637000 +CVE-2024-38592,0,1,05588f2b7ced16b85036b6966bff690fa7126b1bbbd3653d3eefb89b41f1a1cd,2024-06-20T12:44:01.637000 +CVE-2024-38593,0,1,9043806a5b5221b7873fc93aa5bedce151ab1ba872266f0d9498a3ee99ad8924,2024-06-20T12:44:01.637000 +CVE-2024-38594,0,1,263312fa01f21f81aca9ad0b7081ef21ebd3d6736f9b7e154b2f81c32355a546,2024-06-20T12:44:01.637000 +CVE-2024-38595,0,1,167986f4e289cbbc06db285514230af9b31fe84bc5e2e51a3cbba38552a9a3ef,2024-06-20T12:44:01.637000 +CVE-2024-38596,0,1,381521411c5fe0069bf95df12d280703f758562ab779941c7fd27f311301c84e,2024-06-20T12:43:25.663000 +CVE-2024-38597,0,1,dfd9b26fbd1f75c8aa3c1f19bb92c71363166efbbd82c3534172982ab0e709ac,2024-06-20T12:43:25.663000 +CVE-2024-38598,0,1,b948e5e2a96e4f2604c682eaf6a27616c9418ca539855cded9c5008fe055cbdd,2024-06-20T12:43:25.663000 +CVE-2024-38599,0,1,ead42b07c723488112c8a76d939471fabc0315640eef143c2046fde4b2486f9d,2024-06-20T12:43:25.663000 CVE-2024-3860,0,0,c33e8c657cfe3956cd70903ab7912357e9142226690438c85322ce7b941ed7f2,2024-04-17T12:48:31.863000 -CVE-2024-38600,0,0,0eb5aed4a0821ad7eb94dea908bd0bf60a95a413ea97f1a161056d0691867413,2024-06-19T14:15:19.990000 -CVE-2024-38601,0,0,14290d338e43f7c8f09ce82532aaa6a385c08ccea7c1bda9eab3a9ba1c721b8a,2024-06-19T14:15:20.087000 -CVE-2024-38602,0,0,bc88589ab05565c4530e6b0234872cb036cd4c672b2e7d7f41deb1811cd821a2,2024-06-19T14:15:20.183000 -CVE-2024-38603,0,0,f69f89b8ecf842d7ddaf0b08ff6d467aa049e9ca7ad554e3f42f03d898abeb59,2024-06-19T14:15:20.270000 -CVE-2024-38604,0,0,1047fab40d7dde24aa0ba8480911088ae7ea3f162c67ddd78b88f28ed7c39357,2024-06-19T14:15:20.357000 -CVE-2024-38605,0,0,5b8f6f2af9a184c81e695274ed04b54920e7320d8e419dd82d180c9fff6226b5,2024-06-19T14:15:20.443000 -CVE-2024-38606,0,0,240a0eea1c30af1825b2968f3613c0d57d6c485a2bf0c1d51941277b814dd5a5,2024-06-19T14:15:20.567000 -CVE-2024-38607,0,0,44dd8c9524d27803f3382fb09fd4fc15f706eacb3ac52f58dfd664a92ce65d11,2024-06-19T14:15:20.650000 -CVE-2024-38608,0,0,068ed4d8c365587cd933fc0c05415455de990d212404f4d38ca1899158c0bae0,2024-06-19T14:15:20.737000 -CVE-2024-38609,0,0,fb0aaf2425805d5807654250537040fb97568b7f62d010dc38d04db14552fd66,2024-06-19T14:15:20.813000 +CVE-2024-38600,0,1,c9563c70f22652ebe1de7c7cc7f742e6fb8edc19caa32f1a7a6fa2c104c44ef8,2024-06-20T12:43:25.663000 +CVE-2024-38601,0,1,add858065c300b4dd3e338dbd2f12e07861bf7260b29505ec31ca100061842f6,2024-06-20T12:43:25.663000 +CVE-2024-38602,0,1,9a80355cc21e33c080d1b076281ffae3e2e5deed03254094e225183d4901578c,2024-06-20T12:43:25.663000 +CVE-2024-38603,0,1,2e6ffe264b8f7d29692c9fa8910cbe9efc4c6ac4cd0660382cf13ff5b0949cfe,2024-06-20T12:43:25.663000 +CVE-2024-38604,0,1,2774a468bb1e28e6ecd0cb6e8825f2bc4f300c9700b1b90f2627bc020f94a4ce,2024-06-20T12:43:25.663000 +CVE-2024-38605,0,1,284e8faf962af23a3027f4706f39f0bd1cbeb02f1904945be570abdec92a24a6,2024-06-20T12:43:25.663000 +CVE-2024-38606,0,1,9f6359ceccd6950e6f174b7a3d98677dd3e810cdff76a24028869e81ac53d4fc,2024-06-20T12:43:25.663000 +CVE-2024-38607,0,1,b4ac9545970d8e8cc1928b417e090211e47ad577bebad64bd080d1987850875a,2024-06-20T12:43:25.663000 +CVE-2024-38608,0,1,7737edfe46fb47f195726e0c7c632204c84811e284d710ed238cbe4299694fd0,2024-06-20T12:43:25.663000 +CVE-2024-38609,0,1,db774524e58ca6f0eefca9518e6396633842bb781a3277855e12f8fbba63d8de,2024-06-20T12:43:25.663000 CVE-2024-3861,0,0,891d68faecae715fa9ed74917dcc8c6b8466167516a2b34c2f3aaf1667ff2bc5,2024-04-22T10:15:07.620000 -CVE-2024-38610,0,0,f8da9241ed09a21ecfc605182b3993fac64b34bbb8b0647e50b152c0f57ea388,2024-06-19T14:15:20.893000 -CVE-2024-38611,0,0,ac956472025bb0d7dbb96b894189bb170c4652cffa67014bfe66ac5fc0926658,2024-06-19T14:15:20.980000 -CVE-2024-38612,0,0,1806092921d131bf9d9530fcd15878aa95da3cc078a3859ff6d91c1c0d2342a7,2024-06-19T14:15:21.060000 -CVE-2024-38613,0,0,edd8024269567b593810e281c17603a5bbc6b2ce82a73e1c6ae14265926a458d,2024-06-19T14:15:21.147000 -CVE-2024-38614,0,0,0a4ba8814c9c0ee348e61e815ff755992077860337ffd18b6e42b3f0079bf2fe,2024-06-19T14:15:21.240000 -CVE-2024-38615,0,0,cd0cb9cadb10e6ec8f0952d21d8998d348b0724824fc945dca4d131da03ae5ae,2024-06-19T14:15:21.320000 -CVE-2024-38616,0,0,2d6e2f70ac9dd0bba4b624050f77118d35857a36401a01447394dcac7cabb457,2024-06-19T14:15:21.403000 -CVE-2024-38617,0,0,d2e96d7280323f32ed957d3b647a6c9211c0b9099dfb0dd2366229f84463ce19,2024-06-19T14:15:21.490000 -CVE-2024-38618,0,0,2355a65d823178dbc67530257af22b7ca0cd2b710a40f5d1c17535efa8ffc772,2024-06-19T14:15:21.567000 -CVE-2024-38619,0,0,04916e6841fea2c2384a6e8546cea3a04b4c5fe37f91ff2f098a22d640694557,2024-06-20T07:15:41.830000 +CVE-2024-38610,0,1,29353cc675ddf7fdfb11ab2c2ee9e633c6e3a71d49824683ceb2244130fd130b,2024-06-20T12:43:25.663000 +CVE-2024-38611,0,1,da00074115add864f490a027525486c8284afa31e189c50727dcb4c7424e8f65,2024-06-20T12:43:25.663000 +CVE-2024-38612,0,1,0456de92f77917b035ee8e47490618b5f4703713a4e1020b4b29858b592b081c,2024-06-20T12:43:25.663000 +CVE-2024-38613,0,1,693b4c2b59c67cd93392d22cc43d2f41b73124550e270fd775740e2c797f5616,2024-06-20T12:43:25.663000 +CVE-2024-38614,0,1,cf11629b661e0fdd3caf78fc8ad16f9623893b32e3f007f9cb07ed9675a254cf,2024-06-20T12:43:25.663000 +CVE-2024-38615,0,1,6b2b30021c462b67b43c68a1b611bf4e256aef4b2202d2a4ffcd14a365f0996c,2024-06-20T12:43:25.663000 +CVE-2024-38616,0,1,5973b89685927d01a2bc6739c9869c62b013e73534589bc0a28a6ca91ac6e344,2024-06-20T12:43:25.663000 +CVE-2024-38617,0,1,9c97e58cf4d706f899e8162b3f89b78d980789c28dbd9a8d8811544e01702995,2024-06-20T12:43:25.663000 +CVE-2024-38618,0,1,5399a5e4fc905e343797fec50dc7ef2ceb4c0711d2428c49772522361284e789,2024-06-20T12:43:25.663000 +CVE-2024-38619,0,1,5407c8a2f7b4593da0f1cdd114add38eecdc64008f26285e518c2bb461dfbd53,2024-06-20T12:43:25.663000 CVE-2024-3862,0,0,d892c55e37e2ad71ebd3e4aade996aff767de8739f62e2d71c93704431b2b09c,2024-04-17T12:48:31.863000 -CVE-2024-38620,0,0,2d2b83ae1032a00e82c63edf9ae617b9ef9a62e18f90d060d3b153645c9e6bf1,2024-06-20T08:15:38.377000 +CVE-2024-38620,0,1,6148b861a5093fff5387ffdb934470362842871878e29323f4b878a27c1f924b,2024-06-20T12:43:25.663000 CVE-2024-3863,0,0,2bcd7aff2d943e7ab42e23b79c60d375ad9e243a307a827bee502e9df179514c,2024-04-19T17:15:55.333000 CVE-2024-3864,0,0,19d7836c62228b8f626d6423c9bc9a43211c93bf4b17c3a151f2e9e764cbca42,2024-04-24T10:15:07.597000 CVE-2024-3865,0,0,8b230c3d643bf4def0090616d3b729148802c45f8b0915e5522b00babc710a03,2024-04-17T12:48:31.863000 @@ -253245,7 +253299,7 @@ CVE-2024-3890,0,0,167befe3a418fe829a07bf47548aa5d5c5fe13f91b75a3184f188bef038919 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,0e1a5ee4bdb96e30955d93f7eeb5a1ca1957a6840cbdbd26882844253349e849,2024-06-19T07:15:46.847000 +CVE-2024-3894,0,1,edf80459282b8df89b54e83306b1e3308990b8425170b8aae8ee5dd50d193a39,2024-06-20T12:44:01.637000 CVE-2024-3895,0,0,e17d122bfb4ca0c486d0790093f87ef90da21ea7556181e7099c23bc52ef24ea,2024-05-02T18:00:37.360000 CVE-2024-3897,0,0,2e6547d98bffe49274878683fd846b0dea4d063f5cc123163d759ecec392b068,2024-05-02T18:00:37.360000 CVE-2024-3900,0,0,5bafaa90d65e26f460054cb65a089d31ecb0030e0f85c3f0ee595a0cce123691,2024-04-17T20:08:21.887000 @@ -253306,7 +253360,7 @@ CVE-2024-3974,0,0,30b94b89b01dd2c6057362330f67dc78937f3f3edffa0c5a57e7602f711f91 CVE-2024-3977,0,0,e9f44416847592725fc2cd47ffed9c743bca75989a5c2d940c73903d22d68b79,2024-06-17T12:42:04.623000 CVE-2024-3978,0,0,338ec55d360d0ecf1dfe595690a2d37e24aa4129fa5a75aae324bfa31cd2fe9a,2024-06-17T12:42:04.623000 CVE-2024-3979,0,0,4ac2126fe63098861061c1ed3772b0712449f42e64a5481492de94fd61a5b947,2024-06-06T20:15:14.127000 -CVE-2024-3984,0,0,cb13d99fc80b6409a686317ff1e135ad2da1da6558955948ac3ee4d4625aa0a5,2024-06-19T04:15:11.213000 +CVE-2024-3984,0,1,bee410e9bf0342c5ecf3886d76050e2314329db97e17f53f9285ff32a0d9ee8f,2024-06-20T12:44:01.637000 CVE-2024-3985,0,0,73586f1cedc99952324792e19f078c055584e6e606f6222ac3907090ad395ced,2024-05-02T18:00:37.360000 CVE-2024-3987,0,0,05499205f937534ee026fd5a41dcafd44deae059117eea743b5e3e3c53eaee01,2024-06-07T14:56:05.647000 CVE-2024-3988,0,0,ed49ad0e503298ba2fe40c90a665a86dcb918b5087ac61c1edfd746c2ca95d24,2024-04-25T13:18:13.537000 @@ -253338,7 +253392,7 @@ CVE-2024-4026,0,0,9eff728af4fb17cd0b046ae2444303f230bc7685cadbda3feb2bd1007c7666 CVE-2024-4029,0,0,afc8def3dff015c790bb6f1fba36f8919ca09d0c14ec4f09004e6bb6d31f1058,2024-05-02T18:00:37.360000 CVE-2024-4030,0,0,c7e71f4aa9c8e1fed63372a5ecebe14dddf19d5400caf27393d092efafbf0f25,2024-06-13T20:15:15.570000 CVE-2024-4031,0,0,4baeaad68cf3411bf45d41e53c64aca0aa19dc8cf620cd2c5028b0d61a50ba2c,2024-04-23T12:52:09.397000 -CVE-2024-4032,0,0,03894ea0efe4adf33eae6b6c4a5d257a2cf4187fd23c9230c41cf9b02106eb41,2024-06-17T18:15:18.047000 +CVE-2024-4032,0,1,52c6b9eccf7e021076c0ce344d44b2f19b27dbd5716fada0f5ba921e591652d5,2024-06-20T12:44:22.977000 CVE-2024-4033,0,0,9c08f15b4d3308634dd41e6afc3001fb3d24483554aaa58982323fa330ce651a,2024-05-02T18:00:37.360000 CVE-2024-4034,0,0,fbbc9986eba42f39f504e14d62a8f5aac7c2749ef90d02af8ad89eb5ef4d1cca,2024-05-02T18:00:37.360000 CVE-2024-4035,0,0,02906ca1b496a2e42ac8610e4dfcaad284409da5fa1faeb0fe6ebb26c1e7ae4c,2024-04-25T13:18:02.660000 @@ -253384,10 +253438,10 @@ CVE-2024-4087,0,0,c042d2a1de26e6b1fe0621a6edcac1fb8cab9f866d13a8bc2e77c06eafe2f2 CVE-2024-4088,0,0,c8ca3e8553223ece7fd626b7957017d2d8aae2ed445db80654c73542bf17135f,2024-06-11T17:11:30.193000 CVE-2024-4092,0,0,4be02f9c67d30932bc0929e64c1c04dde83d92e769e6b30b60cbc598e8e37f4c,2024-05-02T18:00:37.360000 CVE-2024-4093,0,0,5d27408cc41c323f4b0e69479d9f46468fbd0106e510632bee156499f1d6b2eb,2024-05-17T02:40:15.433000 -CVE-2024-4094,0,0,5568bb7b9c58d0dfc0e61c5b0d15fec28f7a97c2856c9b64fe0b97085b61ff12,2024-06-18T06:15:12.360000 +CVE-2024-4094,0,1,6d8deca1afbfa1fdf68d5b04106f4db1e40121230438bc63c3aa56f88308cb6e,2024-06-20T12:44:01.637000 CVE-2024-4095,0,0,31c469f286897b03d948d4fae3cbc92250d27af63fa8e1eb75ef9d0aeba13389,2024-06-17T12:42:04.623000 CVE-2024-4097,0,0,6a60177672bc62dbe43e4e7ccd78e74b9159babed54b0d3a303c5a9a6fcd009a,2024-05-02T18:00:37.360000 -CVE-2024-4098,0,0,cb73ebe09904e382d0c5ce739d9d4659a207104f7c802fc61cc7679a1f5f21a1,2024-06-20T07:15:41.933000 +CVE-2024-4098,0,1,a3e4777d420e1b3bcafda1cf3d039c925611c1ff1c0ae02e65a01fb1638060ec,2024-06-20T12:43:25.663000 CVE-2024-4103,0,0,db40310890aaaffd4decfd17ebe6978d2575902ae5387a15070f6cb8b96b8e99,2024-05-14T16:11:39.510000 CVE-2024-4104,0,0,8fd82744b8bcdbccac2be79cc70a35ed94046651bf70570898ef2c659d60f12d,2024-05-14T16:11:39.510000 CVE-2024-4107,0,0,ffdcb25066b63e479c86de36da9033958cd11095a536f4d270fcccd4e4bc4dda,2024-05-14T16:11:39.510000 @@ -253609,7 +253663,7 @@ CVE-2024-4371,0,0,6cec3438f9da16aaaf81036d5252f279057c04fa33a9a5b8c9aee6667c7b57 CVE-2024-4372,0,0,88e318f3c277cb3db68d033332d7a1ea039944347227497506fc7085644cb64e,2024-05-21T12:37:59.687000 CVE-2024-4373,0,0,f38def9014d5248f107e6bba87e0f735d485b9410ddb561204173488b0ad462b,2024-05-15T16:40:19.330000 CVE-2024-4374,0,0,d60604ecf379bdaaec2b6706393723f20191611e78669219836ffafca51bb0b7,2024-05-20T13:00:34.807000 -CVE-2024-4375,0,0,0c05d2181d27372e2e73037a21c8284a668309e752ea21705c58e83f5006338b,2024-06-18T03:15:09.797000 +CVE-2024-4375,0,1,5d37e83ec1ec9e1f6c05f9d245bb382afff17f477592ccba2fad5e662af0db81,2024-06-20T12:44:01.637000 CVE-2024-4376,0,0,a37f8f2c30013a9ce99cf3397e8919ec44dbe48bf70335aec6d3a9f3c4d5ff1f,2024-05-31T13:01:46.727000 CVE-2024-4378,0,0,3d00b0a6c1463c84b18edbc3f37b735155a12d4e83c941a4e59e5c575fc8dda7,2024-05-24T01:15:30.977000 CVE-2024-4379,0,0,4d59152fb4b73c11db800a656f5856d441c43de1bb0066c24dea588b8283a5e6,2024-05-31T13:01:46.727000 @@ -253618,7 +253672,7 @@ CVE-2024-4385,0,0,ca3b527b38ef117a25bd1a563993108f86670c5409f332b50d53521ab7d618 CVE-2024-4386,0,0,57810600ce2cb57e3b791eb883cd1cf3cd600b48831c08c0c6ff5f338408f5ca,2024-05-14T16:11:39.510000 CVE-2024-4387,0,0,9ee50ad7bc6299cf393d49fb5522fa18479c94f2c9950e2c45d0cf70a824aaad,2024-06-11T10:15:13.637000 CVE-2024-4388,0,0,684fa93214b643d863a1f4b43d949a4a035e5481cc5c9e9fbbff1ed7d8cb315e,2024-05-24T01:15:30.977000 -CVE-2024-4390,0,0,23c3a5452e82f9d4f4f5a16ddb13514356c7f6fd6668fdaf9447bbf58719ac2a,2024-06-20T04:15:17.857000 +CVE-2024-4390,0,1,e0f292a38c635f40275a1e1f559f35ce9d0874913091030d18dfd937968c272f,2024-06-20T12:43:25.663000 CVE-2024-4391,0,0,606dfcb7000017430c9016faa846742a8e75fccee77649ce6753dd6affa1593a,2024-05-16T13:03:05.353000 CVE-2024-4392,0,0,42aa790771d322d803e80e41696519285313df90a0aa7c7e222147b471317291,2024-05-14T19:17:55.627000 CVE-2024-4393,0,0,104b496ba9688611beda7ef57b83424396e65d62ee7d7a6e8c7b696d3fc66e71,2024-05-08T13:15:00.690000 @@ -253663,7 +253717,7 @@ CVE-2024-4445,0,0,42f5f65e0ec1a0527ed0ebe136ff3e505384e30728c0f33fdcc95acd928f2f CVE-2024-4446,0,0,c1a78a1d4c0d05d17b6cead174a683289ca018fac3b1c104ff2e5b23dbf06e48,2024-05-14T16:11:39.510000 CVE-2024-4448,0,0,c0706d1927abee0ebde095d1bd8c9375ae579980372e3f8e4e4c3b77a255c913,2024-05-14T16:11:39.510000 CVE-2024-4449,0,0,5f461a2e161ed0d547590d7983036c434e3239f67f76e9397bc8163418dcb335,2024-05-14T16:11:39.510000 -CVE-2024-4450,0,0,7a491d8042ff672f697b3ae9dc2b62d6e777c4d0cac1fa3342780217f3c4f06e,2024-06-19T04:15:11.497000 +CVE-2024-4450,0,1,f3937db375fdeba0ae03fdb42a8d22b14895cd6374568384bdbbae27e3da26af,2024-06-20T12:44:01.637000 CVE-2024-4451,0,0,f70e360fa3f5a5d6e18bdbe208091339d7cb5cb309615badd1f0a4ad058c1f13,2024-06-11T18:09:15.847000 CVE-2024-4452,0,0,3d66d1a1960a575e299177a954e31a59092574d107ebd8033a3f44850e26c060,2024-05-21T16:54:26.047000 CVE-2024-4453,0,0,707eb1eb10614c3d7f7f21e0ec15b9b3559f199dd400220131735a7028223558,2024-06-10T17:16:33.460000 @@ -253740,7 +253794,7 @@ CVE-2024-4537,0,0,bc82aa6954c5799b0476dc279149a81ab940e42aa35e918500f89f663af922 CVE-2024-4538,0,0,dbb952ff57fc82a37e26bc4eac10a9f198285e190e0ce1d17eb40564657c4b33,2024-05-07T13:39:32.710000 CVE-2024-4539,0,0,83e8dd6ad2ba7f5df744ac27f19ba7dd20f88687370090b4e13c20c65e81aa4f,2024-05-14T16:11:39.510000 CVE-2024-4540,0,0,dc537153d649e10b7c874b04ae96fc2345a92f4b276e017e0d8b384efb35ed61,2024-06-03T23:15:08.930000 -CVE-2024-4541,0,0,8f81895621381934d510861cb3ed17efdd3ae5fc04fdbba54982b8a485cbc2bb,2024-06-19T04:15:11.793000 +CVE-2024-4541,0,1,4a3da304d2331b57d3e541aebfe20ad4a144b63766e310ccc54304f1be43b1dd,2024-06-20T12:44:01.637000 CVE-2024-4542,0,0,d17f875757344f90ad0b6ea46d223a5444286908c9043b3fba1504d3883c4c6d,2024-05-16T14:15:08.980000 CVE-2024-4544,0,0,5a154bb8f5362adfa7d1d9ca8e07fcce2012291bc3a87e95a1b546af1c241c8c,2024-05-24T13:03:11.993000 CVE-2024-4545,0,0,6a8513e5f42227bdebff4b9eb7cd99ee2da82484e9d02165945026400c877f9c,2024-05-14T16:11:39.510000 @@ -253758,7 +253812,7 @@ CVE-2024-4561,0,0,419f075cb470fc0bcbe1e02ad47a96fd3735721568a3ea0b27d92242ea08e5 CVE-2024-4562,0,0,4b41dac3b3dc0160472fa769fd66d4820687adcd6a603b6680aeb5866557430b,2024-05-15T16:40:19.330000 CVE-2024-4563,0,0,43e81ccbb963e983297369a19c921ee8c5a4d32bc8be4a7c8277c1c258a5c174,2024-05-23T16:15:08.867000 CVE-2024-4564,0,0,4e10c9acbdd4f88d210f4dd1739d9efe5b9317a176118d23abd270246fa28562,2024-06-13T18:36:09.013000 -CVE-2024-4565,0,0,9e16384c1deeaddd0195082106205b41a2710419ce70589e041320cb81ad0ca0,2024-06-20T06:15:09.950000 +CVE-2024-4565,0,1,67d994d050778f99ebea00dffeedd75aa1729789c9eb9581753d556845ec5e7b,2024-06-20T12:43:25.663000 CVE-2024-4566,0,0,5bf64390fca62ba0e88600d1f0954e23dea48d7610695fd2ef891697361d3217,2024-05-21T12:37:59.687000 CVE-2024-4567,0,0,bff521ec958712c348010a89da0e0aec519b6a717613a798e9a8fee426de5e74,2024-05-14T16:11:39.510000 CVE-2024-4568,0,0,79c6e65478e2e86d702896e792fead76bbebdb118f8c0f66e6390a241a22321a,2024-05-07T13:39:32.710000 @@ -253805,12 +253859,12 @@ CVE-2024-4619,0,0,e5a9884a731cd527eccadb69d8fea8c7f9c7a04a1fc119314f14a8f7a5fe1b CVE-2024-4620,0,0,aca290e81a01c9aa0297c2a2a6f363e13c691584f35f3993ff959e5f7ab27226,2024-06-07T14:56:05.647000 CVE-2024-4621,0,0,0dcad97674134d7acc0f6a3b23542c7c7b4811503a20f42bfd18c3bed8fb5fba,2024-06-07T14:56:05.647000 CVE-2024-4622,0,0,4b1992fe33b227c66e64bdd4cf1c71e31b73a98abda6bdd8e7687e0db4e86196,2024-05-15T18:35:11.453000 -CVE-2024-4623,0,0,cd721a04521d6e02c865f3b0b5d4fa5dafaaa0badffaa20fa9d718d9a931704d,2024-06-19T04:15:12.107000 +CVE-2024-4623,0,1,47ffc2e7580d30150a9d70c6a59a76ed1e3bc3dd5141525204779a13dc1a77fb,2024-06-20T12:44:01.637000 CVE-2024-4624,0,0,2a601b2b9934f4e4184c90fc3ba9cbddeec712a59701e0372ed6d18cfcc3b7c7,2024-05-14T19:17:55.627000 -CVE-2024-4626,0,0,1737ca763d8dab682eb9c7440e886feabd631f674bded8e18f747432571b5179,2024-06-20T02:15:11.270000 +CVE-2024-4626,0,1,f72dde4d01fdccbcae8f7fa43d1f4fdba6634ccf9a4eedc330d8e157eccf8120,2024-06-20T12:43:25.663000 CVE-2024-4630,0,0,f5808b44be131bdae6b6920228d425b0dd235ef4afe8685cc2ea30d538a619f5,2024-05-14T16:11:39.510000 CVE-2024-4631,0,0,e8ed3d07eca49fd9ce5a62406bcf23da9793cbcc792a956665a267b4f25fd693,2024-05-14T15:44:13.487000 -CVE-2024-4632,0,0,171126908555386a9eebbbcc3e4f5f7a8e1ab1327161a7a2dc0367d749ddc44d,2024-06-19T09:15:11.740000 +CVE-2024-4632,0,1,34df16eb26fbe037cb544d7499c4d02f03b9e69baf43a3990c97609a249304ed,2024-06-20T12:44:01.637000 CVE-2024-4634,0,0,26305cc83de7193b57243a5cab6ca5caf74694a0d7bbca15218a554118aa8eb8,2024-05-16T13:03:05.353000 CVE-2024-4635,0,0,39b2c6bf6977107b11329776563f920ebcfe13f250d063c0984d8282a28a8353,2024-05-16T13:03:05.353000 CVE-2024-4636,0,0,408131d6e6f7a1de019141a0a08ced7ddc9316cec6084c2dbfd44b2d5b664bc5,2024-05-15T16:40:19.330000 @@ -253830,7 +253884,7 @@ CVE-2024-4654,0,0,eca077048d127add67f133585649496d1af539c8d39e41b186d99947e2c0e5 CVE-2024-4656,0,0,23093c7ec18a8f42da4c8fc1c86b9aa6984d979cf63954576e1d332548405180,2024-05-15T16:40:19.330000 CVE-2024-4661,0,0,e86145aa3dfc1a1e846a3970af65d72463f2a51aba17ea6b9d5a34de37b2fc53,2024-06-10T02:52:08.267000 CVE-2024-4662,0,0,271820e0248036cdcfeea2da470b958f93caba3600263b2df375c674d931507f,2024-05-24T01:15:30.977000 -CVE-2024-4663,0,0,5093a4590cc188b434b70527cead1f0677701d00c0a0a1f762d93a826b9c03ed,2024-06-19T04:15:12.403000 +CVE-2024-4663,0,1,ac32c04a2cae0071224eeefc80f9a000b8618e2f1af1abc8eb33d3a9321c7d70,2024-06-20T12:44:01.637000 CVE-2024-4666,0,0,dde8d66c76bdf850b898b9f95df0d92f0ac3da730c1f32826d61843a6ef06bf5,2024-05-15T16:40:19.330000 CVE-2024-4668,0,0,3c2f34d91ee8c9aacf0f125fe94ffbbe9a611b8f1a54ab65e0473cea71baad6f,2024-05-30T13:15:41.297000 CVE-2024-4669,0,0,cb3ea770e599714f2de5e50bc4195c130850e813b58882b88bfe234ded1dcd7f,2024-06-13T18:36:09.013000 @@ -253896,7 +253950,7 @@ CVE-2024-4735,0,0,525831e83b784b99ed7ef48881d0a232b57485de376b3c68786c9225fdef83 CVE-2024-4736,0,0,35e0fe51ccd6e16c666173722ffd72f471827cead112caeaf869dd95515427ec,2024-06-04T19:20:48.497000 CVE-2024-4737,0,0,0d605ad76fcca9d9a8748ea1570213b2a20be8e7af59e1490aa0de37640ee426,2024-06-04T19:20:48.597000 CVE-2024-4738,0,0,703597dd680fa7def2747a141a4237503bd7e8917e070a49546a7e715e951f69,2024-06-04T19:20:48.783000 -CVE-2024-4742,0,0,950346e30ea4fa96f70dfef723fb3b7840bcad29ae25b8002204ca2d63cef11d,2024-06-20T02:15:11.500000 +CVE-2024-4742,0,1,e35fdb079407834fe9eb2dd0070366e163ef435c09e138979a25f59ff892ff7c,2024-06-20T12:43:25.663000 CVE-2024-4743,0,0,e42c9380fd03fa2e7e8dd1d108eb6ee48e234f06ee604011f8e8a51de81bb3cb,2024-06-11T17:32:50.367000 CVE-2024-4744,0,0,00389d0f632a53abd6687abe1695ed0d94106b42a5446a5e1de91a20dcdffac8,2024-06-12T16:44:12.157000 CVE-2024-4745,0,0,52090afb58a281a3371ee6c6ad54ec80b0aac7a7ded5dbbe0e95b57b1a9dc746,2024-06-12T16:23:34.197000 @@ -253925,7 +253979,7 @@ CVE-2024-4777,0,0,463b2af71f8f2a9d1c562c36b6fb26878d601ac505a437b31aefb6540cc53c CVE-2024-4778,0,0,37531b60d89a44d35c14fde25587b4d8cbf891fd39da513ae2adbe2646535312,2024-05-14T19:17:55.627000 CVE-2024-4779,0,0,e93e79f4a86fab8cb11a3f6a53c3afceec1606ec76ba934e81e552f2e4a9a244,2024-05-24T01:15:30.977000 CVE-2024-4783,0,0,daba56adbc0652555be3afeccbdbe190fb7cbe9964b63627bf6508f75d28c65f,2024-05-24T01:15:30.977000 -CVE-2024-4787,0,0,0634b5ae623dc2a3f970d60256690d931423d37861b65ad1443a3e504a5b5c0b,2024-06-19T04:15:12.730000 +CVE-2024-4787,0,1,20a16e1f74cb3e944eacd8337852aa9641c9a9f479c35a6b627f90bdd3958503,2024-06-20T12:44:01.637000 CVE-2024-4788,0,0,1c9a8fbf6bcaa04fd9a337cf6b1788c99808cca0f3735caac5c9d9e2c279004c,2024-06-06T14:17:35.017000 CVE-2024-4789,0,0,c3ead1522386330c98ef03f50054b683a63e62c43c9e3867ea226ff37f2983a1,2024-05-17T18:35:35.070000 CVE-2024-4790,0,0,9ca82e19e832a950283217f2bfd1db7efd6838c8a8bf54a7d78165e2752eb0b9,2024-05-17T02:40:36.990000 @@ -253987,7 +254041,7 @@ CVE-2024-4863,0,0,0f2a759d2230ea6d690206f8dcf95872d885a68184080990b57fd14696b638 CVE-2024-4865,0,0,034a7c12f3d6f4bd5ac54ee1f34abd70a559c5b9a18ae852351f79db6d61b9c9,2024-05-20T13:00:34.807000 CVE-2024-4870,0,0,789ccad79b53f3162faaa4d0c14e00ab550e7e413c46a4332529e5d35d1d0423,2024-06-04T16:57:41.053000 CVE-2024-4871,0,0,089a89f3309c27433f20e3be4ef9a00379f9f19601c1c8029649846113aed43a,2024-05-14T19:17:55.627000 -CVE-2024-4873,0,0,b5297926ea8d8726afad8cdbe9f36c5996133b3dce2df8fcf7cd1919ebcb1e78,2024-06-19T04:15:12.990000 +CVE-2024-4873,0,1,6d8194e640b182e2a2eb107c362a6b36fc019fdb0666ba51ea48c7f29b4462a1,2024-06-20T12:44:01.637000 CVE-2024-4875,0,0,aa35cb89fee530b58aa987ffc67ea97738c0ba567903bf01429a1a1259923db8,2024-05-21T12:37:59.687000 CVE-2024-4876,0,0,02aac8d1be489833aa2e07f8be8ce083249ac7dc2fcc33fd144386b8d365fef2,2024-05-21T12:37:59.687000 CVE-2024-4881,0,0,4f17be95dbf63ebb1e221e9270b941e4838c9b4d4b1f7c998cfbd25da7153e04,2024-06-07T14:56:05.647000 @@ -254078,13 +254132,13 @@ CVE-2024-5000,0,0,21f44bae275ca5e7f3a45da963612f2fb705c74e44c15e2681f54ff4506e6a CVE-2024-5001,0,0,bac0073c23ed28e836068e8632acf1110bc49b73246f9cff53f5a706acc4a57d,2024-06-06T14:17:35.017000 CVE-2024-5003,0,0,d7f0fc1b6b7797a26bbde28f3345c21309ee3aa5cb19350abdc4f1d0ca9ec31a,2024-06-07T14:56:05.647000 CVE-2024-5006,0,0,982820e7e91a551bd12476d9f6731c77df87e69f9a4499c2643412449b7b2aa0,2024-06-11T17:36:24 -CVE-2024-5021,0,0,6741dd7fe6cfc37a6c6b7484b86a601d6466e88034b83883016a9a8e99345405,2024-06-19T04:15:13.310000 +CVE-2024-5021,0,1,872edc6307495a559587b3d1d37e361f617cf9935ecc4133654cc9effee7c33c,2024-06-20T12:44:01.637000 CVE-2024-5022,0,0,106355f86b530d1586a5d339031de27a1a2312467a76eb449e8e9901150235d8,2024-05-20T13:00:34.807000 CVE-2024-5023,0,0,974704283893df4cc9d8e0bcce8bb65ebf635268235f75f47c922033893214ce,2024-05-17T18:36:31.297000 CVE-2024-5025,0,0,d287dc9bcba0fba1784ec3f3fe4bf65eea235ed5e6f91d741018beb442d992d7,2024-05-22T12:46:53.887000 CVE-2024-5031,0,0,e598ebc5c9fa457f9bece560d72de6fc8851ac943a5e7908ec776eb9202f17df,2024-05-22T12:46:53.887000 CVE-2024-5035,0,0,04b94f66274e3d3d22c52a6f453c8b285ab22579cfad76ef028d6a110e1aa148,2024-05-29T05:16:08.793000 -CVE-2024-5036,1,1,b6a781315c42c4b8b49e1f2649a8f7674d4e50a4b7588101a14d43dc8e75c278,2024-06-20T11:15:56.273000 +CVE-2024-5036,0,1,e3ae54d07fb41ce4fd356143d834c0744cccfcb0f7c15179bf5d5b0f79f65ca1,2024-06-20T12:43:25.663000 CVE-2024-5037,0,0,5a13acce718f507f5063e90d1fbe76947aa8c069dd7062440b3d79f97548841b,2024-06-18T17:04:31.360000 CVE-2024-5038,0,0,06b42bf2f2d8413cc0f40932a00eaaea0786a8ef2cd369c2d799d355c720323a,2024-06-11T17:41:37.883000 CVE-2024-5039,0,0,42959b486bf28971702f84d5d970f64301a550626d1348beb35b7505e0fa75c5,2024-05-29T15:18:26.427000 @@ -254188,11 +254242,11 @@ CVE-2024-5165,0,0,1249b447729c1b58db4dd874ebf3238410613919325ce73c31963c57eb2e60 CVE-2024-5166,0,0,acd04bdcb3927ae2fc6875213ce44649287d9e14ecc961e10fc982fe1f8beeeb,2024-05-22T18:59:20.240000 CVE-2024-5168,0,0,306ce12eec3dfa604048647f5d45c62ae3c9962c8122be3c41030f354ed300c2,2024-05-24T01:15:30.977000 CVE-2024-5171,0,0,48a4e93c0e5c114307317a61f5ebb55a23b4e7180462277e993e611f49dd510f,2024-06-06T14:17:35.017000 -CVE-2024-5172,0,0,6f81a674f5782cb8792fa5dd56ecc7e266f5bfc474a6989e555bcaf073124def,2024-06-18T06:15:12.440000 +CVE-2024-5172,0,1,c11e28cee00d03ca550aa31f6a4a4e2619eb7f584486db6cbc532617ccc0d3c9,2024-06-20T12:44:01.637000 CVE-2024-5176,0,0,d56ed998903dfaef1849b554412c043d7bedaec08a06683735e348a1e4cdd46d,2024-06-05T15:15:12.620000 CVE-2024-5177,0,0,754731e9b12ab9d5b8190add19111b94a5e340744a68664c6a765c48e93c422c,2024-05-24T01:15:30.977000 CVE-2024-5179,0,0,54358caa6e0360966d6f1b65f621cdbf9937e802ed8f2b5c2ee31999cdede484,2024-06-06T14:17:35.017000 -CVE-2024-5182,0,0,75843e136ff752684512fe999e6c26d863acb5df23a67529923a59ab0a6bd209,2024-06-20T00:15:09.487000 +CVE-2024-5182,0,1,05eb067250c704bd4c420313ce1da2aeb70843fd4dce4dbb10fdc9fbc9defbb8,2024-06-20T12:43:25.663000 CVE-2024-5184,0,0,de97ef0558df300043d1123a6fe8d6e2df5444a09bff76f28ec8a01317d2d79c,2024-06-18T17:06:20.257000 CVE-2024-5185,0,0,b5caf3da810dd6351b96bbd5e231331a05f92e8956c63f18c155c13a8af19485,2024-05-29T15:18:26.427000 CVE-2024-5186,0,0,c6b2efdad9b4d04477e8bc0a562c3aef2ed32ffb2bffbc88ea5624073db9f4b8,2024-06-07T14:56:05.647000 @@ -254212,9 +254266,9 @@ CVE-2024-5204,0,0,f5f46d30f5f5fcefc4a351787eb0bfde8706d10be20e1d771d5abcd1008399 CVE-2024-5205,0,0,cb36ec671fed104039900e6835467ad487e54c052bb39844cd3bc6979a6fc551,2024-05-24T13:03:11.993000 CVE-2024-5206,0,0,dfdbb2d2210fa9604e6469b5345cbda30a0f0ae57d39e7dfc070825e6f931647,2024-06-17T19:15:59.190000 CVE-2024-5207,0,0,837facf8fac5843bbf7aea1ce36fa00287f1ba077f8fbca1302b0ab4087ec522,2024-05-30T13:15:41.297000 -CVE-2024-5208,0,0,ac2fc4715d85a3e7f4f64d0ecbe8e701363c156621f940cec8a96468853fa2ea,2024-06-19T06:15:11.420000 +CVE-2024-5208,0,1,3985337bac39b70213766ebf64511613ec02cc254f1933a2c8ecd567239b3cc0,2024-06-20T12:44:01.637000 CVE-2024-5211,0,0,a4277f26aaa565cc417eac86a473b48ddc12386cf29490b9b3d30644e664c347,2024-06-13T18:36:09.010000 -CVE-2024-5213,0,0,03605ea4a03b33511830b296d344f60cd868c58f83804e2bd653db0d056f404f,2024-06-20T03:15:09.067000 +CVE-2024-5213,0,1,5a68006f91028e70fb3202f4e898c6483c20faed2d33be845b22e07c07dc81e8,2024-06-20T12:43:25.663000 CVE-2024-5214,0,0,77a86526714522a20940695733fe46b4562089752d3c663cf289b583b7c6bbda,2024-06-03T19:15:09.360000 CVE-2024-5218,0,0,928b5f8d4e08afc285c0cf6e370373ec87899b716b1cb4db68027907b01d2a82,2024-05-28T12:39:42.673000 CVE-2024-5220,0,0,f61a4e43424028e9a9336f6f6ed766295c86a8a5421f6ff87daa2be13ac80d02,2024-05-28T12:39:42.673000 @@ -254261,7 +254315,7 @@ CVE-2024-5271,0,0,d3f4377983bdb14b36061f7826a2769c4b74dac3ab0fd218e99cb4bdcc673a CVE-2024-5272,0,0,485554be89aaf429d625f742d41620b7105b55f3f82c1bd7e7c2afb7e9a676c6,2024-05-28T12:39:28.377000 CVE-2024-5273,0,0,f7b775afc6e46cbf2933f26022bd5d6a5054d80bf2d607df2ea5eeb06bc0b97e,2024-06-10T18:15:38.157000 CVE-2024-5274,0,0,815675421e4b9c2b34f2340865cc1ed903b3b9cc89dafcd7624436bba1c58088,2024-06-10T17:16:34.257000 -CVE-2024-5275,0,0,3fb2b6e2f4f5581f7159d80c2786ba7ce437c9192c9875764b2c058bc3295bc8,2024-06-18T15:15:52.493000 +CVE-2024-5275,0,1,b81fd6634b953b380acd7d67040183676d61d3e908aa91611721c09fa7243801,2024-06-20T12:44:01.637000 CVE-2024-5277,0,0,08c2f56d5f9c6263336a67bd47c4fa52288bb09bcb2d8aeff245d6d39899edcf,2024-06-07T14:56:05.647000 CVE-2024-5278,0,0,ba4b6329b00a48ecb03cef9d2f0cd09adc7cfa79e9cd9e8eb891a1136335fb69,2024-06-07T14:56:05.647000 CVE-2024-5279,0,0,1f630d4d53c39cf2174e2a1edce8e1a5ead56a314739580d23644f8e4fedef07,2024-06-04T19:21:04.240000 @@ -254301,7 +254355,7 @@ CVE-2024-5339,0,0,dff314e9f4c01abbc68b16981f5aeded8be46345bf871723981d333f3ae3b5 CVE-2024-5340,0,0,b7957b42011f8f774e1db1ddaec566846336d3063a4d70dd9b49754c316b8f99,2024-06-04T19:21:05.373000 CVE-2024-5341,0,0,2b72dd4ef57e598a2469a1d6786a4762ce0fcb8187c35f2f4bd1ff39b4044b7e,2024-05-30T13:15:41.297000 CVE-2024-5342,0,0,2ad102e094253384b79cb972f14f27186ce8a4683bb8eb4d7004a3553600b118,2024-06-06T14:17:35.017000 -CVE-2024-5343,0,0,47cfe4d550f1f0dbfee9a2af60d2296f61f9aa0a2239b425798aba3eec939905,2024-06-19T06:15:11.723000 +CVE-2024-5343,0,1,9c4ca8593b34d766d7b52cb001faa9ca8155eefb491f359cde7885e1510a1702,2024-06-20T12:44:01.637000 CVE-2024-5345,0,0,6eb378e53e73ecd765d027e2916fd67b3a9d8ae24f673780d53a54e981925c7f,2024-05-31T13:01:46.727000 CVE-2024-5347,0,0,1da2ccb898789a7c7262d2aa6524b222bbe92ed9796804e25855dd4dd20a5fae,2024-05-31T13:01:46.727000 CVE-2024-5348,0,0,cdabb7de233f48a7127c4333bb3ba86c3b13ada38da5d506ab1226337e3a511b,2024-06-03T14:46:24.250000 @@ -254375,7 +254429,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-5432,0,0,c03f9b3047ee58a33a5e5ee412fc11310da04ed3865ca3a5438e8299a0046ea3,2024-06-20T02:15:11.737000 +CVE-2024-5432,0,1,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 CVE-2024-5436,0,0,512ff808a53596bd19353e26c03602bd4b39921efe131952ebcd76460c505fa6,2024-05-31T13:01:46.727000 @@ -254392,7 +254446,7 @@ CVE-2024-5464,0,0,20ac6d6efa943df789ee80e23b81c0dadba3276ccc683b7cb6fcce26ba339b CVE-2024-5465,0,0,9b677e9ed42136d68b443cf9dc4afa859310d29bdd1dad1920c040ce3c57d334,2024-06-17T12:42:04.623000 CVE-2024-5468,0,0,2bc9c38a1a2994a4c4ceddf0376e8b3ff5412f95fe840378ab4577710a81e066,2024-06-13T18:36:09.010000 CVE-2024-5469,0,0,a6ac25b89021bcbe477171d4304d10733bc198409739b73a4d379d6ba636b5b0,2024-06-17T12:42:04.623000 -CVE-2024-5475,0,0,097636162e4977d156e22d79d1f6c03e0fc9dc771a7805003543c3e6b3fe955d,2024-06-20T06:15:10.077000 +CVE-2024-5475,0,1,9a35a27ed618b47a569e72c9eedce24392059deeff1f9ce687dca2ba057faa99,2024-06-20T12:43:25.663000 CVE-2024-5478,0,0,cbce39d40f4102e26dfaf35e6a6b20bf349245ad3d94d864b4543f6f43a9d245,2024-06-07T14:56:05.647000 CVE-2024-5480,0,0,0c96379cb76c4f8b6d9852cdcc0f60ebab5e5f97f64e4439ef99fbfb3e3714ee,2024-06-07T14:56:05.647000 CVE-2024-5481,0,0,7e1e4455e255ae80e6041eac91512213cb57b2091c06ce10c4272331eb1d58af,2024-06-11T18:00:09.740000 @@ -254422,18 +254476,18 @@ CVE-2024-5518,0,0,7be8efd54096829bb11c5abb04e19bf1a49b1768c0ad36f7ac88e032ad73e0 CVE-2024-5519,0,0,676af88d878b937cce3af5b28731e1191247d663004f92c739f5db0d966e0d3f,2024-06-04T19:21:10.043000 CVE-2024-5520,0,0,63f9c32911da3f67c58779f2c8ba34d9aa4b55d3386d570dad5bc0397c8cb5db,2024-05-30T13:15:41.297000 CVE-2024-5521,0,0,ccb2ba49d7e4be9859a81cd0c950d08f47c4a44700fa46f5775af6da3418abbd,2024-05-30T13:15:41.297000 -CVE-2024-5522,0,0,e90f5c28c2f7d912ff2ae30546e3593ce47fa168f0624b0e32070153ce1d46fc,2024-06-20T06:15:10.197000 +CVE-2024-5522,0,1,c96fcc2950cb5d3776a6659e311c7cdc83ac15b85b1861dfcc027e4e48db75bc,2024-06-20T12:43:25.663000 CVE-2024-5523,0,0,047cc71fb1f4320881d428c79c80679ee2da549498da604407797261c69d069c,2024-05-31T13:01:46.727000 CVE-2024-5524,0,0,e7e0fe13822be5d672aca31e1ee31e0f364bc62cac379db56dfa86e4e6649c5d,2024-05-31T13:01:46.727000 CVE-2024-5525,0,0,27d51e0f90117d5f6e29d565f6efd293c83de249201cb9426e9c70697dbb918d,2024-05-31T13:01:46.727000 CVE-2024-5526,0,0,e88e82e62b5e4c5aebe68213504a5aa190a1c186279f7068714569f91c3de73e,2024-06-11T17:25:55.677000 CVE-2024-5530,0,0,a1a0702e27e4a4e3934db43cd9ea561e00ac905016f120852abcc67a37fa7a55,2024-06-11T13:54:12.057000 CVE-2024-5531,0,0,aff596c4345d9e9649e4107c993c40fc7416a56fa205089ee8692b6e8ba6cecf,2024-06-11T13:54:12.057000 -CVE-2024-5533,0,0,1c4322ac76e572f0c173bcdd34efadb5c3ffbed7ed1a6e60f6379858613a9887,2024-06-18T08:15:50.723000 +CVE-2024-5533,0,1,1994262e08a7071f611be7c6d84dc9ffdd2ad4dec717c16feb005eeb66301b8d,2024-06-20T12:44:01.637000 CVE-2024-5536,0,0,d892d63cd79e6d462fe4485ce154b4e3b14e14d416b8b4d67114661d27280a01,2024-06-11T17:28:37.343000 CVE-2024-5537,0,0,071475eb8c0f92cc8ea9522d658283ad0e8213ba6740ff46ee05e5b24c18c3d8,2024-05-30T17:15:34.583000 CVE-2024-5538,0,0,183cea799fa9410e329e72f326a10b8369aedcea9a5b7583a44bf33ecc305070,2024-05-31T11:15:09.923000 -CVE-2024-5541,0,0,abee97a7911b8ced43e1d9fd59bbf81c997c44a26dd0413a404147eb4da33232,2024-06-18T03:15:10.020000 +CVE-2024-5541,0,1,3cf16189373492b41668e36a2b5359be696c8d9818a4c855e885b2ed02acbca6,2024-06-20T12:44:01.637000 CVE-2024-5542,0,0,77ae3f3a7c4ffc662d4e5625f82b1efcc56a12c39abbd3546ebc6e9e7e619033,2024-06-11T18:25:51.200000 CVE-2024-5543,0,0,8e93e3d42337fd51f8d8d19b50b3f68377ba39e905a95b2594b9c3824c59b9ee,2024-06-13T18:36:09.013000 CVE-2024-5550,0,0,e4fc13aea5b719d7c555043aa9a8be47a59e2f4d5eac2e9fa0d5ff8a8edb892f,2024-06-07T14:56:05.647000 @@ -254447,7 +254501,7 @@ CVE-2024-5560,0,0,f1a6e79f857dcb0da00298e85540b2901c155f3f4e8e842ef291f9f993b61e CVE-2024-5564,0,0,dcea96840208d2ac663aaa4f0f3c3d4a29deb4a56217e3b064f75f0ccdd62128,2024-06-19T20:15:12.277000 CVE-2024-5565,0,0,830316f5c713618fdad4a0eda5b7296c22d5d93c87a8813197db3ff9cf28c4ee,2024-05-31T19:14:47.793000 CVE-2024-5571,0,0,105c4e644019eeccf72c6e63813cdc36601b1b9a7e3cba5bc172df86631261e6,2024-06-11T17:29:03.277000 -CVE-2024-5574,0,0,e61398b52e7e578c38514d99e1cd854ee3b9045f14e28a4d2db6de7566257631,2024-06-19T06:15:11.993000 +CVE-2024-5574,0,1,3e624f806d94dcff352fde1d5be73aa27a333a70d66ed500b1d4bd0c17214488,2024-06-20T12:44:01.637000 CVE-2024-5577,0,0,0394e112329dfafbe6884a2484f7873076e1a8201ddc51d40c9b2393b5d88276,2024-06-17T12:42:04.623000 CVE-2024-5584,0,0,612eacfcf6c3fd3d6fdd0ff2c66e496cc817b02568ea9f69c40277bbc0300578,2024-06-11T13:54:12.057000 CVE-2024-5585,0,0,7ca8acd7f48a83dc2f9c7f2dbf799bd4542c4abbbf9453c8a4fa401160a3a849,2024-06-13T04:15:17.407000 @@ -254457,7 +254511,7 @@ CVE-2024-5589,0,0,dc63c38434ce5bb089af0d0f8aa09f6a46f1fae34dd45c15f4542741dea047 CVE-2024-5590,0,0,ca60332ff9933405c7b9b37e93d2404b53274b9ec741b4065c0c1eadbd60da94,2024-06-03T14:46:24.250000 CVE-2024-5597,0,0,652827ff26b80eabae5b3eddf519a61b0da7de181ce61fd257911ec48c45cdb0,2024-06-12T18:10:47.080000 CVE-2024-5599,0,0,e4d8d3217ca804a33354b51b54e1f3f41ce0e1fc1f554dedfe90ad1a46a87370,2024-06-11T18:24:39.057000 -CVE-2024-5605,0,0,92a314be0ccc9a24209380c359e9e1dd4a66479f45e5316bf6f0fe7c37e61024,2024-06-20T04:15:18.590000 +CVE-2024-5605,0,1,4bb70fac398eb5e1fc6a3b8761dcfee9993510711b196c5d9f90dc1e34c785a3,2024-06-20T12:43:25.663000 CVE-2024-5607,0,0,9601597658129a089207c1a0e7e7267aceda952302ad39754d738e7307549543,2024-06-07T14:56:05.647000 CVE-2024-5609,0,0,f28c83e3e9d04345913d36de3bfdbd0d644d73b3d20045d9399b3368319c8d47,2024-06-06T19:16:09.920000 CVE-2024-5611,0,0,7f38716b1ccbe035f7f86ea6c7617ab6f4cac8651e00e7906bbdbf77091ab5a1,2024-06-17T12:42:04.623000 @@ -254472,7 +254526,7 @@ CVE-2024-5638,0,0,ecd29107ace2c39372f8ad7d26b6d92a031cf986dc4e07d96162e8140ebd09 CVE-2024-5640,0,0,86163b3d741cee0a4e50ef8553f0c82f1f0c15bd48d022d2d250ef0f55c23f10,2024-06-07T14:56:05.647000 CVE-2024-5645,0,0,1faba0fd6e05694e3fff7011c206b3ecee3c45fddb7e6c575993af231224a181,2024-06-11T17:57:47.197000 CVE-2024-5646,0,0,23240aeec5f40e46e6951e19eff4b72273567c29932f06ca0851d3144bb5ebaa,2024-06-13T18:36:09.013000 -CVE-2024-5649,0,0,f665abdaa2c1bd0ad8c015322d62e738c982959dc32c2a416c1178883f55387c,2024-06-19T04:15:13.583000 +CVE-2024-5649,0,1,dc95f59c6efdf5cedf3d7e0f6c5bd262dc96a14a6be79337241ad862a0888246,2024-06-20T12:44:01.637000 CVE-2024-5650,0,0,65f855892c82055621a01afe5dfbac2eeb37ab3d50eb12f09dc0d9a40779b9ee,2024-06-17T12:42:04.623000 CVE-2024-5653,0,0,283076b6ccce08ae3d1ddf9d7f5983a839d66c80929543a8a527d0bfdf86a2f9,2024-06-06T14:17:35.017000 CVE-2024-5654,0,0,e22a0b433d38e113ff7c2fe935a2ac4a2eac96ee27b605312aa4a4c8d50d69a0,2024-06-10T02:52:08.267000 @@ -254487,10 +254541,10 @@ CVE-2024-5671,0,0,b302da9933b51baa02aebe638443397fc8a4c366af898c1301a8da65258325 CVE-2024-5673,0,0,f6db27a8b7c99bb0a58922425d96edcb461eeb527f78adfd8d9aed9c99330140,2024-06-11T18:17:10.037000 CVE-2024-5674,0,0,69b0f5cdcc6414c1b3093ac76e322fc42e17eb869b8f1b328084f458395232cf,2024-06-13T18:36:09.010000 CVE-2024-5675,0,0,c04fc1bf8ef6e3f232c30ddf0bd6a524958c9eab63fe205331e1fedef14ccf13,2024-06-11T18:14:02.017000 -CVE-2024-5676,0,0,5a121d6526be119c8e5c7b8c110cf59258470155d78d7100c259e2e0aea78192,2024-06-19T10:15:10.740000 +CVE-2024-5676,0,1,473afaf284f71bf5a70da32132b549e65bb38e43f74153bdf5c4c7ebd172ca40,2024-06-20T12:44:01.637000 CVE-2024-5684,0,0,e183f6f3c944efddc1281bf86b4d20b3677f4c3ab127fc0c8f4bc522f6d9ba19,2024-06-11T18:13:30.163000 CVE-2024-5685,0,0,e8364a4460a12edf9e3cf94a37b74977806b751958607c5dfe543a64e3c22871,2024-06-19T09:15:12.173000 -CVE-2024-5686,0,0,1f0374400e47fda8fd1ffbab58c7b25a04b08df944ad48074abfe60adaaf3e8f,2024-06-20T04:15:18.890000 +CVE-2024-5686,0,1,5baef36d265e76c8a185391151bfaa15c3d3a21cf5116dcf4f0b4cb376e1e9d1,2024-06-20T12:43:25.663000 CVE-2024-5687,0,0,b3163ba80d711118288940f35942362f888184d516eedb8a121f43c8b6e99d13,2024-06-11T13:54:12.057000 CVE-2024-5688,0,0,95b546c05aa2ff613844572a96d4d10e5d464e0191f6ea34f9e436196d40e472,2024-06-19T10:15:11.017000 CVE-2024-5689,0,0,43d9e6c4643e481c8669e8de5c0cdbeeb708721474986d0f913b6c90e34aa5bd,2024-06-11T13:54:12.057000 @@ -254507,7 +254561,7 @@ CVE-2024-5699,0,0,d1e1ab6a164c3c763187b9b9eaa5ede2a373113d6efcf901de284e7d644c77 CVE-2024-5700,0,0,bf41828814d49bd1ca21d234dd56d9b9baae6eae1faa482eef0b223ac08cdef3,2024-06-19T10:15:11.510000 CVE-2024-5701,0,0,c0b77ae9f34889006ada566ff239d80e91c1e1e51e6239a509f45a6d387ce8ce,2024-06-11T13:54:12.057000 CVE-2024-5702,0,0,050114b692a9d22e1a3779ff238583d9efc9d6e8072ff7c077a659f94eb85b8c,2024-06-19T10:15:11.583000 -CVE-2024-5724,0,0,24dddb5050acc506e9e5eeb9f762d2a963da30de50c8c0e5d9cc8895166543d7,2024-06-19T04:15:13.860000 +CVE-2024-5724,0,1,03384c71395c84af225b0ffa60ba9818c028df2b73c4ae064cd0a263a53e8317,2024-06-20T12:44:01.637000 CVE-2024-5731,0,0,f8f18711dc1e7684e37f428b0d6e39ca275690790dad9599ea32c8e89b131e02,2024-06-17T12:42:04.623000 CVE-2024-5732,0,0,2b69cb5542c2f91e3e2021ac007049b3634a9137bdf0c325241236594abc7cc6,2024-06-11T17:57:13.767000 CVE-2024-5733,0,0,78152e13cdabf162486c62849d39e4c95e26727ad5623fb603c3826108c4ab9b,2024-06-11T18:30:50.690000 @@ -254522,7 +254576,7 @@ CVE-2024-5758,0,0,250b274bfcefb72defbd26103c82d5c8ed585b7571d3785565c3013fdb6e4a CVE-2024-5759,0,0,a8b20ed9df5a502bc1dbe4283a67eed19771ffb4a4f02a90724215ed5101a898,2024-06-13T18:36:09.010000 CVE-2024-5761,0,0,e0022a8d80317cd3941058bae14b514f68707790a5051038049a1d552ba8de69,2024-06-07T19:15:24.467000 CVE-2024-5766,0,0,f4f0065e1ad74a475f6d00e1f328df39da374dfe97f7b4c54df1858a2ce42e5e,2024-06-10T02:52:08.267000 -CVE-2024-5768,0,0,883a7648b70c7db908481ffb4058973239dab8acdd6105dbbe5f540b4ae85522,2024-06-19T04:15:14.160000 +CVE-2024-5768,0,1,4723f0c08a5f7c047718f7b87ad6f2c66db14b3e8d318e841a1bb9034ace5943,2024-06-20T12:44:01.637000 CVE-2024-5770,0,0,25b3f0241d69604556f37a6471fa9a6892ce290ef4b03f2d5525dd585c681fcd,2024-06-10T02:52:08.267000 CVE-2024-5771,0,0,378b86ddb7266a39f3407b18465f75a96b2cb76a6e911ad726ef8ee0f827d15d,2024-06-10T02:52:08.267000 CVE-2024-5772,0,0,5d02fcc48cc4ed4858aa4bf1d7006f9e16a6fd1e467e74217e74d7e97c0dddba,2024-06-10T02:52:08.267000 @@ -254558,19 +254612,19 @@ CVE-2024-5839,0,0,9385cf79947c22201f388072890d4a84ad896bd84a0c79be045472d41533d8 CVE-2024-5840,0,0,41d5814b56b31241400aef4aa8c21488bc60dcb0127be4480bb3f70878d720bf,2024-06-14T06:15:16.280000 CVE-2024-5841,0,0,fc2825c590d3dabd7d249c734745bb1917b16d1b1c72fe6b085504236fbe4cc5,2024-06-14T06:15:16.640000 CVE-2024-5842,0,0,301d3a395c81e4dc9ba2691b2833db68fc5849d1946b31ae7783d35485ed5340,2024-06-14T06:15:16.913000 -CVE-2024-5843,0,0,81371d406cade98cb83087451923af34bb6f5ea9eaf77c377946b07408120495,2024-06-14T06:15:17.170000 -CVE-2024-5844,0,0,1c3a78f056ffbc9b1ed0a3a188f5811994a2ce518b4c74d8268ec52de232e3e2,2024-06-14T06:15:17.517000 -CVE-2024-5845,0,0,28e710c840580f9b5d0c9aab1fc91ec1984fab91f431147e1991ab23cd56311c,2024-06-14T06:15:17.790000 -CVE-2024-5846,0,0,8596c41192d23b04ffefaebe0c667db32523a400050cb25e84292f5e37a4f295,2024-06-14T06:15:18.070000 -CVE-2024-5847,0,0,76f96d2cf40d152418dfceab1870d176c207d7169255daea84a0ed5e5bb52b47,2024-06-14T06:15:18.340000 +CVE-2024-5843,0,1,b053c19dc1f27009bdf49ecd84eb42ff5cf8eb4bd496e96f6cb04053a0843a6f,2024-06-20T13:22:50.317000 +CVE-2024-5844,0,1,2d28c41604a9ba82bebcd99ac808450f4fff866ab0885f4b7c6e54f8ade5bfe3,2024-06-20T13:23:18.707000 +CVE-2024-5845,0,1,81cef0ce322e71a4bed434dbc7ea9d65be8ec3ba295af42053db9235d9f0408f,2024-06-20T13:24:38.797000 +CVE-2024-5846,0,1,5609dd7477433b65308e4f00728623f0cbb335d708d82c23fe7d233bf5bad701,2024-06-20T13:05:14.410000 +CVE-2024-5847,0,1,a9c5c4d55b667879ca2540ce0f100ade6913bb045068cf41dbc793953586289f,2024-06-20T13:05:43.187000 CVE-2024-5851,0,0,1ff86bf427427298fe5dc39bbfedb897b9870fd2315cf065507e70165fb41d41,2024-06-13T18:36:09.013000 -CVE-2024-5853,0,0,538b1f17c65b66062c6a2483518dca6c20ff3b599904ecdb66f3a7979ae05110,2024-06-19T06:15:12.287000 +CVE-2024-5853,0,1,4db307c3757855b51e51fa12e1eb9aa67e540512d9bb40f822c5370c3893dc4f,2024-06-20T12:44:01.637000 CVE-2024-5858,0,0,30241924d409355226bb80c4fb982c4833f84483f4f89b94e986f70fe7751e71,2024-06-17T12:42:04.623000 -CVE-2024-5860,0,0,c5c9f1df18adaa1e39e379691a52abd56fb4990c1e90abbe780c7d7d36e07346,2024-06-18T04:15:11.607000 +CVE-2024-5860,0,1,f855eee13286327286a851090329abd51f0ce228b863644ab8e1f7f80e1d731d,2024-06-20T12:44:01.637000 CVE-2024-5868,0,0,cddb0a1baa550d897574c2505eb276b5cd69c2fd57d27d79dec0dad91553a572,2024-06-17T12:42:04.623000 CVE-2024-5871,0,0,83e6d3ea3d7363cdcbcb485d9161ada2b3d6bba887290fa58ab89820983d4022,2024-06-17T12:42:04.623000 CVE-2024-5873,0,0,4affe4b1f71505ca05298a33c7e23c3ae147869580237755bed2d180fbea1b8e,2024-06-12T08:15:51.550000 -CVE-2024-5886,1,1,0c13c4ee009af0d9946120b2238809bd0a7459b4e90701a2a72b91121b1d711b,2024-06-20T11:15:56.580000 +CVE-2024-5886,0,0,0c13c4ee009af0d9946120b2238809bd0a7459b4e90701a2a72b91121b1d711b,2024-06-20T11:15:56.580000 CVE-2024-5891,0,0,da4ba5748ecb097f5befd86d4787f2c76143132bf594110b21f16b774e08e15d,2024-06-13T18:36:09.010000 CVE-2024-5892,0,0,890747e3858b777381fac245c58cda030faeadae1530ec4012d9670fde261a4e,2024-06-13T18:36:09.013000 CVE-2024-5893,0,0,8bbdd4fceee6f55f46acaf4e2e772cd5b071a8548251271838818c6acd356beb,2024-06-13T18:36:09.010000 @@ -254579,7 +254633,7 @@ CVE-2024-5895,0,0,adce2320c8f2da0eb4076cf48b8528b0367e1a91f9f4f56c3200b06ef2e34d CVE-2024-5896,0,0,74561a30f59034551bf30203dd9d488264eda62db1d6fb3f9fe44d921fc69839,2024-06-13T18:36:09.010000 CVE-2024-5897,0,0,ae4d2a8aeafd445ed5a0eb6a013a1f5f8d0cd09f1eb619f9e05beaa5efdbf2f0,2024-06-13T18:36:09.010000 CVE-2024-5898,0,0,2556a153e2769b2848dc3169e1f22718fe5b8f425c00f464c0cc68408399ec6a,2024-06-13T18:36:09.010000 -CVE-2024-5899,0,0,245f17f428e9e1e62838ca77aac18c3a3f2c82b4ea4c8e0b16de72a2626c4ba3,2024-06-18T09:15:09.767000 +CVE-2024-5899,0,1,cc9e433fee08f0a2737b6eb6a672aa21365721aef58982862ac384a6aa1437cb,2024-06-20T12:44:01.637000 CVE-2024-5905,0,0,52472d1772ec890cf9f052f234eba7e8e08aa90a47029f036f0775ad3cc74056,2024-06-13T18:36:09.010000 CVE-2024-5906,0,0,b7fc466b9931ce265a1ef81017e39098b5ad31bf494bc22103ede7f6c2cace23,2024-06-13T18:36:09.010000 CVE-2024-5907,0,0,17327a712757852c4b43c811f24252c9a6d5917388dc8b093882f86e14b7ae5b,2024-06-13T18:36:09.010000 @@ -254594,10 +254648,10 @@ CVE-2024-5949,0,0,d7dee9eee40bd92a70c4f623828d380d2dd593c00c7f59e1204a1a9d39be48 CVE-2024-5950,0,0,63f8256c9087af57fddfc205322f9075c204b1d3853d2ea1d0284b0d233997a1,2024-06-17T12:43:31.090000 CVE-2024-5951,0,0,7ddd1cddf9a9fdc846148c5866e7aa3c8ed2def81486ca15d97d818d600ecbf4,2024-06-17T12:43:31.090000 CVE-2024-5952,0,0,a56b129ed0896e22b77ffae27056ae02e2ff1e28286e49f9b0ac6b9f084a57b2,2024-06-17T12:43:31.090000 -CVE-2024-5953,0,0,9ea5135a8dda1dad51ca93f6728c4080a08758d993efcfa67e208f3eb48bc4e5,2024-06-18T10:15:11.170000 +CVE-2024-5953,0,1,5a82a23010422744b690f4b6e35b5f6ac9a7dbe5fabc2cd37af30b93c2bed444,2024-06-20T12:44:01.637000 CVE-2024-5961,0,0,5b2a3ec0406c808b5387d2b9b0077c5bc424b1c4427d5cb7165a954efcfd8c0c,2024-06-17T12:42:04.623000 -CVE-2024-5967,0,0,2e6937701802b31975daa50ca2c8947b1ca4041c2416c87363e635155af92998,2024-06-18T12:15:12.707000 -CVE-2024-5970,0,0,94f8680e2f0cb752b36ee3c5326d183ae5ea735621ee86ce87d8c4c11bfd479d,2024-06-18T22:15:09.487000 +CVE-2024-5967,0,1,a8cf0971f84f68dc327704c7b15af8c68f3ca5a6cf4ca8aa54163d9ca95100d5,2024-06-20T12:44:01.637000 +CVE-2024-5970,0,1,118b7b2e028a3447b60495fc36df0133e6c8ea6adad2a5f3d89bac8698786790,2024-06-20T12:44:01.637000 CVE-2024-5976,0,0,e855126a3e03657c0f9ccfb70e360e6531fe17aa442fb39ef6227c53616360fe,2024-06-17T12:43:31.090000 CVE-2024-5981,0,0,7870df79665c127e5a33d8fe67e56d8db296d9f7a121386a1275e14871265ba2,2024-06-17T12:43:31.090000 CVE-2024-5983,0,0,c879618580c4659b3410af89e8bf56c9d9f664bfd2edad2ed7d70a9157784269,2024-06-17T12:43:31.090000 @@ -254626,47 +254680,52 @@ CVE-2024-6045,0,0,2dcda6a0cbff8cd9e195f4d3ab65f0210762794017ec56ef72ed3655d46b17 CVE-2024-6046,0,0,91371f2b9afd0a654dc4dc6a88ac5fb04a186cb82713804dda3cac2d7733c344,2024-06-18T11:15:52.513000 CVE-2024-6047,0,0,4cdf0f1acff12373f8f857c8d442b9de2221d44745323cc3f60bf66bccd7a239,2024-06-17T14:15:13.040000 CVE-2024-6048,0,0,03e9485ef23720c113f11fed6c539200d9a1624e025ca24798cddf9d0c1a9e3b,2024-06-17T12:42:04.623000 -CVE-2024-6055,0,0,93ffb465c6acddf15e4142ae2e8b4bcae95c7241e5f24a2dedc05f862f5d2e79,2024-06-17T13:15:53.697000 -CVE-2024-6056,0,0,636228dd1a2c8f5c63676f25cc803d23af23082b986789068b58dd9fd2a57ea9,2024-06-17T18:15:18.143000 -CVE-2024-6057,0,0,cfabce49b9db224e3720b6479e81ee1edcd2fcbaabb39bed0063a52236765ccd,2024-06-17T13:15:53.800000 -CVE-2024-6058,0,0,aa275b0b4c0751acbaa33c801c38fa610b52df9d20bf9563a4c6dbb0bdfcf145,2024-06-18T16:15:10.860000 -CVE-2024-6059,0,0,8dc3785d03b4bbf495bb7b9e0db50afd358453b35356b7519dfcb40c8d9c6a71,2024-06-17T19:15:59.467000 -CVE-2024-6061,0,0,39aa63f2908fac2ea5c6c93ac26be0cb4e028f86f6241c593e1bff1e191c4192,2024-06-18T14:15:11.533000 -CVE-2024-6062,0,0,dadd6f95b83f87273cc3430212566c912259c48e3b6224cff1d8d43c9528602d,2024-06-18T14:15:11.670000 -CVE-2024-6063,0,0,a884af0a7239f5992275086d49c24161d8ae303993e8264675b0420da667ecf0,2024-06-18T14:15:11.787000 -CVE-2024-6064,0,0,a437d20d126de2e6302df618fc0fd61b6c1098a65016c7857130e623e34d608e,2024-06-18T14:15:11.917000 -CVE-2024-6065,0,0,12bfac21a4497db8b2fae053bb336fb3006fa216a4f3adf1332cf2a8bbd53392,2024-06-18T14:15:12.040000 -CVE-2024-6066,0,0,f38956b7531d73be2ff37e0312497b9f2b99af618ba528ef846e38c1b677fe14,2024-06-18T14:15:12.183000 -CVE-2024-6067,0,0,917ec11acc59771cd289e02ed472e235338a36350e131e2242624c6b5a660576,2024-06-17T22:15:10.657000 -CVE-2024-6080,0,0,ce117abbbf27c271f3b1c554aeba9f1090748517ce038abb4811acdf5fadb2ed,2024-06-17T23:15:51.583000 -CVE-2024-6082,0,0,b34a8b9e9d7597c030b945a5724fac42f5803ca75f53728fefe9f424acf1cad3,2024-06-17T23:15:51.920000 -CVE-2024-6083,0,0,6fddaebd6fd505529ccfd2377fbb90eb3ff967f1b7daa3e62aab60a1d99a55f2,2024-06-18T00:15:09.853000 -CVE-2024-6084,0,0,e83127a2367dfc14c5a74f105b11646fecd7f02b89d4abf85a631505a5590b54,2024-06-18T14:15:12.317000 -CVE-2024-6100,0,0,54010ce6f238bde544fe7f7d259cdef651074d4c63d3f1e19c90005e63648320,2024-06-20T00:15:09.810000 -CVE-2024-6101,0,0,ef79fea232f05f9286b27581de6444f5cbf6f48ca26c4b4a071a7186f13e9abe,2024-06-20T00:15:09.967000 -CVE-2024-6102,0,0,0a75cd12056caf692bff4dd6d8b4e609f3c0d523976ccb9d5e105b14b81085b8,2024-06-20T00:15:10.053000 -CVE-2024-6103,0,0,3c22aa639787761a456bc2fa5de7b15f8c606a7657056ec8f8b4a112895ac4c2,2024-06-20T00:15:10.133000 -CVE-2024-6108,0,0,629cb2a981568eef963fe0fd8730638a990cab0f00ba579fb1df944ef1acda4c,2024-06-18T10:15:11.653000 -CVE-2024-6109,0,0,ac88b829202223826825501cf9791e4a037baf3e8842ea6d10b43cea56f9fb4c,2024-06-18T12:15:12.987000 -CVE-2024-6110,0,0,a93edb70ebaea05e4db1d298919bf28b75b9891dd6a65a876e1ff434451eb3ce,2024-06-18T12:15:13.290000 -CVE-2024-6111,0,0,88ff3438da2fa6dff09fb1e17ea9913d07168b3e37cac6ddb91200dd8cb971da,2024-06-18T15:15:52.873000 -CVE-2024-6112,0,0,3793178079993987ba7bf7b37db89ff5b23660048ce424d2f0351839dfc7b7ff,2024-06-18T15:15:52.993000 -CVE-2024-6113,0,0,c85a8a6a99c4e7341510804bf21b5466b2444897fe50231d9a7b1521955dc286,2024-06-20T06:15:10.310000 -CVE-2024-6114,0,0,b861f686c72ead40271b9e15f5d48ada8c079a2c4c9ea1405ca71da7d3acf766,2024-06-18T13:15:52.897000 -CVE-2024-6115,0,0,8370727144c08f52daee8853cdc1c595dffde958a895699c94efac517eada338,2024-06-18T13:15:53.267000 -CVE-2024-6116,0,0,9c214becff49a599c0981aa0de917221cc0b2f05b538da5ededc03f464bf8356,2024-06-18T16:15:10.983000 -CVE-2024-6125,0,0,fa267cc2485605b04afb41f92061ceba58b846de96eed178a247c22981f2edf8,2024-06-19T02:15:09.873000 -CVE-2024-6128,0,0,55dd86526ffc64aa22b4ae50ac75f79328093ce905e507fd46907528cb0d85a5,2024-06-18T21:15:56.877000 -CVE-2024-6129,0,0,2988cb8a677c36eeb9291aae9a3963f084f044e15211a677c78cefdb57c80496,2024-06-18T21:15:57.217000 -CVE-2024-6132,0,0,c367d3a0ed20202620cd157d11fd19374c3525d7eb4a0c76bc25e89726c84938,2024-06-19T06:15:12.520000 -CVE-2024-6142,0,0,b72e1389b74690e00d255349d35caab25cc2db5a4c7637f27b1d47463c0fc348,2024-06-19T00:15:49.580000 -CVE-2024-6143,0,0,9532ba45db565215853ddf49c1a0164531f9356075191c1044d52df46080533d,2024-06-19T00:15:49.847000 -CVE-2024-6144,0,0,7cec310494d62a62033523df063be2341004a6dea8160cb5bd0d55e2f0065cc2,2024-06-19T00:15:50.133000 -CVE-2024-6145,0,0,16e7e12932fe3f6cc4edd6cd1b11782632ac16fbbec9fab4c39f453507b11bae,2024-06-19T00:15:50.413000 -CVE-2024-6146,0,0,b20add1bacc42bc316876ff3352b5fc3b113cf054bc134b5a4212df29f6f9ae6,2024-06-19T00:15:50.703000 -CVE-2024-6176,0,0,bd660c0cde647fe1bccb04d647014bfeadeca873814685115b39e74c61c8f2a1,2024-06-20T01:15:49.023000 -CVE-2024-6177,0,0,e2006bd8c117b361d15d615544253325ed284d266829d0d7c581f459913766c1,2024-06-20T02:15:11.980000 -CVE-2024-6178,0,0,b585588c1b5751ce256a7f1d8c6c6c4f50d67eb468665169500a1bbf3e780a64,2024-06-20T02:15:12.123000 -CVE-2024-6179,0,0,65c180015474b6671311fe92692345a2f1123e438c5d25ef1d3bb1089c68bc2d,2024-06-20T02:15:12.257000 -CVE-2024-6181,1,1,81641b8b9146260b7f48c485111a885e8d9e1f90d760cc4da98aa2245841c1c6,2024-06-20T11:15:56.723000 -CVE-2024-6182,1,1,07cfc08451dd84c1512a6d840f28fec61137669b55946f78e994e0b1a9b7b62c,2024-06-20T11:15:57.117000 +CVE-2024-6055,0,1,7490ef4c1367b62a13fc44ec964fb12263f9fa479e5bd4bbc3820296c19002e0,2024-06-20T12:44:22.977000 +CVE-2024-6056,0,1,9210a6d5e69cda44c36495fe4964320c8f6a47f4e723a559827fc7a6d2ee595f,2024-06-20T12:44:22.977000 +CVE-2024-6057,0,1,3fe0cc3f033e9735165b225d202aca1a708a694e0fe3a8863e85d03de2c16d7c,2024-06-20T12:44:22.977000 +CVE-2024-6058,0,1,a8d358e50f82c303138db4a312533e61278f479f2387c71d6c209ba9ed223766,2024-06-20T12:44:22.977000 +CVE-2024-6059,0,1,0652872fd6b84bdbe955862646f7076a37dc5f6685ecdae3319bf6195e0e8f13,2024-06-20T12:44:22.977000 +CVE-2024-6061,0,1,3fef78bcd0588e7cd49d6e518ec4c2f5bfa6c9508485b37687f3859e72f1e0b3,2024-06-20T12:44:22.977000 +CVE-2024-6062,0,1,4376548ceed49a6279fb764d06a2668721f5b2377b1cd81005297361a58fafee,2024-06-20T12:44:22.977000 +CVE-2024-6063,0,1,105b47008bd97b9ef828e0642500faec85639c6116c40931e2e5a8256ab187a7,2024-06-20T12:44:22.977000 +CVE-2024-6064,0,1,6c37569e777aad3e1a715d1d67e59381aa9d19e46235bcb0abd84ff598ca13c1,2024-06-20T12:44:22.977000 +CVE-2024-6065,0,1,8dd99f4d37f301246412681f45228fac07d3ea15c1391b550b52738ce1d9d096,2024-06-20T12:44:01.637000 +CVE-2024-6066,0,1,bdecbe263c05a4772a78f07626fc1e3f9d1817cac413c3ff735f168ece871a97,2024-06-20T12:44:01.637000 +CVE-2024-6067,0,1,6728784af54ae6b64b1bb52b7887afb1ba68c7ac0e5f2ef2339910430d39d127,2024-06-20T12:44:01.637000 +CVE-2024-6080,0,1,adb3e70f170e91cc2a703b54ba2915021bd3bf11cdec3f426a1169556de7cdf0,2024-06-20T12:44:01.637000 +CVE-2024-6082,0,1,1d236589845be46c55129b507b1dd3b80bd97a229aa963846065aaa4c28f158d,2024-06-20T12:44:01.637000 +CVE-2024-6083,0,1,7e7a5636ed7255d0fcfcd2ad673b2a41cb1a824617e25b4cc387230a5aebb333,2024-06-20T12:44:01.637000 +CVE-2024-6084,0,1,7af730199a10f594b6ce1f1e9ecc3a7779c7858f9e2bf364f776ef80922995a6,2024-06-20T12:44:01.637000 +CVE-2024-6100,0,1,016cae23b79effa3d85d3cbb17faa4d3555a792118b9bc148204d799c480fb0a,2024-06-20T12:43:25.663000 +CVE-2024-6101,0,1,5ae01d22b86bb964b20c8f7af115a34694f07ac7b0af3e448bc02f8e279b03cf,2024-06-20T12:43:25.663000 +CVE-2024-6102,0,1,f40f01a52bc8cb59edf71d21a2f57acc23143055faa36562465e0082cbad9d06,2024-06-20T12:43:25.663000 +CVE-2024-6103,0,1,82cc3a68320cd6a01505e8463f8fe3be3d527f39c6027b47ff0b113e4a1ac0c5,2024-06-20T12:43:25.663000 +CVE-2024-6108,0,1,287fb4573b0804d515ce73f8bec36cd5b44a3d911922aa114371918392ae0b1f,2024-06-20T12:44:01.637000 +CVE-2024-6109,0,1,702c63a72777bc30119b051d43a51c9500c42d0a474f7fbd46aa104abc3ca24e,2024-06-20T12:44:01.637000 +CVE-2024-6110,0,1,77e534960ad85d30edf7076a8f116e04d866b8d511433c762f024f5d4ee0191a,2024-06-20T12:44:01.637000 +CVE-2024-6111,0,1,f20702eed3361b3beb2dae76c89a81ed94b0c8a0acf5a7d3cec50d9a0acc9abe,2024-06-20T12:44:01.637000 +CVE-2024-6112,0,1,1ff47feb724f954645cccaec0945743239c6d70e9a608ecdc58b6c3e51543a1a,2024-06-20T12:44:01.637000 +CVE-2024-6113,0,1,2758e7c3cd85245ae6a2ad9a4a7217abac687e9fa00a3d92e721d936abed15fc,2024-06-20T12:43:25.663000 +CVE-2024-6114,0,1,dc0a82373381e9c7cd4b1e6c5bf523878ecb08863d5210f6468d495d6395d8da,2024-06-20T12:44:01.637000 +CVE-2024-6115,0,1,a9f6dd92ef3b2f9b6542508effdf3ace054749ced1343c5fd4f924ccbd13328b,2024-06-20T12:44:01.637000 +CVE-2024-6116,0,1,5843dd08daba10a4f1c43a634f4172ccf9c702c464ac49dc5f784b4aa5e3fcb5,2024-06-20T12:44:01.637000 +CVE-2024-6125,0,1,85b92914638eb24a081146fd823c584c2333b183768ef26d618955e83646311b,2024-06-20T12:44:01.637000 +CVE-2024-6128,0,1,239b6d4abd5e28d8fee8ba89aff428cc031bedf0b52d0558401b57c48fa12a4c,2024-06-20T12:44:01.637000 +CVE-2024-6129,0,1,dfa20fd20a0a3099fcdc2f66c56de27040819ee45bd7efe66cb95f894b77d645,2024-06-20T12:44:01.637000 +CVE-2024-6132,0,1,c816ab5ddbf096dbfac6131f33b5d3d3e264dd5fbb695e6c347719e5920b43ca,2024-06-20T12:44:01.637000 +CVE-2024-6142,0,1,23f480e47c156f1dad9ad13e0d7590969d38d5491fbe00b3021017412ace7767,2024-06-20T12:44:01.637000 +CVE-2024-6143,0,1,8ecb1606cf08b70c452136729986c382308670f8f5aa74c9caba844228d971e4,2024-06-20T12:44:01.637000 +CVE-2024-6144,0,1,282f248ec161eadd8599a33b6d11a75bd4ed1ccd1aa15e9b959a4a72d41d30ce,2024-06-20T12:44:01.637000 +CVE-2024-6145,0,1,74f99a0157ef2eb5160bc64159bab3cd3614efb0f0cae9420b13288ce6d516ff,2024-06-20T12:44:01.637000 +CVE-2024-6146,0,1,835232b778d7e80b1c73cad2f19f1275692bff270d5e664fd4c7fc64973110ef,2024-06-20T12:44:01.637000 +CVE-2024-6176,0,1,855875508d6019a3b7cc5455db83c0ed155c5813092b253896702a30576b2ecb,2024-06-20T12:43:25.663000 +CVE-2024-6177,0,1,8ae8844999995f9ee14daf2f851ec98e44dd516dd31b5ad932fa994d643f6000,2024-06-20T12:43:25.663000 +CVE-2024-6178,0,1,26cb0e544a55f21433ffa680a6dbfa3e1586f3282623fdc62b48fe72f34029a9,2024-06-20T12:43:25.663000 +CVE-2024-6179,0,1,fcda122acaf698ceb3de03ce249e6591d1c98435571bcfacb38183b030b95674,2024-06-20T12:43:25.663000 +CVE-2024-6181,0,1,1c63cdd3e00b6cb3192ef95a2fb860e0b788909d22b3c517df0e72c2135a7363,2024-06-20T12:43:25.663000 +CVE-2024-6182,0,1,8a8e1ba35f7ad1adfa2fde2ddce70813bba5c327045751f131f1b9af2084c644,2024-06-20T12:43:25.663000 +CVE-2024-6183,1,1,fef6e8dfbc94db0402f5ba61f2c034227fdd10eac7a240b1c241052128b5fd25,2024-06-20T12:43:25.663000 +CVE-2024-6184,1,1,b6626457ddb310324bab2cedc5cc5d252a487e6ac6bb1c28fe691915e137426e,2024-06-20T12:43:25.663000 +CVE-2024-6185,1,1,1dc0b9263b85bb33ca9310e6b4c081d0f0e1e123ba9f93581c17c7bd1d1c72e2,2024-06-20T12:43:25.663000 +CVE-2024-6186,1,1,d2094b298e0e80ed3f8c73d6bf8f261087042e59c99ee050d24e62de39a74950,2024-06-20T13:15:50.007000 +CVE-2024-6187,1,1,8d0e5413fa3414444fa7cbb264a7a37066b24e9211fa3873e91950a5c8f2d217,2024-06-20T13:15:50.320000