Logilab Common

Vendor:

First CVE: Mar 11, 2014 · Active for 12 years

2
Total CVEs
More Total CVEs than 49% of tracked products
2.0
Avg CVEs / Year
Higher CVE frequency than 60% of tracked products
4.4
Avg CVSS
Higher Avg CVSS than 4% of tracked products
0.0%
KEV Rate
Bottom 1%

Trends Over Time

The number and severity of CVEs published that impact Logilab Common over time

Volume of CVEsAvg CVSS Base Score
First CVE
Mar 11, 2014
12 years ago
Most Recent CVE
Mar 11, 2014
4,520 days ago

CVE Severity & Scoring

Logilab Common2 CVEs
All CVEs352,708 CVEs
Medium
Attack Vector
Local0 (0.0%)
Network0 (0.0%)
Unknown2 (100.0%)
Physical0 (0.0%)
Adjacent Network0 (0.0%)
Attack Complexity
Low0 (0.0%)
High0 (0.0%)
Unknown2 (100.0%)
User Interaction
None0 (0.0%)
Unknown2 (100.0%)
Required0 (0.0%)
Privileges Required
Low0 (0.0%)
High0 (0.0%)
None0 (0.0%)
Unknown2 (100.0%)

Top CVEs

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

2 CVEs · Highest risk first

CVEPublishedCVSSRiskKEVExploit
The Execute class in shellutils in logilab-commons before 0.61.0 uses tempfile.mktemp, which allows local users to have an unspecified impact by pre-creating the temporary file.
Mar 11, 20144.414NONO
The (1) extract_keys_from_pdf and (2) fill_pdf functions in pdf_ext.py in logilab-commons before 0.61.0 allows local users to overwrite arbitrary files and possibly have other unsp
Mar 11, 20144.414NONO

Exploit Exposure

Signals from CVEs in this product scope (2 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 (2 CVEs).

Media Mentions

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

Top CNAs Publishing CVEs For Logilab Common

Top CWEs

Versions

No cataloged versions.