Aggregator

A vulnerability has been found in Microsoft Office Publisher 2007 and classified as critical. This vulnerability affects unknown code of the component Pointer Handler. The manipulation leads to improper resource management. This vulnerability was named CVE-2007-1754. The attack can be initiated remotely. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability was found in Ipsec-tools 0.6.2. It has been declared as problematic. Affected by this vulnerability is the function isakmp_info_recv. The manipulation leads to denial of service. This vulnerability is known as CVE-2007-1841. The attack can be launched remotely. There is no exploit available. It is recommended to upgrade the affected component.

本期周报简介：1、如何有效管理第三方Onsite员工账号，避免账号未及时注销引发的安全隐患？ 2、国内后量子密码学加密算法的发展现状如何，面临哪些挑战？ 3、对关基单位进行模拟攻击时需要遵循哪些合规要求，如何平衡模拟攻击的效果与风险管控？

A vulnerability was found in Employee Managment System 1.0. It has been rated as critical. Affected by this issue is some unknown functionality of the file /edit.php. The manipulation of the argument ID leads to sql injection. This vulnerability is handled as CVE-2024-25213. Access to the local network is required for this attack to succeed. There is no exploit available.

A vulnerability classified as critical has been found in Employee Managment System 1.0. This affects an unknown part of the file /aprocess.php. The manipulation of the argument pwd leads to sql injection. This vulnerability is uniquely identified as CVE-2024-25215. The attack needs to be approached within the local network. There is no exploit available.

A vulnerability, which was classified as problematic, has been found in Barangay Population Monitoring System 1.0. Affected by this issue is some unknown functionality of the file /barangay-population-monitoring-system/masterlist.php. The manipulation of the argument Full Name leads to cross site scripting. This vulnerability is handled as CVE-2024-25208. The attack may be launched remotely. There is no exploit available.

A vulnerability, which was classified as problematic, was found in Barangay Population Monitoring System 1.0. This affects an unknown part of the file /barangay-population-monitoring-system/masterlist.php. The manipulation of the argument Contact Number leads to cross site scripting. This vulnerability is uniquely identified as CVE-2024-25207. It is possible to initiate the attack remotely. There is no exploit available.

A vulnerability has been found in Barangay Population Monitoring System 1.0 and classified as critical. This vulnerability affects unknown code of the file /endpoint/delete-resident.php. The manipulation of the argument resident leads to sql injection. This vulnerability was named CVE-2024-25209. The attack can only be initiated within the local network. There is no exploit available.

A vulnerability was found in Simple Expense Tracker 1.0 and classified as critical. This issue affects some unknown processing of the file /endpoint/delete_expense.php. The manipulation of the argument expense leads to sql injection. The identification of this vulnerability is CVE-2024-25210. The attack needs to be done within the local network. There is no exploit available.

A vulnerability was found in Simple Expense Tracker 1.0. It has been classified as critical. Affected is an unknown function of the file /endpoint/delete_category.php. The manipulation of the argument Category leads to sql injection. This vulnerability is traded as CVE-2024-25211. The attack needs to be initiated within the local network. There is no exploit available.

A vulnerability was found in ElkaGroup Image Gallery 1.0 and classified as critical. This issue affects some unknown processing of the file view.php. The manipulation of the argument cid leads to sql injection. The identification of this vulnerability is CVE-2008-5037. The attack may be initiated remotely. Furthermore, there is an exploit available.

A vulnerability was found in Qualiteam X-Cart 4.5. It has been rated as problematic. This issue affects some unknown processing of the file products_map.php. The manipulation of the argument symb leads to cross site scripting. The identification of this vulnerability is CVE-2012-2570. The attack may be initiated remotely. Furthermore, there is an exploit available.

A vulnerability, which was classified as problematic, has been found in PHPGurukul User Registration & Login and User Management System 1.0. This issue affects some unknown processing of the component Search Bar. The manipulation leads to cross site scripting. The identification of this vulnerability is CVE-2024-25202. The attack may be initiated remotely. There is no exploit available.

A vulnerability, which was classified as problematic, has been found in Mitsubishi Electric CPU Module Logging Configuration Tool, CSGL, CW Configurator, Data Transfer, Data Transfer Classic, EZSocket, FR Configurator SW3, FR Configurator2, GENESIS64, GT Designer3, GT SoftGOT1000, GT SoftGOT2000, GX Developer, GX LogViewer, GX Works2, GX Works3, iQ Works, MI Configurator, Numerical Control Device Communication Software, MR Configurator, MR Configurator2, MRZJW3-MC2-UTL, MX Component, MX OPC Server DA UA, PX Developer Monitor Tool, RT ToolBox3, RT VisualBox, Monitoring tools for the C Controller Module, SW0DNC-MNETH-B, SW1DNC-CCBD2-B, SW1DNC-CCIEF-J, SW1DNC-CCIEF-B, SW1DNC-MNETG-B, SW1DNC-QSCCF-B and SW1DND-EMSDK-B. This issue affects some unknown processing. The manipulation leads to resource consumption. The identification of this vulnerability is CVE-2024-25087. The attack may be initiated remotely. There is no exploit available.

