Skip to main content
No exploitation reportedFix available

CVE-2017-18096

No exploitation reported by the sources we read.

  • Published2018-04-04
  • Fixed in5.4.3 · 5.3.4 · 5.2.7
  • WeaknessCWE-918

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

The OAuth status rest resource in Atlassian Application Links before version 5.2.7, from 5.3.0 before 5.3.4 and from 5.4.0 before 5.4.3 allows remote attackers with administrative rights to access the content of internal network resources via a Server Side Request Forgery (SSRF) by creating an OAuth application link to a location they control and then redirecting access from the linked location's OAuth status rest resource to an internal location. When running in an environment like Amazon EC2, this flaw maybe used to access to a metadata resource that provides access credentials and other potentially confidential information.

Timeline

dates in UTC
  1. 2018-04-0412:29CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2017-18096?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-18096?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Atlassian application links
BranchAffectedFixed in
5.4≥ 5.4.0, < 5.4.35.4.3
5.3≥ 5.3.0, < 5.3.45.3.4
5.2< 5.2.75.2.7

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

  1. Update Atlassian application links to 5.4.3 · 5.3.4 · 5.2.7

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • NVDCVSS 3.07.2read 2026-10-23
  • NVDCVSS 2.04read 2026-10-23
  • NVDweakness (CWE)CWE-918read 2026-10-23
  • FIRST EPSSEPSS score1.2 %2026-10-23

Technical details

CVSS v3 Vector
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Published
2018-04-04
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2017-18096?

The OAuth status rest resource in Atlassian Application Links before version 5.2.7, from 5.3.0 before 5.3.4 and from 5.4.0 before 5.4.3 allows remote attackers with administrative rights to access the content of internal network resources via a Server Side Request Forgery (SSRF) by creating an OAuth application link to a location they control and then redirecting access from the linked location's OAuth status rest resource to an internal location. When running in an environment like Amazon EC2, this flaw maybe used to access to a metadata resource that provides access credentials and other potentially confidential information.

Is CVE-2017-18096 actively exploited?

Active exploitation of CVE-2017-18096 has not been confirmed. Its EPSS score was 1.2% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2017-18096?

CVE-2017-18096 has a CVSS v3 base score of 7.2 (HIGH severity), with vector string CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month