cve.bz

CVE-2017-9506 atlassian oauth: SSRF

6.1 mediumExploit referenceEPSS 76%

Medium (6.1) in atlassian oauth. EPSS 76% estimated probability of exploitation activity in the next 30 days.

On this page
The IconUriServlet of the Atlassian OAuth Plugin from version 1.3.0 before version 1.9.12 and from version 2.0.0 before version 2.0.4 allows remote attackers to access the content of internal network resources and/or perform an XSS attack via Server Side Request Forgery (SSRF).

Severity

CVSS 3.0

6.1 medium
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
EPSS
76% (unchanged from 76% a week ago; 72% 30 days ago) estimated probability of exploitation activity in the next 30 days; 100th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2024-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain 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.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
atlassian:oauth1.3.0
atlassian:oauth1.3.1
atlassian:oauth1.3.2
atlassian:oauth1.3.3
atlassian:oauth1.3.4
atlassian:oauth1.3.5
atlassian:oauth1.3.6
atlassian:oauth1.3.7
atlassian:oauth1.3.8
atlassian:oauth1.3.9
atlassian:oauth1.3.10
atlassian:oauth1.4.0
atlassian:oauth1.4.0:m1
atlassian:oauth1.4.0:m2
atlassian:oauth1.4.1
atlassian:oauth1.5.0
atlassian:oauth1.5.0:m1
atlassian:oauth1.5.0:m3
atlassian:oauth1.6.0
atlassian:oauth1.6.0:m1
atlassian:oauth1.6.0:m4
atlassian:oauth1.6.1
atlassian:oauth1.7.0
atlassian:oauth1.8.0
atlassian:oauth1.8.0:m1
atlassian:oauth1.8.1
atlassian:oauth1.8.2
atlassian:oauth1.8.3
atlassian:oauth1.8.4
atlassian:oauth1.8.5
atlassian:oauth1.9.0
atlassian:oauth1.9.0:m1
atlassian:oauth1.9.0:m2
atlassian:oauth1.9.1
atlassian:oauth1.9.2
atlassian:oauth1.9.3
atlassian:oauth1.9.4
atlassian:oauth1.9.5
atlassian:oauth1.9.6
atlassian:oauth1.9.7
atlassian:oauth1.9.8
atlassian:oauth1.9.9
atlassian:oauth1.9.10
atlassian:oauth1.9.11
atlassian:oauth2.0.0
atlassian:oauth2.0.1
atlassian:oauth2.0.2
atlassian:oauth2.0.3

Detection rules

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.

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON