LiveActive security incident?Get immediate response
CVE Record

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...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2017-18096 is an SSRF issue in Atlassian Application Links. An attacker who already has administrative rights could make the server fetch internal network resources, including cloud metadata endpoints that may expose credentials or confidential data.

Executive priority

Prioritize remediation for internet-facing or cloud-hosted Atlassian environments, especially where administrators are numerous or loosely controlled. Treat as high business risk if cloud metadata credentials are reachable.

Technical view

The OAuth status REST resource in Application Links before 5.2.7, 5.3.0 before 5.3.4, and 5.4.0 before 5.4.3 can be redirected from an OAuth application link to internal resources. The reported precondition is remote administrative access.

Likely exposure

Exposure is most likely where affected Application Links versions are deployed and administrators can create OAuth application links. Cloud-hosted environments are more sensitive if the server can reach metadata resources or internal-only services.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. The issue requires administrative rights, reducing opportunistic exposure, but the impact can be serious if internal credentials are reachable.

Researcher notes

Evidence is limited to the CVE description and Atlassian issue reference. No CVSS, CWE, or exploit-in-the-wild source is provided. The key validation focus is version exposure, administrative access paths, and server-side reachability to sensitive internal resources.

Mitigation direction

  • Upgrade affected Application Links branches to 5.2.7, 5.3.4, 5.4.3, or later.
  • Review Atlassian APL-1359 for vendor-specific remediation guidance.
  • Limit administrative rights to trusted users only.
  • Restrict server access to cloud metadata and internal management endpoints where feasible.
  • Audit existing OAuth application links for unexpected destinations.

Validation and detection

  • Inventory installed Atlassian Application Links versions.
  • Confirm whether versions fall before 5.2.7, 5.3.4, or 5.4.3.
  • Review who can create or modify OAuth application links.
  • Check network controls between the application server and internal metadata endpoints.
  • Look for unusual OAuth application links or unexpected redirect destinations.
Prepared
Confidence
medium
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Cloud metadata behavior lookup

The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-18096 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AtlassianAtlassian Application Linksunspecified, 5.3.0, unspecified, 5.4.0, unspecifiedListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.