YoutrackApplication · Jetbrains

CVE-2024-54156

MEDIUM · 6.5 CVSS v3.1 Published 2024-12-04
Fix available
A fix is available. Upgrade to 2024.3.52635 or later.
See remediation →
74/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 multiple merge functions were vulnerable to prototype pollution attack

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

Multiple merge functions in JetBrains YouTrack before version 2024.3.52635 are vulnerable to prototype pollution attacks. This JavaScript vulnerability allows attackers to modify Object.prototype properties by manipulating input to merge operations, potentially leading to privilege escalation or unexpected application behavior.

MitigationUpgrade YouTrack to version 2024.3.52635 or later to patch the vulnerable merge functions.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Check YouTrack version
    Navigate to Administration > Diagnostics > About in the YouTrack UI, or inspect the build number in the installation directory (youtrack.jar or changelog.xml). Compare the version to 2024.3.52635.
    Affected if Installed version is below 2024.3.52635 (e.g., 2024.3.12345 or earlier)
  2. Identify custom plugins using merge operations
    Review any custom plugins, scripts, or integrations in the /plugins or /scripts directories. Look for code that uses JavaScript Object.assign, $.extend, or custom merge functions handling user-controlled input.
    Affected if Custom plugins or scripts contain merge logic that processes external input without sanitizing object keys
  3. Check for exposed API endpoints accepting merge payloads
    Review REST API documentation or network traffic for endpoints that accept JSON objects and pass them to merge operations. Use browser developer tools or server logs to identify POST/PUT requests with nested object parameters.
    Affected if API endpoints accept JSON payloads containing __proto__, constructor, or other object properties that could be merged into Object.prototype
  4. Inspect server-side request handling
    Examine YouTrack server logs and request traces for any merge-related operations. Look for patterns like 'merge', 'Object.assign', or deep merge utility calls in request handlers.
    Affected if Server logs show merge operations processing requests with potentially malicious object keys

A YouTrack installation is affected if its version is below 2024.3.52635 and it processes external input through merge operations, either via custom plugins, API endpoints, or integrated systems.

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 to patch the vulnerable merge functions.

Recommended fix High confidence

2024.3.52635 or later

  1. Upgrade YouTrack to version 2024.3.52635 or later
  2. Verify the upgrade by checking the YouTrack version in Administration > Application section
  3. Review the YouTrack 2024.3 release notes for any configuration or migration requirements
Caveat Review YouTrack 2024.3 release notes for potential breaking changes before upgrading

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

Fix this in Youtrack Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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