CVE-2013-6444: PyWBEM 0.7 and earlier does not verify that the server hostname matches a domain name in the subject's Common

Q: How do I fix CVE-2013-6444?

pywbem: upgrade to newer than 0.7. Exact commands for each OS are on this page.

Q: Is CVE-2013-6444 being exploited?

CVE-2013-6444 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2013-6444 affect?

CVE-2013-6444 affects pywbem. Severity is medium (CVSS 5.8). 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 allows man-in-the-middle attackers to spoof SSL servers via an a

Q: How urgent is CVE-2013-6444?

Priority 36/100. No elevated risk signals yet.

Routine

MEDIUM 5.8UPGRADE

CVE-2013-6444 is a medium-severity flaw (CVSS 5.8) affecting pywbem. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.8 (Medium)
EPSS exploit chance	1.1% (top 35%)
CISA exploited list	No
Weakness	CWE-20
Published	2014-05-05
Last modified	2026-06-17

Publisher (CNA): Red Hat, Inc. · Vendor: pywbem project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2014-05-05 17:06 UTCPublished CVE record published
2026-06-17 00:00 UTCUpdated Record last modified

pywbem project pywbem UPGRADE

Affected: <= 0.7

Fixed in: newer than 0.7

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy pywbem || rpm -q pywbem || pywbem --version

2. UPGRADE to newer than 0.7 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade pywbem

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade pywbem

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2013-6444?

pywbem: upgrade to newer than 0.7. Exact commands for each OS are on this page.

Is CVE-2013-6444 being exploited?

CVE-2013-6444 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2013-6444 affect?

CVE-2013-6444 affects pywbem. Severity is medium (CVSS 5.8). 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 allows man-in-the-middle attackers to spoof SSL servers via an a

How urgent is CVE-2013-6444?

Priority 36/100. No elevated risk signals yet.

Related CVEs

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

References

← Back to latest CVEs