| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Hipchat Plugin and classified as problematic. Impacted is an unknown function. The manipulation results in information disclosure (Key). This vulnerability is known as CVE-2016-6668. It is possible to launch the attack remotely. No exploit is available. It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as critical, was found in Hipchat Plugin (Chat Software) (the affected version is unknown). Affected is an unknown code. The manipulation with an unknown input leads to a information disclosure vulnerability (Key). CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality.
The weakness was published 10/06/2016 by David Black as not defined mailinglist post (Bugtraq). The advisory is shared for download at seclists.org. This vulnerability is traded as CVE-2016-6668 since 08/10/2016. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1592. The advisory points out:
The Atlassian Hipchat Integration Plugin for Bitbucket Server exposed the secret key it used to communicate with a linked HipChat service in various administration pages. For this vulnerability to affect your Bitbucket Server instance you must have a HipChat integration established. To exploit this issue, attackers must have Admin access to a Bitbucket Server. Using the secret key attackers could gain full control over a linked HipChat instance.
The commercial vulnerability scanner Qualys is able to test this issue with plugin 13331 (Atlassian Hipchat Integration Plugin for Bitbucket Server, Jira, Confluence Secret Key Vulnerability).
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 93159†). Once again VulDB remains the best source for vulnerability data.
Product
Type
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.5VulDB Meta Temp Score: 7.2
VulDB Base Score: 7.5
VulDB Temp Score: 6.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Name: KeyClass: Information disclosure / Key
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
08/10/2016 🔍09/21/2016 🔍
10/06/2016 🔍
10/06/2016 🔍
01/23/2017 🔍
09/22/2022 🔍
Sources
Advisory: 139004Researcher: David Black
Status: Not defined
Confirmation: 🔍
CVE: CVE-2016-6668 (🔍)
GCVE (CVE): GCVE-0-2016-6668
GCVE (VulDB): GCVE-100-92460
SecurityFocus: 93159 - Atlassian HipChat Plugin CVE-2016-6668 Information Disclosure Vulnerability
Entry
Created: 10/06/2016 16:45Updated: 09/22/2022 14:15
Changes: 10/06/2016 16:45 (53), 05/03/2019 21:47 (12), 09/22/2022 14:15 (4)
Complete: 🔍
Cache ID: 216:FD8:103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.