Application LinksApplication · Atlassian
CVE-2017-16860
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 invalidRedirectUrl template in Atlassian Application Links before version 5.2.7, from version 5.3.0 before version 5.3.4 and from version 5.4.0 before version 5.4.3 allows remote attackers to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability in the redirectUrl parameter link in the redirect warning message.
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 confidenceA cross-site scripting (XSS) vulnerability in Atlassian Application Links allows remote attackers to inject arbitrary HTML or JavaScript via the redirectUrl parameter in the invalidRedirectUrl template's redirect warning message. The vulnerability affects versions 5.2.7之前的版本, 5.3.0-5.3.4, and 5.4.0-5.4.3.
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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Verify Atlassian Application Links is installedCheck for Atlassian Application Links installation by reviewing application directories or using system inventory tools. Common installation paths include /opt/atlassian/ or the application's home directory.Affected if The product is present on the system
-
Determine installed version of Atlassian Application LinksLocate the version information in the application's configuration files, about page, or by running the application's version command. Check the application manifest or version.properties file typically found in the application installation directory.Affected if The version cannot be determined or is not documented
-
Compare installed version against vulnerable rangesReview the version identified in step 2 against the affected ranges: < 5.2.7, 5.3.0-5.3.4, or 5.4.0-5.4.3Affected if The installed version falls within any of these ranges: < 5.2.7, >= 5.3.0 and < 5.3.4, or >= 5.4.0 and < 5.4.3
-
Check if redirect URL feature is accessibleVerify whether the invalidRedirectUrl template is accessible. This is the template that handles the redirectUrl parameter in the application's redirect warning message functionality.Affected if The redirect warning feature with the redirectUrl parameter is exposed or accessible to users
The environment is affected if Atlassian Application Links is installed with a version less than 5.2.7, between 5.3.0-5.3.4, or between 5.4.0-5.4.3, and the redirect URL feature is accessible.
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 patch the XSS vulnerability in the redirectUrl parameter.
Fix this in Application Links
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-16860 — 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-16860 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