JiraApplication · Atlassian
CVE-2019-3401
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 ManageFilters.jspa resource in Jira before version 7.13.3 and from version 8.0.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 ManageFilters.jspa resource in Atlassian Jira versions before 7.13.3 and 8.0.0 before 8.1.1 contains an incorrect authorization check that allows remote attackers to enumerate valid usernames by sending requests to the filter management endpoint and analyzing differential responses.
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.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.
-
Check Jira versionNavigate to the Jira administration about page (typically /secure/About.jspa) or access it via the gear icon > Apps > Manage apps > Jira info. Locate the version number displayed.Affected if The installed version is lower than 7.13.3, OR the installed version is 8.0.0 through 8.1.0 (inclusive).
-
Confirm ManageFilters.jspa endpoint existsAttempt to access the URL pattern /secure/ManageFilters.jspa on your Jira server (e.g., https://yourjira.example.com/secure/ManageFilters.jspa). Note that this endpoint was present in vulnerable versions.Affected if The endpoint returns a valid response (whether login prompt, error, or filter management page) rather than a 404. A 404 indicates the endpoint may have been removed or the version is patched.
-
Verify filter management permissionsAs a non-administrator user (or an authenticated user without Admin permission), log into Jira and attempt to navigate to the filter management page or send a crafted request to /secure/ManageFilters.jspa. Observe whether the application returns different responses for valid versus invalid usernames in filter ownership fields.Affected if The application allows enumeration by returning distinct responses when different usernames are referenced in filter management operations, allowing an attacker to confirm valid user accounts.
You are affected if your Jira version is below 7.13.3 or falls between 8.0.0 and 8.1.0 inclusive, AND the ManageFilters.jspa endpoint is accessible to authenticated users, allowing differential responses that reveal valid 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.38.1.1
Upgrade Jira to version 7.13.3, 8.1.1, or later to receive the patched authorization checks for the ManageFilters.jspa resource.
Fix this in Jira
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3401 — 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-3401 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