CVE-2021-39235: Access mode of block tokens are not enforced
First published: Fri Nov 19 2021(Updated: )
In Apache Ozone before 1.2.0, Ozone Datanode doesn't check the access mode parameter of the block token. Authenticated users with valid READ block token can do any write operation on the same block.
Credit: security@apache.org security@apache.org security@apache.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Apache Ozone | <1.2.0 | |
| maven/org.apache.ozone:ozone-main | <1.2.0 | 1.2.0 |
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 CVE-2021-39235?
CVE-2021-39235 is a vulnerability in Apache Ozone where the access mode of block tokens is not enforced.
How does CVE-2021-39235 impact Apache Ozone?
CVE-2021-39235 allows authenticated users with a valid READ block token to perform any write operation on the same block.
What is the severity of CVE-2021-39235?
CVE-2021-39235 has a severity rating of 6.5 (medium).
Which versions of Apache Ozone are affected by CVE-2021-39235?
CVE-2021-39235 affects Apache Ozone versions up to and excluding 1.2.0.
How can I mitigate CVE-2021-39235 in Apache Ozone?
To mitigate CVE-2021-39235, it is recommended to update Apache Ozone to version 1.2.0 or later.
- collector/nvd-index
- collector/github-advisory-latest
- alias/GHSA-c6j7-4fr9-c76p
- alias/CVE-2021-39235
- collector/nvd-cve
- collector/github-advisory
- collector/nvd-api
- agent/type
- agent/references
- agent/softwarecombine
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- agent/title
- agent/last-modified-date
- agent/author
- agent/weakness
- agent/severity
- agent/tags
- agent/description
- agent/event
- agent/trending
- vendor/apache
- canonical/apache ozone
- package-manager/maven