dbcve.org
YoutrackApplication · Jetbrains

CVE-2024-54158

MEDIUM · 5.3 CVSS v3.1 Published 2024-12-04
Fix available
A fix is available. Upgrade to 2024.3.52635 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.3.52635 potential spoofing attack was possible via lack of Punycode encoding

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 versions prior to 2024.3.52635, the lack of proper Punycode encoding on internationalized domain names could allow attackers to craft visually similar domain names (homograph attacks) to spoof legitimate resources, potentially tricking users into trusting malicious links or content.

MitigationUpgrade YouTrack to version 2024.3.52635 or later which includes proper Punycode encoding implementation.

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

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 location
    Locate the YouTrack installation directory - common paths include /opt/youtrack, /usr/local/youtrack, or C:\Program Files\JetBrains\YouTrack on Windows. Check for the youtrack.jar or youtrack startup scripts.
    Affected if YouTrack is not installed on the system
  2. Determine installed YouTrack version
    Open the YouTrack web interface and navigate to Administration > About, or access /api/version endpoint. Alternatively, check the version.txt file in the YouTrack installation directory, or run: java -jar youtrack.jar --version
    Affected if Unable to retrieve version information
  3. Compare version against fixed release
    Check if the installed version is 2024.3.52635 or later. The affected version range is any build prior to 2024.3.52635.
    Affected if Installed version is less than 2024.3.52635 (for example, 2024.2.x, 2024.1.x, or earlier)
  4. Verify YouTrack service is running
    Confirm the YouTrack service is actively running. On Linux: systemctl status youtrack or ps aux | grep youtrack. On Windows: check services.msc for YouTrack service.
    Affected if YouTrack service is not running (not vulnerable when not in use)

A system is affected if YouTrack is installed and running a version prior to 2024.3.52635, as these versions lack proper Punycode encoding for internationalized domain names.

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.52635 or later
Fixed in 2024.3.52635
Interim mitigation

Upgrade YouTrack to version 2024.3.52635 or later which includes proper Punycode encoding implementation.

Recommended fix High confidence

YouTrack 2024.3.52635

  1. 1. Back up your YouTrack database and configuration files before starting the upgrade
  2. 2. Download the fixed YouTrack version (2024.3.52635 or later) from the official JetBrains website (www.jetbrains.com/youtrack/download)
  3. 3. Stop the YouTrack service to ensure no active connections during upgrade
  4. 4. Install or extract the new YouTrack version to your deployment directory
  5. 5. Start the YouTrack service and verify the upgrade completed successfully
  6. 6. Confirm the version number in YouTrack Administration > System > About shows version 2024.3.52635 or later
  7. 7. Test that the application is functioning normally including user authentication and project access
Caveat Review JetBrains upgrade notes for potential configuration or migration considerations; standard upgrades typically preserve data

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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