CVE-2018-11768 user/group information can be corrupted across storing in fsimage and reading back from fsimage
High 7.5
Published
Updated
Check this codebase for CVE-2018-11768 and fix it if it is affected.
What it is: CVE-2018-11768 is a high-severity vulnerability in Apache Hadoop, published on 4 Oct 2019.
Exploitation: There is no known exploitation of CVE-2018-11768 in the wild and no public exploit code.
Affected packages and fixed versions:
- org.apache.hadoop:hadoop-main (Maven): affected from 2.2.0; fixed in 2.8.5
- org.apache.hadoop:hadoop-main (Maven): affected from 2.2.0; fixed in 2.8.5
- org.apache.hadoop:hadoop-main (Maven): affected from 2.9.0; fixed in 2.9.2
- org.apache.hadoop:hadoop-main (Maven): affected from 2.9.0; fixed in 2.9.2
- org.apache.hadoop:hadoop-main (Maven): affected from 3.0.0; fixed in 3.1.1
- org.apache.hadoop:hadoop-main (Maven): affected from 3.0.0; fixed in 3.1.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-11768/ (Markdown: https://insights.sbomify.com/CVE-2018-11768/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2018-11768?
CVE-2018-11768 is a high-severity vulnerability in Apache Hadoop, published on 4 Oct 2019.
Official description
In Apache Hadoop 3.1.0 to 3.1.1, 3.0.0-alpha1 to 3.0.3, 2.9.0 to 2.9.1, and 2.0.0-alpha to 2.8.4, the user/group information can be corrupted across storing in fsimage and reading back from fsimage.
Weakness: CWE-119
Which versions are affected by CVE-2018-11768?
6 open source packages ship an affected version, including org.apache.hadoop:hadoop-main. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
org.apache.hadoop:hadoop-main Maven | From 2.2.0 | 2.8.5 |
org.apache.hadoop:hadoop-main Maven | From 2.2.0 | 2.8.5 |
org.apache.hadoop:hadoop-main Maven | From 2.9.0 | 2.9.2 |
org.apache.hadoop:hadoop-main Maven | From 2.9.0 | 2.9.2 |
org.apache.hadoop:hadoop-main Maven | From 3.0.0 | 3.1.1 |
org.apache.hadoop:hadoop-main Maven | From 3.0.0 | 3.1.1 |
Products include Apache Hadoop.
How do I fix CVE-2018-11768?
Upgrade org.apache.hadoop:hadoop-main to a fixed version for your release line: 2.8.5, 2.9.2 or 3.1.1.
Is CVE-2018-11768 being exploited?
There is no known exploitation of CVE-2018-11768 in the wild and no public exploit code.
Other vulnerabilities in Apache Hadoop
- CVE-2022-25168 Command injection in org.apache.hadoop.fs.FileUtil.unTarUsingTar
- CVE-2021-37404 Heap buffer overflow in libhdfs native library
- CVE-2022-26612 Arbitrary file write in FileUtil#unpackEntries on Windows
- CVE-2019-17195 Improper Check for Unusual or Exceptional Conditions in Connect2id Nimbus JOSE+JWT
- CVE-2017-15718 Exposure of Sensitive Information in Hadoop
Sources
Also known as GHSA-hx83-rpqf-m267.