PatchTheCVEpywbem vulnerabilities and fixes
Recent CVEs affecting pywbem, with upgrade or downgrade steps. 2 tracked.
pywbem has 2 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 2. Most recent: 2014-05-05. Highest priority: CVE-2013-6418 (score 39/100).
- CVE-2013-6444 MEDIUM 5.8 UPGRADE PyWBEM 0.7 and earlier does not verify that the server hostname matches a domain name in the subject's Common
- CVE-2013-6418 MEDIUM 5.8 UPGRADE PyWBEM 0.7 and earlier uses a separate connection to validate X.509 certificates, which allows man-in-the-midd
FAQ
How do I fix pywbem vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is pywbem being exploited right now?
None of the tracked pywbem CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which pywbem CVE should I patch first?
CVE-2013-6418 currently ranks highest (39/100): PyWBEM 0.7 and earlier uses a separate connection to validate X.509 certificates, which allows man-in-the-midd.