Enterprise LinuxOperating system · Redhat
CVE-2018-1079
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedpcs 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe pcsd REST interface has a path traversal vulnerability in the /remote/put_file endpoint that fails to sanitize file paths properly. An authenticated attacker with write permissions can use this to create or overwrite arbitrary files outside the intended /etc/booth directory by manipulating path traversal sequences (e.g., ../../../etc/cron.d) in the file name parameter.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Enterprise LinuxOperating system
= 7.0= 7.5<= 0.9.164= 0.10CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify pcs package is installedRun 'rpm -q pcs' or 'which pcs' to check if the pcs package is present on the systemAffected if pcs package is not installed - the vulnerability does not apply
-
Determine installed pcs versionRun 'rpm -q --qf "%{VERSION}\n" pcs' to get the installed version number, then compare against affected versions <= 0.9.164 or = 0.10Affected if Installed version is 0.9.164 or earlier, or exactly 0.10
-
Check if pcsd service is runningRun 'systemctl status pcsd' or check if port 2224 is listening (pcs daemon by default listens on this port)Affected if pcsd service is not running - the vulnerable REST interface is not exposed
-
Inspect /etc/booth directory existenceRun 'ls -la /etc/booth' to check if this directory exists on the systemAffected if Directory /etc/booth exists - this is the intended target directory for the put_file endpoint, and existence of this directory indicates the feature is in use
-
Check pcsd authentication configurationReview /etc/pcsd/pcsd.conf or check if authentication is required for REST API access (default requires authentication)Affected if pcsd accepts authenticated requests - an attacker with valid credentials could exploit the path traversal
A system is affected by CVE-2018-1079 if pcs/pcsd is installed with version 0.9.164 or earlier (or exactly 0.10), the pcsd service is running and accessible, and an attacker could obtain authenticated access to the /remote/put_file endpoint.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade pcs to version 0.9.164 or 0.10 or later to obtain the patched version. As a compensating control, ensure the /etc/booth directory does not exist if immediate upgrade is not feasible.
Fix this in Enterprise Linux
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1079 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-1079 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data