JiraApplication · Atlassian
CVE-2019-3403
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 · uneditedThe /rest/api/2/user/picker rest resource in Jira before version 7.13.3, from version 8.0.0 before version 8.0.4, and from version 8.1.0 before version 8.1.1 allows remote attackers to enumerate usernames via an incorrect authorisation check.
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 confidenceThe /rest/api/2/user/picker REST endpoint in Atlassian Jira versions before 7.13.3, 8.0.0-8.0.4, and 8.1.0-8.1.1 contains an incorrect authorization check that allows remote unauthenticated attackers to enumerate valid usernames by querying the user picker resource.
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
JiraApplication
< 7.13.3
Jira ServerApplication
>= 8.0.0, < 8.0.4>= 8.1.0, < 8.1.1CVSS 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.
-
Identify Jira versionCheck the Jira application version by navigating to the Jira administration page, typically at /admin, or by checking the 'About' section in the Jira UI. The version is also often visible in the footer of Jira pages.Affected if The installed version is below 7.13.3, OR between 8.0.0 and 8.0.4 inclusive, OR between 8.1.0 and 8.1.1 inclusive.
-
Verify network exposureConfirm that the Jira web interface is accessible over the network to unauthenticated users. This can be done by accessing the Jira base URL from an unauthenticated browser or using a curl command to the base URL.Affected if Jira is reachable from the network without authentication.
-
Test user picker endpoint accessibilitySend an unauthenticated HTTP GET request to /rest/api/2/user/picker and examine the response. Example: curl -s 'https://jira.example.com/rest/api/2/user/picker?query=test'Affected if The endpoint returns HTTP 200 with a JSON response containing user-related data without requiring authentication.
-
Confirm user enumeration is possibleAnalyze the JSON response from the user picker endpoint. If the response contains a 'users' array with user account details (such as 'key', 'name', 'displayName') when querying arbitrary strings, this indicates the flaw is present.Affected if The response includes valid user information such as user keys, names, or display names without providing credentials.
You are affected if your Jira version falls within the vulnerable ranges AND the /rest/api/2/user/picker endpoint is accessible without authentication and returns user account information.
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 data7.13.38.0.48.1.1
Upgrade Jira to version 7.13.3, 8.0.4, 8.1.1 or later to resolve the improper authorization check in the user picker endpoint.
Fix this in Jira
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3403 — 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-2019-3403 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