GuacamoleApplication · Apache
CVE-2024-35164
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 · uneditedThe terminal emulator of Apache Guacamole 1.5.5 and older does not properly validate console codes received from servers via text-based protocols like SSH. If a malicious user has access to a text-based connection, a specially-crafted sequence of console codes could allow arbitrary code to be executed with the privileges of the running guacd process. Users are recommended to upgrade to version 1.6.0, which fixes this issue.
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's terminal emulator in versions 1.5.5 and older fails to properly validate console codes received from servers via text-based protocols like SSH. A malicious user with access to a text-based connection can send specially-crafted console code sequences that enable arbitrary code execution with the privileges of the guacd daemon process.
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.8.0, < 1.6.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/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 Guacamole installation and versionLocate the Apache Guacamole installation (client web app, guacd daemon, or libguac libraries) and retrieve its version number. Check package managers, installed files, or the guacd daemon version flag if available.Affected if The installed version is 0.8.0 or higher but lower than 1.6.0
-
Determine if terminal emulator is in useIdentify whether connections using text-based protocols (SSH, Telnet, or similar) are configured or active in the Guacamole environment. These connections use the terminal emulator component.Affected if Text-based protocol connections (SSH, Telnet) are created or configured in Guacamole, enabling the vulnerable terminal emulator component
-
Verify guacd daemon is runningCheck if the guacd daemon process is active. This is the service that handles Guacamole connections and would execute code with its privileges if exploited.Affected if The guacd daemon is running and handling connections, which means it could be exploited to run code with its user-level privileges
You are affected if Apache Guacamole version is 1.5.5 or earlier (or any version >= 0.8.0 and < 1.6.0) and you use SSH or other text-based protocol connections that could receive console codes from remote servers.
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.6.0
Upgrade Apache Guacamole to version 1.6.0 or later, which contains the fix for proper console code validation in the terminal emulator.
1.6.0
- Backup your current Guacamole configuration and any custom settings
- Stop the guacd service to ensure no active connections during upgrade
- Install or upgrade to Apache Guacamole version 1.6.0 using your distribution's package manager or by compiling from source
- Restart the guacd service to apply the updated version
- Verify the installation by checking the guacd version and ensuring all connections work properly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Guacamole
Scoped from the published advisory
- Consultation3.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 $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35164 — 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-2024-35164 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