Pcmanfm

Vendor:

First CVE: May 15, 2017 · Active for 9 years

1
Total CVEs
Bottom 1%
1.0
Avg CVEs / Year
Bottom 1%
5.5
Avg CVSS
Higher Avg CVSS than 14% of tracked products
0.0%
KEV Rate
Bottom 1%

Trends Over Time

The number and severity of CVEs published that impact Pcmanfm over time

Volume of CVEsAvg CVSS Base Score
First CVE
May 15, 2017
9 years ago
Most Recent CVE
May 15, 2017
3,357 days ago

CVE Severity & Scoring

Pcmanfm1 CVEs
All CVEs352,231 CVEs
Medium
Attack Vector
Local1 (100.0%)
Network0 (0.0%)
Unknown0 (0.0%)
Physical0 (0.0%)
Adjacent Network0 (0.0%)
Attack Complexity
Low1 (100.0%)
High0 (0.0%)
Unknown0 (0.0%)
User Interaction
None1 (100.0%)
Unknown0 (0.0%)
Required0 (0.0%)
Privileges Required
Low1 (100.0%)
High0 (0.0%)
None0 (0.0%)
Unknown0 (0.0%)

Top CVEs

Signals from CVEs in this product scope (1 CVEs).

1 CVEs · Highest risk first

CVEPublishedCVSSRiskKEVExploit
PCManFM 1.2.5 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (application unavailability).
May 15, 20175.520NONO

Exploit Exposure

Signals from CVEs in this product scope (1 CVEs).

CISA KEV
0 CVEs
0.0% of CVEs· Bottom 1%
Metasploit
0 CVEs
0.0% of CVEs· Bottom 1%
Nuclei
0 CVEs
0.0% of CVEs· Bottom 1%
ExploitDB
0 CVEs
0.0% of CVEs· Bottom 1%

Social Chatter

Signals from CVEs in this product scope (1 CVEs).

Media Mentions

Signals from CVEs in this product scope (1 CVEs).

Top CNAs Publishing CVEs For Pcmanfm

Top CWEs

Versions

VersionCVE CountAvg CVSSAvg EPSSKEVExploits
1.2.515.50.3%00