C is a critical in Microsoft Exchange due to use of static
keys. Although exploitation requires valid credentials (at an email user level) and
the risk of mass-exploitation is low, this might be very useful in
targeted attacks as it leads to SYSTEM level RCE.
More information:
-
-
-
There are several sources of known false negatives ( Exchange servers that will
be missed by this script):
1. Potential Exchange servers are prescreened by identifying hosts that have both
port 25 and 443 open. If there are any setups that block one of these, they will
get missed.
2. zmap is optimized for speed and scalability at the expense of precision.
Typically multiple consecutive runs of zmap provide slightly different results.
As a result, multiple runs of this script will show slightly different results
as well.
Not sure whether this is caused purely by network congestion or by buggy code.
Pull-request with patches/workarounds are certainly welcome!
3. We're not trying to be sneaky here, so some firewalls might simply block us
as a robot.
4. Since we're not doing any fancy fingerprinting and only rely on the
that Exchange ser itself, we are limited to first three fields in
number.
For example, latest cumulati for Exchange Server 2019 is 15.2.529.5
which has been released in December and is . The latest update
that contains the patch is 15.2.529.8. Both of these self-report their
as 15.2.529, so the script will assume that the server is patched even if does
not have the latest patch installed and is .
In practice though it seems that there are either Exchange admins that update their
systems as soon as patches come out or those that live by "if it works, don't touch
it" principle. There's no in between.
zmap, Python >= 3.5, modules:
- dnspython
- pyOpenSSL
- requests
You can install them globally with:
or:
Python modules can be installed locally as well, through :
For basic scanning all you need is a file with IPs/subnets (in CIDR format) to scan:
Output will be written in a CS with following columns:
| IP | Exchange | Server Name | PTR | Common Name (from TLS cert) |
|----|------------------|-------------|-----|-----------------------------|
Optionally, you can ask to output info on all Exchange servers found:
In which case there will be one more column to indicate whether server is or not:
| IP | Exchange | ? | Server Name | PTR | Common Name (from TLS cert) |
|----|------------------|-------------|-------------|-----|-----------------------------|
You can also provide a file with blacklisted IPs/subnets (option -b), change the number of
parallel tasks (-p) or length of the timeouts (-t):
开发语言:Python
Star 数:9
该项目属于安全软件方向的开源资源,代码结构清晰,适合安全研究人员学习参考。项目围绕Vulnerability scanner for CVE-2020-0688展开,提供了可运行的实现,对理解相关安全机制、工具原理与攻防技术具有较高的研究价值。
从技术实现角度看,此类项目的核心在于对底层原理的深入理解与工程化落地。开发者在研究过程中可以结合官方文档与社区讨论,梳理项目的初始化流程、核心模块职责与数据流转,逐步掌握其中的技术细节与设计思路。
1. 下载源码压缩包,解压到本地环境。
2. 根据项目类型准备对应的运行环境与依赖。
3. 按照 README 中的步骤完成配置与部署。
4. 在隔离的测试环境中运行验证,避免影响生产系统。
本资源来源于开源社区,仅供安全研究、技术学习与合法授权范围内的攻防演练使用,请勿用于任何非法或侵害他人权益的用途。使用本项目产生的一切后果由使用者自行承担。
| 资源标题 | CVE-2020-0688 - Vulnerability scanner for CVE-2020-0688 |
| 所属分类 | 安全软件 |
| 发布作者 | admin |
| 发布时间 | 2026-10-05 23:03:34 |
| 下载权限 | 免费下载 |
| 附件数量 | 2 个下载链接 |
| 浏览次数 | 251 |
| 讨论数量 | 0 |
| 主题状态 | 正常讨论中 |