dbcve.org
CheApplication · Eclipse

CVE-2020-14368

HIGH · 7.1 CVSS v3.1 Published 2020-12-14
Fix available
A fix is available. Upgrade to 7.14.0 or later.
See remediation →
75/100
Remediation priority · High
Remotely reachable

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 · unedited
A flaw was found in Eclipse Che in versions prior to 7.14.0 that impacts CodeReady Workspaces. When configured with cookies authentication, Theia IDE doesn't properly set the SameSite value, allowing a Cross-Site Request Forgery (CSRF) and consequently allowing a cross-site WebSocket hijack on Theia IDE. This flaw allows an attacker to gain full access to the victim's workspace through the /services endpoint. To perform a successful attack, the attacker conducts a Man-in-the-middle attack (MITM) and tricks the victim into executing a request via an untrusted link, which performs the CSRF and the Socket hijack. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability.

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 confidence

In Eclipse Che/CodeReady Workspaces versions prior to 7.14.0, Theia IDE does not set the SameSite attribute on authentication cookies. This allows an attacker to perform Cross-Site Request Forgery (CSRF) attacks and hijack WebSocket connections to the /services endpoint, granting full access to the victim's workspace. Successful exploitation requires a Man-in-the-Middle (MITM) position and tricking the victim into clicking a malicious link.

MitigationUpgrade to Eclipse Che version 7.14.0 or later, which properly sets the SameSite attribute on cookies. As a temporary mitigation, ensure users are educated about untrusted links and network integrity is maintained to reduce MITM risk.

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
CheApplication
Affected:< 7.14.0

CVSS 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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine Eclipse Che version
    Run 'chectl server:deploy' with no arguments to see version, or check the Che operator deployment: 'kubectl get checluster -o jsonpath="{.items[0].status.cheVersion}"' in the namespace where Che is installed
    Affected if The installed version is less than 7.14.0
  2. Confirm Theia IDE is the active IDE
    Check the Che workspace devfile or Theia IDE plugin deployment: 'kubectl get devworkspaces -A -o jsonpath="{.items[0].spec.template.components[?(@.name==\"theia-ide\")].name}"' or inspect the workspace configuration for Theia IDE references
    Affected if Theia IDE is the configured IDE in use for workspaces
  3. Verify SameSite cookie attribute configuration
    Inspect the Che server cookies by accessing the Che dashboard, opening browser developer tools, logging in, and examining the Set-Cookie headers for the authentication session cookies (che-token and related auth cookies)
    Affected if The authentication cookies lack the SameSite attribute or have SameSite=NULL/Lax without Secure flag when accessed over HTTPS
  4. Check for exposed /services WebSocket endpoint
    Verify if the Che server has an exposed WebSocket endpoint at /services accessible externally: 'kubectl get ingress -A | grep -i services' and confirm WebSocket upgrades are permitted
    Affected if The /services WebSocket endpoint is externally accessible without additional network segmentation

You are affected if Eclipse Che version is below 7.14.0, Theia IDE is in use, and the authentication cookies do not contain a SameSite attribute in their Set-Cookie headers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 7.14.0 or later
Fixed in 7.14.0
Interim mitigation

Upgrade to Eclipse Che version 7.14.0 or later, which properly sets the SameSite attribute on cookies. As a temporary mitigation, ensure users are educated about untrusted links and network integrity is maintained to reduce MITM risk.

Fix this in Che Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-14368 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-14368 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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