Hipchat Plugin up to 2.2.0 on Jenkins Authorization HipChatNotifier.java Notification credentials management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Hipchat Plugin up to 2.2.0 on Jenkins. It has been rated as critical. The affected element is an unknown function of the file HipChatNotifier.java of the component Authorization. The manipulation as part of Notification leads to credentials management. This vulnerability is traded as CVE-2018-1000418. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in Hipchat Plugin up to 2.2.0 on Jenkins (Jenkins Plugin) and classified as critical. This issue affects an unknown function of the file HipChatNotifier.java of the component Authorization. The manipulation as part of a Notification leads to a credentials management vulnerability. Using CWE to declare the problem leads to CWE-255. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
An improper authorization vulnerability exists in Jenkins HipChat Plugin 2.2.0 and earlier in HipChatNotifier.java that allows attackers with Overall/Read access to send test notifications to an attacker-specified HipChat server with attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
The bug was discovered 09/25/2018. The weakness was shared 01/09/2019 with CloudBees, Inc. (Website). The advisory is shared at jenkins.io. The identification of this vulnerability is CVE-2018-1000418 since 01/09/2019. The exploitation is known to be easy. The attack may be initiated remotely. The successful exploitation requires a simple authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1552 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 106 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 106532†). The entries VDB-128837, VDB-128838, VDB-128839 and VDB-128840 are related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
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
Class: Credentials managementCWE: CWE-255
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
09/25/2018 🔍01/09/2019 🔍
01/09/2019 🔍
01/09/2019 🔍
01/09/2019 🔍
01/10/2019 🔍
04/27/2020 🔍
Sources
Advisory: jenkins.ioOrganization: CloudBees, Inc.
Status: Not defined
Confirmation: 🔍
CVE: CVE-2018-1000418 (🔍)
GCVE (CVE): GCVE-0-2018-1000418
GCVE (VulDB): GCVE-100-128849
SecurityFocus: 106532 - Jenkins Multiple Security Vulnerabilities
See also: 🔍
Entry
Created: 01/10/2019 11:10Updated: 04/27/2020 11:32
Changes: 01/10/2019 11:10 (63), 04/27/2020 11:32 (5)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.