CVE-2021-45074
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 · uneditedJFrog Artifactory before 7.29.3 and 6.23.38, is vulnerable to Broken Access Control, a low-privileged user is able to delete other known users OAuth token, which will force a reauthentication on an active session or in the next UI session.
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 confidenceJFrog Artifactory versions before 7.29.3 and 6.23.38 contain a Broken Access Control vulnerability (IDOR) where a low-privileged user can delete OAuth tokens belonging to other known users. This allows the attacker to force reauthentication on active or subsequent UI sessions, potentially disrupting legitimate user workflows and causing denial of authenticated 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>= 6.0.0, < 6.23.38>= 7.0.0, < 7.29.3CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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.
-
Determine installed Artifactory versionAccess the Artifactory UI as an administrator and navigate to the 'About' or 'System Info' page, or execute: curl -u admin:password http://<artifactory-host>/artifactory/api/system/versionAffected if The version is >= 6.0.0 and < 6.23.38, OR >= 7.0.0 and < 7.29.3
-
Verify OAuth provider configurationNavigate to Administration > Identity and Access > OAuth in the Artifactory UI, or check the system configuration for enabled OAuth providersAffected if OAuth is enabled and configured with at least one identity provider
-
Check for low-privileged usersNavigate to Administration > Identity and Access > Users in the Artifactory UI, or query the users API endpoint to identify accounts with non-admin rolesAffected if There are user accounts with limited permissions (non-admin) present in the system
-
Review audit logs for token deletion eventsNavigate to Administration > Audit Logs in the Artifactory UI, or query the audit API for events involving OAuth token deletion by low-privilege usersAffected if Audit logs show token deletion events performed by users who should not have permission to modify other users' tokens
You are affected if your Artifactory version falls within the vulnerable ranges (6.0.0-6.23.37 or 7.0.0-7.29.2), OAuth is enabled, and low-privileged users exist who could potentially delete other users' OAuth tokens.
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 · scoped6.23.387.29.3
Upgrade JFrog Artifactory to version 7.29.3, 6.23.38, or later to patch the broken access control vulnerability. Verify OAuth functionality after upgrade.
Upgrade to Artifactory 6.23.38 or 7.29.3 (or later stable releases)
- Back up your current Artifactory installation and database
- Download the fixed version (6.23.38 for 6.x branch or 7.29.3 for 7.x branch) from the official JFrog distribution
- Review JFrog's official upgrade documentation for your specific version path
- Execute the upgrade following vendor best practices and release notes
- Verify the upgrade was successful and test that OAuth token functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.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,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-45074 — 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-45074 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