# CVE-2018-11765: Improper Authentication in Apache Hadoop > Attackers can access protected servlets without authentication in Apache Hadoop when Kerberos is enabled but SPNEGO is disabled. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 30 Sep 2020 - **Updated:** 5 Aug 2024 - **Also known as:** GHSA-rhh9-cm65-3w54 ## What is CVE-2018-11765? CVE-2018-11765 is a high-severity missing authorization vulnerability in Apache Hadoop, published on 30 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description In Apache Hadoop versions 3.0.0-alpha2 to 3.0.0, 2.9.0 to 2.9.2, 2.8.0 to 2.8.5, any users can access some servlets without authentication when Kerberos authentication is enabled and SPNEGO through HTTP is not enabled. Weakness: CWE-287 (Improper Authentication) ## Which versions are affected by CVE-2018-11765? 6 open source packages ship an affected version, including org.apache.hadoop:hadoop-main. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.hadoop:hadoop-main` | Maven | From 2.8.0 | 2.8.6 | | `org.apache.hadoop:hadoop-main` | Maven | From 2.8.0 | 2.8.6 | | `org.apache.hadoop:hadoop-main` | Maven | From 2.9.0 | 2.9.3 | | `org.apache.hadoop:hadoop-main` | Maven | From 2.9.0 | 2.9.3 | | `org.apache.hadoop:hadoop-main` | Maven | From 3.0.0-alpha2 | 3.0.1 | | `org.apache.hadoop:hadoop-main` | Maven | From 3.0.0-alpha2 | 3.0.1 | Products: Apache Hadoop. ## How do I fix CVE-2018-11765? Upgrade org.apache.hadoop:hadoop-main to a fixed version for your release line: 2.8.6, 2.9.3 or 3.0.1. ## Is CVE-2018-11765 being exploited? There is no known exploitation of CVE-2018-11765 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-2018-11765 and fix it if it is affected. What it is: CVE-2018-11765 is a high-severity missing authorization vulnerability in Apache Hadoop, published on 30 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2018-11765 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.hadoop:hadoop-main (Maven): affected from 2.8.0; fixed in 2.8.6 - org.apache.hadoop:hadoop-main (Maven): affected from 2.8.0; fixed in 2.8.6 - org.apache.hadoop:hadoop-main (Maven): affected from 2.9.0; fixed in 2.9.3 - org.apache.hadoop:hadoop-main (Maven): affected from 2.9.0; fixed in 2.9.3 - org.apache.hadoop:hadoop-main (Maven): affected from 3.0.0-alpha2; fixed in 3.0.1 - org.apache.hadoop:hadoop-main (Maven): affected from 3.0.0-alpha2; fixed in 3.0.1 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-2018-11765/ (Markdown: https://insights.sbomify.com/CVE-2018-11765/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2018-11765 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-11765 - OSV: https://osv.dev/vulnerability/CVE-2018-11765 --- From sbomify Insights: https://insights.sbomify.com/CVE-2018-11765/ Summaries are generated and may contain mistakes; the official description above is the record.