Skip to content
Fencer Vulns
medium 6.7

CVE-2020-9498 json

Apache Guacamole 1.1.0 and older may mishandle pointers involved inprocessing data received via RDP static virtual channels.

published 2020-07-02 6 y ago modified 2026-06-17 4 mo ago also BIT-guacamole-2020-9498 , BIT-guacamole-server-2020-9498 , EUVD-2020-30304

cvss
6.7
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 54%
public exploits
0
none known

Summary

Apache Guacamole 1.1.0 and older may mishandle pointers involved inprocessing data received via RDP static virtual channels. If a userconnects to a malicious or compromised RDP server, a series ofspecially-crafted PDUs could result in memory corruption, possiblyallowing arbitrary code to be executed with the privileges of therunning guacd process.

Patch / fix

  • bitnami guacamole 1.1.0
  • bitnami guacamole-server 1.1.0
  • guacamole-server Debian 11 1.3.0-1

debian advisories DEBIAN-CVE-2020-9498

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-9498 updated cvss 8.8

guacamole-server: Dangling pointer in RDP static virtual channel handling

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.74% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 6.7 CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.2 AV:L/AC:H/Au:N/C:C/I:C/A:C
OSV 3.1 6.7 CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
bitnami guacamole
<1.1.0
1.1.0
bitnami guacamole-server
<1.1.0
1.1.0

Affected products

  • n/a Apache Guacamole

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.