CVSS 3.0
6.1 mediumCVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NMedium (6.1) in atlassian oauth. EPSS 76% estimated probability of exploitation activity in the next 30 days.
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NExplain CVE-2017-9506 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2017-9506?via=ask-ai-copy and https://cve.bz/cve/CVE-2017-9506?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-9506 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:oauth | 1.3.0 |
| atlassian:oauth | 1.3.1 |
| atlassian:oauth | 1.3.2 |
| atlassian:oauth | 1.3.3 |
| atlassian:oauth | 1.3.4 |
| atlassian:oauth | 1.3.5 |
| atlassian:oauth | 1.3.6 |
| atlassian:oauth | 1.3.7 |
| atlassian:oauth | 1.3.8 |
| atlassian:oauth | 1.3.9 |
| atlassian:oauth | 1.3.10 |
| atlassian:oauth | 1.4.0 |
| atlassian:oauth | 1.4.0:m1 |
| atlassian:oauth | 1.4.0:m2 |
| atlassian:oauth | 1.4.1 |
| atlassian:oauth | 1.5.0 |
| atlassian:oauth | 1.5.0:m1 |
| atlassian:oauth | 1.5.0:m3 |
| atlassian:oauth | 1.6.0 |
| atlassian:oauth | 1.6.0:m1 |
| atlassian:oauth | 1.6.0:m4 |
| atlassian:oauth | 1.6.1 |
| atlassian:oauth | 1.7.0 |
| atlassian:oauth | 1.8.0 |
| atlassian:oauth | 1.8.0:m1 |
| atlassian:oauth | 1.8.1 |
| atlassian:oauth | 1.8.2 |
| atlassian:oauth | 1.8.3 |
| atlassian:oauth | 1.8.4 |
| atlassian:oauth | 1.8.5 |
| atlassian:oauth | 1.9.0 |
| atlassian:oauth | 1.9.0:m1 |
| atlassian:oauth | 1.9.0:m2 |
| atlassian:oauth | 1.9.1 |
| atlassian:oauth | 1.9.2 |
| atlassian:oauth | 1.9.3 |
| atlassian:oauth | 1.9.4 |
| atlassian:oauth | 1.9.5 |
| atlassian:oauth | 1.9.6 |
| atlassian:oauth | 1.9.7 |
| atlassian:oauth | 1.9.8 |
| atlassian:oauth | 1.9.9 |
| atlassian:oauth | 1.9.10 |
| atlassian:oauth | 1.9.11 |
| atlassian:oauth | 2.0.0 |
| atlassian:oauth | 2.0.1 |
| atlassian:oauth | 2.0.2 |
| atlassian:oauth | 2.0.3 |
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.