Jira ServerApplication · Atlassian
CVE-2019-8448
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 login.jsp resource in Jira before version 7.13.4, and from version 8.0.0 before version 8.2.2 allows remote attackers to enumerate usernames via an information disclosure vulnerability.
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 login.jsp resource in Atlassian Jira versions before 7.13.4 and 8.0.0 before 8.2.2 contains an information disclosure vulnerability that allows remote unauthenticated attackers to enumerate valid usernames by observing differences in application responses when submitting login requests with existing versus non-existing usernames.
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
Jira ServerApplication
>= 7.11.0, < 7.13.4>= 8.0.0, < 8.2.2CVSS 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.0/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 Server versionAccess the Jira administration console or check the <jira-install>/atlassian-jira/WEB-INF/classes/jira-config.properties file, or run 'java -jar atlassian-jira-core.jar --version' if applicable. The version is typically displayed on the 'About' page under the administration gear icon.Affected if The installed version falls within 7.11.0 to 7.13.3 (inclusive) OR 8.0.0 to 8.2.1 (inclusive)
-
Confirm login.jsp endpoint is accessibleMake an HTTP GET request to <jira-base-url>/login.jsp using a web browser or tool like curl. Verify the page loads and displays a username/password login form.Affected if The login.jsp page is accessible without authentication (no login required)
-
Test for username enumeration via differential responsesSubmit two POST requests to <jira-base-url>/login.jsp with the login form: one with a known-valid username (such as 'admin') and another with a random non-existent username (such as 'nonexistentuser123'). Compare the HTTP response status codes, response times, and any differences in the error messages or page content returned.Affected if The responses differ between the existing and non-existing usernames (for example, different error messages like 'username does not exist' versus 'invalid password', or different response codes or timings)
A user is affected if their Jira Server version is 7.11.0-7.13.3 or 8.0.0-8.2.1 AND the login.jsp endpoint is exposed and exhibits different responses for valid versus invalid usernames.
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.48.2.2
Upgrade Jira to version 7.13.4, 8.2.2, or later to receive the security patch that fixes the username enumeration vector.
Fix this in Jira Server
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-8448 — 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-8448 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