CVE-2025-59088: Python-kdcproxy: unauthenticated ssrf via realm‑controlled dns srv
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.
Security readout for executives and security teams
Plain-English summary
Kdcproxy can be tricked into making network connections chosen through attacker-controlled DNS SRV records. The business risk is internal network exposure from a service that may sit near identity infrastructure. Deployments with use_dns explicitly set to false are stated as not affected.
Executive priority
Prioritize remediation for identity-facing or internet-reachable kdcproxy deployments, especially on affected Red Hat platforms. The issue is high severity because it can turn a trusted service into an internal network probing path without authentication.
Technical view
When a requested realm lacks configured server addresses, kdcproxy may query SRV records under that realm. An unauthenticated requester controlling that DNS zone can influence target hostnames and ports, creating CWE-918 SSRF. The supplied CVSS is 8.6, with high confidentiality impact and no stated integrity or availability impact.
Likely exposure
Affected exposure is Red Hat python-kdcproxy or IdM client/DL1 packages on listed RHEL 7 ELS, 8 streams, 9 streams, and 10 variants where kdcproxy is deployed and use_dns is not explicitly false.
Exploitation context
The bundle does not show CISA KEV listing or active exploitation. It describes unauthenticated network access with low attack complexity and no user interaction. Practical impact is probing internal topology, firewall rules, port reachability, and possible data exfiltration through server-side requests.
Researcher notes
The strongest evidence is the CVE description, affected Red Hat package list, CVSS vector, and vendor advisories. Evidence in the bundle does not confirm exploitation in the wild. Treat use_dns=false as a clear non-affected condition, but validate actual runtime configuration.
Mitigation direction
Set kdcproxy use_dns explicitly to false where DNS discovery is not required.
Define trusted server addresses for realms instead of relying on DNS SRV fallback.
Review the listed Red Hat RHSA advisories for applicable package updates.
Restrict network egress from kdcproxy to expected Kerberos infrastructure.
Monitor vendor guidance before assuming upstream or downstream fix availability.
Validation and detection
Inventory systems running kdcproxy, python-kdcproxy, or affected Red Hat IdM module streams.
Check kdcproxy configuration for use_dns and missing realm server address definitions.
Map affected RHEL versions against the package and stream list in the CVE bundle.
Verify whether exposed kdcproxy endpoints are reachable by unauthenticated users.
Review egress logs for unexpected connections from kdcproxy hosts.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-918 · source CWE mapping
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.