# CVE-2020-9492: Improper Privilege Management in Apache Hadoop > The WebHDFS client may leak SPNEGO authorization headers to remote URLs, potentially exposing sensitive authentication data to attackers. - **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/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:** Yes - **Published:** 26 Jan 2021 - **Updated:** 4 Aug 2024 - **Also known as:** BIT-solr-2020-9492, GHSA-f8vc-wfc8-hxqh, OESA-2021-1201 ## What is CVE-2020-9492? CVE-2020-9492 is a high-severity vulnerability in Apache Hadoop, published on 26 Jan 2021. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description In Apache Hadoop 3.2.0 to 3.2.1, 3.0.0-alpha1 to 3.1.3, and 2.0.0-alpha to 2.10.0, WebHDFS client might send SPNEGO authorization header to remote URL without proper verification. Weakness: CWE-863 (Incorrect Authorization) ## Which versions are affected by CVE-2020-9492? 7 open source packages ship an affected version, including org.apache.hadoop:hadoop-common and solr. It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.hadoop:hadoop-common` | Maven | From 2.0.0 | 2.10.1 | | `org.apache.hadoop:hadoop-common` | Maven | From 2.0.0 | 2.10.1 | | `org.apache.hadoop:hadoop-common` | Maven | From 3.0.0 | 3.1.4 | | `org.apache.hadoop:hadoop-common` | Maven | From 3.0.0 | 3.1.4 | | `org.apache.hadoop:hadoop-common` | Maven | From 3.2.0 | 3.2.2 | | `org.apache.hadoop:hadoop-common` | Maven | From 3.2.0 | 3.2.2 | | `solr` | Bitnami | From 8.6.0 | 8.6.1, 8.6.3 | Products: Apache Hadoop, Apache Solr, Oracle Financial Services Crime and Compliance Management Studio. ## How do I fix CVE-2020-9492? Upgrade org.apache.hadoop:hadoop-common to a fixed version for your release line: 2.10.1, 3.1.4 or 3.2.2. ## Is CVE-2020-9492 being exploited? There is no known exploitation of CVE-2020-9492 in the wild and no public exploit code. ## Other vulnerabilities in Apache Hadoop - [CVE-2022-25168](https://insights.sbomify.com/CVE-2022-25168/): Command injection in org.apache.hadoop.fs.FileUtil.unTarUsingTar (critical 9.8) - [CVE-2021-37404](https://insights.sbomify.com/CVE-2021-37404/): Heap buffer overflow in libhdfs native library (critical 9.8) - [CVE-2022-26612](https://insights.sbomify.com/CVE-2022-26612/): Arbitrary file write in FileUtil#unpackEntries on Windows (critical 9.8) - [CVE-2019-17195](https://insights.sbomify.com/CVE-2019-17195/): Improper Check for Unusual or Exceptional Conditions in Connect2id Nimbus JOSE+JWT (critical 9.8) - [CVE-2017-15718](https://insights.sbomify.com/CVE-2017-15718/): Exposure of Sensitive Information in Hadoop (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-9492 and fix it if it is affected. What it is: CVE-2020-9492 is a high-severity vulnerability in Apache Hadoop, published on 26 Jan 2021. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2020-9492 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.hadoop:hadoop-common (Maven): affected from 2.0.0; fixed in 2.10.1 - org.apache.hadoop:hadoop-common (Maven): affected from 2.0.0; fixed in 2.10.1 - org.apache.hadoop:hadoop-common (Maven): affected from 3.0.0; fixed in 3.1.4 - org.apache.hadoop:hadoop-common (Maven): affected from 3.0.0; fixed in 3.1.4 - org.apache.hadoop:hadoop-common (Maven): affected from 3.2.0; fixed in 3.2.2 - org.apache.hadoop:hadoop-common (Maven): affected from 3.2.0; fixed in 3.2.2 - solr (Bitnami): affected from 8.6.0; fixed in 8.6.1, 8.6.3 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-2020-9492/ (Markdown: https://insights.sbomify.com/CVE-2020-9492/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-9492 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-9492 - OSV: https://osv.dev/vulnerability/CVE-2020-9492 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-9492/ Summaries are generated and may contain mistakes; the official description above is the record.