The version of Tencent Linux installed on the remote TencentOS Server 3 host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the TSSA-2024:0248 advisory.

    Package updates are available for TencentOS Server 3 that fix the following vulnerabilities:

    CVE-2024-31080:
    A heap-based buffer over-read vulnerability was found in the X.org server's ProcXIGetSelectedEvents()     function. This issue occurs when byte-swapped length values are used in replies, potentially leading to     memory leakage and segmentation faults, particularly when triggered by a client with a different     endianness. This vulnerability could be exploited by an attacker to cause the X server to read heap memory     values and then transmit them back to the client until encountering an unmapped page, resulting in a     crash. Despite the attacker's inability to control the specific memory copied into the replies, the small     length values typically stored in a 32-bit integer can result in significant attempted out-of-bounds     reads.

    CVE-2024-31081:
    A heap-based buffer over-read vulnerability was found in the X.org server's ProcXIPassiveGrabDevice()     function. This issue occurs when byte-swapped length values are used in replies, potentially leading to     memory leakage and segmentation faults, particularly when triggered by a client with a different     endianness. This vulnerability could be exploited by an attacker to cause the X server to read heap memory     values and then transmit them back to the client until encountering an unmapped page, resulting in a     crash. Despite the attacker's inability to control the specific memory copied into the replies, the small     length values typically stored in a 32-bit integer can result in significant attempted out-of-bounds     reads.

    CVE-2024-31083:
    A use-after-free vulnerability was found in the ProcRenderAddGlyphs() function of Xorg servers. This issue     occurs when AllocateGlyph() is called to store new glyphs sent by the client to the X server, potentially     resulting in multiple entries pointing to the same non-refcounted glyphs. Consequently,     ProcRenderAddGlyphs() may free a glyph, leading to a use-after-free scenario when the same glyph pointer     is subsequently accessed. This flaw allows an authenticated attacker to execute arbitrary code on the     system by sending a specially crafted request.

Tenable has extracted the preceding description block directly from the Tencent Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote MiracleLinux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the AXSA:2024-7730:07 advisory.

    * xorg-x11-server: Heap buffer overread/data leakage in ProcXIGetSelectedEvents (CVE-2024-31080)
      * xorg-x11-server: Heap buffer overread/data leakage in ProcXIPassiveGrabDevice (CVE-2024-31081)
      * xorg-x11-server: User-after-free in ProcRenderAddGlyphs (CVE-2024-31083)

