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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2012-3376US | high7.5 | — | ||
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,… | ||||
02
references
External citations — patches, advisories, analysis.
- http://archives.neohapsis.com/archives/bugtraq/2012-07/0049.htmlWEB
- https://github.com/apache/hadoopPACKAGE
- https://nvd.nist.gov/vuln/detail/CVE-2012-3376ADVISORY
- https://seclists.org/fulldisclosure/2012/Jul/78WEB
- https://www.cloudera.com/documentation/other/security-bulletins/topics/csb_topic_1.htmlWEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan