Pywbem

Vendor:

First CVE: May 5, 2014 · Active for 12 years

2
Total CVEs
More Total CVEs than 53% of tracked products
2.0
Avg CVEs / Year
Higher CVE frequency than 63% of tracked products
5.8
Avg CVSS
Higher Avg CVSS than 21% of tracked products
0.0%
KEV Rate
Bottom 1%

Trends Over Time

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

Volume of CVEsAvg CVSS Base Score
First CVE
May 5, 2014
12 years ago
Most Recent CVE
May 5, 2014
4,467 days ago

CVE Severity & Scoring

Pywbem2 CVEs
All CVEs353,173 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
PyWBEM 0.7 and earlier uses a separate connection to validate X.509 certificates, which allows man-in-the-middle attackers to spoof a peer via an arbitrary certificate.
May 5, 20145.817NONO
PyWBEM 0.7 and earlier does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allo
May 5, 20145.816NONO

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 Pywbem

Top CWEs

Versions

No cataloged versions.