Client BlockTokens not checked in Apache Hadoop
DataNodes in Apache Hadoop 2.0.0 alpha does not check the BlockTokens of clients when Kerberos is enabled and the DataNode has checked out the same BlockPool twice from a NodeName, which might allow remote clients to read arbitrary blocks, write to blocks to which they only have read access, and have other unspecified impacts.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Java / Kotlin (Maven) | org.apache.hadoop:hadoop-client | >= 2.0.0-alpha, < 2.0.1-alpha | 2.0.1-alpha |
References
- Weakness (CWE)
-- Platform
- Java / Kotlin (Maven)
- Package
org.apache.hadoop:hadoop-client- Disclosed
- 17.05.2022
- Updated
- 11.10.2026 11:20
Sources and licenses
OSV / GitHub Advisory Database - GHSA-qmh2-h7r6-gm6q - CC BY 4.0
Vulnerability history: org.apache.hadoop:hadoop-client
All published vulnerabilities of this package (Java / Kotlin (Maven)), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 5
- First → latest
- 05.2022 05.2022
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- Critical 1
- High 2
- Medium 2
Disclosures per year
- 2022: 5
- 2023: 0
- 2024: 0
- 2025: 0
- 2026: 0
-
Client BlockTokens not checked in Apache Hadoop this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.