CVE-2024-13448
Mar, 28/01/2025 – 07:15
CVE-2024-13448
CVE-2024-13448
Mar, 28/01/2025 – 07:15
CVE-2024-13448
CVE-2024-13509
Mar, 28/01/2025 – 07:15
CVE-2024-13509
CVE-2025-0321
Mar, 28/01/2025 – 08:15
CVE-2025-0321
CVE-2024-13521
Mar, 28/01/2025 – 08:15
CVE-2024-13521
CVE-2024-13527
Mar, 28/01/2025 – 09:15
CVE-2024-13527
CVE-2025-0736
Mar, 28/01/2025 – 09:15
CVE-2025-0736
CVE-2025-0290
Mar, 28/01/2025 – 09:15
CVE-2025-0290
CVE-2024-23953
Mar, 28/01/2025 – 09:15
CVE-2024-23953
The problem occurs when an application doesn’t use a constant-time algorithm for validating a signature. The method Arrays.equals() returns false right away when it sees that one of the input’s bytes are different. It means that the comparison time depends on the contents of the arrays. This little thing may allow an attacker to forge a valid signature for an arbitrary message byte by byte. So it might allow malicious users to submit splits/work with selected signatures to LLAP without running as a privileged user, potentially leading to DDoS attack.
More details in the reference section.
CVE-2024-0140
Mar, 28/01/2025 – 04:15
CVE-2024-0140
CVE-2024-0150
Mar, 28/01/2025 – 04:15
CVE-2024-0150