CVE-2021-30482
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 UpSource before 2020.1.1883, application passwords were not revoked correctly
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 UpSource versions prior to 2020.1.1883, application passwords (used for API and integration access) were not properly invalidated when they should have been revoked. This authentication bypass could allow previously revoked credentials to continue functioning, enabling unauthorized access to the UpSource repository and code review capabilities.
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< 2020.1.1883CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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.
-
Identify UpSource installation and versionLocate the UpSource installation directory and check the version number of the installed instance. Common methods include checking the about page in the UpSource admin interface, viewing installation metadata files, or running version query commands provided by UpSource.Affected if The installed version is any release prior to 2020.1.1883 (for example, 2020.1.1500, 2019.x, or earlier)
-
Confirm application passwords are in useCheck if the UpSource instance has any application passwords configured. Access the administration settings related to authentication or user management and review whether application passwords have been created for API or integration access.Affected if Application passwords exist in the UpSource instance - the vulnerability only affects environments using this feature
-
Review application password audit logsExamine UpSource logs for historical application password creation, use, and revocation events. Look for entries indicating when passwords were supposedly revoked versus when they were last successfully used for authentication.Affected if There is a discrepancy between the recorded revocation time and the most recent authentication activity for any application password, or if logs are missing revocation events entirely
An UpSource instance is affected if it runs a version prior to 2020.1.1883 AND uses application passwords, regardless of whether they have been revoked, because revoked credentials may still be valid.
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.
From vendor data2020.1.1883
Upgrade JetBrains UpSource to version 2020.1.1883 or later. Additionally, audit active application passwords and revoke any that should no longer be valid given the prior vulnerability.
- 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-30482 — 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-30482 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