fkie_cve-2024-23953
Vulnerability from fkie_nvd
Published
2025-01-28 09:15
Modified
2025-02-18 19:15
Severity ?
Summary
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. 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.
References
security@apache.orghttps://blog.gypsyengineer.com/en/security/preventing-timing-attacks-with-codeql.html
security@apache.orghttps://cqr.company/web-vulnerabilities/timing-attacks/
security@apache.orghttps://github.com/apache/hive
security@apache.orghttps://github.com/apache/hive/commit/b418e3c9f479ba8e7d31e6470306111002ffa809
security@apache.orghttps://issues.apache.org/jira/browse/HIVE-28030
security@apache.orghttps://lists.apache.org/thread/0nloywj49nbtlc6l3c6363qvq7o1ztb7
af854a3a-2127-422b-91ae-364da2661108http://www.openwall.com/lists/oss-security/2025/01/28/3
Impacted products
Vendor Product Version


To clipboard 

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "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."
    },
    {
      "lang": "es",
      "value": "El uso de Arrays.equals() en LlapSignerImpl en Apache Hive para comparar firmas de mensajes permite a un atacante falsificar una firma v\u00e1lida para un mensaje arbitrario byte a byte. El atacante debe ser un usuario autorizado del producto para realizar este ataque. Se recomienda a los usuarios que actualicen a la versi\u00f3n 4.0.0, que soluciona este problema. El problema ocurre cuando una aplicaci\u00f3n no utiliza un algoritmo de tiempo constante para validar una firma. El m\u00e9todo Arrays.equals() devuelve falso de inmediato cuando ve que uno de los bytes de entrada es diferente. Significa que el tiempo de comparaci\u00f3n depende del contenido de las matrices. Esta peque\u00f1a cosa puede permitir a un atacante falsificar una firma v\u00e1lida para un mensaje arbitrario byte a byte. Por lo tanto, podr\u00eda permitir que los usuarios malintencionados env\u00eden divisiones/trabajos con firmas seleccionadas a LLAP sin ejecutarse como un usuario privilegiado, lo que podr\u00eda conducir a un ataque DDoS. M\u00e1s detalles en la secci\u00f3n de referencia."
    }
  ],
  "id": "CVE-2024-23953",
  "lastModified": "2025-02-18T19:15:15.100",
  "metrics": {},
  "published": "2025-01-28T09:15:09.187",
  "references": [
    {
      "source": "security@apache.org",
      "url": "https://blog.gypsyengineer.com/en/security/preventing-timing-attacks-with-codeql.html"
    },
    {
      "source": "security@apache.org",
      "url": "https://cqr.company/web-vulnerabilities/timing-attacks/"
    },
    {
      "source": "security@apache.org",
      "url": "https://github.com/apache/hive"
    },
    {
      "source": "security@apache.org",
      "url": "https://github.com/apache/hive/commit/b418e3c9f479ba8e7d31e6470306111002ffa809"
    },
    {
      "source": "security@apache.org",
      "url": "https://issues.apache.org/jira/browse/HIVE-28030"
    },
    {
      "source": "security@apache.org",
      "url": "https://lists.apache.org/thread/0nloywj49nbtlc6l3c6363qvq7o1ztb7"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "url": "http://www.openwall.com/lists/oss-security/2025/01/28/3"
    }
  ],
  "sourceIdentifier": "security@apache.org",
  "vulnStatus": "Awaiting Analysis",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-208"
        }
      ],
      "source": "security@apache.org",
      "type": "Primary"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.