Tenable has extracted the preceding description block directly from the MiracleLinux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of Tencent Linux installed on the remote TencentOS Server 4 host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the TSSA-2024:0641 advisory.

    Package updates are available for TencentOS Server 4 that fix the following vulnerabilities:

    CVE-2024-31081:
    A heap-based buffer over-read vulnerability was found in the X.org server's ProcXIPassiveGrabDevice()     function. This issue occurs when byte-swapped length values are used in replies, potentially leading to     memory leakage and segmentation faults, particularly when triggered by a client with a different     endianness. This vulnerability could be exploited by an attacker to cause the X server to read heap memory     values and then transmit them back to the client until encountering an unmapped page, resulting in a     crash. Despite the attacker's inability to control the specific memory copied into the replies, the small     length values typically stored in a 32-bit integer can result in significant attempted out-of-bounds     reads.

    CVE-2024-31080:
    A heap-based buffer over-read vulnerability was found in the X.org server's ProcXIGetSelectedEvents()     function. This issue occurs when byte-swapped length values are used in replies, potentially leading to     memory leakage and segmentation faults, particularly when triggered by a client with a different     endianness. This vulnerability could be exploited by an attacker to cause the X server to read heap memory     values and then transmit them back to the client until encountering an unmapped page, resulting in a     crash. Despite the attacker's inability to control the specific memory copied into the replies, the small     length values typically stored in a 32-bit integer can result in significant attempted out-of-bounds     reads.

    CVE-2024-21886:
    A heap buffer overflow flaw was found in the DisableDevice function in the X.Org server. This issue may     lead to an application crash or, in some circumstances, remote code execution in SSH X11 forwarding     environments.

    CVE-2023-6377:
    A flaw was found in xorg-server. Querying or changing XKB button actions such as moving from a touchpad to     a mouse can result in out-of-bounds memory reads and writes. This may allow local privilege escalation or     possible remote code execution in cases where X11 forwarding is involved.

    CVE-2023-5367:
    A out-of-bounds write flaw was found in the xorg-x11-server. This issue occurs due to an incorrect     calculation of a buffer offset when copying data stored in the heap in the XIChangeDeviceProperty function     in Xi/xiproperty.c and in RRChangeOutputProperty function in randr/rrproperty.c, allowing for possible     escalation of privileges or denial of service.

    CVE-2024-21885:
    A flaw was found in X.Org server. In the XISendDeviceHierarchyEvent function, it is possible to exceed the     allocated array length when certain new device IDs are added to the xXIHierarchyInfo struct. This can     trigger a heap buffer overflow condition, which may lead to an application crash or remote code execution     in SSH X11 forwarding environments.

    CVE-2024-0408:
    A flaw was found in the X.Org server. The GLX PBuffer code does not call the XACE hook when creating the     buffer, leaving it unlabeled. When the client issues another request to access that resource (as with a     GetGeometry) or when it creates another resource that needs to access that buffer, such as a GC, the     XSELINUX code will try to use an object that was never labeled and crash because the SID is NULL.

    CVE-2024-0409:
    A flaw was found in the X.Org server. The cursor code in both Xephyr and Xwayland uses the wrong type of     private at creation. It uses the cursor bits type with the cursor as private, and when initiating the     cursor, that overwrites the XSELINUX context.

    CVE-2024-0229:
    An out-of-bounds memory access flaw was found in the X.Org server. This issue can be triggered when a     device frozen by a sync grab is reattached to a different master device. This issue may lead to an     application crash, local privilege escalation (if the server runs with extended privileges), or remote     code execution in SSH X11 forwarding environments.

    CVE-2023-6816:
    A flaw was found in X.Org server. Both DeviceFocusEvent and the XIQueryPointer reply contain a bit for     each logical button currently down. Buttons can be arbitrarily mapped to any value up to 255, but the     X.Org Server was only allocating space for the device's particular number of buttons, leading to a heap     overflow if a bigger value was used.

    CVE-2024-31083:
    A use-after-free vulnerability was found in the ProcRenderAddGlyphs() function of Xorg servers. This issue     occurs when AllocateGlyph() is called to store new glyphs sent by the client to the X server, potentially     resulting in multiple entries pointing to the same non-refcounted glyphs. Consequently,     ProcRenderAddGlyphs() may free a glyph, leading to a use-after-free scenario when the same glyph pointer     is subsequently accessed. This flaw allows an authenticated attacker to execute arbitrary code on the     system by sending a specially crafted request.

