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

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2020-25603

Quick assessment

Affected
n/a n/a
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Xen是英国剑桥大学的一款开源的虚拟机监视器产品。该产品能够使不同和不兼容的操作系统运行在同一台计算机上,并支持在运行时进行迁移,保证正常运行并且避免宕机。 Xen 4.14版本及之前版本中存在安全漏洞。该漏洞源于在访问/分配事件通道时缺少内存屏障。

AI Predicted 7.8 Difficulty: Hard EPSS 0.41% · P33
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2020-25603

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: CVE Program / CVE List V5
Vulnerability Description
An issue was discovered in Xen through 4.14.x. There are missing memory barriers when accessing/allocating an event channel. Event channels control structures can be accessed lockless as long as the port is considered to be valid. Such a sequence is missing an appropriate memory barrier (e.g., smp_*mb()) to prevent both the compiler and CPU from re-ordering access. A malicious guest may be able to cause a hypervisor crash resulting in a Denial of Service (DoS). Information leak and privilege escalation cannot be excluded. Systems running all versions of Xen are affected. Whether a system is vulnerable will depend on the CPU and compiler used to build Xen. For all systems, the presence and the scope of the vulnerability depend on the precise re-ordering performed by the compiler used to build Xen. We have not been able to survey compilers; consequently we cannot say which compiler(s) might produce vulnerable code (with which code generation options). GCC documentation clearly suggests that re-ordering is possible. Arm systems will also be vulnerable if the CPU is able to re-order memory access. Please consult your CPU vendor. x86 systems are only vulnerable if a compiler performs re-ordering.
Source: CVE Program / CVE List V5
CVSS Information
N/A
Source: CVE Program / CVE List V5
Vulnerability Type
N/A
Source: CVE Program / CVE List V5
Vulnerability Title
Xen 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Xen是英国剑桥大学的一款开源的虚拟机监视器产品。该产品能够使不同和不兼容的操作系统运行在同一台计算机上,并支持在运行时进行迁移,保证正常运行并且避免宕机。 Xen 4.14版本及之前版本中存在安全漏洞。该漏洞源于在访问/分配事件通道时缺少内存屏障。
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

Vendor Product Affected Versions CPE Subscribe
- n/a n/a -

II. Public POCs for CVE-2020-25603

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2020-25603

请登录查看更多情报信息。

Vendor Advisories for CVE-2020-25603 (2)

Mailing List Discussions for CVE-2020-25603 (4)

Other References for CVE-2020-25603 (1)

Same Patch Batch · n/a · 2020-09-23 · 28 CVEs total

CVE-2020-25739 Ruby 跨站脚本漏洞
CVE-2020-14370 Docker 信息泄露漏洞
CVE-2020-25821 peg-markdown 代码问题漏洞
CVE-2020-25826 Windows PingID 安全漏洞
CVE-2020-14365 Red Hat Ansible 数据伪造问题漏洞
CVE-2020-10714 Red Hat WildFly Elytron 授权问题漏洞
CVE-2020-10687 Red Hat Undertow 环境问题漏洞
CVE-2020-7122 Aruba CX Switches 缓冲区错误漏洞
CVE-2020-7121 Aruba CX 交换机 缓冲区错误漏洞
CVE-2020-24624 HPE Pay 路径遍历漏洞
CVE-2020-24625 HPE Pay 路径遍历漏洞
CVE-2020-24626 HPE Pay 路径遍历漏洞
CVE-2020-16244 APM Classic 安全漏洞
CVE-2020-16240 GE APM Classic 安全漏洞
CVE-2020-25596 Xen 注入漏洞
CVE-2020-24213 YGOPro ygocore 输入验证错误漏洞
CVE-2020-5783 IgniteNet HeliOS GLinq 跨站请求伪造漏洞
CVE-2020-5782 IgniteNet HeliOS GLinq 输入验证错误漏洞
CVE-2020-5781 IgniteNet HeliOS GLinq 跨站脚本漏洞
CVE-2020-25595 Xen 安全漏洞

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

IV. Related Vulnerabilities

V. Comments for CVE-2020-25603

No comments yet


Leave a comment