Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2020-15567

EPSS 0.06% · P17
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2020-15567

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Description
An issue was discovered in Xen through 4.13.x, allowing Intel guest OS users to gain privileges or cause a denial of service because of non-atomic modification of a live EPT PTE. When mapping guest EPT (nested paging) tables, Xen would in some circumstances use a series of non-atomic bitfield writes. Depending on the compiler version and optimisation flags, Xen might expose a dangerous partially written PTE to the hardware, which an attacker might be able to race to exploit. A guest administrator or perhaps even an unprivileged guest user might be able to cause denial of service, data corruption, or privilege escalation. Only systems using Intel CPUs are vulnerable. Systems using AMD CPUs, and Arm systems, are not vulnerable. Only systems using nested paging (hap, aka nested paging, aka in this case Intel EPT) are vulnerable. Only HVM and PVH guests can exploit the vulnerability. The presence and scope of the vulnerability depends on the precise optimisations performed by the compiler used to build Xen. If the compiler generates (a) a single 64-bit write, or (b) a series of read-modify-write operations in the same order as the source code, the hypervisor is not vulnerable. For example, in one test build using GCC 8.3 with normal settings, the compiler generated multiple (unlocked) read-modify-write operations in source-code order, which did not constitute a vulnerability. We have not been able to survey compilers; consequently we cannot say which compiler(s) might produce vulnerable code (with which code-generation options). The source code clearly violates the C rules, and thus should be considered vulnerable.
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Xen 竞争条件问题漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Xen是英国剑桥大学的一款开源的虚拟机监视器产品。该产品能够使不同和不兼容的操作系统运行在同一台计算机上,并支持在运行时进行迁移,保证正常运行并且避免宕机。 Xen 4.13.x及之前版本中存在安全漏洞。攻击者可利用该漏洞造成拒绝服务或提升权限。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

VendorProductAffected VersionsCPESubscribe
-n/a n/a -

II. Public POCs for CVE-2020-15567

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2020-15567

登录查看更多情报信息。

Same Patch Batch · n/a · 2020-07-07 · 52 CVEs total

CVE-2020-15580Samsung移动设备安全漏洞
CVE-2020-15507MobileIron Core 信息泄露漏洞
CVE-2020-15506MobileIron Core 授权问题漏洞
CVE-2020-15564Xen 缓冲区错误漏洞
CVE-2020-15566Xen 代码问题漏洞
CVE-2020-15563Xen 缓冲区错误漏洞
CVE-2020-15565Xen 资源管理错误漏洞
CVE-2020-15505多款MobileIron产品安全漏洞
CVE-2020-15582Samsung移动设备缓冲区错误漏洞
CVE-2020-15581Samsung Mobile Device 信息泄露漏洞
CVE-2020-15583Samsung移动设备路径遍历漏洞
CVE-2020-15579Samsung移动设备安全漏洞
CVE-2020-15578Samsung移动设备安全漏洞
CVE-2020-10745Samba 资源管理错误漏洞
CVE-2020-15577Samsung移动设备安全漏洞
CVE-2020-10730Samba 资源管理错误漏洞
CVE-2020-15517TYPO3 ke_search extension 跨站脚本漏洞
CVE-2020-15516TYPO3 mm_forum extension 跨站请求伪造漏洞
CVE-2020-15514TYPO3 jh_captcha extension 跨站脚本漏洞
CVE-2020-15513TYPO3 typo3_forum extension 安全漏洞

Showing top 20 of 52 CVEs. View all on vendor page → →

IV. Related Vulnerabilities

V. Comments for CVE-2020-15567

No comments yet


Leave a comment