Activity StreamsApplication · Atlassian
CVE-2017-9513
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 · uneditedSeveral rest inline action resources of Atlassian Activity Streams before version 6.3.0 allows remote authenticated attackers to watch any Confluence page & receive notifications when comments are added to the watched page, and vote & watch JIRA issues that they do not have access to, although they will not receive notifications for the issue, via missing permission checks.
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 a broken access control vulnerability in Atlassian Activity Streams plugin versions prior to 6.3.0. Several REST inline action endpoints lack proper permission checks, allowing authenticated users to watch arbitrary Confluence pages (gaining notification access) and vote/watch JIRA issues they don't have permission to access.
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
Activity StreamsApplication
< 6.3.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/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.
-
Locate the Atlassian Activity Streams plugin versionNavigate to the Universal Plugin Manager (UPM) or admin Add-ons page in your Confluence or JIRA instance. Find the Activity Streams plugin in the list of installed plugins and note its displayed version number.Affected if The version listed is less than 6.3.0 (for example, 6.2.0, 6.1.0, etc.)
-
Confirm the plugin is enabledIn the UPM admin interface, verify that the Activity Streams plugin shows as 'Enabled' or 'Active' and not disabled or uninstalled.Affected if The plugin is enabled and its version is below 6.3.0
-
Identify if Confluence is using the affected pluginCheck if Confluence has the Activity Streams plugin installed. This plugin adds activity streams and inline actions to Confluence pages. Look for the plugin in Confluence Administration > Manage Add-ons.Affected if Confluence is running with Activity Streams plugin version below 6.3.0
-
Identify if JIRA is using the affected pluginCheck if JIRA has the Activity Streams plugin installed. This plugin adds activity streams and voting/watch features to JIRA issues. Look for the plugin in JIRA Administration > Add-ons > Manage Add-ons.Affected if JIRA is running with Activity Streams plugin version below 6.3.0
Your environment is affected if the Atlassian Activity Streams plugin is installed and enabled with a version number lower than 6.3.0 in either Confluence or JIRA.
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 data6.3.0
Upgrade Atlassian Activity Streams to version 6.3.0 or later which implements proper permission checks on the affected REST endpoints.
Fix this in Activity Streams
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9513 — 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-9513 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