python-kdcproxy - Debian Package Tracker

general

source: python-kdcproxy (main)
version: 1.0.0-2.1
maintainer: Debian FreeIPA Team (archive) (DMD)
uploaders: Timo Aaltonen [DMD]
arch: all
std-ver: 4.6.0
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 1.0.0-1
oldstable: 1.0.0-1
stable: 1.0.0-2
testing: 1.0.0-2
unstable: 1.0.0-2.1

versioned links

1.0.0-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.0.0-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.0.0-2.1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

python3-kdcproxy

action needed

A new upstream version is available: 1.1.0 high

A new upstream version 1.1.0 is available, you should consider packaging it.

Created: 2026-10-06 Last update: 2026-10-06 15:30

The VCS repository is not up to date, push the missing commits. high

vcswatch reports that the current version of the package is not in its VCS.
Either you need to push your commits and/or your tags, or the information about the package's VCS are out of date. A common cause of the latter issue when using the Git VCS is not specifying the correct branch when the packaging is not in the default one (remote HEAD branch), which is usually "master" but can be modified in salsa.debian.org in the project's general settings with the "Default Branch" field). Alternatively the Vcs-Git field in debian/control can contain a "-b <branch-name>" suffix to indicate what branch is used for the Debian packaging.

Created: 2026-10-05 Last update: 2026-10-05 22:33

2 security issues in sid high

There are 2 open security issues in sid.

2 important issues:

CVE-2025-59088: If kdcproxy receives a request for a realm which does not have server addresses defined in its configuration, by default, it will query SRV records in the DNS zone matching the requested realm name. This creates a server-side request forgery vulnerability, since an attacker could send a request for a realm matching a DNS zone where they created SRV records pointing to arbitrary ports and hostnames (which may resolve to loopback or internal IP addresses). This vulnerability can be exploited to probe internal network topology and firewall rules, perform port scanning, and exfiltrate data. Deployments where the "use_dns" setting is explicitly set to false are not affected.
CVE-2025-59089: If an attacker causes kdcproxy to connect to an attacker-controlled KDC server (e.g. through server-side request forgery), they can exploit the fact that kdcproxy does not enforce bounds on TCP response length to conduct a denial-of-service attack. While receiving the KDC's response, kdcproxy copies the entire buffered stream into a new buffer on each recv() call, even when the transfer is incomplete, causing excessive memory allocation and CPU usage. Additionally, kdcproxy accepts incoming response chunks as long as the received data length is not exactly equal to the length indicated in the response header, even when individual chunks or the total buffer exceed the maximum length of a Kerberos message. This allows an attacker to send unbounded data until the connection timeout is reached (approximately 12 seconds), exhausting server memory or CPU resources. Multiple concurrent requests can cause accept queue overflow, denying service to legitimate clients.

Created: 2025-11-13 Last update: 2026-10-05 22:00

2 security issues in forky high

There are 2 open security issues in forky.

2 important issues:

CVE-2025-59088: If kdcproxy receives a request for a realm which does not have server addresses defined in its configuration, by default, it will query SRV records in the DNS zone matching the requested realm name. This creates a server-side request forgery vulnerability, since an attacker could send a request for a realm matching a DNS zone where they created SRV records pointing to arbitrary ports and hostnames (which may resolve to loopback or internal IP addresses). This vulnerability can be exploited to probe internal network topology and firewall rules, perform port scanning, and exfiltrate data. Deployments where the "use_dns" setting is explicitly set to false are not affected.
CVE-2025-59089: If an attacker causes kdcproxy to connect to an attacker-controlled KDC server (e.g. through server-side request forgery), they can exploit the fact that kdcproxy does not enforce bounds on TCP response length to conduct a denial-of-service attack. While receiving the KDC's response, kdcproxy copies the entire buffered stream into a new buffer on each recv() call, even when the transfer is incomplete, causing excessive memory allocation and CPU usage. Additionally, kdcproxy accepts incoming response chunks as long as the received data length is not exactly equal to the length indicated in the response header, even when individual chunks or the total buffer exceed the maximum length of a Kerberos message. This allows an attacker to send unbounded data until the connection timeout is reached (approximately 12 seconds), exhausting server memory or CPU resources. Multiple concurrent requests can cause accept queue overflow, denying service to legitimate clients.

Created: 2025-11-13 Last update: 2026-10-05 22:00

2 low-priority security issues in trixie low

There are 2 open security issues in trixie.

2 issues left for the package maintainer to handle:

