Server-Side Request Forgery (SSRF) Affecting python-kdcproxy package, versions *


Severity

Recommended
low

Based on Debian security rating.

Threat Intelligence

EPSS
0.06% (18th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Server-Side Request Forgery (SSRF) vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-DEBIAN12-PYTHONKDCPROXY-13916494
  • published13 Nov 2025
  • disclosed12 Nov 2025

Introduced: 12 Nov 2025

NewCVE-2025-59088  (opens in a new tab)
CWE-918  (opens in a new tab)

How to fix?

There is no fixed version for Debian:12 python-kdcproxy.

NVD Description

Note: Versions mentioned in the description apply only to the upstream python-kdcproxy package and not the python-kdcproxy package as distributed by Debian. See How to fix? for Debian:12 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1