CVE-2021-43187
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, the client-side cache on iOS could contain sensitive information.
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 confidenceThe iOS version of JetBrains YouTrack Mobile prior to 2021.2 stored sensitive information in the client-side cache. This could expose credentials, authentication tokens, or other confidential data to anyone with access to the device's cached files, potentially leading to unauthorized account access.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify YouTrack Mobile iOS is installedCheck your iOS device for the YouTrack Mobile app icon in the home screen, App Library, or in the list of installed apps in the App Store.Affected if The YouTrack Mobile app is present on the iOS device
-
Locate the YouTrack Mobile version numberOpen the App Store app, tap your profile icon at the top right, scroll to 'Purchased' and find YouTrack Mobile, or open the YouTrack Mobile app and navigate to Settings > About to view the version.Affected if You are able to retrieve a version number for the app
-
Compare installed version to 2021.2Take the version number shown (for example, 2021.1.2 or 2021.1) and compare it numerically to version 2021.2.Affected if The installed version is a lower number than 2021.2 (such as 2021.1.x, 2020.x, or any version prior to the 2021.2 release)
If YouTrack Mobile iOS is installed and the version is below 2021.2, the app stores sensitive data in an insecure cache and the environment is affected.
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
Upgrade YouTrack Mobile iOS clients to version 2021.2 or later to ensure sensitive data is no longer persisted in the cache, or implement additional encryption/wiping of cache data on the client side.
2021.2
- Open the App Store on your iOS device
- Search for YouTrack Mobile
- Tap Update to install version 2021.2 or later
- Alternatively, navigate to blog.jetbrains.com for official YouTrack Mobile release notes and update instructions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-43187 — 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-43187 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