CVE-2025-59088: (needs triaging) If kdcproxy receives a request for a realm which does not have server addresses defined in its configuration, by default, it will query SRV records in the DNS zone matching the requested realm name. This creates a server-side request forgery vulnerability, since an attacker could send a request for a realm matching a DNS zone where they created SRV records pointing to arbitrary ports and hostnames (which may resolve to loopback or internal IP addresses). This vulnerability can be exploited to probe internal network topology and firewall rules, perform port scanning, and exfiltrate data. Deployments where the "use_dns" setting is explicitly set to false are not affected.
CVE-2025-59089: (needs triaging) If an attacker causes kdcproxy to connect to an attacker-controlled KDC server (e.g. through server-side request forgery), they can exploit the fact that kdcproxy does not enforce bounds on TCP response length to conduct a denial-of-service attack. While receiving the KDC's response, kdcproxy copies the entire buffered stream into a new buffer on each recv() call, even when the transfer is incomplete, causing excessive memory allocation and CPU usage. Additionally, kdcproxy accepts incoming response chunks as long as the received data length is not exactly equal to the length indicated in the response header, even when individual chunks or the total buffer exceed the maximum length of a Kerberos message. This allows an attacker to send unbounded data until the connection timeout is reached (approximately 12 seconds), exhausting server memory or CPU resources. Multiple concurrent requests can cause accept queue overflow, denying service to legitimate clients.

You can find information about how to handle these issues in the security team's documentation.

Created: 2025-11-13 Last update: 2026-10-05 22:00

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.4 instead of 4.6.0).

Created: 2021-08-18 Last update: 2026-10-06 01:49

testing migrations

excuses:
- Migration status for python-kdcproxy (1.0.0-2 to 1.0.0-2.1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- ∙ ∙ Too young, only 0 of 5 days old
- Additional info (not blocking):
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-kdcproxy.html
- ∙ ∙ Reproduced on amd64 - info
- ∙ ∙ Reproduced on arm64 - info
- ∙ ∙ Reproduced on armhf - info
- ∙ ∙ Reproduced on i386 - info
- Not considered

news

[rss feed]

[2026-10-05] Accepted python-kdcproxy 1.0.0-2.1 (source) into unstable (Alexandre Detiste)
[2024-02-20] python-kdcproxy 1.0.0-2 MIGRATED to testing (Debian testing watch)
[2024-02-15] Accepted python-kdcproxy 1.0.0-2 (source) into unstable (Timo Aaltonen)
[2020-12-22] python-kdcproxy 1.0.0-1 MIGRATED to testing (Debian testing watch)
[2020-12-17] Accepted python-kdcproxy 1.0.0-1 (source) into unstable (Timo Aaltonen)
[2019-09-17] python-kdcproxy 0.4.2-1 MIGRATED to testing (Debian testing watch)
[2019-09-11] Accepted python-kdcproxy 0.4.2-1 (source) into unstable (Timo Aaltonen)
[2018-10-22] python-kdcproxy 0.4-1 MIGRATED to testing (Debian testing watch)
[2018-10-17] Accepted python-kdcproxy 0.4-1 (source) into unstable (Timo Aaltonen)
[2018-08-09] python-kdcproxy 0.3.3-1 MIGRATED to testing (Debian testing watch)
[2018-08-04] Accepted python-kdcproxy 0.3.3-1 (source) into unstable (Timo Aaltonen)
[2017-06-20] python-kdcproxy 0.3.2-5 MIGRATED to testing (Debian testing watch)
[2017-02-05] Accepted python-kdcproxy 0.3.2-5 (source) into unstable (Timo Aaltonen)
[2016-11-02] python-kdcproxy 0.3.2-4 MIGRATED to testing (Debian testing watch)
[2016-10-27] Accepted python-kdcproxy 0.3.2-4 (source) into unstable (Timo Aaltonen)
[2016-08-29] python-kdcproxy REMOVED from testing (Debian testing watch)
[2016-03-29] python-kdcproxy 0.3.2-3 MIGRATED to testing (Debian testing watch)
[2016-03-23] Accepted python-kdcproxy 0.3.2-3 (source all) into unstable, unstable (Timo Aaltonen)
[2016-03-17] Accepted python-kdcproxy 0.3.2-2 (source) into unstable (Timo Aaltonen)
[2015-11-01] python-kdcproxy 0.3.2-1 MIGRATED to testing (Britney)
[2015-10-21] Accepted python-kdcproxy 0.3.2-1 (source all) into unstable, unstable (Timo Aaltonen)

bugs [bug history graph]

all: 1
RC: 0
I&N: 1
M&W: 0
F&P: 0
patch: 0

links

homepage
lintian
buildd: logs, reproducibility
popcon
browse source code
other distros
security tracker

ubuntu

[Information about Ubuntu for Debian Developers]

version: 1.0.0-2build1