CVE-2017-14681

CVE-2017-14681 is a medium-severity vulnerability in P3scan Project P3scan with a CVSS 3.x base score of 5.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-665.

Key facts

Description

The daemon in P3Scan 3.0_rc1 and earlier creates a p3scan.pid file after dropping privileges to a non-root account, which might allow local users to kill arbitrary processes by leveraging access to this non-root account for p3scan.pid modification before a root script executes a "kill `cat /pathname/p3scan.pid`" command, as demonstrated by etc/init.d/p3scan.

Frequently asked questions

What is CVE-2017-14681?
The daemon in P3Scan 3.0_rc1 and earlier creates a p3scan.pid file after dropping privileges to a non-root account, which might allow local users to kill arbitrary processes by leveraging access to this non-root account for p3scan.pid modification before a root script executes a "kill `cat /pathname/p3scan.pid`" command, as demonstrated by etc/init.d/p3scan.
How severe is CVE-2017-14681?
CVE-2017-14681 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2017-14681 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (20th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-14681?
CVE-2017-14681 affects P3scan Project P3scan. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2017-14681?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2017-14681 published?
CVE-2017-14681 was published on 2017-09-21 and last updated on 2026-06-17.

References

Affected products (1)

Other CWE-665 (Improper Initialization) vulnerabilities

Browse all CWE-665 (Improper Initialization) vulnerabilities →