GuacamoleApplication · Apache
CVE-2023-30576
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedApache Guacamole 0.9.10 through 1.5.1 may continue to reference a freed RDP audio input buffer. Depending on timing, this may allow an attacker to execute arbitrary code with the privileges of the guacd process.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceApache Guacamole versions 0.9.10 through 1.5.1 contain a use-after-free vulnerability in RDP audio input buffer handling. The guacd process may continue referencing a freed audio buffer, which under certain timing conditions allows an attacker to achieve arbitrary code execution with guacd process privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
GuacamoleApplication
>= 0.9.0, < 1.5.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Guacamole versionRun `guacd --version` or check your package manager (dpkg -l guacamole-server or rpm -qa guacamole-server) to obtain the exact version numberAffected if The version is 1.5.1 or lower, or between 0.9.10 and 1.5.1 inclusive, indicating it falls within the vulnerable range < 1.5.2
-
Verify guacd process is runningRun `ps aux | grep guacd` to confirm the guacd daemon is activeAffected if guacd is running - this is the process vulnerable to the use-after-free
-
Confirm RDP support is enabled in guacdCheck if the RDP protocol support is compiled or loaded - look for librdp-related modules in guacd configuration or run `ldd $(which guacd) | grep -i rdp`Affected if RDP support is present in guacd - the vulnerability exists specifically in RDP audio input handling
-
Check for RDP connections with audio inputReview active Guacamole connections via admin UI or check connection configuration files in /etc/guacamole/ for RDP connections that have audio input enabledAffected if There are active RDP connections or saved configurations using RDP with audio input feature - this is the trigger condition for the vulnerability
You are affected if your guacd version is less than 1.5.2, runs with RDP support enabled, and handles RDP connections that utilize the audio input feature.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.5.2
Upgrade Apache Guacamole to version 1.5.2 or later to address the use-after-free vulnerability in RDP audio input processing.
1.5.2
- 1. Back up the current Guacamole configuration and data directory
- 2. Stop the guacd service and any web application servers running Guacamole
- 3. Upgrade Apache Guacamole to version 1.5.2 or later using your installation method (package manager, source compilation, or Docker)
- 4. Verify the installed version matches the target (1.5.2 or higher)
- 5. Restore the backed-up configuration if needed
- 6. Start the guacd service and web application servers
- 7. Test that RDP connections with audio input work correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Guacamole
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30576 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-30576 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data