dbcve.org
HubApplication · Jetbrains

CVE-2022-24327

HIGH · 7.5 CVSS v3.1 Published 2022-02-25
Fix available
A fix is available. Upgrade to 2021.1.13890 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 Hub before 2021.1.13890, integration with JetBrains Account exposed an API key with excessive permissions.

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

In JetBrains Hub versions prior to 1.1.13890, the integration with JetBrains Account inadvertently exposed an API key through the system. This exposed API key was configured with excessive permissions beyond what was required for the integration to function, allowing potential unauthorized actions if the key were discovered by an attacker.

MitigationUpgrade JetBrains Hub to version 1.1.13890 or later. Additionally, rotate any credentials or API keys associated with the JetBrains Account integration as a precautionary measure, and review user access permissions to ensure adherence to the principle of least privilege.

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
HubApplication
Affected:< 2021.1.13890

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
High
Integrity
None
Availability
None

CVSS:3.1/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 checks

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

  1. Identify JetBrains Hub installation and version
    Locate the Hub installation directory and check the version file or use the Hub admin interface to view the current version number
    Affected if The installed version is less than 2021.1.13890 (or 1.1.13890)
  2. Verify JetBrains Account integration status
    Access Hub administration settings and check if the JetBrains Account integration module is enabled or configured
    Affected if The JetBrains Account integration is currently enabled or was previously configured
  3. Inspect configuration files for exposed credentials
    Search Hub configuration files (typically in conf/ or config/ directories) for any stored API keys, tokens, or credentials related to JetBrains Account integration
    Affected if An API key or token associated with JetBrains Account is found in plain text configuration files
  4. Review Hub logs for credential exposure
    Examine Hub log files for any instances where API keys may have been logged, printed in error messages, or inadvertently disclosed
    Affected if API keys or sensitive credentials appear in log files
  5. Audit API key permissions
    If an API key is found, review what permissions or scopes it possesses by checking the JetBrains Account integration settings or associated API key documentation
    Affected if The discovered API key has permissions beyond basic read-only access or beyond what is required for the integration

You are affected if running a JetBrains Hub version prior to 2021.1.13890 AND the JetBrains Account integration is or was enabled, as this combination allowed API key exposure with excessive permissions.

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.

dbcve · scoped
Upgrade available Upgrade to 2021.1.13890 or later
Fixed in 2021.1.13890
Interim mitigation

Upgrade JetBrains Hub to version 1.1.13890 or later. Additionally, rotate any credentials or API keys associated with the JetBrains Account integration as a precautionary measure, and review user access permissions to ensure adherence to the principle of least privilege.

Recommended fix High confidence

2021.1.13890 or later

  1. 1. Back up your JetBrains Hub installation and database before upgrading
  2. 2. Download Hub version 2021.1.13890 or later from the JetBrains website or your existing license portal
  3. 3. Follow the standard JetBrains Hub upgrade procedure for your deployment method (installer, Docker, or manual)
  4. 4. After upgrade, verify the Hub instance is operational and the JetBrains Account integration is functioning correctly
  5. 5. As a best practice, rotate any API keys or credentials used with the Hub integration after the upgrade
Caveat Standard JetBrains upgrade risks apply - test in non-production first, ensure plugin compatibility with the new version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Hub Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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 locally
dbcve dependency scanner

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