Application LinksApplication · Atlassian
CVE-2017-18096
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is an SSRF vulnerability in Atlassian Application Links' OAuth status rest resource. Attackers with administrative rights can create an OAuth application link to a location they control, then redirect requests to internal network resources. In cloud environments like Amazon EC2, this allows access to instance metadata services that expose sensitive credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Application LinksApplication
< 5.2.7>= 5.3.0, < 5.3.4>= 5.4.0, < 5.4.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Atlassian Application Links versionCheck the Application Links version in the Atlassian administration console under 'Application Links' or inspect the applicationlinks-x.x.x.jar file in the installation directory. The version is typically found in the 'atlassian-applicationlinks' JAR file name or in the product information page.Affected if The installed version is less than 5.2.7, or between 5.3.0 and 5.3.4 exclusive, or between 5.4.0 and 5.4.3 exclusive.
-
Verify Application Links are configuredIn the Atlassian administration interface, navigate to Applications > Application Links. Check if any application links have been created and configured.Affected if Application links exist in the environment, enabling the OAuth status rest resource endpoint.
-
Confirm OAuth authentication is enabled for application linksNavigate to the Application Links configuration and inspect the authentication settings for each linked application. Look for OAuth (1a or 2.0) authentication being configured as the connection method.Affected if OAuth authentication is configured on any application link, which enables the vulnerable OAuth status endpoint.
-
Check administrative user permissionsIn the Atlassian administration console, review users with 'Admin' or 'System Admin' permissions, particularly those with access to create or modify Application Links.Affected if There are administrative users who can create or modify application links, which is required to exploit this vulnerability.
You are affected if your Atlassian Application Links version falls within the vulnerable ranges AND OAuth-enabled application links are configured, allowing an administrator to redirect OAuth status requests to internal network resources.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data5.2.75.3.45.4.3
Upgrade Atlassian Application Links to version 5.2.7, 5.3.4, 5.4.3 or later to remediate this vulnerability. In EC2 environments, also consider disabling or restricting metadata service access as a defense-in-depth measure.
Fix this in Application Links
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18096 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-18096 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data