Tenable has extracted the preceding description block directly from the Tencent Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of Tencent Linux installed on the remote TencentOS Server 4 host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the TSSA-2024:0568 advisory.

    Package updates are available for TencentOS Server 4 that fix the following vulnerabilities:

    CVE-2024-31080:
    A heap-based buffer over-read vulnerability was found in the X.org server's ProcXIGetSelectedEvents()     function. This issue occurs when byte-swapped length values are used in replies, potentially leading to     memory leakage and segmentation faults, particularly when triggered by a client with a different     endianness. This vulnerability could be exploited by an attacker to cause the X server to read heap memory     values and then transmit them back to the client until encountering an unmapped page, resulting in a     crash. Despite the attacker's inability to control the specific memory copied into the replies, the small     length values typically stored in a 32-bit integer can result in significant attempted out-of-bounds     reads.

    CVE-2024-31081:
    A heap-based buffer over-read vulnerability was found in the X.org server's ProcXIPassiveGrabDevice()     function. This issue occurs when byte-swapped length values are used in replies, potentially leading to     memory leakage and segmentation faults, particularly when triggered by a client with a different     endianness. This vulnerability could be exploited by an attacker to cause the X server to read heap memory     values and then transmit them back to the client until encountering an unmapped page, resulting in a     crash. Despite the attacker's inability to control the specific memory copied into the replies, the small     length values typically stored in a 32-bit integer can result in significant attempted out-of-bounds     reads.

    CVE-2023-6478:
    A flaw was found in xorg-server. A specially crafted request to RRChangeProviderProperty or     RRChangeOutputProperty can trigger an integer overflow which may lead to a disclosure of sensitive     information.

    CVE-2023-5367:
    A out-of-bounds write flaw was found in the xorg-x11-server. This issue occurs due to an incorrect     calculation of a buffer offset when copying data stored in the heap in the XIChangeDeviceProperty function     in Xi/xiproperty.c and in RRChangeOutputProperty function in randr/rrproperty.c, allowing for possible     escalation of privileges or denial of service.

    CVE-2023-5380:
    A use-after-free flaw was found in the xorg-x11-server. An X server crash may occur in a very specific and     legacy configuration (a multi-screen setup with multiple protocol screens, also known as Zaphod mode) if     the pointer is warped from within a window on one screen to the root window of the other screen and if the     original window is destroyed followed by another window being destroyed.

    CVE-2023-6816:
    A flaw was found in X.Org server. Both DeviceFocusEvent and the XIQueryPointer reply contain a bit for     each logical button currently down. Buttons can be arbitrarily mapped to any value up to 255, but the     X.Org Server was only allocating space for the device's particular number of buttons, leading to a heap     overflow if a bigger value was used.

    CVE-2024-0229:
    An out-of-bounds memory access flaw was found in the X.Org server. This issue can be triggered when a     device frozen by a sync grab is reattached to a different master device. This issue may lead to an     application crash, local privilege escalation (if the server runs with extended privileges), or remote     code execution in SSH X11 forwarding environments.

    CVE-2024-21885:
    A flaw was found in X.Org server. In the XISendDeviceHierarchyEvent function, it is possible to exceed the     allocated array length when certain new device IDs are added to the xXIHierarchyInfo struct. This can     trigger a heap buffer overflow condition, which may lead to an application crash or remote code execution     in SSH X11 forwarding environments.

    CVE-2024-21886:
    A heap buffer overflow flaw was found in the DisableDevice function in the X.Org server. This issue may     lead to an application crash or, in some circumstances, remote code execution in SSH X11 forwarding     environments.

    CVE-2024-0408:
    A flaw was found in the X.Org server. The GLX PBuffer code does not call the XACE hook when creating the     buffer, leaving it unlabeled. When the client issues another request to access that resource (as with a     GetGeometry) or when it creates another resource that needs to access that buffer, such as a GC, the     XSELINUX code will try to use an object that was never labeled and crash because the SID is NULL.

    CVE-2024-0409:
    A flaw was found in the X.Org server. The cursor code in both Xephyr and Xwayland uses the wrong type of     private at creation. It uses the cursor bits type with the cursor as private, and when initiating the     cursor, that overwrites the XSELINUX context.

Tenable has extracted the preceding description block directly from the Tencent Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

