# CVE-2017-14585: Server-side request forgery in Hipchat Data Center

> Authenticated administrators can exploit an SSRF vulnerability to achieve remote code execution on Hipchat Server or Data Center instances.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Nov 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-7hgh-752m-38mj

## What is CVE-2017-14585?

CVE-2017-14585 is a high-severity server-side request forgery vulnerability in Atlassian Hipchat Data Center, published on 27 Nov 2017. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A Server Side Request Forgery (SSRF) vulnerability could lead to remote code execution for authenticated administrators. This issue was introduced in version 2.2.0 of Hipchat Server and version 3.0.0 of Hipchat Data Center. Versions of Hipchat Server starting with 2.2.0 and before 2.2.6 are affected by this vulnerability. Versions of Hipchat Data Center starting with 3.0.0 and before 3.1.0 are affected.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 2 products.


Products: Atlassian Hipchat Data Center, Atlassian Hipchat Server.

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

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

## Is CVE-2017-14585 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-14585 is a high-severity server-side request forgery vulnerability in Atlassian Hipchat Data Center, published on 27 Nov 2017. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-14585 in the wild and no public exploit code.

Affected product: Atlassian Hipchat Data Center. 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-14585/ (Markdown: https://insights.sbomify.com/CVE-2017-14585/index.md)
```

## Sources

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

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