pcs before version 0.9.164 and 0.10 is vulnerable to a privilege escalation via authorized user malicious REST call.
pcs before version 0.9.164 and 0.10 is vulnerable to a privilege escalation via authorized user malicious REST call. The REST interface of the pcsd service did not properly sanitize the file name from the /remote/put_file query. If the /etc/booth directory exists, an authenticated attacker with write permissions could create or overwrite arbitrary files with arbitrary data outside of the /etc/booth directory, in the context of the pcsd process.
- Published
- Apr 12, 2018
- Updated
- Jun 16, 2026
- EPSS
- 1.1% · 63th percentile
- CWE
- CWE-552
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.1%
CNA vs NVD score
- NVD
- 6.5
- CNA · redhat
- 8.7
- 2.2 point gap
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| clusterlabs | pacemaker command line interface | cpe:2.3:a:clusterlabs:pacemaker_command_line_interface |
| redhat | enterprise linux | cpe:2.3:o:redhat:enterprise_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- clusterlabs pacemaker command line interfaceup to 0.9.164 inclusive
- clusterlabs pacemaker command line interface0.10
- redhat enterprise linux7.0
- redhat enterprise linux7.5
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
unspecified pcs
- pcs 0.9.164, pcs 0.10affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | pcs | before 0.9.164-1 | 0.9.164-1 |
| Red Hat:enterprise_linux:7::server | pcs | before 0:0.9.162-5.el7_5.1 | 0:0.9.162-5.el7_5.1 |
| Red Hat:enterprise_linux:7::server | pcs-debuginfo | before 0:0.9.162-5.el7_5.1 | 0:0.9.162-5.el7_5.1 |
| Red Hat:enterprise_linux:7::server | pcs-snmp | before 0:0.9.162-5.el7_5.1 | 0:0.9.162-5.el7_5.1 |
Same product
clusterlabs: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-1086pcs before versions 0.9.164 and 0.10 is vulnerable to a debug parameter removal bypass.31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:pcs | 0.9.164-1 · Debian:12 | Package registry (OSV) |
| red hat:pcs | 0:0.9.162-5.el7_5.1 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:pcs-debuginfo | 0:0.9.162-5.el7_5.1 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:pcs-snmp | 0:0.9.162-5.el7_5.1 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-552 · Files or Directories Accessible to External PartiesCVSS vector
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
- OS Credential DumpingT1003
- Data from Network Shared DriveT1039
- Automated CollectionT1119
- Data from Information RepositoriesT1213
- Data from Cloud Storage ObjectT1530
- Unsecured Credentials: Credentials in FilesT1552.001
- Unsecured Credentials: Bash HistoryT1552.003
- Unsecured Credentials: Private KeysT1552.004
- Unsecured Credentials: Group Policy PreferencesT1552.006
- Credentials from Password StoresT1555
- Data from Configuration RepositoryT1602
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.