dbcve.org
Data CenterApplication · Atlassian

CVE-2021-39118

MEDIUM · 5.3 CVSS v3.1 Published 2021-09-14
Fix available
A fix is available. Upgrade to 8.19.0 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 remote attackers to discover the usernames and full names of users via an enumeration vulnerability in the /rest/api/1.0/render endpoint. The affected versions are before version 8.19.0.

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 /rest/api/1.0/render endpoint that allows unauthenticated remote attackers to discover valid usernames and full names of users. This information disclosure occurs before version 8.19.0.

MitigationUpgrade Jira Server or Data Center to version 8.19.0 or later to remediate this vulnerability.

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.19.0
JiraApplication
Affected:< 8.19.0

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 installed Jira version
    Access the Jira administration console or check the installation banner/footer which typically displays the version. Alternatively, query the /rest/api/2/serverInfo endpoint which returns version information.
    Affected if The installed version is 8.x less than 8.19.0, or the version cannot be determined but is reportedly pre-8.19.0.
  2. Verify Jira is accessible via network
    Confirm that the Jira web interface is reachable over HTTP/HTTPS from the network.
    Affected if Jira is exposed to network access and version is below 8.19.0.
  3. Test user enumeration on the render endpoint
    Send a POST request to /rest/api/1.0/renderauthors with a crafted payload containing a likely username. A 200 response with user data indicates the vulnerability is present.
    Affected if The endpoint responds with valid user information (username or full name) for arbitrary input, confirming the enumeration vulnerability.

A user is affected if their Jira installation version is 8.x below 8.19.0 and the /rest/api/1.0/render endpoint is accessible, allowing unauthenticated enumeration of valid usernames.

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.19.0 or later
Fixed in 8.19.0
Interim mitigation

Upgrade Jira Server or Data Center to version 8.19.0 or later to remediate this vulnerability.

Recommended fix High confidence

8.19.0

  1. 1. Back up your Jira database and installation directory before proceeding
  2. 2. Download Jira Server or Data Center version 8.19.0 from the official Atlassian download center
  3. 3. Stop the Jira application service
  4. 4. Follow Atlassian's upgrade documentation for your deployment type (Server or Data Center)
  5. 5. Run the upgrade installer/console script on the primary node first
  6. 6. If running Data Center, ensure all nodes are upgraded to the same version
  7. 7. Start Jira and verify the application is operational
  8. 8. Validate that the /rest/api/1.0/render endpoint no longer exposes user enumeration
Caveat Review Atlassian Jira 8.19.0 release notes for any known compatibility or migration considerations

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

Fix this in Data Center Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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