# CVE-2019-15006: Other in Confluence Server

> An attacker can perform a man-in-the-middle attack to observe or modify files and access user information via the Confluence Previews plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Dec 2019
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-86mx-982p-mgc2

## What is CVE-2019-15006?

CVE-2019-15006 is a medium-severity vulnerability in Atlassian Confluence Server, published on 19 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

There was a man-in-the-middle (MITM) vulnerability present in the Confluence Previews plugin in Confluence Server and Confluence Data Center. This plugin was used to facilitate communication with the Atlassian Companion application. The Confluence Previews plugin in Confluence Server and Confluence Data Center communicated with the Companion application via the atlassian-domain-for-localhost-connections-only.com domain name, the DNS A record of which points at 127.0.0.1. Additionally, a signed certificate for the domain was publicly distributed with the Companion application. An attacker in the position to control DNS resolution of their victim could carry out a man-in-the-middle (MITM) attack between Confluence Server (or Confluence Data Center) and the atlassian-domain-for-localhost-connections-only.com domain intended to be used with the Companion application. This certificate has been revoked, however, usage of the atlassian-domain-for-localhost-connections-only.com domain name was still present in Confluence Server and Confluence Data Center. An attacker could perform the described attack by denying their victim access to certificate revocation information, and carry out a man-in-the-middle (MITM) attack to observe files being edited using the Companion application and/or modify them, and access some limited user information.

Weakness: CWE-913 (Improper Control of Dynamically-Managed Code Resources)

## Which versions are affected by CVE-2019-15006?

It affects 2 products.


Products: Atlassian Confluence, Atlassian Confluence Server.

## How do I fix CVE-2019-15006?

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

## Is CVE-2019-15006 being exploited?

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

## Other vulnerabilities in Atlassian Confluence Server

- [CVE-2019-3395](https://insights.sbomify.com/CVE-2019-3395/): Server-side request forgery in Confluence Server (critical 9.8)
- [CVE-2019-3394](https://insights.sbomify.com/CVE-2019-3394/): Path traversal in Confluence Server (high 8.8)
- [CVE-2019-20406](https://insights.sbomify.com/CVE-2019-20406/): Privilege escalation in Confluence Data Center (high 7.8)
- [CVE-2017-18085](https://insights.sbomify.com/CVE-2017-18085/): Cross-site scripting in Confluence (medium 6.1)
- [CVE-2017-18086](https://insights.sbomify.com/CVE-2017-18086/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-15006 and fix it if it is affected.

What it is: CVE-2019-15006 is a medium-severity vulnerability in Atlassian Confluence Server, published on 19 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-15006 in the wild and no public exploit code.

Affected product: Atlassian Confluence 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-2019-15006/ (Markdown: https://insights.sbomify.com/CVE-2019-15006/index.md)
```

## Sources

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

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