YoutrackApplication · Jetbrains

CVE-2024-50577

MEDIUM · 5.4 CVSS v3.1 Published 2024-10-28
Fix available
A fix is available. Upgrade to 2024.3.47707 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 YouTrack before 2024.3.47707 stored XSS was possible via Angular template injection in Hub settings

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

Stored cross-site scripting (XSS) vulnerability in JetBrains YouTrack versions prior to 2024.3.47707 allows attackers to inject malicious code via Angular template injection in Hub settings. The injected payload persists in the application and executes when administrators view the affected Hub settings pages.

MitigationUpgrade YouTrack to version 2024.3.47707 or later to patch the Angular template injection vulnerability. Until patching is feasible, limit access to Hub settings to trusted administrators only and audit user activity.

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.3.47707

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 installed YouTrack version
    Access the YouTrack administration interface and navigate to About (typically under Administration > System > About) or check the version via the /api/version endpoint if accessible. Compare this version number to 2024.3.47707.
    Affected if The installed version is lower than 2024.3.47707 (for example, 2024.2.45890 or any 2024.x version prior to 2024.3.47707).
  2. Verify Hub settings accessibility
    Log into YouTrack as an administrator and confirm access to Hub settings (Administration > Hub > Settings). The vulnerability exists in Hub settings pages, so these must be reachable.
    Affected if You are running an affected version AND have access to Hub settings as an administrator or privileged user.
  3. Inspect Hub settings for suspicious content
    Review all configurable fields in Hub settings pages (such as user profile fields, custom fields, or setting inputs) for any unexpected or encoded content that resembles HTML, JavaScript, or Angular template syntax (such as {{, ng-app, or script tags).
    Affected if Any such suspicious payload is found stored in Hub settings configuration fields.

You are affected if your YouTrack version is below 2024.3.47707 and you have administrators accessing Hub settings, particularly if unknown or malicious content is found in Hub settings fields.

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.3.47707 or later
Fixed in 2024.3.47707
Interim mitigation

Upgrade YouTrack to version 2024.3.47707 or later to patch the Angular template injection vulnerability. Until patching is feasible, limit access to Hub settings to trusted administrators only and audit user activity.

Recommended fix High confidence

YouTrack 2024.3.47707 or later

  1. Back up your YouTrack database and configuration files before upgrading
  2. Download YouTrack version 2024.3.47707 or later from the official JetBrains website (www.jetbrains.com/youtrack/download)
  3. Stop the YouTrack service
  4. Run the installation/upgrade following JetBrains standard upgrade procedures
  5. Start the YouTrack service
  6. Verify the upgrade was successful and the XSS vulnerability is resolved by checking that Angular template injection in Hub settings is no longer possible
Caveat Review JetBrains release notes for version 2024.3 for any breaking changes or migration requirements before upgrading

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-50577 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-50577 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