{"answers":{"affected":"2 open source packages ship an affected version, including org.apache.hive:hive-llap-common. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-23953 in the wild and no public exploit code.","fix":"Upgrade org.apache.hive:hive-llap-common to 4.0.0 or later.","what":"CVE-2024-23953 is a medium-severity vulnerability in Apache Hive, published on 28 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-23953 and fix it if it is affected.\n\nWhat it is: CVE-2024-23953 is a medium-severity vulnerability in Apache Hive, published on 28 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-23953 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.hive:hive-llap-common (Maven): affected all versions; fixed in 4.0.0\n- org.apache.hive:hive-llap-common (Maven): affected all versions; fixed in 4.0.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-23953/ (Markdown: https://insights.sbomify.com/CVE-2024-23953/index.md)","id":"CVE-2024-23953","markdown":"https://insights.sbomify.com/CVE-2024-23953/index.md","name":"CVE-2024-23953","record":{"aliases":["CLEANSTART-2026-NO09997","CLEANSTART-2026-RT97024","CLEANSTART-2026-SY76687","GHSA-p953-3j66-hg45","MINI-3fmj-m98c-m2ff"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache Hive","requires_auth":"low_privilege","summary":"An authorized user can bypass signature validation in Apache Hive LLAP to forge signatures, potentially escalating privileges or causing denial of service.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"hive","vendor":"apache"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-208","name":"Observable Timing Discrepancy"}],"description":"Use of Arrays.equals() in LlapSignerImpl in Apache Hive to compare message signatures allows 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. Users are recommended to upgrade to version 4.0.0, which fixes this issue.\n\nThe 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.\n\nMore details in the reference section.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Apache Hive: Timing Attack Against Signature in LLAP util","id":"CVE-2024-23953","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"security_feature_bypass","year":"2024"},"n_packages":2,"n_references":6,"next":{"headline":"Memory corruption in MaxiCharger AC Elite Business C50","id":"CVE-2024-23957"},"packages":[{"ecosystem":"Maven","fixed":["4.0.0"],"introduced":["0"],"last_affected":[],"package":"org.apache.hive:hive-llap-common","purl":null,"source":"GHSA-p953-3j66-hg45"},{"ecosystem":"Maven","fixed":["4.0.0"],"introduced":["0"],"last_affected":[],"package":"org.apache.hive:hive-llap-common","purl":"pkg:maven/org.apache.hive/hive-llap-common","source":"GHSA-p953-3j66-hg45"}],"prev":{"headline":"Apache Superset: Allows for uncontrolled resource consumption via a ZIP bomb (version range fix for CVE-2023-46104)","id":"CVE-2024-23952"},"products":["Apache Hive"],"published":"2025-01-28","related":[{"cvss_score":9.8,"headline":"Apache Hive: SQL Injection vulnerability in HiveMetaStore partition-name direct-SQL paths","id":"CVE-2026-49845","kev_date_added":null,"published":"2026-08-25"},{"cvss_score":9.8,"headline":"Deserialization of Untrusted Data in Jodd","id":"CVE-2018-21234","kev_date_added":null,"published":"2020-05-21"},{"cvss_score":9.1,"headline":"Apache Hive: SSRF vulnerability in Hive Avro Serde due to Insufficient input validation on avro.schema.url","id":"CVE-2026-55976","kev_date_added":null,"published":"2026-08-25"},{"cvss_score":9.1,"headline":"SQL Injection in hive-jdbc","id":"CVE-2018-1282","kev_date_added":null,"published":"2018-04-05"},{"cvss_score":8.3,"headline":"Apache Hive: Deserialization of untrusted data when fetching partitions from the Metastore","id":"CVE-2022-41137","kev_date_added":null,"published":"2024-12-05"},{"cvss_score":8.3,"headline":"High severity vulnerability that affects org.apache.hive:hive, org.apache.hive:hive-exec, and org.apache.hive:hive-service","id":"CVE-2015-7521","kev_date_added":null,"published":"2016-01-29"},{"cvss_score":8.1,"headline":"Improper Authentication in hive:hive-exec","id":"CVE-2018-11777","kev_date_added":null,"published":"2018-11-08"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-14","vendors":["Apache Software Foundation"]},"summary":"An authorized user can bypass signature validation in Apache Hive LLAP to forge signatures, potentially escalating privileges or causing denial of service.","url":"https://insights.sbomify.com/CVE-2024-23953/"}