Sharon Goldberg

Nome do software vulnerável e versões afetadas: Protocolo RADIUS (versões afetadas não especificadas) FreeRadius (versões afetadas não especificadas) Palo Alto Networks PAN-OS (versões afetadas não especificadas) eduMFA anterior à versão 2.2.0 Descrição: O protocolo RADIUS, conforme a RFC 2865, é suscetível a ataques de falsificação por um invasor local, que pode modificar qualquer resposta válida (Access-Accept, Access-Reject ou Access-Challenge) para qualquer outra resposta, utilizando um ataque de colisão de prefixo escolhido contra a assinatura do autenticador de resposta MD5. Essa vulnerabilidade permite que um invasor realize um ataque man-in-the-middle entre um cliente e um servidor RADIUS para contornar a autenticação e escalar privilégios. O número estimado de dispositivos potencialmente afetados em todo o mundo não foi especificado. Não há informações sobre incidentes reais em que essa vulnerabilidade tenha sido explorada. Recomendações: Para o Protocolo RADIUS: Atualize o protocolo para usar um método de autenticação seguro, como um código de autenticação de mensagem com hash (HMAC) ou uma assinatura digital. Para o FreeRadius: Atualize para uma versão que inclua uma correção para essa vulnerabilidade. Para o Palo Alto Networks PAN-OS: atualize o perfil do servidor RADIUS para usar um protocolo de autenticação seguro, como o TLS, e certifique-se de que o CHAP ou o PAP não sejam usados, a menos que encapsulados por um túnel criptografado. Para o eduMFA: atualize para a versão 2.2.0 ou posterior. Como solução alternativa temporária, considere restringir o acesso ao servidor RADIUS e limitar o uso de protocolos vulneráveis, como o CHAP ou

**Name of the Vulnerable Software and Affected Versions** NTP versions prior to 4.2.8p9 **Description** The issue allows remote attackers to set or unset traps via a crafted control mode packet, which can lead to a denial of service caused by a NULL pointer dereference when the trap service has been enabled. By sending specially crafted packets, a remote attacker could exploit this to cause the application to crash. **Recommendations** For versions prior to 4.2.8p9, update to version 4.2.8p9 or later to resolve the issue. As a temporary workaround, consider disabling the trap service to minimize the risk of exploitation. Restrict access to the control mode functionality to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** NTP versions prior to 4.2.8p9 **Description** The issue allows remote attackers to bypass the origin timestamp protection mechanism via an origin timestamp of zero. This is due to a regression of a previous issue. Multiple vulnerabilities could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition or modify the time being advertised by a device acting as a Network Time Protocol (NTP) server. These vulnerabilities include issues with the Network Time Protocol Trap Service, Broadcast Mode, Insufficient Resource Pool, Configuration Modification, mrulist Query Requests, Multiple Binds to the Same Port, and Rate Limiting. **Recommendations** For NTP versions prior to 4.2.8p9, update to version 4.2.8p9 or later to resolve the issue. As a temporary workaround, consider restricting access to the NTP service to minimize the risk of exploitation. Additionally, workarounds may be available and are documented in the Cisco bug for each affected product.

**Name of the Vulnerable Software and Affected Versions** NTP versions prior to 4.2.8p9 **Description** The issue is related to the initial sync calculations in NTP, which could allow remote attackers to have an unspecified impact via unknown vectors. This is due to a "root distance that did not include the peer dispersion." Multiple vulnerabilities in the NTP daemon package could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition or modify the time being advertised by a device acting as an NTP server. **Recommendations** For NTP versions prior to 4.2.8p9, update to version 4.2.8p9 or later to resolve the issue. As a temporary workaround, consider restricting access to NTP services to minimize the risk of exploitation. Additionally, workarounds may be available and are documented in the Cisco bug for each affected product.

**Name of the Vulnerable Software and Affected Versions** NTP versions prior to 4.2.8p5 **Description** The issue allows remote attackers to bypass security restrictions by exploiting the failure to correctly implement the threshold limitation for the '-g' option. This can be achieved by responding to an unspecified number of requests from trusted sources, potentially allowing an attacker to set NTP to an arbitrary time or alter the time by up to 900 seconds, and leveraging a resulting denial of service. An attacker could exploit this using man-in-the-middle techniques to intercept NTP traffic and make multiple steps larger than the panic threshold. **Recommendations** For NTP versions prior to 4.2.8p5, update to version 4.2.8p5 or later to resolve the issue. As a temporary workaround, consider restricting access to trusted sources to minimize the risk of exploitation. Avoid using the '-g' option until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** NTP versions 4.x before 4.2.8p4 NTP versions 4.3.x before 4.3.77 **Description** The issue allows remote attackers to cause a denial of service via a number of crafted "KOD" messages. **Recommendations** For NTP versions 4.x before 4.2.8p4, update to version 4.2.8p4 or later. For NTP versions 4.3.x before 4.3.77, update to version 4.3.77 or later.

**Name of the Vulnerable Software and Affected Versions** NTP versions 4.x before 4.2.8p4 NTP versions 4.3.x before 4.3.77 **Description** The rate limiting feature in NTP allows remote attackers to have unspecified impact via a large number of crafted requests. This issue exists due to insufficient input validation, which may allow a remote attacker to cause partial disruption of confidentiality, integrity, and availability of protected information by sending a large number of reverse requests. **Recommendations** For NTP versions 4.x before 4.2.8p4, update to version 4.2.8p4 or later. For NTP versions 4.3.x before 4.3.77, update to version 4.3.77 or later.