CVE-2013-6418 json
PyWBEM TOCTOU vulnerability in certificate validation
published 12y ago modified 4mo ago also GHSA-f9q5-46qg-74x4 , PYSEC-2014-93 , EUVD-2014-0094
- cvss
- 7.5
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 76%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi pywbem 0.8.1
- python-pywbem openSUSE Tumbleweed 1.8.1-2.5
- python-pywbem openSUSE Tumbleweed 1.1.1-2.7
- python-pywbem openSUSE Tumbleweed 1.7.2-1.1
opensuse advisories openSUSE-SU-2026:12035-1openSUSE-SU-2024:11263-1openSUSE-SU-2024:13977-1
Is CVE-2013-6418 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor 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-6418 updated cvss 5.8
pywbem: TOCTOU vulnerability in certificate validation
-
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.65% chance of exploitation in the next 30 days, higher than 76% 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 |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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
-
suse.com
/support/update/announcement/2014/suse-su-20140580-1.html
vendor-advisory, web
-
sourceforge.net
/p/pywbem/code/627/
vendor-advisory, web
-
seclists.org
/oss-sec/2013/q4/531
mailing-list, web
-
sourceforge.net
/p/pywbem/mailman/message/31757312/
mailing-list, web
-
secunia.com
/advisories/58327
third-party-advisory, advisory
-
securityfocus.com
/bid/64544
vdb-entry, web
-
oracle.com
/technetwork/topics/security/bulletinjan2016-2867206.html
web
-
bugzilla.redhat.com
/show_bug.cgi?id=1039801
web, report
-
nvd.nist.gov
/vuln/detail/CVE-2013-6418
advisory
-
github.com
/pypa/advisory-database/tree/main/vulns/pywbem/PYSEC-2014-93.yaml
web
-
github.com
/pywbem/pywbem
package
-
web.archive.org
/web/20161110005052/http://secunia.com/advisories/58327
web
-
web.archive.org
/web/20200228040356/http://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-f9q5-46qg-74x4
advisory
Sources
- CVE List CVE-2013-6418
- GitHub Advisory GHSA-f9q5-46qg-74x4
- NVD CVE-2013-6418
- OSV PYSEC-2014-93
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.