dbcve.org
YoutrackApplication · Jetbrains

CVE-2025-24457

MEDIUM · 5.5 CVSS v3.1 Published 2025-01-21
Fix available
A fix is available. Upgrade to 2024.3.55417 or later.
See remediation →
57/100
Remediation priority · Elevated
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.55417 permanent tokens could be exposed in logs

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.55417, permanent authentication tokens were being written to application logs, allowing anyone with log access to potentially obtain valid credentials and impersonate users.

MitigationUpgrade YouTrack to version 2024.3.55417 or later. Review existing logs for exposed tokens and rotate any potentially compromised permanent tokens.

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

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 the About page, or check the version from the startup logs or installation directory. You can also query the YouTrack API endpoint /api/admin/about or check the {youtrack-installation}/conf/app.properties file.
    Affected if The installed version is earlier than 2024.3.55417 (for example, 2024.2, 2024.1, 2023.x, or earlier)
  2. Locate YouTrack application logs
    Identify the YouTrack data directory and locate the logs folder, typically found at {youtrack-home}/logs/ or within the {youtrack-data}/logs directory. Check main log files such as youtrack.log, console.log, or wrapper.log.
    Affected if Log files exist and were written during any version prior to 2024.3.55417
  3. Search logs for authentication token patterns
    Use a text search utility (grep, Select-String, or a text editor) to search log files for patterns indicating authentication tokens. Look for keywords such as 'token', 'Authorization', 'Bearer', 'X-Token', 'auth', or long alphanumeric strings that resemble API keys or permanent tokens. Also search for 'permanent token', 'saved token', or 'stored credentials'.
    Affected if Log files contain any of these token-related strings, especially in requests, authentication events, or user login entries
  4. Verify token validity if found
    If tokens or credential-like strings are discovered in logs, examine their context. Tokens appearing in URL parameters, HTTP headers within log entries, or associated with user authentication events indicate potential exposure. Cross-reference with YouTrack audit logs if available to determine if these tokens were used for authentication.
    Affected if Readable tokens are present in log entries, especially in contexts indicating they were used for user authentication or API access

A user is affected if their YouTrack installation is version 2024.3.55417 or earlier AND application logs contain visible authentication tokens or credential strings that could be extracted and reused.

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.55417 or later
Fixed in 2024.3.55417
Interim mitigation

Upgrade YouTrack to version 2024.3.55417 or later. Review existing logs for exposed tokens and rotate any potentially compromised permanent tokens.

Recommended fix High confidence

2024.3.55417

  1. Backup your YouTrack database and configuration before starting the upgrade
  2. Download YouTrack version 2024.3.55417 or later from the official JetBrains website (youtrack.jetbrains.com)
  3. Stop the currently running YouTrack service
  4. Install the new YouTrack version following the JetBrains upgrade documentation
  5. Start the YouTrack service after installation completes
  6. Verify that permanent tokens are no longer exposed in logs and that the system functions normally

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

Fix this in Youtrack Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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