Skip to main content
CVE-2023-3255VulnerabilityPublished Updated

CVE-2023-3255: Red Hat Enterprise Linux 8 · Infinite Loop

Affects Red Hat Enterprise Linux 8Source CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.8% chance of exploitation in 30 days – higher than 79% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Sep 2023

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

AI-suggested

To mitigate CVE-2023-3255, European organizations should take the following specific actions: 1) Apply the latest security patches and updates provided by Red Hat for Red Hat Enterprise Linux 8 and QEMU as soon as they become available to fix the infinite loop condition. 2) Restrict VNC server access to trusted and authenticated users only, enforcing strong authentication mechanisms such as multi-factor authentication to reduce the attack surface. 3) Disable clipboard sharing over VNC if it is not required, as this feature is the attack vector for the vulnerability. 4) Monitor VNC server logs and network traffic for unusual clipboard activity or repeated connection attempts that could indicate exploitation attempts. 5) Implement network segmentation and firewall rules to limit VNC access to only necessary systems and users. 6) Consider alternative remote management tools or VNC implementations that do not exhibit this vulnerability if patching is delayed. 7) Conduct regular vulnerability assessments and penetration tests focusing on virtualization infrastructure to identify and remediate similar issues proactively.

Description

A flaw was found in the QEMU built-in VNC server while processing ClientCutText messages. A wrong exit condition may lead to an infinite loop when inflating an attacker controlled zlib buffer in the `inflate_buffer` function. This could allow a remote authenticated client who is able to send a clipboard to the VNC server to trigger a denial of service.

References

Community reviews

Loading reviews…