According to the versions of the xorg-x11-server package installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

    A flaw was found in X.Org Server Overlay Window. A Use-After-Free may lead to local privilege escalation.
    If a client explicitly destroys the compositor overlay window (aka COW), the Xserver would leave a     dangling pointer to that window in the CompScreen structure, which will trigger a use-after-free     later.(CVE-2023-1393)

    A out-of-bounds write flaw was found in the xorg-x11-server. This issue occurs due to an incorrect     calculation of a buffer offset when copying data stored in the heap in the XIChangeDeviceProperty function     in Xi/xiproperty.c and in RRChangeOutputProperty function in randr/rrproperty.c, allowing for possible     escalation of privileges or denial of service.(CVE-2023-5367)

    A use-after-free flaw was found in the xorg-x11-server. An X server crash may occur in a very specific and     legacy configuration (a multi-screen setup with multiple protocol screens, also known as Zaphod mode) if     the pointer is warped from within a window on one screen to the root window of the other screen and if the     original window is destroyed followed by another window being destroyed.(CVE-2023-5380)

    A heap-based buffer over-read vulnerability was found in the X.org server's ProcAppleDRICreatePixmap()     function. This issue occurs when byte-swapped length values are used in replies, potentially leading to     memory leakage and segmentation faults, particularly when triggered by a client with a different     endianness. This vulnerability could be exploited by an attacker to cause the X server to read heap memory     values and then transmit them back to the client until encountering an unmapped page, resulting in a     crash. Despite the attacker's inability to control the specific memory copied into the replies, the small     length values typically stored in a 32-bit integer can result in significant attempted out-of-bounds     reads.(CVE-2024-31082)

    A heap-based buffer over-read vulnerability was found in the X.org server's ProcXIPassiveGrabDevice()     function. This issue occurs when byte-swapped length values are used in replies, potentially leading to     memory leakage and segmentation faults, particularly when triggered by a client with a different     endianness. This vulnerability could be exploited by an attacker to cause the X server to read heap memory     values and then transmit them back to the client until encountering an unmapped page, resulting in a     crash. Despite the attacker's inability to control the specific memory copied into the replies, the small     length values typically stored in a 32-bit integer can result in significant attempted out-of-bounds     reads.(CVE-2024-31081)

    A use-after-free vulnerability was found in the ProcRenderAddGlyphs() function of Xorg servers. This issue     occurs when AllocateGlyph() is called to store new glyphs sent by the client to the X server, potentially     resulting in multiple entries pointing to the same non-refcounted glyphs. Consequently,     ProcRenderAddGlyphs() may free a glyph, leading to a use-after-free scenario when the same glyph pointer     is subsequently accessed. This flaw allows an authenticated attacker to execute arbitrary code on the     system by sending a specially crafted request.(CVE-2024-31083)

    A heap-based buffer over-read vulnerability was found in the X.org server's ProcXIGetSelectedEvents()     function. This issue occurs when byte-swapped length values are used in replies, potentially leading to     memory leakage and segmentation faults, particularly when triggered by a client with a different     endianness. This vulnerability could be exploited by an attacker to cause the X server to read heap memory     values and then transmit them back to the client until encountering an unmapped page, resulting in a     crash. Despite the attacker's inability to control the specific memory copied into the replies, the small     length values typically stored in a 32-bit integer can result in significant attempted out-of-bounds     reads.(CVE-2024-31080)

Tenable has extracted the preceding description block directly from the EulerOS xorg-x11-server security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2024:1261-1 advisory.

    - CVE-2024-31080: Fixed ProcXIGetSelectedEvents to use unswapped length (bsc#1222309).
    - CVE-2024-31081: Fixed ProcXIPassiveGrabDevice to use unswapped length to send reply (bsc#1222310).
    - CVE-2024-31082: Fixed ProcAppleDRICreatePixmap to use unswapped length to send reply (bsc#1222311).
    - CVE-2024-31083: Fixed refcounting of glyphs during ProcRenderAddGlyphs (bsc#1222312).

    Other fixes:
    - Fixed regression for security fix for CVE-2024-31083 when using Android Studio (bnc#1222442)

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
239888	TencentOS Server 3: tigervnc (TSSA-2024:0248)	Nessus	Tencent Local Security Checks	2025/6/16	2025/11/20	high
293452	MiracleLinux 8 : tigervnc-1.13.1-2.el8_9.10.ML.1 (AXSA:2024-7730:07)	Nessus	Miracle Linux Local Security Checks	2026/1/20	2026/1/20	high
240020	TencentOS Server 4: xorg-x11-server-Xwayland (TSSA-2024:0641)	Nessus	Tencent Local Security Checks	2025/6/16	2025/11/20	critical
276083	TencentOS Server 4: xorg-x11-server (TSSA-2024:0568)	Nessus	Tencent Local Security Checks	2025/11/20	2025/11/20	critical
202552	EulerOS 2.0 SP9 : xorg-x11-server (EulerOS-SA-2024-1979)	Nessus	Huawei Local Security Checks	2024/7/16	2024/7/16	high
193302	SUSE SLED15: xorg-x11-server / xorg-x11-server-extra / xorg-x11-server-sdk / etc (SUSE-SU-2024:1261-1)	Nessus	SuSE Local Security Checks	2024/4/13	2026/6/26	high

检测

插件搜索

high

high

critical

critical

high

high