dbcve.org
YoutrackApplication · Jetbrains

CVE-2024-38506

HIGH · 8.1 CVSS v3.1 Published 2024-06-18
Fix available
A fix is available. Upgrade to 2024.2.34646 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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.2.34646 user without appropriate permissions could enable the auto-attach option for workflows

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 YouTrack before version 2024.2.34646, an authorization bypass vulnerability exists where users lacking appropriate permissions can enable the auto-attach option for workflows, potentially allowing unauthorized attachment of files or data to workflow items.

MitigationUpgrade YouTrack to version 2024.2.34646 or later. Verify that permission controls properly restrict auto-attach functionality to authorized users only.

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.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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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. Identify the installed YouTrack version
    Navigate to the Administration > About section in the YouTrack UI, or check the version displayed on the login page. Compare this version number to 2024.2.34646.
    Affected if The installed version is earlier than 2024.2.34646 (for example, 2024.1.x or earlier).
  2. Review workflow configurations for auto-attach settings
    Go to Administration > Workflows and examine each workflow configuration. Look for any workflow that has the auto-attach option enabled, which allows files or data to be automatically attached to workflow items.
    Affected if Any workflow has the auto-attach option enabled and the YouTrack version is below 2024.2.34646.
  3. Verify user permissions for workflow auto-attach functionality
    In Administration > Users and Roles, examine which users or groups have permissions to modify workflow settings or enable the auto-attach feature. Check if any users without proper authorization have been granted workflow management capabilities.
    Affected if Users lacking appropriate permissions have been granted the ability to enable or modify auto-attach settings in workflows.
  4. Audit recent workflow configuration changes
    Review the audit logs or history for the Workflows section to identify any recent changes to auto-attach settings, particularly changes made by users who should not have such permissions.
    Affected if Unauthorized users have recently modified workflow auto-attach configurations.

A user is affected if their YouTrack installation is version 2024.2.34646 or earlier AND any workflow has auto-attach enabled accessible to users without proper authorization.

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 YouTrack to version 2024.2.34646 or later. Verify that permission controls properly restrict auto-attach functionality to authorized users only.

Recommended fix High confidence

2024.2.34646 or later

  1. Back up your YouTrack database and configuration before upgrading
  2. Download YouTrack version 2024.2.34646 or later from the official JetBrains website (www.jetbrains.com/youtrack)
  3. Stop the YouTrack service
  4. Upgrade YouTrack to the downloaded version following the standard upgrade procedure
  5. Restart the YouTrack service
  6. Verify the upgrade was successful by checking the YouTrack version in Administration > System > Overview
  7. Confirm that users without appropriate permissions can no longer enable the auto-attach option for workflows
Caveat This is a routine security patch upgrade; review JetBrains release notes for any minor changes

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

Fix this in Youtrack Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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