Hipchat Data CenterApplication · Atlassian
CVE-2017-14585
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 · uneditedA 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.
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 confidenceServer-Side Request Forgery (SSRF) vulnerability in Hipchat Server and Hipchat Data Center allows authenticated administrators to make the server perform arbitrary requests to internal or external resources, potentially leading to remote code execution.
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
Hipchat Data CenterApplication
>= 3.0.0, < 3.1.0
Hipchat ServerApplication
>= 2.2.0, < 2.2.6CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify Hipchat product variantDetermine whether the installation is Hipchat Server or Hipchat Data Center. This can be found in the product documentation, about page, or installation metadata.Affected if Product is Hipchat Data Center or Hipchat Server
-
Locate installed Hipchat versionCheck the Hipchat admin console, installation directory, or version file. On the server, this is typically accessible via the admin interface under 'About' or through command line tools if you have server access.Affected if Version cannot be determined
-
Compare version against affected ranges for Hipchat Data CenterIf the product is Hipchat Data Center, verify if the version is >= 3.0.0 and < 3.1.0. Check the version string in the admin panel or version file.Affected if Version falls within >= 3.0.0 and < 3.1.0 for Data Center
-
Compare version against affected ranges for Hipchat ServerIf the product is Hipchat Server, verify if the version is >= 2.2.0 and < 2.2.6. Check the version string in the admin panel or version file.Affected if Version falls within >= 2.2.0 and < 2.2.6 for Server
-
Confirm admin authentication is configuredVerify that administrator accounts exist and authentication is enabled for the Hipchat admin interface. This vulnerability requires an authenticated administrator to exploit the SSRF.Affected if Admin authentication is enabled and an admin user account exists
User is affected if Hipchat Data Center version is between 3.0.0 and 3.1.0 (exclusive), or Hipchat Server version is between 2.2.0 and 2.2.6 (exclusive), and administrator authentication is configured.
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 data2.2.63.1.0
Upgrade Hipchat Server to version 2.2.6 or later, or Hipchat Data Center to version 3.1.0 or later.
Fix this in Hipchat Data Center
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14585 — 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-14585 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