dbcve.org
Data CenterApplication · Atlassian

CVE-2021-39125

MEDIUM · 5.3 CVSS v3.1 Published 2021-09-14
Fix available
A fix is available. Upgrade to 8.5.10 / 8.13.1 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
Affected versions of Atlassian Jira Server and Data Center allow anonymous remote attackers to discover the usernames of users via an enumeration vulnerability in the password reset page. The affected versions are before version 8.5.10, and from version 8.6.0 before 8.13.1.

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 confidence

Affected versions of Atlassian Jira Server and Data Center contain an enumeration vulnerability in the password reset functionality that allows anonymous remote attackers to discover valid usernames by observing different responses from the password reset page.

MitigationUpgrade Jira Server and Data Center to version 8.5.10, 8.13.1, or later. As an interim measure, consider implementing rate limiting or CAPTCHA on the password reset endpoint.

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
Data CenterApplication
Affected:< 8.5.10>= 8.6.0, < 8.13.1
JiraApplication
Affected:< 8.5.10
Jira ServerApplication
Affected:>= 8.6.0, < 8.13.1

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Jira installation version
    Access the Jira About page (typically at /secure/About.jspa) or check the installation directory for version files. In the UI: Jira settings > Applications > About Jira shows the version number.
    Affected if The installed version falls within the affected ranges: < 8.5.10, or >= 8.6.0 and < 8.13.1.
  2. Confirm password reset feature is enabled
    Check the Jira administration settings at Jira settings > Security > Password Policy. Ensure 'Forgot your password?' functionality is available to anonymous users on the login page.
    Affected if The password reset feature is accessible to unauthenticated users (this is the default configuration).
  3. Verify if custom user enumeration protections exist
    Review any web application firewall (WAF) rules, rate limiting, or CAPTCHA implementation in front of the /ForgotPassword.jspa endpoint.
    Affected if No rate limiting, CAPTCHA, or enumeration protection is configured on the password reset endpoint.
  4. Check Jira Data Center cluster configuration
    If using Data Center, verify the version across all cluster nodes by checking each node's About page or the support diagnostics.
    Affected if Any node in the cluster runs an affected version.

Your Jira instance is affected if it is version < 8.5.10 or >= 8.6.0 and < 8.13.1 AND the password reset page is accessible to anonymous users (default state).

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 8.5.10 / 8.13.1 or later
Fixed in 8.5.108.13.1
Interim mitigation

Upgrade Jira Server and Data Center to version 8.5.10, 8.13.1, or later. As an interim measure, consider implementing rate limiting or CAPTCHA on the password reset endpoint.

Recommended fix High confidence

8.13.1 or later (or 8.5.10 if staying on earlier LTS branch)

  1. Backup your Jira database and configuration files before proceeding
  2. Review Atlassian upgrade documentation for Jira 8.x to check for any specific migration requirements or known issues
  3. Test the upgrade in a staging or development environment first
  4. Download and install Jira version 8.13.1 or later (recommended: latest 8.x LTS or current version)
  5. After upgrade, verify the password reset functionality works correctly and the enumeration vulnerability is fixed
  6. Confirm anonymous users can no longer enumerate valid usernames through the password reset page
Caveat Standard Jira upgrade considerations apply - review Atlassian upgrade guide for database compatibility, plugin/app compatibility, and any required migration steps

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

Fix this in Data Center Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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