CVE-2012-3376
First published: Thu Jul 12 2012(Updated: )
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.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Apache Hadoop | =2.0.0-alpha |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2012-3376?
CVE-2012-3376 is considered a high severity vulnerability due to its potential to allow unauthorized access to sensitive data.
How do I fix CVE-2012-3376?
To fix CVE-2012-3376, update to a secure version of Apache Hadoop that addresses this vulnerability.
Who is affected by CVE-2012-3376?
CVE-2012-3376 affects users of Apache Hadoop version 2.0.0-alpha when Kerberos authentication is enabled.
What are the consequences of CVE-2012-3376?
The consequences of CVE-2012-3376 include unauthorized access to arbitrary blocks, which can lead to data breaches.
Is CVE-2012-3376 a known issue with Apache Hadoop?
Yes, CVE-2012-3376 is a known issue within Apache Hadoop 2.0.0-alpha versions.
- collector/nvd-index
- agent/author
- agent/severity
- agent/references
- agent/weakness
- agent/tags
- agent/description
- agent/type
- agent/event
- agent/softwarecombine
- agent/first-publish-date
- agent/last-modified-date
- vendor/apache
- canonical/apache hadoop
- version/apache hadoop/2.0.0-alpha