JiraApplication · Atlassian
CVE-2019-3399
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 BrowseProjects.jspa resource in Jira before version 7.13.2, and from version 8.0.0 before version 8.0.2 allows remote attackers to see information for archived projects through a missing 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 confidenceThis is an information disclosure vulnerability in Atlassian Jira. The BrowseProjects.jspa resource lacks proper authorization checks, allowing unauthenticated remote attackers to view information about archived projects they should not have access to. The vulnerability affects Jira versions before 7.13.2 and from 8.0.0 before 8.0.2.
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.2
Jira ServerApplication
>= 8.0.0, < 8.0.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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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.
-
Determine installed Jira versionAccess the Jira administration panel and navigate to Jira settings > Troubleshooting and support > System info, or check the <jira-install>/atlassian-jira/WEB-INF/classes/com/atlassian/jira/version.properties file for the jira.version propertyAffected if The installed version is less than 7.13.2, or greater than or equal to 8.0.0 but less than 8.0.2
-
Verify Jira web application is accessibleConfirm the Jira web interface is reachable at the base URL and the BrowseProjects.jspa endpoint responds (e.g., https://your-jira-host/browse/projects.jspa)Affected if The Jira web application is exposed and responds to requests
-
Check for archived projectsAs an administrator, navigate to Jira administration > Projects > View all projects, or query the database table 'project' for records where 'archived' = trueAffected if There are archived projects configured in the Jira instance
The environment is affected if Jira version is below 7.13.2 or between 8.0.0 and 8.0.2 (inclusive), and the Jira web interface is accessible with archived projects present.
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.28.0.2
Update Jira to version 7.13.2 or later, or version 8.0.2 or later to apply the vendor patch. As this is a server-side web application vulnerability affecting a well-defined component, the fix is a straightforward version upgrade.
Fix this in Jira
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing4.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,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3399 — 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-3399 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