🛡️ AZL-70181 — python-kdcproxy
Description
CVE-2025-59089 affecting package python-kdcproxy 0.4.2-5
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.
Affected software
AZL-70181 is recorded against 1 package.
- python-kdcproxy
Timeline and source
Published on 12 November 2025 and last revised on 21 April 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
Details
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| python-kdcproxy | — | — |
References
Similar Threats
- Unknown AZL-70171
- Unknown AZL-70174
- Unknown AZL-70184
- Unknown DEBIAN-CVE-2025-59088
- Unknown DEBIAN-CVE-2025-59089
More AZL 7 advisories
Browse all of AZL 7 in the advisory index.
Free Vulnerability Check
Is your site affected by AZL-70181?
BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against AZL-70181 and other known CVE records.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.