2 results (0.006 seconds)

CVSS: 7.5EPSS: 0%CPEs: 2EXPL: 0

In all previously released Apache HBase 2.x versions (2.0.0-2.0.4, 2.1.0-2.1.3), authorization was incorrectly applied to users of the HBase REST server. Requests sent to the HBase REST server were executed with the permissions of the REST server itself, not with the permissions of the end-user. This issue is only relevant when HBase is configured with Kerberos authentication, HBase authorization is enabled, and the REST server is configured with SPNEGO authentication. This issue does not extend beyond the HBase REST server. En todas las versiones anteriormente publicadas de Apache HBase 2.x (2.0.0-2.0.4, 2.1.0-2.1.3), se aplicaba una autorización de manera incorrecta a los usuarios del servidor REST "HBase". • http://www.openwall.com/lists/oss-security/2019/03/27/3 http://www.securityfocus.com/bid/107624 https://lists.apache.org/thread.html/519eb0fd45642dcecd9ff74cb3e71c20a4753f7d82e2f07864b5108f%40%3Cdev.drill.apache.org%3E https://lists.apache.org/thread.html/66535e15007cda8f9308eec10e12ffe349e0b8b55e56ec6ee02b71d2%40%3Cdev.hbase.apache.org%3E https://lists.apache.org/thread.html/b0656d359c7d40ec9f39c8cc61bca66802ef9a2a12ee199f5b0c1442%40%3Cdev.drill.apache.org%3E •

CVSS: 8.1EPSS: 0%CPEs: 2EXPL: 0

CVE-2018-8025 describes an issue in Apache HBase that affects the optional "Thrift 1" API server when running over HTTP. There is a race-condition which could lead to authenticated sessions being incorrectly applied to users, e.g. one authenticated user would be considered a different user or an unauthenticated user would be treated as an authenticated user. https://issues.apache.org/jira/browse/HBASE-20664 implements a fix for this issue. It has been fixed in versions: 1.2.6.1, 1.3.2.1, 1.4.5, 2.0.1. CVE-2018-8025 describe un problema en Apache HBase que afecta al servidor opcional de la API "Thrift 1" cuando se ejecuta por HTTP. Hay una condición de carrera que puede conducir a que se aplican sesiones autenticadas incorrectamente a los usuarios, por ejemplo, un usuario autenticado se consideraría un usuario diferente o un usuario no autenticado se trataría como usuario autenticado. https://issues.apache.org/jira/browse/HBASE-20664 implementa una solución para este problema. • http://www.securityfocus.com/bid/104554 https://lists.apache.org/thread.html/a919e38f587c714c386a01d40fc8f45bd4219a65aaf2dc0bb4eccc96%40%3Cdev.hbase.apache.org%3E • CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') •