JiraApplication · Atlassian
CVE-2017-16865
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 Trello importer in Atlassian Jira before version 7.6.1 allows remote attackers to access the content of internal network resources via a Server Side Request Forgery (SSRF). 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 confidenceServer-Side Request Forgery (SSRF) vulnerability in the Trello importer of Atlassian Jira versions before 7.6.1 allows remote attackers to induce the Jira server to make arbitrary requests to internal network resources. In cloud environments like Amazon EC2, this can be exploited to access the metadata service at the169.254.169.254 endpoint, potentially exposing sensitive credential information.
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
JiraApplication
< 7.6.1CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/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.
-
Check Jira versionNavigate to Jira administration > System > System Info or check the Jira installation directory for the version file. The version is typically displayed on the System Info page under 'Jira version' or can be found in the about.json file in the Jira home directory.Affected if The installed Jira version is lower than 7.6.1 (e.g., 7.6.0, 7.5.x, 7.4.x, etc.)
-
Verify Trello importer availabilityNavigate to Jira administration > Apps > Find the Trello importer in the list of installed apps or check under Project settings > Import/Export to see if Trello integration options are present.Affected if The Trello importer functionality is accessible or enabled in the Jira instance
-
Confirm network accessibility to metadata endpointsFrom the Jira server, attempt to reach the EC2 metadata endpoint using: curl -s http://169.254.169.254/latest/meta-data/ (if running on AWS EC2) or check firewall rules allowing outbound HTTP/HTTPS to internal IP ranges.Affected if The Jira server can make outbound HTTP requests to 169.254.169.254 or other internal network resources without restriction
You are affected if your Jira version is below 7.6.1 and the Trello importer feature is enabled, allowing potential SSRF attacks to internal metadata services.
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 data7.6.1
Upgrade Atlassian Jira to version 7.6.1 or later to remediate this SSRF vulnerability. Until the upgrade can be completed, consider network segmentation to restrict the Jira server's ability to reach internal metadata endpoints.
Fix this in Jira
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-16865 — 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-16865 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