# CVE-2017-9513: Missing authorization in Activity Streams

> Authenticated attackers can watch and vote on restricted JIRA issues or Confluence pages due to missing permission checks in Activity Streams.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jan 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-hv3r-96x4-645h

## What is CVE-2017-9513?

CVE-2017-9513 is a medium-severity missing authorization vulnerability in Atlassian Activity Streams, published on 29 Jan 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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

Weakness: CWE-862 (Missing Authorization), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2017-9513?

It affects 1 product.


Products: Atlassian Activity Streams.

## How do I fix CVE-2017-9513?

No fix has been published for CVE-2017-9513 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-9513 being exploited?

There is no known exploitation of CVE-2017-9513 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-9513 and fix it if it is affected.

What it is: CVE-2017-9513 is a medium-severity missing authorization vulnerability in Atlassian Activity Streams, published on 29 Jan 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-9513 in the wild and no public exploit code.

Affected product: Atlassian Activity Streams. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-9513/ (Markdown: https://insights.sbomify.com/CVE-2017-9513/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-9513
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-9513
- OSV: https://osv.dev/vulnerability/CVE-2017-9513

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-9513/
Summaries are generated and may contain mistakes; the official description above is the record.