CVSS 3.0
9.8 criticalCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCritical (9.8) in atlassian jira. EPSS 16% estimated probability of exploitation activity in the next 30 days.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExplain CVE-2017-5983 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2017-5983?via=ask-ai-copy and https://cve.bz/cve/CVE-2017-5983?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2017-5983 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| atlassian:jira | 4.2.4 |
| atlassian:jira | 4.3 |
| atlassian:jira | 4.3.1 |
| atlassian:jira | 4.3.2 |
| atlassian:jira | 4.3.3 |
| atlassian:jira | 4.3.4 |
| atlassian:jira | 4.4 |
| atlassian:jira | 4.4.1 |
| atlassian:jira | 4.4.2 |
| atlassian:jira | 4.4.3 |
| atlassian:jira | 4.4.4 |
| atlassian:jira | 4.4.5 |
| atlassian:jira | 5.0 |
| atlassian:jira | 5.0.1 |
| atlassian:jira | 5.0.2 |
| atlassian:jira | 5.0.3 |
| atlassian:jira | 5.0.4 |
| atlassian:jira | 5.0.5 |
| atlassian:jira | 5.0.7 |
| atlassian:jira | 5.1 |
| atlassian:jira | 5.1.1 |
| atlassian:jira | 5.1.2 |
| atlassian:jira | 5.1.3 |
| atlassian:jira | 5.1.4 |
| atlassian:jira | 5.1.5 |
| atlassian:jira | 5.1.6 |
| atlassian:jira | 5.1.7 |
| atlassian:jira | 5.1.8 |
| atlassian:jira | 5.2 |
| atlassian:jira | 5.2.1 |
| atlassian:jira | 5.2.2 |
| atlassian:jira | 5.2.3 |
| atlassian:jira | 5.2.4 |
| atlassian:jira | 5.2.5 |
| atlassian:jira | 5.2.6 |
| atlassian:jira | 5.2.7 |
| atlassian:jira | 5.2.8 |
| atlassian:jira | 5.2.9 |
| atlassian:jira | 5.2.10 |
| atlassian:jira | 5.2.11 |
| atlassian:jira | 6.0 |
| atlassian:jira | 6.0.1 |
| atlassian:jira | 6.0.2 |
| atlassian:jira | 6.0.3 |
| atlassian:jira | 6.0.4 |
| atlassian:jira | 6.0.5 |
| atlassian:jira | 6.0.7 |
| atlassian:jira | 6.0.8 |
| atlassian:jira | 6.1 |
| atlassian:jira | 6.1.1 |
| atlassian:jira | 6.1.2 |
| atlassian:jira | 6.1.3 |
| atlassian:jira | 6.1.4 |
| atlassian:jira | 6.1.5 |
| atlassian:jira | 6.1.6 |
| atlassian:jira | 6.1.7 |
| atlassian:jira | 6.1.8 |
| atlassian:jira | 6.1.9 |
| atlassian:jira | 6.2 |
| atlassian:jira | 6.2.1 |
| atlassian:jira | 6.2.2 |
| atlassian:jira | 6.2.3 |
| atlassian:jira | 6.2.4 |
| atlassian:jira | 6.2.5 |
| atlassian:jira | 6.2.6 |
| atlassian:jira | 6.2.7 |
Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.