dbcve.org
Youtrack MobileApplication · Jetbrains

CVE-2021-43192

MEDIUM · 5.3 CVSS v3.1 Published 2021-11-09
Fix available
A fix is available. Upgrade to 2021.2 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 Mobile before 2021.2, iOS URL scheme hijacking is possible.

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 Mobile iOS versions prior to 2021.2, the application's custom URL scheme (youtrack://) can be hijacked due to improper validation of incoming URLs. This could allow a malicious application on the same iOS device to intercept or manipulate URL-based operations intended for YouTrack.

MitigationUpdate the YouTrack Mobile iOS application to version 2021.2 or later to obtain the patched version that properly handles URL scheme validation.

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
Youtrack MobileApplication
Affected:< 2021.2

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. Verify YouTrack Mobile iOS is installed
    Open the iOS device settings, navigate to 'General' > 'iPhone Storage' (or 'Storage'), scroll to find YouTrack Mobile in the app list, or check the App Library/Home Screen for the YouTrack icon.
    Affected if The app is present on the device and the following version check applies.
  2. Identify the installed YouTrack Mobile iOS version
    On the iOS device, tap and hold the YouTrack Mobile app icon, select 'App Info' or go to Settings > General > iPhone Storage > YouTrack Mobile. Record the version number displayed (e.g., shown as '2021.1.3' or similar).
    Affected if Version number cannot be determined, assume affected.
  3. Compare version against the affected range
    Compare the identified version to the threshold: versions below 2021.2 are affected. The format typically shows as year.version (e.g., 2021.1.x, 2020.3.x). Any version where the year is 2021 and the second number is less than 2, or any version prior to 2021, is in the affected range.
    Affected if The installed version is less than 2021.2 (for example, 2021.1, 2021.0, 2020.x, etc.).
  4. Confirm URL scheme usage (context check)
    Determine if YouTrack Mobile is configured to handle URL-based operations. Check if integrations, deep links, or workflow automations are set up that use the youtrack:// URL scheme. This can be verified in YouTrack settings under 'Administration' > 'System' > 'IDEs and Tools' or by reviewing any saved URL shortcuts.
    Affected if The youtrack:// URL scheme is actively used or configured for integrations, and the version is below 2021.2.

A user is affected if YouTrack Mobile iOS version is installed and is less than 2021.2, regardless of whether the youtrack:// URL scheme is actively used.

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.2 or later
Fixed in 2021.2
Interim mitigation

Update the YouTrack Mobile iOS application to version 2021.2 or later to obtain the patched version that properly handles URL scheme validation.

Recommended fix Moderate confidence

2021.2

  1. Upgrade JetBrains YouTrack Mobile to version 2021.2 or later to resolve the iOS URL scheme hijacking vulnerability
  2. Verify the upgrade by checking the app version in the iOS App Store or within the application's about/settings section
  3. After upgrading, test any custom URL scheme integrations (if used) to ensure they function correctly

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

Fix this in Youtrack Mobile Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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