# CVE-2015-8481: Information disclosure in n/a

> Remote attackers can obtain sensitive information by exploiting incorrect image attachment handling in JIRA email notifications.

- **Severity:** Low 3.1 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/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:** 8 Jan 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9w67-5jpv-rm8v

## What is CVE-2015-8481?

CVE-2015-8481 is a low-severity vulnerability in Atlassian Jira Server, published on 8 Jan 2016. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Atlassian JIRA Software 7.0.3, JIRA Core 7.0.3, and the bundled JIRA Service Desk 3.0.3 installer attaches the wrong image to e-mail notifications when a user views an issue with inline wiki markup referencing an image attachment, which might allow remote attackers to obtain sensitive information by updating a different issue that includes wiki markup for an external image reference.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2015-8481?

It affects 3 products.


Products: Atlassian Jira Core, Atlassian Jira Server, Atlassian Jira Service Desk.

## How do I fix CVE-2015-8481?

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

## Is CVE-2015-8481 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-8481 and fix it if it is affected.

What it is: CVE-2015-8481 is a low-severity vulnerability in Atlassian Jira Server, published on 8 Jan 2016. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-8481 in the wild and no public exploit code.

Affected product: Atlassian Jira Server. 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-2015-8481/ (Markdown: https://insights.sbomify.com/CVE-2015-8481/index.md)
```

## Sources

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

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