CVE-2024-50573
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 · uneditedIn JetBrains Hub before 2024.3.47707 improper access control allowed users to generate permanent tokens for unauthorized services
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 confidenceImproper access control in JetBrains Hub before version 2024.3.47707 allows authenticated users to generate permanent API tokens for services they are not authorized to access, potentially enabling privilege escalation or unauthorized access to integrated services.
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< 2024.3.47707CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed JetBrains Hub versionAccess the Hub administration interface and navigate to the About section, or check the Hub installation directory for a version file. The version is typically displayed in the UI footer or in the admin settings under 'Hub Information'.Affected if The installed version is lower than 2024.3.47707 (for example, 2024.2.x, 2024.1.x, or earlier).
-
Verify API token generation is accessibleNavigate to Hub Settings > API Tokens or equivalent token management section. Confirm that the API token generation feature is available and enabled for authenticated users.Affected if API token generation is enabled and accessible to non-admin authenticated users.
-
Review existing permanent API tokensIn Hub administration, list all generated API tokens and check which services they grant access to. Look for tokens created by users who should not have access to certain integrated services (such as YouTrack, Upsource, or other connected tools).Affected if There are API tokens created by users that grant access to services beyond their assigned permissions.
You are affected if your JetBrains Hub version is below 2024.3.47707 AND API token generation is accessible to authenticated users who may create tokens for services they are not authorized to access.
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.
dbcve · scoped2024.3.47707
Upgrade JetBrains Hub to version 2024.3.47707 or later to enforce proper authorization checks on token generation.
2024.3.47707
- Backup the current Hub installation and all existing data/configuration
- Download Hub version 2024.3.47707 or a later stable release from the official JetBrains website (www.jetbrains.com)
- Stop the running Hub service before proceeding with the upgrade
- Install the new version following JetBrains standard upgrade procedures
- Verify the upgrade completed successfully
- Restart the Hub service
- Confirm that the improper access control vulnerability is resolved by verifying that users can no longer generate permanent tokens for unauthorized services
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.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,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50573 — 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-2024-50573 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