Skip to content
Fencer Intel
critical 9.1

CVE-2013-6396 json

Python Swift client is vulnerable to Missing SSL Certificate Check

published 12y ago modified 4mo ago also GHSA-p3xv-97g8-4wmj , PYSEC-2014-12 , EUVD-2014-0093

cvss
9.1
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 54%
public exploits
0
none known

Summary

The OpenStack Python client library for Swift (python-swiftclient) 1.0 through 1.9.0 does not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate.

Patch / fix

  • pypi python-swiftclient 2.0
  • python-swiftclient Debian 14, Debian 13, Debian 12 1:2.0.2-1

debian advisories DEBIAN-CVE-2013-6396

Is CVE-2013-6396 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 Fencer

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-6396 updated cvss 4.3

python-swiftclient: SSL certificate verification security issue

  • Red Hat OpenStack Platform 3 python-swiftclient Red Hat OpenStack Platform 4 python-swiftclient
    affected: no fix available

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

0.73% chance of exploitation in the next 30 days, higher than 54% 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 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
pypi python-swiftclient
>=1.0, <2.0
2.0

Classification

Weakness
  • CWE-310 Cryptographic Issues
  • CWE-295 Improper Certificate Validation

References

Sources

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.