CVE-2021-43189
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 · uneditedIn JetBrains YouTrack Mobile before 2021.2, access token protection on Android is incomplete.
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 confidenceIn JetBrains YouTrack Mobile for Android before version 2021.2, access tokens used for authentication are not adequately protected. This likely means tokens are stored in an insecure manner (e.g., plaintext in shared preferences, unencrypted storage) or handled improperly during the authentication flow, allowing potentially malicious applications on the same device to extract valid session 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< 2021.2CVSS 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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Check YouTrack Mobile Android versionOpen Android Settings > Apps > YouTrack Mobile and view the Version information, or check via Google Play Store app listingAffected if The displayed version is any version prior to 2021.2 (e.g., 2021.1.x, 2021.0.x, etc.)
-
Verify version in app package infoUse ADB command: adb shell dumpsys package jetbrains.youtrack.mobile | grep versionNameAffected if The versionName field shows a version number lower than 2021.2
-
Confirm Android platformEnsure the device is running Android (the CVE specifically affects the Android version of YouTrack Mobile, not iOS)Affected if The YouTrack Mobile Android app is installed and running on any Android version
A user is affected if they have YouTrack Mobile for Android installed with any version lower than 2021.2, as this version range contains the insecure token storage vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2021.2
Update YouTrack Mobile Android app to version 2021.2 or later where the token protection mechanism has been improved. Until then, avoid using YouTrack Mobile on shared or potentially compromised Android devices.
2021.2 or later
- 1. Open the Google Play Store app on your Android device
- 2. Search for "YouTrack Mobile"
- 3. If an update is available, tap "Update" to install version 2021.2 or later
- 4. Alternatively, navigate to the YouTrack Mobile app in Google Play Store and verify the installed version is 2021.2 or newer
- 5. After updating, verify that access tokens are now properly protected on the Android platform
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-43189 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-43189 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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