dbcve.org
YoutrackApplication · Jetbrains

CVE-2022-28649

MEDIUM · 5.4 CVSS v3.1 Published 2022-04-05
Fix available
A fix is available. Upgrade to 2022.1.43563 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 2022.1.43563 it was possible to include an iframe from a third-party domain in the issue description

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

YouTrack before version 2022.1.43563 does not properly sanitize the issue description field, allowing injection of iframe elements from third-party domains. This could enable phishing attacks, clickjacking, or malicious content embedding.

MitigationUpgrade YouTrack to version 2022.1.43563 or later. Prior to upgrade, perform a full backup and test in a staging environment to ensure compatibility with existing workflows.

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

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 the installed YouTrack version
    Log into the YouTrack administration console and navigate to the About section, or check the version displayed in the footer of the YouTrack interface. You can also check the version via the administrative API endpoint or the version.json file in the installation directory if self-hosted.
    Affected if The installed version is lower than 2022.1.43563
  2. Verify access to issue creation and editing
    Confirm that users or groups in your YouTrack instance have permissions to create new issues or edit existing ones. Check the user roles and permissions in the Administration > Users section and verify which roles include the 'Create issues' or 'Edit issues' permissions.
    Affected if Users have permission to create or edit issues and the YouTrack version is below 2022.1.43563
  3. Inspect existing issue descriptions for iframe content
    Use the YouTrack search functionality or database query to scan existing issue descriptions for iframe tags. You can search using a command like 'description: {iframe' or access the database directly if you have administrative database access to examine the issue description fields.
    Affected if Any issues contain iframe tags in their description fields, indicating potential exploitation or misconfiguration
  4. Review custom field configurations
    Navigate to Administration > Custom fields and review any custom fields that store text or description-like content. Check if any custom fields are configured to render HTML or allow rich text that could include iframe elements.
    Affected if Custom fields with rich text or HTML rendering are enabled for issue-related content and the YouTrack version is below 2022.1.43563
  5. Check for third-party integrations handling issue content
    Review any installed plugins, webhooks, or integrations that process or display issue descriptions. Examine the plugin list in Administration > Plugins and review any custom workflows or automation rules that may handle issue description data.
    Affected if Third-party integrations or workflows process issue description content and the YouTrack version is below 2022.1.43563

You are affected if your YouTrack installation is version 2022.1.43563 or lower and users have permissions to create or edit issue descriptions.

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

Upgrade YouTrack to version 2022.1.43563 or later. Prior to upgrade, perform a full backup and test in a staging environment to ensure compatibility with existing workflows.

Recommended fix High confidence

2022.1.43563 or later

  1. Upgrade YouTrack to version 2022.1.43563 or later

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 / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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