CVE-2021-28131

{"id": "CVE-2021-28131", "metrics": {"cvssMetricV2": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"version": "2.0", "baseScore": 6.0, "accessVector": "NETWORK", "vectorString": "AV:N/AC:M/Au:S/C:P/I:P/A:P", "authentication": "SINGLE", "integrityImpact": "PARTIAL", "accessComplexity": "MEDIUM", "availabilityImpact": "PARTIAL", "confidentialityImpact": "PARTIAL"}, "acInsufInfo": false, "impactScore": 6.4, "baseSeverity": "MEDIUM", "obtainAllPrivilege": false, "exploitabilityScore": 6.8, "obtainUserPrivilege": false, "obtainOtherPrivilege": false, "userInteractionRequired": false}], "cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.5, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "HIGH", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 1.6}]}, "published": "2021-07-22T10:15:07.850", "references": [{"url": "http://www.openwall.com/lists/oss-security/2021/07/22/3", "tags": ["Mailing List", "Third Party Advisory"], "source": "security@apache.org"}, {"url": "https://lists.apache.org/thread.html/rb54f54a91b7abaf1ed772f3a9cec290153c24881b25567b06f1b4a8c%40%3Cannounce.apache.org%3E", "source": "security@apache.org"}, {"url": "https://lists.apache.org/thread.html/rb54f54a91b7abaf1ed772f3a9cec290153c24881b25567b06f1b4a8c%40%3Cuser.impala.apache.org%3E", "tags": ["Mailing List", "Vendor Advisory"], "source": "security@apache.org"}, {"url": "https://lists.apache.org/thread.html/rb54f54a91b7abaf1ed772f3a9cec290153c24881b25567b06f1b4a8c%40%3Cuser.impala.apache.org%3E", "tags": ["Mailing List", "Vendor Advisory"], "source": "security@apache.org"}, {"url": "http://www.openwall.com/lists/oss-security/2021/07/22/3", "tags": ["Mailing List", "Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://lists.apache.org/thread.html/rb54f54a91b7abaf1ed772f3a9cec290153c24881b25567b06f1b4a8c%40%3Cannounce.apache.org%3E", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://lists.apache.org/thread.html/rb54f54a91b7abaf1ed772f3a9cec290153c24881b25567b06f1b4a8c%40%3Cuser.impala.apache.org%3E", "tags": ["Mailing List", "Vendor Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://lists.apache.org/thread.html/rb54f54a91b7abaf1ed772f3a9cec290153c24881b25567b06f1b4a8c%40%3Cuser.impala.apache.org%3E", "tags": ["Mailing List", "Vendor Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Secondary", "source": "security@apache.org", "description": [{"lang": "en", "value": "CWE-288"}]}, {"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-532"}]}], "descriptions": [{"lang": "en", "value": "Impala sessions use a 16 byte secret to verify that the session is not being hijacked by another user. However, these secrets appear in the Impala logs, therefore Impala users with access to the logs can use another authenticated user's sessions with specially constructed requests. This means the attacker is able to execute statements for which they don't have the necessary privileges otherwise. Impala deployments with Apache Sentry or Apache Ranger authorization enabled may be vulnerable to privilege escalation if an authenticated attacker is able to hijack a session or query from another authenticated user with privileges not assigned to the attacker. Impala deployments with audit logging enabled may be vulnerable to incorrect audit logging as a user could undertake actions that were logged under the name of a different authenticated user. Constructing an attack requires a high degree of technical sophistication and access to the Impala system as an authenticated user. Mitigation: If an Impala deployment uses Apache Sentry, Apache Ranger or audit logging, then users should upgrade to a version of Impala with the fix for IMPALA-10600. The Impala 4.0 release includes this fix. This hides session secrets from the logs to eliminate the risk of any attack using this mechanism. In lieu of an upgrade, restricting access to logs that expose secrets will reduce the risk of an attack. Restricting access to the Impala deployment to trusted users will also reduce the risk of an attack. Log redaction techniques can be used to redact secrets from the logs."}, {"lang": "es", "value": "Las sesiones de Impala usan un secreto 16 byte para verificar que la sesi\u00f3n no est\u00e1 siendo secuestrada por otro usuario. Sin embargo, estos secretos aparecen los registros de Impala, por lo que unos usuarios de Impala con acceso a los registros pueden usar las sesiones de otro usuario autenticado con peticiones especialmente construidas. Esto significa que el atacante es capaz de ejecutar sentencias para las que no presenta los privilegios necesarios de otra manera. Unas implementaciones de Impala con la autorizaci\u00f3n de Apache Sentry o Apache Ranger habilitada pueden ser vulnerables a una escalada de privilegios si un atacante autenticado es capaz de secuestrar una sesi\u00f3n o consulta de otro usuario autenticado con privilegios no asignados al atacante. Las implementaciones de Impala con el registro de auditor\u00eda habilitado pueden ser vulnerables a un registro de auditor\u00eda incorrecto, ya que un usuario podr\u00eda realizar acciones que se registraron bajo el nombre de un usuario autenticado diferente. Construir un ataque requiere un alto grado de sofisticaci\u00f3n t\u00e9cnica y el acceso al sistema Impala como un usuario autenticado. Mitigaci\u00f3n: Si un despliegue de Impala usa Apache Sentry, Apache Ranger o registro de auditor\u00eda, los usuarios entonces deben actualizar a una versi\u00f3n de Impala con la correcci\u00f3n de IMPALA-10600. La versi\u00f3n Impala 4.0 incluye esta correcci\u00f3n. Esto oculta los secretos de sesi\u00f3n de los registros para eliminar el riesgo de cualquier ataque usando este mecanismo. En lugar de una actualizaci\u00f3n, restringir el acceso a los registros que exponen los secretos reducir\u00e1n el riesgo de un ataque. Restringir el acceso a la implementaci\u00f3n de Impala a usuarios confiables tambi\u00e9n reducir\u00e1 el riesgo de un ataque. Pueden ser usadas t\u00e9cnicas de redacci\u00f3n de registros para eliminar los secretos de los registros"}], "lastModified": "2024-11-21T05:59:08.840", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:apache:impala:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "2FE0AC91-AE64-43ED-9D3B-B21E1E3932E9", "versionEndExcluding": "4.0.0"}], "operator": "OR"}]}], "sourceIdentifier": "security@apache.org"}