CVE-2013-6444 json
PyWBEM TOCTOU vulnerability in certificate validation
published 2014-05-05 12 y ago modified 2026-06-17 4 mo ago also GHSA-gh2c-6m38-c78j , PYSEC-2014-94 , EUVD-2014-0095
- cvss
- 5.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 64%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi pywbem 0.8.1
- pywbem Ubuntu 14.04 LTS 0.7.0-4ubuntu1~14.04.1
- pywbem Ubuntu 18.04 LTS, Ubuntu 16.04 LTS 0.8.0~dev650-1
ubuntu advisories UBUNTU-CVE-2013-6444
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2013-6444 updated cvss 5.8
pywbem: failure to check certificate hostname
-
Red Hat Enterprise Linux 6 pywbem Red Hat Enterprise Linux 7 pywbemaffected: no fix planned “Will not fix”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.05% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:P/I:P/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | pywbem | <0.8.1 |
0.8.1 |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
github.com
/pywbem/pywbem/commit/f7599379b26a685d772b2620a16316130f46c474
web
-
sourceforge.net
/p/pywbem/code/627/
vendor-advisory, web
-
bugzilla.redhat.com
/show_bug.cgi?id=1044246
web, report
-
sourceforge.net
/p/pywbem/mailman/message/31757312/
mailing-list, web
-
seclists.org
/oss-sec/2013/q4/524
mailing-list, web
-
oracle.com
/technetwork/topics/security/bulletinapr2016-2952098.html
web
-
securityfocus.com
/bid/64544
vdb-entry, web
-
nvd.nist.gov
/vuln/detail/CVE-2013-6444
advisory
-
github.com
/pypa/advisory-database/tree/main/vulns/pywbem/PYSEC-2014-94.yaml
web
-
github.com
/pywbem/pywbem
package
-
web.archive.org
/web/20200228035408/https://www.securityfocus.com/bid/64544
web
-
sourceforge.net
/p/pywbem/code/627
web
-
sourceforge.net
/p/pywbem/mailman/message/31757312
web
-
github.com
/advisories/GHSA-gh2c-6m38-c78j
advisory
Sources
- CVE List CVE-2013-6444
- GitHub Advisory GHSA-gh2c-6m38-c78j
- NVD CVE-2013-6444
- OSV PYSEC-2014-94
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.