A vulnerability classified as problematic was found in BeyondTrust Privilege Management up to 24.0 on Windows. Affected by this vulnerability is an unknown functionality. The manipulation leads to incorrect privilege assignment. This vulnerability is known as CVE-2024-25083. The attack needs to be approached locally. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability, which was classified as problematic, has been found in Samsung Exynos 9820, Exynos 9825, Exynos 980, Exynos 990, Exynos 850, Exynos 1080, Exynos 2100, Exynos 2200, Exynos 1280, Exynos 1380, Exynos 1330, Exynos 9110, Exynos W920, Exynos W930, Exynos Modem 5123 and Exynos Modem 5300. Affected by this issue is some unknown functionality of the component Call Control Module. The manipulation leads to denial of service. This vulnerability is handled as CVE-2024-25073. The attack may be launched remotely. There is no exploit available.

A vulnerability, which was classified as problematic, was found in Samsung Exynos 9820, Exynos 9825, Exynos 980, Exynos 990, Exynos 850, Exynos 1080, Exynos 2100, Exynos 2200, Exynos 1280, Exynos 1380, Exynos 1330, Exynos 9110, Exynos W920, Exynos W930, Exynos Modem 5123 and Exynos Modem 5300. This affects an unknown part. The manipulation leads to manage user sessions. This vulnerability is uniquely identified as CVE-2024-25074. It is possible to initiate the attack remotely. There is no exploit available.

A vulnerability classified as critical was found in Backdrop CMS up to 1.27.2/1.28.1. Affected by this vulnerability is an unknown functionality of the component Field Label Handler. The manipulation leads to permission issues. This vulnerability is known as CVE-2024-41709. The attack can be launched remotely. There is no exploit available. It is recommended to upgrade the affected component.

A vulnerability has been found in RSA Authentication Manager up to 8.7 SP2 and classified as critical. Affected by this vulnerability is an unknown functionality. The manipulation leads to xml external entity reference. This vulnerability is known as CVE-2024-25066. The attack can be launched remotely. There is no exploit available. It is recommended to apply a patch to fix this issue.

这种情况在实际场景中，是存在的。所以在制定开发安全提测规范等制度时，应该考虑进去，并明确不同扫描器发现的不同等级漏洞验收标准，对于达不到要求的，需要开辟“绿色通道”： 1、审批流程要有高度：比如安全团队针对未修复的漏洞做出评估，由业务线一把手甚至CTO进行审批，同意后方可上线； 2、安全要为业务护航：除了跟进业务修复外，还应该在业务带病上线时制定对应的防护、监测措施，要第一时间发现漏洞被利用并处置。 此处尤其想说的是第二点，不少同行道听途说、觉得把责任分清楚就好，但若业务因此出了安全事件，高层领导会以为与安全团队无关？我想答案无需再述，大家心里已明白。 更多内容，可以访问： 1、SDL 100问 SDL100问：我与SDL的故事 SAST误报太高，如何解决？ SDL需要哪些人参与？ SDL如何做成平台化以及价值？ 安全SDK提供安全API是怎么做的？ 安全测试，测不出逻辑漏洞怎么办？ 如何逐步建设XAST安全测试工具？ 如何设计安全开发平台的架构和功能？ SDL 69/100问：大家都有哪些SDL运营指标？ 2、SDL创新实践 首发！“ 研发安全运营 ” 架构研究与实践 DevSecOps实施关键：研发安全团队 DevSecOps实施关键：研发安全流程 DevSecOps实施关键：研发安全规范 从安全视角，看研发安全 数字化转型下研发安全痛点 一个思考：安全测试驱动产品安全？ 3、SDL最初实践 【SDL最初实践】开篇 【SDL最初实践】安全培训 【SDL最初实践】安全需求 【SDL最初实践】安全设计 【SDL最初实践】安全开发 【SDL最初实践】安全测试 【SDL最初实践】安全审核 【SDL最初实践】安全响应 4、软件供应链安全 软件供应商面临的攻防实战风险 软件供应商实战对抗十大安全举措 软件供应商攻防常规战之SDL 软件供应链投毒事件应急响应 5、安全运营实践 基于实践的安全事件简述 安全事件运营SOP：钓鱼邮件 安全事件运营SOP：网络攻击 安全事件运营SOP：蜜罐告警 安全事件运营SOP：webshell事件 安全事件运营SOP：接收漏洞事件 应急能力提升：实战应急困境与突破 应急能力提升：挖矿权限维持攻击模拟 应急能力提升：内网横向移动攻击模拟 应急能力提升：实战应急响应经验