# CVE-2019-10084: Missing authorization in Impala > Authenticated attackers can hijack sessions or queries by predicting IDs, bypassing authorization and audit logs in Apache Impala deployments. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 5 Nov 2019 - **Updated:** 4 Aug 2024 - **Also known as:** GHSA-2552-7vjw-33qv ## What is CVE-2019-10084? CVE-2019-10084 is a high-severity missing authorization vulnerability in Apache Software Foundation Impala, published on 5 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description In Apache Impala 2.7.0 to 3.2.0, an authenticated user with access to the IDs of active Impala queries or sessions can interact with those sessions or queries via a specially-constructed request and thereby potentially bypass authorization and audit mechanisms. Session and query IDs are unique and random, but have not been documented or consistently treated as sensitive secrets. Therefore they may be exposed in logs or interfaces. They were also not generated with a cryptographically secure random number generator, so are vulnerable to random number generator attacks that predict future IDs based on past IDs. 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. Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-532 (Insertion of Sensitive Information into Log File), CWE-384 (Session Fixation), CWE-330 (Use of Insufficiently Random Values), CWE-311 (Missing Encryption of Sensitive Data) ## Which versions are affected by CVE-2019-10084? It affects 1 product. Products: Apache Impala. ## How do I fix CVE-2019-10084? No fix has been published for CVE-2019-10084 yet. Limit exposure of the affected software until one is available. ## Is CVE-2019-10084 being exploited? There is no known exploitation of CVE-2019-10084 in the wild and no public exploit code. ## Other vulnerabilities in Apache Software Foundation Impala - [CVE-2026-56207](https://insights.sbomify.com/CVE-2026-56207/): Apache Impala: SAML authentication bypass via forged bearer token (critical 9.8) - [CVE-2018-11792](https://insights.sbomify.com/CVE-2018-11792/): Privilege escalation in Apache Impala (critical 9.8) - [CVE-2017-5640](https://insights.sbomify.com/CVE-2017-5640/): Auth bypass in Apache Impala (critical 9.8) - [CVE-2026-57866](https://insights.sbomify.com/CVE-2026-57866/): Apache Impala: Secrets Exfiltration via SSRF (high 8.8) - [CVE-2026-65181](https://insights.sbomify.com/CVE-2026-65181/): Apache Impala: RCE via External Data Source Class Loading (high 8.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-10084 and fix it if it is affected. What it is: CVE-2019-10084 is a high-severity missing authorization vulnerability in Apache Software Foundation Impala, published on 5 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2019-10084 in the wild and no public exploit code. Affected product: Apache Software Foundation Impala. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2019-10084/ (Markdown: https://insights.sbomify.com/CVE-2019-10084/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-10084 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-10084 - OSV: https://osv.dev/vulnerability/CVE-2019-10084 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-10084/ Summaries are generated and may contain mistakes; the official description above is the record.