{"uuid": "4a90b493-941a-4135-8466-2d5199f6ffb4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-23953", "type": "seen", "source": "https://t.me/cvedetector/16592", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-23953 - Apache Hive LlapSignerImpl signature forgery\u00e1veis\", \n  \"Content\": \"CVE ID : CVE-2024-23953 \nPublished : Jan. 28, 2025, 9:15 a.m. | 2\u00a0hours, 4\u00a0minutes ago \nDescription : Use of Arrays.equals() in LlapSignerImpl in\u00a0Apache Hive to compare message signatures\u00a0allows attacker to forge a valid signature for an arbitrary message byte by byte. The attacker should be an authorized user of the product to perform this attack.\u00a0Users are recommended to upgrade to version 4.0.0, which fixes this issue.  \n  \nThe problem occurs when an application doesn\u2019t use a constant-time algorithm for validating a signature.\u00a0The method Arrays.equals()\u00a0returns false\u00a0right away when it sees that one of the input\u2019s 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.\u00a0So 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.  \n  \nMore details in the reference section. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"28 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-28T12:56:14.000000Z"}