ALT-PU-2025-14874-4

Обновление пакета python3-module-kdcproxy в ветке sisyphus

Версия1.1.0-alt1

Задание#400693

Опубликовано2026-03-20

Макс. серьёзностьHIGH

Серьёзность:

Закрытые проблемы (4)

HIGH8.6

Уязвимость прокси-сервера для протокола Kerberos Python-kdcproxy, связанная с недостаточной проверкой поступающих запросов, позволяющая нарушителю получить доступ к конфиденциальным данным

Опубликовано: 2026-03-13Изменено: 2026-04-20

CVSS 3.xВЫСОКАЯ 8.6

CVSS:3.x/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

CVSS 2.0ВЫСОКАЯ 7.8

CVSS:2.0/AV:N/AC:L/Au:N/C:C/I:N/A:N

Ссылки

CVE-2025-59088

MEDIUM5.9

Уязвимость функции Application.__handle_recv() прокси-сервера для протокола Kerberos Python-kdcproxy, позволяющая нарушителю вызвать отказ в обслуживании

Опубликовано: 2026-03-19Изменено: 2026-04-20

CVSS 3.xСРЕДНЯЯ 5.9

CVSS:3.x/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

CVSS 2.0СРЕДНЯЯ 5.4

CVSS:2.0/AV:N/AC:H/Au:N/C:N/I:N/A:C

Ссылки

HIGH8.6

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.

Опубликовано: 2025-11-12Изменено: 2026-04-15

CVSS 3.xВЫСОКАЯ 8.6

CVSS:3.x/CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Ссылки

MEDIUM5.9

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.

Опубликовано: 2025-11-12Изменено: 2026-04-20

CVSS 3.xСРЕДНЯЯ 5.9

CVSS:3.x/CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Ссылки