dbcve.org
YoutrackApplication · Jetbrains

CVE-2024-28228

MEDIUM · 5.3 CVSS v3.1 Published 2024-03-07
Fix available
A fix is available. Upgrade to 2024.1.25893 or later.
See remediation →
62/100
Remediation priority · Elevated
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 YouTrack before 2024.1.25893 creation comments on behalf of an arbitrary user in HelpDesk 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 · moderate confidence

This is an authorization bypass vulnerability in JetBrains YouTrack's HelpDesk module. An authenticated user could create comments on behalf of arbitrary other users due to insufficient authorization checks when submitting HelpDesk comments. This allows impersonation of other users in the ticket system.

MitigationUpgrade YouTrack to version 2024.1.25893 or later. Apply the vendor patch to remediate the improper authorization in the HelpDesk comment creation functionality.

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
YoutrackApplication
Affected:< 2024.1.25893

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
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 YouTrack installation and version
    Access the YouTrack administration interface and navigate to the 'About' page or check the build number in the footer of any YouTrack page. Alternatively, check the installation directory for a version file or run 'youtrack --version' if you have CLI access.
    Affected if The installed version is less than 2024.1.25893 (e.g., 2024.1.25700, 2023.3.x, etc.)
  2. Confirm HelpDesk module is active
    Navigate to YouTrack administration > Plugins or Features and verify if the HelpDesk (or Customer Portal) module is enabled. Check project settings for any project that has HelpDesk functionality configured.
    Affected if HelpDesk module is enabled and being used in any project
  3. Review HelpDesk comment audit logs
    Access YouTrack administration > Audit Log or project-specific activity logs. Filter for comment creation events in HelpDesk requests. Look for comments where the author field does not match the actual user session that created it.
    Affected if There are comment entries where the displayed author differs from the session user, or there are comments created by users who should not have been able to comment as other users
  4. Check for unauthorized user impersonation in tickets
    Open recent HelpDesk requests/tickets and inspect the comment history. Verify that each comment's author matches a legitimate user who actually has access and would have submitted that comment.
    Affected if You find comments in HelpDesk tickets that appear to be authored by users who did not create them, or there are comments from users who should not have had permission to comment on those specific tickets

You are affected if your YouTrack version is below 2024.1.25893 AND the HelpDesk module is enabled, with potential evidence of unauthorized comment impersonation in audit logs or ticket histories.

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.1.25893 or later
Fixed in 2024.1.25893
Interim mitigation

Upgrade YouTrack to version 2024.1.25893 or later. Apply the vendor patch to remediate the improper authorization in the HelpDesk comment creation functionality.

Recommended fix High confidence

2024.1.25893 or later

  1. Backup your YouTrack database and configuration files before starting the upgrade
  2. Download YouTrack version 2024.1.25893 or later from the official JetBrains website (www.jetbrains.com/youtrack)
  3. Stop the YouTrack service
  4. Follow the standard YouTrack upgrade procedure: either use the installer for in-place upgrade or restore from backup to the new version
  5. Start the YouTrack service
  6. Verify the fix by attempting to create a comment as a different user in HelpDesk (the vulnerability should no longer allow arbitrary user impersonation)
Caveat Review JetBrains release notes for any configuration or feature changes between your current version and 2024.1.25893

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

Fix this in Youtrack Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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