Menu

Star on GitHub · 3.2k

CVE-2018-1079

8.7 · HIGH

pcs before version 0.9.164 and 0.10 is vulnerable to a privilege escalation via authorized user malicious REST call.

Published Apr 12, 2018CWE-552EPSS 1.06%

Overview

CVE-2018-1079 is a high-severity vulnerability. It was published on April 12, 2018 and has a CVSS 3.0 base score of 8.7 (HIGH).

This vulnerability has a CVSS 3.0 base score of 8.7, rated HIGH. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

Technical description

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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2018-1079?

CVE-2018-1079 is a high-severity vulnerability. It was published on April 12, 2018 and has a CVSS 3.0 base score of 8.7 (HIGH).

How severe is CVE-2018-1079?

This vulnerability has a CVSS 3.0 base score of 8.7, rated HIGH. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2018-1079?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2018-1079?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2018-1079 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2018

View all