dbcve.org
SpaceApplication · Jetbrains

CVE-2020-11795

HIGH · 7.5 CVSS v3.1 Published 2020-04-22
Fix available
A fix is available. Upgrade to 2020-04-22 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
In JetBrains Space through 2020-04-22, the session timeout period was configured improperly.

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 · moderate confidence

JetBrains Space had an improperly configured session timeout period, allowing user sessions to persist longer than intended. This could enable attackers to hijack valid user sessions or conduct session-related attacks if sessions are not properly invalidated after periods of inactivity.

MitigationConfigure appropriate session timeout values in JetBrains Space administration settings to ensure sessions expire within a reasonable timeframe (typically 15-30 minutes of inactivity).

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
SpaceApplication
Affected:< 2020-04-22

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

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

  1. Check JetBrains Space version
    Access the JetBrains Space administration interface or API to determine the current Space version. Look for version information in the admin dashboard or check via Space API if available.
    Affected if The installed version is dated before 2020-04-22 (any version prior to the April 22, 2020 release)
  2. Review session timeout configuration
    Navigate to JetBrains Space administration settings. Look for session management, security, or authentication settings where session timeout or session lifetime can be configured.
    Affected if Session timeout is set to an extended period, or if the configuration allows sessions to persist indefinitely without expiration after user inactivity
  3. Verify session invalidation behavior
    Log into Space, remain inactive for a period exceeding typical usage, then attempt to use the existing session to determine if it remains valid.
    Affected if Sessions remain active and usable after periods of inactivity longer than 15-30 minutes, indicating improper session timeout enforcement

You are affected if your JetBrains Space version predates the 2020-04-22 release AND the session timeout allows sessions to persist beyond the recommended 15-30 minute inactivity window.

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 2020-04-22 or later
Fixed in 2020-04-22
Interim mitigation

Configure appropriate session timeout values in JetBrains Space administration settings to ensure sessions expire within a reasonable timeframe (typically 15-30 minutes of inactivity).

Fix this in Space Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-11795 — 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-11795 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