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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2020-29484

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

I. Basic Information for CVE-2020-29484

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.14.x. When a Xenstore watch fires, the xenstore client that registered the watch will receive a Xenstore message containing the path of the modified Xenstore entry that triggered the watch, and the tag that was specified when registering the watch. Any communication with xenstored is done via Xenstore messages, consisting of a message header and the payload. The payload length is limited to 4096 bytes. Any request to xenstored resulting in a response with a payload longer than 4096 bytes will result in an error. When registering a watch, the payload length limit applies to the combined length of the watched path and the specified tag. Because watches for a specific path are also triggered for all nodes below that path, the payload of a watch event message can be longer than the payload needed to register the watch. A malicious guest that registers a watch using a very large tag (i.e., with a registration operation payload length close to the 4096 byte limit) can cause the generation of watch events with a payload length larger than 4096 bytes, by writing to Xenstore entries below the watched path. This will result in an error condition in xenstored. This error can result in a NULL pointer dereference, leading to a crash of xenstored. A malicious guest administrator can cause xenstored to crash, leading to a denial of service. Following a xenstored crash, domains may continue to run, but management operations will be impossible. Only C xenstored is affected, oxenstored is not affected.
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是英国剑桥(Cambridge)大学的一款开源的虚拟机监视器产品。该产品能够使不同和不兼容的操作系统运行在同一台计算机上,并支持在运行时进行迁移,保证正常运行并且避免宕机。 Xen 4.14.x 版本存在安全漏洞,该漏洞源于Xenstore watch fires的Xenstore客户端将收到一条Xenstore消息,其中包含触发手表的修改后的Xenstore条目的路径,以及在注册手表时指定的标记。与xenstored的任何通信都是通过Xenstore消息完成的,该消息由消息头和负载组成。有效负载长
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-29484

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2020-29484

登录查看更多情报信息。

Same Patch Batch · n/a · 2020-12-15 · 116 CVEs total

CVE-2020-284427.5 HIGHPrototype Pollution
CVE-2020-284567.3 HIGHCross-site Scripting (XSS)
CVE-2020-284577.2 HIGHCross-site Scripting (XSS)
CVE-2020-27055Google Android 安全漏洞
CVE-2020-29480Xen 授权问题漏洞
CVE-2020-29479Xen 权限许可和访问控制问题漏洞
CVE-2020-29571Xen 代码问题漏洞
CVE-2020-29570Xen 安全漏洞
CVE-2020-29569Linux kernel 资源管理错误漏洞
CVE-2020-27777Linux kernel 授权问题漏洞
CVE-2020-25712xorg-x11-server 缓冲区错误漏洞
CVE-2020-29568Xen 缓冲区错误漏洞
CVE-2020-29567Xen 安全漏洞
CVE-2020-29566Xen 处理逻辑错误漏洞
CVE-2020-27068Google Android 缓冲区错误漏洞
CVE-2020-27067Google Android 资源管理错误漏洞
CVE-2020-27066Google Android 资源管理错误漏洞
CVE-2020-27048Google Android 缓冲区错误漏洞
CVE-2020-27047Google Android 缓冲区错误漏洞
CVE-2020-27046Google Android 缓冲区错误漏洞

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

IV. Related Vulnerabilities

V. Comments for CVE-2020-29484

No comments yet


Leave a comment