dbcve.org
YoutrackApplication · Jetbrains

CVE-2022-24442

CRITICAL · 9.8 CVSS v3.1 Published 2022-02-25
Fix available
A fix is available. Upgrade to 2021.4.40426 or later.
See remediation →
100/100
Remediation priority · Urgent
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
JetBrains YouTrack before 2021.4.40426 was vulnerable to SSTI (Server-Side Template Injection) via FreeMarker templates.

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 · high confidence

JetBrains YouTrack before version 2021.4.40426 contains a Server-Side Template Injection (SSTI) vulnerability in its FreeMarker templating engine. This allows remote attackers to inject malicious FreeMarker template expressions, potentially achieving arbitrary code execution on the server.

MitigationUpgrade YouTrack to version 2021.4.40426 or later to apply the vendor patch. If immediate upgrade is not possible, restrict network access to the YouTrack instance as an interim measure.

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:< 2021.4.40426

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 area and navigate to 'About' or check the build number in the installation directory. On Linux, you can also run: sudo systemctl status youtrack or check the logs in /opt/youtrack/logs for the build version string.
    Affected if The installed version number is less than 2021.4.40426
  2. Locate the YouTrack installation directory
    Common locations include /opt/youtrack on Linux, C:\Program Files\YouTrack on Windows, or check the service configuration for the path. Look for a 'versions.json' file or the main JAR file containing the build number.
    Affected if Unable to locate a version equal to or greater than 2021.4.40426 in the installation
  3. Check for custom FreeMarker templates
    Navigate to Administration > Templates in the YouTrack web interface. Review any user-created or imported templates. Also check the <youtrack_install>/conf or <youtrack_install>/data/templates directories for custom .ftl template files.
    Affected if Custom FreeMarker templates exist that could be exploited to inject malicious expressions
  4. Verify network exposure
    Review firewall rules, reverse proxy configurations, and YouTrack's internal 'baseUrl' setting. Check if the YouTrack port (default 8080 or 443) is accessible from untrusted networks.
    Affected if The YouTrack instance is directly exposed to the internet or untrusted internal networks without authentication barriers

You are affected if your installed YouTrack version is below 2021.4.40426 and the server is network-accessible to potential attackers.

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 2021.4.40426 or later
Fixed in 2021.4.40426
Interim mitigation

Upgrade YouTrack to version 2021.4.40426 or later to apply the vendor patch. If immediate upgrade is not possible, restrict network access to the YouTrack instance as an interim measure.

Recommended fix High confidence

YouTrack 2021.4.40426 or later

  1. Backup your YouTrack database and configuration files before starting the upgrade
  2. Download YouTrack version 2021.4.40426 or later from the official JetBrains website
  3. Stop the YouTrack service
  4. Run the YouTrack installer or deploy the new version
  5. Start the YouTrack service and verify it's running correctly
  6. Test that YouTrack is accessible and functioning normally
Caveat Review JetBrains release notes for any configuration or feature changes between your current version and 2021.4.40426

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

Fix this in Youtrack Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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