CVE-2019-20899

The Gadget API in Atlassian Jira Server and Data Center in affected versions allows remote attackers to make Jira unresponsive via repeated requests to a certain endpoint in the Gadget API. The affected versions are before version 8.5.4, and from version 8.6.0 before 8.6.1.

Published: 2020-07-12 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2019-20899 is rated Moderate Risk (50.7/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 2.14%). EPSS rose +1.65% over the last day, indicating growing attacker interest. Review affected assets and schedule 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-20899

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-06-15 0.48% 2.14% +1.65%
2 2025-12-22 0.74% 0.48% -0.26%
3 2025-11-21 — 0.74% —

Full EPSS history (16 records total)

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

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:N/I:N/A:L 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:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 3.9 1.4 [email protected]
5.0 2.0 MEDIUM
AV:N/AC:L/Au:N/C:N/I:N/A:P 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:N)
No confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:P)
Partial availability impact.
 10.0 2.9 [email protected]

Weakness enumeration for CVE-2019-20899

Affected software / configurations for CVE-2019-20899

Vendor Product Version Raw CPE
atlassian jira < 8.5.4 cpe:2.3:a:atlassian:jira:*:*:*:*:*:*:*:*
atlassian jira_data_center >= 8.5.5, < 8.6.1 cpe:2.3:a:atlassian:jira_data_center:*:*:*:*:*:*:*:*
atlassian jira_data_center >= 8.6.2, < 8.7.0 cpe:2.3:a:atlassian:jira_data_center:*:*:*:*:*:*:*:*
atlassian jira_server >= 8.5.5, < 8.6.1 cpe:2.3:a:atlassian:jira_server:*:*:*:*:*:*:*:*
atlassian jira_server >= 8.6.2, < 8.7.0 cpe:2.3:a:atlassian:jira_server:*:*:*:*:*:*:*:*
atlassian jira_software_data_center < 8.5.4 cpe:2.3:a:atlassian:jira_software_data_center:*:*:*:*:*:*:*:*

References for CVE-2019-20899

cvelogic Threat Intelligence