GuacamoleApplication · Apache
CVE-2018-1340
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 · uneditedPrior to 1.0.0, Apache Guacamole used a cookie for client-side storage of the user's session token. This cookie lacked the "secure" flag, which could allow an attacker eavesdropping on the network to intercept the user's session token if unencrypted HTTP requests are made to the same domain.
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 prior to version 1.0.0 stored user session tokens in cookies without the 'secure' flag, allowing these tokens to be transmitted over unencrypted HTTP connections and potentially intercepted by network eavesdroppers.
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.14CVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 Apache Guacamole versionCheck the Guacamole web application version by inspecting the guacamole.war file, or by accessing the Guacamole login page and viewing the version information typically displayed in the UI footer or server status. Alternatively, check the logs or package manager if installed via OS packages.Affected if The installed version is 0.9.14 or any version prior to 0.9.14 (e.g., 0.9.13, 0.9.12, etc.)
-
Locate session cookie configurationInspect the Guacamole web application configuration files, typically the web.xml deployment descriptor located in the servlet container (such as Tomcat) under the Guacamole application directory. Also check any Guacamole-specific configuration files that define session settings.Affected if The configuration exists but does not include the 'secure' attribute set to 'true' for the session cookie, or the 'secure' attribute is missing entirely
-
Verify cookie transmission modeAccess the Guacamole login page over an HTTP (not HTTPS) connection using a browser, then use browser developer tools (F12) to inspect the Set-Cookie header or the cookies stored for the site. Check if the session cookie is being set without the 'Secure' flag.Affected if The session cookie is transmitted and accepted over an HTTP connection without the 'Secure' attribute present in the cookie definition
You are affected if your Apache Guacamole version is 0.9.14 or earlier AND the session cookie configuration does not include the 'secure' flag, meaning session tokens can be sent over unencrypted HTTP connections.
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.
From vendor dataConfigure the session cookie to include the 'secure' flag, ensuring it is only transmitted over HTTPS connections. Upgrade to Apache Guacamole 1.0.0 or later where this issue is resolved.
Fix this in Guacamole
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1340 — 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-2018-1340 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