Skip to content
Fencer Intel
high 8.1

CVE-2015-3206 json

python-kerberos vulnerable to KDC spoofing attacks

published 2017-08-25 9 y ago modified 2026-06-17 4 mo ago also GHSA-mffc-9gx5-99g3 , PYSEC-2017-49 , PYSEC-2017-66 , EUVD-2017-0067

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

Summary

The checkPassword function in python-kerberos does not authenticate the KDC it attempts to communicate with, which allows remote attackers to cause a denial of service (bad response), or have other unspecified impact by performing a man-in-the-middle attack.

Patch / fix

  • pypi pykerberos 1.1.6
  • pykerberos Debian 14, Debian 13, Debian 12 1.1.5-1

debian advisories DEBIAN-CVE-2015-3206

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-2015-3206 updated cvss 4.3

python-kerberos: checkPassword() does not verify KDC authenticity

  • Red Hat Enterprise Linux 5 python-kerberos Red Hat Enterprise Linux 6 python-kerberos Red Hat Enterprise Linux 7 python-kerberos
    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

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

CVSS scores

assigned by version score vector
NVD 3.0 8.1 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P
GitHub 3.0 8.1 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi kerberos
<=1.2.5
>=0.0
no fix listed
pypi pykerberos
<1.1.6
1.1.6

Classification

Weakness

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.