Skip to content
Fencer Intel
medium 5.3

CVE-2017-1000246 json

Pysaml2 improperly initializes encryption vector

published 8y ago modified 4mo ago also GHSA-cq94-qf6q-mf2h , PYSEC-2017-26 , EUVD-2017-0105

cvss
5.3
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 59%
public exploits
0
none known

Summary

Python package pysaml2 version 4.4.0 and earlier reuses the initialization vector across encryptions in the IDP server, resulting in weak encryption of data.

Patch / fix

  • pypi pysaml2 4.6.0
  • pysaml2_project pysaml2 4.6.0
  • python-pysaml2 Debian 14, Debian 13, Debian 12 4.5.0-4

debian advisories DEBIAN-CVE-2017-1000246

  • kibana OpenStack Cloud 7 4.6.3-5.1
  • ansible OpenStack Cloud 7 2.2.3.0-12.2
  • grafana OpenStack Cloud 7 4.6.5-1.14.1
  • memcached OpenStack Cloud 7 1.5.17-3.6.1
  • python-py OpenStack Cloud 7 1.8.1-11.12.1
  • zookeeper OpenStack Cloud 7 3.4.10-6.1
  • crowbar-ha OpenStack Cloud 7 4.0+git.1585316203.d6ad2c8-4.52.4
  • keepalived OpenStack Cloud 7 2.0.19-1.8.1

suse advisories SUSE-RU-2020:2072-1SUSE-SU-2020:1901-1

Is CVE-2017-1000246 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-2017-1000246 updated cvss 5.3

python-pysaml2: Reuse of AES initialization vector in AESCipher

  • Red Hat Enterprise Linux OpenStack Platform 7 (Kilo) python-pysaml2 Red Hat OpenStack Platform 8 (Liberty) python-pysaml2 Red Hat OpenStack Platform 9 (Mitaka) python-pysaml2 Red Hat OpenStack Platform 10 (Newton) python-pysaml2 Red Hat OpenStack Platform 11 (Ocata) python-pysaml2 Red Hat OpenStack Platform 12 (Pike) python-pysaml2
    affected: 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

0.89% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 5.3 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.0 5.3 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
pypi pysaml2
<4.6.0
4.6.0

Classification

Weakness
  • CWE-330 Use of Insufficiently Random Values

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.