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.
Advisories
Source ID Title
EUVD EUVD EUVD-2022-5000 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.
Github GHSA Github GHSA GHSA-qmh2-h7r6-gm6q Client BlockTokens not checked in Apache Hadoop
Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: redhat

Published:

Updated: 2024-08-06T20:05:12.540Z

Reserved: 2012-06-14T00:00:00

Link: CVE-2012-3376

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Deferred

Published: 2012-07-12T19:55:06.343

Modified: 2025-04-11T00:51:21.963

Link: CVE-2012-3376

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.