CVE-2019-3401

The 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.

Published: 2019-05-22 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2019-3401 is rated Moderate Risk (60.7/100): CVSS Medium severity, with high exploitation likelihood (EPSS 65.97%, 98th percentile). EPSS ranks this CVE among the most likely to be exploited in the near term. EPSS rose +19.98% over the last day, indicating growing attacker interest. High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2019-3401

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-04 45.99% 65.97% +19.98%
2 2026-03-01 65.97% 45.99% -19.98%
3 2026-02-04 — 65.97% —

Full EPSS history (43 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-3401

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 1.4 [email protected]
5.0 2.0 MEDIUM
AV:N/AC:L/Au:N/C:P/I:N/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
 10.0 2.9 [email protected]

Weakness enumeration for CVE-2019-3401

Affected software / configurations for CVE-2019-3401

Vendor Product Version Raw CPE
atlassian jira < 7.13.3 cpe:2.3:a:atlassian:jira:*:*:*:*:*:*:*:*
atlassian jira_server >= 8.0.0, < 8.1.1 cpe:2.3:a:atlassian:jira_server:*:*:*:*:*:*:*:*

References for CVE-2019-3401

URL Tags
https://jira.atlassian.com/browse/JRASERVER-69244 Issue Tracking Vendor Advisory
cvelogic Threat Intelligence