CVE-2023-3255: Qemu: vnc: infinite loop in inflate_buffer() leads to denial of service

Published Jun 29, 2023
·
Updated

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 inflatebuffer 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.

Other sources

The vncclientcuttextext function in ui/vnc-clipboard.c calls inflatebuffer with an attacker controlled buffer (size, data). There is a wrong exit condition in inflatebuffer which can trigger an infinite loop. A remote authenticated client who is able to send a clipboard to the QEMU built-in VNC server can trigger this flaw and cause a denial of service.

Red Hat

Affected Software

6 affected componentsFixes available
redhat/qemu<8.1.0
8.1.0
debian/qemu
1:5.2+dfsg-11+deb11u31:5.2+dfsg-11+deb11u21:7.2+dfsg-7+deb12u71:9.0.2+ds-21:9.1.0+ds-3
Qemu Qemu<=8.0.3
redhat Enterprise Linux=8.0
redhat Enterprise Linux=9.0
Fedoraproject Fedora=38

Event History

Sep 13, 2023
CVE Published
via MITRE·04:12 PM
Data Sourced
via MITRE·04:12 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
May 31, 2024
Data Sourced
via Launchpad·09:07 PM
Description
Sep 16, 2024
Data Sourced
via Ubuntu·09:25 PM
RemedyDescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2023-3255?

CVE-2023-3255 is a vulnerability found in the QEMU built-in VNC server while processing ClientCutText messages.

2

What is the severity of CVE-2023-3255?

The severity of CVE-2023-3255 is medium (6.5).

3

How does CVE-2023-3255 affect the software?

CVE-2023-3255 affects QEMU versions up to but not including 8.1.0 and Red Hat Enterprise Linux versions 8.0 and 9.0.

4

How can CVE-2023-3255 be fixed?

To fix CVE-2023-3255, it is recommended to update QEMU to version 8.1.0 or apply the appropriate remedy provided by Red Hat.

5

Where can I find more information about CVE-2023-3255?

More information about CVE-2023-3255 can be found at the following references: - [Red Hat Security Advisory](https://access.redhat.com/security/cve/CVE-2023-3255) - [Bugzilla](https://bugzilla.redhat.com/show_bug.cgi?id=2218486) - [QEMU Developer Mailing List](https://lists.nongnu.org/archive/html/qemu-devel/2023-07/msg00596.html)

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203