注:本文转自天极网。
随着全球范围的黑客入侵不断猖獗,信息安全问题越来越严重。在对抗黑客入侵的安全技术中,实时入侵检测和漏洞扫描评估的技术和产品已经开始占据越来越重要的位置。实时入侵检测和漏洞扫描评估基于的主要方法还是“已知入侵手法检测”和“已知漏洞扫描”,换句话说就是基于知识库的技术。由于没有针对这些扫描器平台的分类标准,直接比较他们的数据库非常困难。使用一个共同的名字,可以帮助用户在各自独立的各种漏洞数据库中和漏洞评估工具中共享数据,CVE就是在这样的环境下应运而生的。
CVE 的英文全称是“Common Vulnerabilities & Exposures”,即通用漏洞披露。它就好像是一个字典表,为广泛认同的信息安全漏洞或者已经暴露出来的弱点提供一个公共的名称。如果在一个漏洞报告中指明的一个漏洞有CVE名称,你就可以快速地在任何其它CVE兼容的数据库中找到相应修补的信息,解决安全问题。
接下来以大家日常使用最多的Windows操作系统来举例。当系统安全漏洞被发现后,就会向CNA(CVE Numbering Authorities)申请CVE编号,系统安全漏洞通过验证并符合相应规则后会发布在MITRE官网,点击首页的“Search CVE List”可以按CVE编号或者关键字查询CVE项目。CVE ID的格式为CVE-YYYY-NNNNN。YYYY部分是分配CVE ID的年份或漏洞公开的年份(如果在分配CVE ID之前)。NNNNN部分为CNA分配的编号。年份部分不用于指示漏洞的发现时间,而仅用于指示漏洞的公开或分配时间。
CNNVD是中国国家信息安全漏洞库,英文名称“China National Vulnerability Database of Information Security”,简称“CNNVD”,隶属于中国信息安全测评中心,是中国信息安全测评中心为切实履行漏洞分析和风险评估的职能,负责建设运维的国家级信息安全漏洞库,为我国信息安全保障提供基础服务。CNNVD采集收录、分析验证涉及国内外主流应用软件、操作系统和网络设备等软硬件系统的信息安全漏洞(CVE),发布于CNNVD官方网站(//cnnvd.org.cn/)并对安全漏洞指定CNNVD编号,与CVE形成对应关系,例如CVE-2021-26855对应CNNVD-202103-192。CNNVD的内容相对CVE更详细。
作为Windows软件厂商的微软公司,针对定期发布的系统安全漏洞,都会提供相应的解决漏洞的方案,一般按月发布在微软安全响应中心(//msrc.microsoft.com/update-guide),例如//msrc.microsoft.com/update-guide/vulnerability/CVE-2021-26870,通过点击“安全更新程序”中相应产品的“Security Update”链接可以下载到修复这个安全漏洞的补丁更新。对于没有补丁更新的情况,可以在“临时解决方案”、“常见问题解答”或“缓解”中找到应对方案。
两个编号由两个不同的主体发布在不同的网站,要求用户有相应的知识背景才知道如何查找。用户在获知漏洞存在时,一般都非常着急,希望能找到官方可靠的修复补丁,但大部分用户并不知道去哪里找。下面是笔者针对近期发布的Windows操作系统安全漏洞整理的对应漏洞补丁列表。
Windows操作系统主要安全漏洞及对应补丁(截至2022年6月21日)
KB编号 | CVE编号 | CNNVD编号 |
Windows 10 21H2: KB5012599 | CVE-2022-24541 | CNNVD-202204-3087 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24542 | CNNVD-202204-3086 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24544 | CNNVD-202204-3085 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24545 | CNNVD-202204-3084 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24546 | CNNVD-202204-3083 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24547 | CNNVD-202204-3073 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24549 | CNNVD-202204-3072 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24550 | CNNVD-202204-3071 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26786 | CNNVD-202204-3053 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26787 | CNNVD-202204-3067 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26788 | CNNVD-202204-3062 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26789 | CNNVD-202204-3054 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26790 | CNNVD-202204-3050 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26791 | CNNVD-202204-3052 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26792 | CNNVD-202204-3045 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26793 | CNNVD-202204-3044 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26794 | CNNVD-202204-3043 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26795 | CNNVD-202204-3042 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26796 | CNNVD-202204-3041 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26797 | CNNVD-202204-3033 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26798 | CNNVD-202204-3032 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26801 | CNNVD-202204-3031 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26802 | CNNVD-202204-3030 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26803 | CNNVD-202204-3029 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26807 | CNNVD-202204-3021 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26808 | CNNVD-202204-3020 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26809 | CNNVD-202204-3019 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26810 | CNNVD-202204-3018 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26826 | CNNVD-202204-2972 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26827 | CNNVD-202204-2970 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26828 | CNNVD-202204-2969 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26831 | CNNVD-202204-2965 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26832 | CNNVD-202204-3008 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26903 | CNNVD-202204-3066 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26904 | CNNVD-202204-2936 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26914 | CNNVD-202204-2956 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26915 | CNNVD-202204-2953 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26916 | CNNVD-202204-2948 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26917 | CNNVD-202204-2949 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26918 | CNNVD-202204-2950 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26919 | CNNVD-202204-2946 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-26920 | CNNVD-202204-2976 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-21983 | CNNVD-202204-3175 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-22008 | CNNVD-202204-3171 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-22009 | CNNVD-202204-3172 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-23257 | CNNVD-202204-3177 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24474 | CNNVD-202204-3107 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24479 | CNNVD-202204-3198 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24481 | CNNVD-202204-3200 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24483 | CNNVD-202204-3188 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24485 | CNNVD-202204-3109 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24486 | CNNVD-202204-3201 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24487 | CNNVD-202204-3196 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24488 | CNNVD-202204-3192 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24491 | CNNVD-202204-3112 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24492 | CNNVD-202204-3113 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24493 | CNNVD-202204-3130 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24494 | CNNVD-202204-3128 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24495 | CNNVD-202204-3123 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24496 | CNNVD-202204-3136 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24498 | CNNVD-202204-3121 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24499 | CNNVD-202204-3117 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24500 | CNNVD-202204-3116 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24521 | CNNVD-202204-3115 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24527 | CNNVD-202204-3114 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24528 | CNNVD-202204-3110 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24530 | CNNVD-202204-3105 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24533 | CNNVD-202204-3100 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24534 | CNNVD-202204-3099 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24537 | CNNVD-202204-3097 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24540 | CNNVD-202204-3088 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24482 | CNNVD-202204-3132 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5012599 | CVE-2022-24497 | CNNVD-202204-3111 |
Windows 10 1809: KB5012647 | ||
Windows 10 21H2: KB5013942 | CVE-2022-21972 | CNNVD-202205-2865 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-22011 | CNNVD-202205-2877 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-22012 | CNNVD-202205-2869 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-22013 | CNNVD-202205-2876 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-22014 | CNNVD-202205-2868 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-22015 | CNNVD-202205-2874 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-22016 | CNNVD-202205-2873 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-22019 | CNNVD-202205-2870 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-22713 | CNNVD-202205-2867 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-23270 | CNNVD-202205-2863 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-23279 | CNNVD-202205-2856 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-24466 | CNNVD-202205-2849 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-26913 | CNNVD-202205-2853 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-26923 | CNNVD-202205-2850 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-26925 | CNNVD-202205-2846 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-26926 | CNNVD-202205-2836 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-26927 | CNNVD-202205-2830 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-26930 | CNNVD-202205-2823 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-26931 | CNNVD-202205-2812 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-26933 | CNNVD-202205-2794 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-26934 | CNNVD-202205-2784 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-26935 | CNNVD-202205-2783 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-26936 | CNNVD-202205-2782 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-29103 | CNNVD-202205-2776 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-29104 | CNNVD-202205-2775 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-29105 | CNNVD-202205-2774 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-29112 | CNNVD-202205-2771 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-29113 | CNNVD-202205-2769 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-29114 | CNNVD-202205-2768 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-29115 | CNNVD-202205-2767 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-29121 | CNNVD-202205-2763 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-29125 | CNNVD-202205-2761 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-29126 | CNNVD-202205-2760 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-29127 | CNNVD-202205-2757 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-29128 | CNNVD-202205-2759 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-29129 | CNNVD-202205-2756 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-29130 | CNNVD-202205-2758 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-29131 | CNNVD-202205-2753 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-29132 | CNNVD-202205-2755 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-29137 | CNNVD-202205-2748 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-29139 | CNNVD-202205-2749 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-29140 | CNNVD-202205-2745 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-29141 | CNNVD-202205-2743 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013942 | CVE-2022-29142 | CNNVD-202205-2747 |
Windows 10 1809: KB5013941 | ||
Windows 10 21H2: KB5013624 | CVE-2022-30130 | CNNVD-202205-2790 |
Windows 10 1809: KB5013868 | ||
Windows 10 21H2: KB5014699 | CVE-2022-21123 | CNNVD-202206-1336 |
Windows 10 1809: KB5014692 | ||
Windows 10 21H2: KB5014699 | CVE-2022-21125 | CNNVD-202206-1339 |
Windows 10 1809: KB5014692 | ||
Windows 10 21H2: KB5014699 | CVE-2022-21127 | CNNVD-202206-1332 |
Windows 10 1809: KB5014692 | ||
Windows 10 21H2: KB5014699 | CVE-2022-21166 | CNNVD-202206-1330 |
Windows 10 1809: KB5014692 | ||
Windows 10 21H2: KB5014699 | CVE-2022-30132 | CNNVD-202206-1291 |
Windows 10 1809: KB5014692 | ||
Windows 10 21H2: KB5014699 | CVE-2022-30139 | CNNVD-202206-1288 |
Windows 10 1809: KB5014692 | ||
Windows 10 21H2: KB5014699 | CVE-2022-30140 | CNNVD-202206-1286 |
Windows 10 1809: KB5014692 | ||
Windows 10 21H2: KB5014699 | CVE-2022-30141 | CNNVD-202206-1285 |
Windows 10 1809: KB5014692 | ||
Windows 10 21H2: KB5014699 | CVE-2022-30142 | CNNVD-202206-1283 |
Windows 10 1809: KB5014692 | ||
Windows 10 21H2: KB5014699 | CVE-2022-30143 | CNNVD-202206-1278 |
Windows 10 1809: KB5014692 | ||
Windows 10 21H2: KB5014699 | CVE-2022-30145 | CNNVD-202206-1270 |
Windows 10 1809: KB5014692 | ||
Windows 10 21H2: KB5014699 | CVE-2022-30146 | CNNVD-202206-1264 |
Windows 10 1809: KB5014692 | ||
Windows 10 21H2: KB5014699 | CVE-2022-30147 | CNNVD-202206-1257 |
Windows 10 1809: KB5014692 | ||
Windows 10 21H2: KB5014699 | CVE-2022-30148 | CNNVD-202206-1246 |
Windows 10 1809: KB5014692 | ||
Windows 10 21H2: KB5014699 | CVE-2022-30149 | CNNVD-202206-1239 |
Windows 10 1809: KB5014692 | ||
Windows 10 21H2: KB5014699 | CVE-2022-30150 | CNNVD-202206-1237 |
Windows 10 1809: KB5014692 | ||
Windows 10 21H2: KB5014699 | CVE-2022-30151 | CNNVD-202206-1234 |
Windows 10 1809: KB5014692 | ||
Windows 10 21H2: KB5014699 | CVE-2022-30152 | CNNVD-202206-1230 |
Windows 10 1809: KB5014692 | ||
Windows 10 21H2: KB5014699 | CVE-2022-30153 | CNNVD-202206-1228 |
Windows 10 1809: KB5014692 | ||
Windows 10 21H2: KB5014699 | CVE-2022-30155 | CNNVD-202206-1229 |
Windows 10 1809: KB5014692 | ||
Windows 10 21H2: KB5014699 | CVE-2022-30160 | CNNVD-202206-1226 |
Windows 10 1809: KB5014692 | ||
Windows 10 21H2: KB5014699 | CVE-2022-30161 | CNNVD-202206-1225 |
Windows 10 1809: KB5014692 | ||
Windows 10 21H2: KB5014699 | CVE-2022-30162 | CNNVD-202206-1224 |
Windows 10 1809: KB5014692 | ||
Windows 10 21H2: KB5014699 | CVE-2022-30163 | CNNVD-202206-1223 |
Windows 10 1809: KB5014692 | ||
Windows 10 21H2: KB5014699 | CVE-2022-30164 | CNNVD-202206-1222 |
Windows 10 1809: KB5014692 | ||
Windows 10 21H2: KB5014699 | CVE-2022-30165 | CNNVD-202206-1219 |
Windows 10 1809: KB5014692 | ||
Windows 10 21H2: KB5014699 | CVE-2022-30166 | CNNVD-202206-1221 |
Windows 10 1809: KB5014692 | ||
Windows 10 21H2: KB5014699 | CVE-2022-30189 | CNNVD-202206-1220 |
Windows 10 1809: KB5014692 | ||
Windows 10 21H2: KB5014699 | CVE-2022-32230 | CNNVD-202206-1215 |
Windows 10 1809: KB5014692 |
有了上面的列表,当你发现一个CVE漏洞时可以简单地通过在Microsoft Update Catalog网站(//www.catalog.update.microsoft.com/home.aspx)中通过搜索KB编号找到修复补丁,也可以通过CNNVD官网(//cnnvd.org.cn/web/vulnerability/querylist.tag)搜索CNNVD编号查看更多关于安全漏洞的详细信息。