dbcve.org
HubApplication · Jetbrains

CVE-2024-38507

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-18
Fix available
A fix is available. Upgrade to 2024.2.34646 or later.
See remediation →
58/100
Remediation priority · Elevated
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
In JetBrains Hub before 2024.2.34646 stored XSS via project description was possible

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

Stored XSS vulnerability in JetBrains Hub allows attackers to inject malicious JavaScript into project description fields. This script executes when other users view the affected project, enabling session hijacking, data theft, or unauthorized actions.

MitigationUpgrade JetBrains Hub to version 2024.2.34646 or later. Implement input sanitization and output encoding for all user-submitted content in project fields.

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:< 2024.2.34646

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 installed version number
    Affected if The installed version is lower than 2024.2.34646 (for example, 2024.1.x, 2023.x, or earlier)
  2. Access Hub admin or project management interface
    Log in to Hub as an administrator and navigate to the projects section or project settings where project metadata is managed
    Affected if You have access to create or edit projects in Hub
  3. Review all project description fields
    Examine each project's description field for any content containing script tags, javascript: URLs, event handlers (onclick, onerror, onload), or other XSS vectors
    Affected if Any project description contains unsanitized HTML, script tags, or JavaScript event handlers that could execute in a user's browser
  4. Check recent project creation or modification activity
    Review project audit logs or activity history to identify any recently created or modified projects, especially those with unusual or encoded content in description fields
    Affected if There are projects with descriptions containing obfuscated code, base64 strings, or unexpected character sequences typical of XSS payloads
  5. Verify if multiple users can view affected projects
    Confirm that projects with suspicious descriptions are accessible to other users beyond the project creator
    Affected if The vulnerable project descriptions are visible to multiple users who could trigger the malicious script upon viewing

You are affected if your JetBrains Hub version is below 2024.2.34646 and you have projects with unsanitized JavaScript or HTML in their description fields that could execute when viewed by other users.

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 2024.2.34646 or later
Fixed in 2024.2.34646
Interim mitigation

Upgrade JetBrains Hub to version 2024.2.34646 or later. Implement input sanitization and output encoding for all user-submitted content in project fields.

Recommended fix High confidence

2024.2.34646 or later

  1. 1. Back up your current JetBrains Hub installation and database
  2. 2. Download JetBrains Hub version 2024.2.34646 or later from the official JetBrains website
  3. 3. Stop the JetBrains Hub service
  4. 4. Install the upgraded version following the standard upgrade procedure
  5. 5. Verify the upgrade was successful by logging into Hub
  6. 6. Test that the stored XSS vulnerability in project descriptions is no longer exploitable

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

Fix this in Hub Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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