CVE-2016-6668 json
The Atlassian Hipchat Integration Plugin for Bitbucket Server 6.26.0 before 6.27.5, 6.28.0 before 7.3.7, and 7.4.0 before 7.8.17; Confluenc…
published 2017-01-23 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-7571
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.8%
- EPSS 3.8% chance of exploitation in 30 days, percentile 90%
- public exploits
- 0
- none known
Summary
The Atlassian Hipchat Integration Plugin for Bitbucket Server 6.26.0 before 6.27.5, 6.28.0 before 7.3.7, and 7.4.0 before 7.8.17; Confluence HipChat plugin 6.26.0 before 7.8.17; and HipChat for JIRA plugin 6.26.0 before 7.8.17 allows remote attackers to obtain the secret key for communicating with HipChat instances by reading unspecified pages.
Exploit prediction
3.82% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
confluence.atlassian.com
/bitbucketserver/bitbucket-server-security-advisory-2016-09-21-840698321.html
vendor-advisory
-
confluence.atlassian.com
/doc/confluence-security-advisory-2016-09-21-849052104.html
vendor-advisory
-
confluence.atlassian.com
/jira/jira-and-hipchat-for-jira-plugin-security-advisory-2016-09-21-849052099.html
vendor-advisory
-
securityfocus.com
/archive/1/539530/100/0/threaded
mailing-list, broken-link, third-party-advisory, vdb-entry
-
securityfocus.com
/bid/93159
vdb-entry, broken-link, third-party-advisory
-
packetstormsecurity.com
/files/139004/Atlassian-HipChat-Secret-Key-Disclosure.html
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2016-6668
- NVD CVE-2016-6668
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.