Pacemaker up to 2.0.0 Client-Server Authentication access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Pacemaker up to 2.0.0. It has been classified as critical. This affects an unknown part of the component Client-Server Authentication. The manipulation leads to access control. This vulnerability is uniquely identified as CVE-2018-16877. Local access is required to approach this attack. No exploit exists. Upgrading the affected component is recommended.
Details
A vulnerability was found in Pacemaker up to 2.0.0 and classified as critical. This issue affects an unknown code block of the component Client-Server Authentication. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-264. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
A flaw was found in the way pacemaker's client-server authentication was implemented in versions up to and including 2.0.0. A local attacker could use this flaw, and combine it with other IPC weaknesses, to achieve local privilege escalation.
The bug was discovered 04/17/2019. The weakness was disclosed 04/18/2019 with Red Hat as confirmed bug report (Bugzilla). The advisory is shared at bugzilla.redhat.com. The identification of this vulnerability is CVE-2018-16877 since 09/11/2018. An attack has to be approached locally. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k. The commercial vulnerability scanner Qualys is able to test this issue with plugin 197435 (Ubuntu Security Notification for Pacemaker Vulnerabilities (USN-3952-1)).
Upgrading to version 2.0.1 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 108036†). The entries VDB-133818 and VDB-133848 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
CNA Base Score: 8.8
CNA Vector (Red Hat, Inc.): 🔍
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: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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: 🔍
Upgrade: Pacemaker 2.0.1
Patch: github.com
Timeline
09/11/2018 🔍04/17/2019 🔍
04/17/2019 🔍
04/18/2019 🔍
04/19/2019 🔍
09/04/2023 🔍
Sources
Advisory: RHSA-2019:1278Organization: Red Hat
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2018-16877 (🔍)
GCVE (CVE): GCVE-0-2018-16877
GCVE (VulDB): GCVE-100-133817
SecurityFocus: 108036 - Pacemaker CVE-2019-3885 Information Disclosure Vulnerability
See also: 🔍
Entry
Created: 04/19/2019 06:52Updated: 09/04/2023 16:01
Changes: 04/19/2019 06:52 (62), 05/30/2020 18:36 (5), 09/04/2023 15:55 (5), 09/04/2023 16:01 (12)
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.