USN-9125-1: ssvnc vulnerabilities

Published Nov 17, 2026
·
Updated

It was discovered that SSVNC incorrectly handled certain CoRRE rectangles, leading to a heap buffer overflow. A malicious VNC server could possibly use this issue to cause SSVNC to crash, resulting in a denial of service, or possibly execute arbitrary code. (CVE-2018-20020)

It was discovered that SSVNC incorrectly handled certain raw rectangles, leading to an infinite loop. A malicious VNC server could possibly use this issue to cause SSVNC to consume excessive resources, leading to a denial of service. (CVE-2018-20021)

It was discovered that SSVNC did not properly initialize certain messages sent to the server. A malicious VNC server could possibly use this issue to obtain sensitive information. (CVE-2018-20022)

It was discovered that SSVNC did not check for memory allocation failures in its zlib and ZRLE decoders, leading to a NULL pointer dereference. A malicious VNC server could possibly use this issue to cause SSVNC to crash, resulting in a denial of service. (CVE-2018-20024)

Affected Software

3 affected componentsFixes available
ubuntu/ssvnc<1.0.29-3ubuntu0.1~esm1
1.0.29-3ubuntu0.1~esm1
All of the following
ubuntu/ssvnc<Ubuntu Pro
Ubuntu Pro
Ubuntu Ubuntu=18.04

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade ubuntu/ssvnc to a version that resolves this vulnerability.

    Fixed in 1.0.29-3ubuntu0.1~esm1
  2. Upgrade

    Upgrade ubuntu/ssvnc to a version that resolves this vulnerability.

    Fixed in Ubuntu Pro

Event History

Nov 17, 2026
Advisory Published
via Ubuntu·12:00 AM
Data Sourced
via Ubuntu·12:00 AM
DescriptionAffected Software
Advisory Published
via OSV·12:06 AM
Data Sourced
via OSV·12:06 AM
DescriptionAffected Software

Frequently Asked Questions

1

Who is exposed to these issues?

SSVNC users are exposed when they connect to a malicious VNC server. The described attacks target the SSVNC client through server-supplied VNC data.

2

What could a malicious VNC server do?

Depending on the flaw, it could crash SSVNC, cause excessive resource consumption through an infinite loop, disclose sensitive information, or possibly execute arbitrary code. The issues involve malformed CoRRE or raw rectangles, improperly initialized messages, and decoder memory-allocation failures.

3

Are these vulnerabilities exploitable without interacting with a VNC server?

The provided information describes exploitation by a malicious VNC server. It does not indicate that local use without connecting to such a server is sufficient.

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